Solution: 120850
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When 2 or more schedules of the same invoice is paid/processed in the same transaction, fatal error occurs.
SOLUTION DESCRIPTION:
Earlier, When 2 or more schedules of the same invoice is paid/processed in the same transaction, fatal error occurs because
of duplicate record.
Now, all schedule lines of the same invoice can be paid in a single transaction.
SOLUTION 125526 ALSO
---------------------------------------------------------------------
VERSION(S):
B50_b, B50_c

Solution: 121466
SITUATION IDENTIFIED IN:
"Material to Issue for Production Orders" (ticst0101s000)
SITUATION DESCRIPTION:
When the material is returned from shop floor, if the outbound order line is open/advised/released and even when the order
quantity in outbound orderline can be reduced, a new inbound order line is created.
SOLUTION DESCRIPTION:
When the material is returned from shop floor, if the outbound order line is open/advised/released, and if the order quantity
in outbound orderline can be reduced, new inbound orderline is not created. Instead, outbound orderline quantity is reduced.
DOCUMENTATION:
For more detailed functional info please ask for document #22199.
SOLUTION 125117 AFTER THIS SOLUTION.
If your Current VRC is B50L_c_bgl0, download solution 125264 also.
VERSION(S):
B50_b, B50_c

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

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

Solution: 122598
SITUATION IDENTIFIED IN:
"Maintain Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Discount amount becomes zero after saving the record.
SOLUTION DESCRIPTION:
Discount amount is not becoming zero after saving the record and it takes the manually given discount as well.

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

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

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

Solution: 123382
SITUATION IDENTIFIED IN:
"Import Journal Voucher Batches by ID Number" (tfgld2215m000)
SITUATION DESCRIPTION:
The journal import status report is not sorted by document number and line number
SOLUTION DESCRIPTION:
Now the report sorted by the document number and line number considering those fields as numeric fields.

Solution: 123397
SITUATION IDENTIFIED IN:
"Write off payment differences" (tfacp2230m000)
SITUATION DESCRIPTION:
When going to write off payment differences the system generates an unbalance batch.
SOLUTION DESCRIPTION:
A balanced batch is created when payment differences are written off.

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

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

Solution: 123610
SITUATION IDENTIFIED IN:
"Print Supplier Aging Summary" (tfacp3425m000)
SITUATION DESCRIPTION:
1. Change functionality : add "Selection by" field.
2. When running session "Print Supplier Aging Summary - tfacp3425" and only changing the "As Of" field, this field is not
taken in account.
SOLUTION DESCRIPTION:
1. Functionality changed by adding the "Selection by" field.
2. When running session "Print Supplier Aging Summary - tfacp3425" and only changing the "As Of" field this field is now
taken in account.

Solution: 123643
SITUATION IDENTIFIED IN:
"Process Payment Batch" (tfcmgl270m00l)
SITUATION DESCRIPTION:
Negative Trade note was created when you run the Process Payment Batch session. This happens in the case of one negative
purchase invoice and another positive purchase invoice entered in the payment advice.
SOLUTION DESCRIPTION:
Now it is creating trade note correctly.

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

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

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

Solution: 123825
SITUATION IDENTIFIED IN:
"Vat Report" (tfgldl406m00l)
SITUATION DESCRIPTION:
Tax Code and Rate were displayed when you enter the specific tax code.
SOLUTION DESCRIPTION:
Now the report is generated correctly.

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

Solution: 123854
SITUATION IDENTIFIED IN:
"Generate invoice by selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
It can happen that a batch is generated with session tfacp2290m000 (generate selfbilled invoices) and that that batch can not
be finalized. The user will get the message "batch header record missing". If you look with table maintenance (ttaad4500) to
the related tables then indeed a record is missing in tfgld101, whereas all the other tables are populated correctly.
SOLUTION
DESCRIPTION:
A batch header record has to be written once in the selfbilling batch as the transaction
type is the same for all documents. Because of this a certain DLL (dynamic link
library) is called to create this record and for performance reasons the creation of a batch header record is only done once.
However when (because of the locking of a table) the process gets into its retry.point() this record will because of this
mechanism never be created again. Now it is also checked whether a db.retry.hit has occurrred for determining whether this
batch header record still needs to be created or not.

Solution: 123858
SITUATION IDENTIFIED IN:
"Sales Invoice Transactions" (tfacr1111s000)
SITUATION DESCRIPTION:
When entering a Sales Credit Note with a Transactiontype that has parameter "Negative amounts for Credit Notes
"disabled" and a Vatcode of type SHIFTED is used the remaining amount in session "Sales Invoice Transactions -
tfacr1111s000" is the Credit Note amount subtracted with the SHIFTED vat amount. This is incorrect because the
Remaining amount should be the Credit Note amount in case of SHIFTED vat. This caused an unbalanced batch.
SOLUTION
DESCRIPTION:
In case of a SHIFTED vat the remaining amount to be assigned in the lines (session "Sales Invoice Transactions -
tfacr1111s000") is the amount of the Credit Note.

Solution: 123864
SITUATION IDENTIFIED IN:
"Generate invoice by selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
There are occasions when there is no tax calculated whereas it actually should calculate tax with session tfacp2290m000.
SOLUTION DESCRIPTION:
With an older solution the user is now able to set the invoice date in tfacp2290m000. This solution is however not complete as
with compression a variable is used which is not always filled correctly now. This variable stands for the date for which the
rates have to be searched for the tax code. Because the date is now 0 it can not find the tax rates and no tax is being
calculated. Now the correct variable is passed to the tax include, so that the correct amount of tax is calculated.

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

Solution: 123903
SITUATION IDENTIFIED IN:
"Termination Process (Actual)" (tfgld1212s000)
SITUATION DESCRIPTION:
It is not updating the Japanese dimension history tables when you finalize the transaction type of which updation mode of '
Real time ' or ' End of session'.
SOLUTION DESCRIPTION:
Now it is updating Japanese dimenstion history tables.

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

Solution: 123934
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260m000)
SITUATION DESCRIPTION:
If many trade note payable are linked to one payment batch, a user have to click OK button and enter output device many
times in tfcmg1260m000 session during the compose payment.
SOLUTION DESCRIPTION:
Now this compose payments process is made automatic so that while processing more than one trade note the user need to
give input only once in session tfcmg1260m000 and for next document onwards it processes automatically by taking the first
document detail for all other doucments,

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

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

Solution: 123995
SITUATION IDENTIFIED IN:
"Print Journal" (tfgld1441m000)
SITUATION DESCRIPTION:
If the current fiscal year is printed and the session gives a report as output and after that the year before the current fiscal
year is printed, the session always give the message 'No Data Within Selection' while there is data available in the system to
be printed for this year.
SOLUTION
DESCRIPTION:
This error was in this session since the variable for the year to print was not reset after the first print. Because of this the
second time the report was printed nothing was selected to be printed.

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

Solution: 124026
SITUATION IDENTIFIED IN:
"Match/Approve purchase invoices" (tfacp2107s000)
SITUATION DESCRIPTION:
When there is a difference in the rates between order currency and the home currencies at the time of registration of the
order and at the time of approving the invoice (where invoice currency equals the order currency) then the invoice amount is
not updated as expected in purchase. If the order currency and the invoice currency equal, and the invoice is matched with
no price difference, then the expected invoice amount in purchase should be exactly the order amount.
SOLUTION
DESCRIPTION:
During the approval process in finance a lot of calculations are done to determine whether there is a
price difference etc. These calculations are done through the reference currency, but only when
the order currency and invoice currency differ. If the invoice and order currency do not
differ then no recalculation through the reference currency should take place.
Everywhere in the script this principle was adopted exept on the place where purchase (distribution) was informed about the
invoice amount, this has now been corrected.

Solution: 124052
SITUATION IDENTIFIED IN:
"Intermediate Closing of Year" (tfgld6201m000)
SITUATION DESCRIPTION:
When you run the ' Intermediate Closing of Year ' session, it was not updating the Japanese History tables with new year
opening balance.
SOLUTION DESCRIPTION:
Now it is updating the Japanese History tables correctly.

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

Solution: 124109
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When you set up the mapping scheme for "Service - Subcontracting" and you do that on project then sometimes not this
mapping is used while approving the purchase invoice. It appears that when the integration transactions for "Service -
Subcontracting" are already posted that then the correct account is used, but when not, sometimes the wrong one.
SOLUTION
DESCRIPTION:
Whenever integration transactions are posted, the integration records are filled with the used ledger account and dimensions. So if approval of
an invoice appears after the posting of these integration transactions then always the correct and same invoice accrual account can be used. If
however the integration transactions are not yet posted then the approval process will have to search the mapping scheme. However this search
was done with the project of the purchase order and not with the project of the subcontracting service order. And as all integration transactions
(except the Purchase - On Order) are logged against the subcontracting order and not the purchase order, also the project of the subcontracting
order should be used and not the project of the purchase order.

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

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

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

Solution: 124147
SITUATION IDENTIFIED IN:
"Assign Credit Notes To Invoices" (tfacr2121m000)
SITUATION DESCRIPTION:
Linking a credit note to a doubtful inv. doesn´t inform about doubtful condition.
SOLUTION DESCRIPTION:
Now whenever a credit note is being linked to doubtful invoice,a message is displayed about the invoice being doubtful.

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

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

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

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

Solution: 124214
SITUATION IDENTIFIED IN:
"Assign Invoices to Credit Notes" (tfacp2121s000)
SITUATION DESCRIPTION:
In session "Assign Invoices to Credit Notes - tfacp2121s000", when using the option "Default Amount", the user gets the
message "To be linked amount cannot exceed balance credit note", although the linked amount is the equal to the credit note
balance.
SOLUTION DESCRIPTION:
The user can use option "Default Amount" if the linked amount does not exceed the credit note balance.

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

Solution: 124219
SITUATION IDENTIFIED IN:
"Purchase-Invoice Transactions" (tfacp1120s000)
SITUATION DESCRIPTION:
The tax amounts are not correctly calculated when a group tax code (VAT + Withholding tax) and the level of tax calculation
is by transaction line. The defaulting is done correct but if the user modifies the defaulted amount because he/she want`s to
enter more than one line the amounts are incorrectly recalculated.
SOLUTION
DESCRIPTION:
Also the modifying the default amount results in correctly recalculated vat amounts.

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

Solution: 124276
SITUATION IDENTIFIED IN:
"Set Schedule Lines as Doubtful" (tfacrl103m00l)
SITUATION DESCRIPTION:
The rounded amounts are incorrect in Home currencies & the rounding is not as per the rounding factors defined for that
currency
SOLUTION DESCRIPTION:
Now the amounts are rounded as per the rounding factors defined for the currency.

Solution: 124299
SITUATION IDENTIFIED IN:
"Assign credit note to invoices" (tfacp2121s000)
SITUATION DESCRIPTION:
After linking a credit note to an invoice (both of type related to order) and the invoice does not have any tax, but the
credit note does and when the invoice has a different currency from the credit note then it appears that there is going
something wrong, because the amount presented to the user for matching is wrong and also after approving the document
does not balance.
SOLUTION
DESCRIPTION:
The net invoice calculation for an invoice (or credit note) is done in invoice currency. Whenever a
credit note with a different currency is linked to an invoice the linked record in the subadministration (open entries)
should store the net amount and the vat amount in invoice currency. The net amount was calculated in the currency of the
invoice, but the vat amount was filled with the vat amount in credit note currency, which is wrong. This has now been
solved, as now also the vat amount in invoice currency is calculated in invoice currency.

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

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

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

Solution: 124338
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
After entering Unallocated receipt, if Posting Data is Maintained it is not Possible to delete this completely from tables
Open Entries , Non -Finalised Transactions and Interim Cash Management Table , thereby it was popping up error message
"Assignments found. Record cannot be deleted" in the session "Bank Transactions", when we try to delete the transaction.
SOLUTION
DESCRIPTION:
Now , it is possible to delete the transaction in the session "Bank Transactions" , when the "Posting Data" has been deleted
from the session "Posting cash Management -Detail".

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

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

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

Solution: 124394
SITUATION IDENTIFIED IN:
"Print Open Entries" (tfacp2421m000)
SITUATION DESCRIPTION:
Open Entry balance was showing wrong invoice balance even when the document was fully reconciled when multiple control
account option range selected from "Non-trade" to "Non-trade" in the following case
1. Multiple control account parameter should be ON
2.Invoice was created with control account option as Non trade control account.
SOLUTION DESCRIPTION:
Now for above parameter setup the Open entry balance of purchase invoices is displaying correct amount.

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

Solution: 124406
SITUATION IDENTIFIED IN:
"Posting Data Standing Orders/Stand alone Payments." (tfcmg1113s000)
SITUATION DESCRIPTION:
While maintaining Posting Data of Standing Orders, when the user tries to modify the default value of the Tax Code to
blank, a Null Pointer is thrown in the when field changes.
SOLUTION DESCRIPTION:
While maintaining Posting Data of Standing Orders, now the user can modify the default value of the Tax Code to blank.

Solution: 124416
SITUATION IDENTIFIED IN:
"Assign Credit Note to Invoices" (tfacp2121s000)
SITUATION DESCRIPTION:
1.When an invoice is assigned to a credit note and an amount is linked, if later again the linked amount is modified, the
system does not update the invoice balance as well as the balance of creditnote.
2. The table tfgld102 is not getting correctly posted.
3.The linked document attached to the credit note in open entries is not getting deleted after unlinking the credit note.
SOLUTION DESCRIPTION:
Problems were occuring because of a bad fix of solution 122078. The following three problems are solved now::
1. The balance in tfacp200(both on invoice and credit note) is getting updated correctly after linking and unlinking of a
credit note.
2. Posting in table tfgld102 is now correct.
3. The linked document attached to the credit note in open entries is now getting deleted after unlinking the credit note.

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

Solution: 124425
SITUATION IDENTIFIED IN:
"Generate Invoices by Self Billing" (tfacp2290m000)
SITUATION DESCRIPTION:
Payment agreement was empty in the accounts payable table while "Generating the Invoices by self-billing"
SOLUTION DESCRIPTION:
Now the payment agreement is filling with the payment agreement given in the purchase order.

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

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

Solution: 124457
SITUATION IDENTIFIED IN:
"Posting Cash Management" (tfcmgl221m000)
SITUATION DESCRIPTION:
Document is not Balanced, when an unallocated receipt is entered for an earlier date (before system Date) and if there is
any Currency Rate difference between these dates.
SOLUTION DESCRIPTION:
Now the document is Balanced, when an unallocated receipt is entered for an earlier date (before system Date) and when
there is any Currency Rate difference between these dates

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

Solution: 124488
SITUATION IDENTIFIED IN:
"Inventory-Inspection Data" (whinh3122s000)
SITUATION DESCRIPTION:
Wrong transaction date for Japanese localization written into Finance integration.
SOLUTION DESCRIPTION:
For Japanese localization solution 106986 was revoked.
In B5.0c it is decided via parameter 'Lower of cost or market price' (tccom936.lcml.l) from table 'tccom936' (General
Localization Parameters) whether program is running with Japanese localization or not.
[ Parameter = 1 means Japanese localization. ]

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

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

Solution: 124507
SITUATION IDENTIFIED IN:
"Select Invoices for Direct Debit" (tgcmg4220m000)
SITUATION DESCRIPTION:
If the invoice is with payment schedule and the original due date is changed with a date before the original one, then the
invoice is not selected if the selection interval doesn't include the original due date.
SOLUTION DESCRIPTION:
Now the selection is done according the actual due date

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

Solution: 124516
SITUATION IDENTIFIED IN:
"Assign invoices to credit notes" (tfacp2121s000)
SITUATION DESCRIPTION:
If the update mode of the transaction type is real time and when the user links an invoice to a credit note in tfacp2121s000
and afterwards immediately unassigns the amount (so change to 0 again) then the transactiontype is ready, but the user can
not finalize. The user gets the message that the background process still has to be invoked. After invoking the
backgroundprocess manually in the general ledger module, finalisation is possible.
SOLUTION
DESCRIPTION:
The backgroundprocess needs to be started whenever something changes in the document status when the update mode is real
time. Because the amount was changed to 0 again the backgroundprocess was not called and still 2 records remain in the
linking document, which should actually be deleted by the backgroundprocess. This has now been corrected.

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

Solution: 124549
SITUATION IDENTIFIED IN:
"Compose/Print/post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
1.When Localazation Parameter "Multiple Tax" is ON, the revenue analysis postings booked in home currencies went
wrong.
2. With the same parameter ON and if an installment is settled with an equal goods amount, the batch created was
unbalanced.
SOLUTION DESCRIPTION:
Now the revenue-analysis postings are booked correctly and also the batch created during setttlement of an installment
with goods amount was balanced.
A correction program(ocicor0114) was created specifically for this customer and the objects are sent to him.

Solution: 124553
SITUATION IDENTIFIED IN:
"Reconciliation Payments/Receipts" (tfcmg2103s000)
SITUATION DESCRIPTION:
Payment reconcilation batch was not balanced because there was no posting to Control account.
SOLUTION DESCRIPTION:
Batch was not balanced.

Solution: 124555
SITUATION IDENTIFIED IN:
"Payment Advice" (tfcmg1120m000)
SITUATION DESCRIPTION:
The default discount amount which was entered in the payment schedule, is not displayed correctly when you select the
purchase invoice in the payment advice manually.
SOLUTION DESCRIPTION:
It is showing correctly the defaulted discount amount.

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

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

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

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

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

Solution: 124650
SITUATION IDENTIFIED IN:
Running Baan Login Daemon, having ASM daemon enabled.
SITUATION DESCRIPTION:
The Baan Login Daemon (blogind6.2) is started in that way that the ASM daemon is enabled.
(The ASM deamon is an integrated in the Baan Login Daemon)
But the ASM daemon is not started correctly, and the following message is given, when running blogind6.2 using the -d
(debug) option:
"ASM daemon information initialization failed"
For example:
# blogind6.2 -p 7150 -d
Node
Node has 3 attributes
Attibute Name: name , Value: BSE
Attibute Name: system , Value: nowis14
Attibute Name: directory , Value: /baan/ivc/bse
Node has 1 attributes
Attibute Name: type , Value: OpenWorld
Node has 4 attributes
Attibute Name: executable , Value: ${BSE}/bin/bshell6.2
Attibute Name: exeparameters , Value: Server
Attibute Name: sessioncode , Value: otmboaasmserver
Attibute Name: sessionparameters , Value: -busc %USERDATA% -asmp %PORT%
Node has 1 attributes
Attibute Name: executable , Value: ${BSE}/bin/bshell6.2
Node has 1 attributes
Attibute Name: type , Value: DedicatedXMLMapper
Node has 4 attributes
Attibute Name: executable , Value: /baan/ivc/bse/bin/bshell6.2
Attibute Name: exeparameters , Value: -server -dbgjvmi -keeplog -logfile asmloge
Attibute Name: sessioncode , Value: otmboaasmserver
Attibute Name: sessionparameters , Value: -busc %USERNAME% -asmp %PORT% -logf ae
Node has 1 attributes
Attibute Name: executable , Value: /baan/ivc/bse/bin/bshell6.2
Node
Node has 3 attributes
Attibute Name: name , Value: BSE
Attibute Name: system , Value: nowis14
Attibute Name: directory , Value: /baan/ivc/bse
Node is has 4 attributes
Attibute Name: servicename , Value: nowis14
Attibute Name: servicetype , Value: DedicatedXMLMapper
Attibute Name: occurance , Value: multiple
Attibute Name: startup , Value: manual
Node has 0 attributes
ASM daemon information initialization failed
Daemon: listen for first connection.
SOLUTION DESCRIPTION:
The ASM daemon creates a small part of shared memory. Usually this is 32 bytes.
But when the kernel parameter shm-min is set too high, for example set to 1024, it is not possible to create a shared memory
of 32 bytes.
The smallest size has be 1024 bytes in this case.
Therefor set the shm-min to 1.

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

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

Solution: 124667
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When a normal advance receipt(which is created from reconciling the anticipated advance receipt) with vat code and country is
linked to an invoice, fatal error occurs.
SOLUTION DESCRIPTION:
Earlier, a fatal error occurs when assigning an advance receipt,having vat code and country, to an invoice.
Now, line number is picked properly to fill vat details avoiding the fatal error

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

Solution: 124745
SITUATION IDENTIFIED IN:
"Select Business Partner Receipts for Interest Invoices" ((tfacr5210m000)
SITUATION DESCRIPTION:
Interest amount is not calculated correctly, It was not considering the interest that has already paid.
SOLUTION DESCRIPTION:
Interest amount is calculated correctly. It considers the interest that has been paid.

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

Solution: 124757
SITUATION IDENTIFIED IN:
"Posting Cash Management-Detail" (tfcmgl202m00l)
SITUATION DESCRIPTION:
A message "Record already exists" is displayed and it cannot process , when we try to insert a record in the session
Posting Cash Management-Detail .
SOLUTION DESCRIPTION:
The sequence number was not getting incremented as the Line No.was not picking up the correct value in the session
Posting Cash Management-Detail .
Now the record is getting inserted properly.

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

Solution: 124791
SITUATION IDENTIFIED IN:
"Assign unallocated/advance payments to invoices" (tfcmg2106s000)
SITUATION DESCRIPTION:
When an unallocated payment is linked with an invoice and pressed "Process assignments" twice, transaction is recorded
twice.
SOLUTION DESCRIPTION:
Earlier, transactions are recorded twice due to initialization problems.
Now, initialization is done properly. Thus, transactions are recorded properly.

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

Solution: 124823
SITUATION IDENTIFIED IN:
"Generate Invoice by selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
With self-billed invoices, the Average purchase prices for items were not calculated correct, when the method of calculating
average purchase price is "Current Inventory". The curent receipt in such a case is added to the old stock, because of which
the current received quantity is counted twice
SOLUTION DESCRIPTION:
The situation occured because the currenct received quantity was counted twice. This is no longer done now.
SOLUTION 125115 ALSO TO AVOID DUPLICATE RECORD ( ERROR 100 )
FATAL ERROR.
VERSION(S):
B50_b, B50_c, B52_a

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 124981
SITUATION IDENTIFIED IN:
"Post Payments" (tfcmg1257m000)
SITUATION DESCRIPTION:
When a Payment invoice with discount is processed, the document balance shows the discount value instead of zero in the
session "Open Entries".
SOLUTION DESCRIPTION:
When a Payment invoice with discount is processed, the document balance will now show the discount value as zero in the
session "Open Entries". The reported problem is solved now.

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

Solution: 125027
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
When changing the Payment Currency of an Invoice with Discount, the Amount in Bank Currency is wrongly calculated.
SOLUTION DESCRIPTION:
When changing the Payment Currency of an Invoice with Discount, the Amount in Bank Currency is correctly calculated
now.

Solution: 125031
SITUATION IDENTIFIED IN:
"Anticipated Document for Notifying" (tfcmgl104m00l)
SITUATION DESCRIPTION:
No records were created in non-finalized transactions when the document status was changed from "Document issued" to
"Document matured"
SOLUTION DESCRIPTION:
Now the documents are creating for non-finalized transactions when the document status is changed from "Document
issued" to "Document matured"

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

Solution: 125039
SITUATION IDENTIFIED IN:
"Reconciliation of Reciepts/Payments " (tfcmg2103s000)
SITUATION DESCRIPTION:
When discounts are given while maintaining a manual anticipated receipt , the discount amount is not considered during
reconcilation,when none of the discount influencing parameters are checked "ON " .
SOLUTION DESCRIPTION:
Now the discounts are calculated and displayed properly

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

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

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

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

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

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

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

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

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

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

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

Solution: 125188
SITUATION IDENTIFIED IN:
"Set Schedule Lines as Doubtful" (tfacrl103m00l)
SITUATION DESCRIPTION:
Session doesnot display all invoices as per the requirements
SOLUTION DESCRIPTION:
Invoices are displayed as per the requirements

Solution: 125201
SITUATION IDENTIFIED IN:
"Manual Invoice Lines" (cisli2125s000)
SITUATION DESCRIPTION:
When Localization Parameter "Multiple Control Account" is ON, the user has a flexibility to define Non-trade control
account for Non-trade invoices. This was possible only in Manual Invoices created in ACR module. This should be possible
for Manual Invoices created in Central Invoicing also.
SOLUTION DESCRIPTION:
Now this functionality is built for Manual Invoices created in Central Invoicing also. While maintaing the line, if the user
defines the "Charge type" as "Not Applicable" then those lines are treated as Non-trade lines and a Non-trade Invoice will
be created. And the Non-trade control account will be used.
Please note that these non-trade lines can never be composed together with the normal sales lines. ie Seperate Invoices will
be created.

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

Solution: 125223
SITUATION IDENTIFIED IN:
"Creation of Recurring Transactions" (tfgld1202m000)
SITUATION DESCRIPTION:
Transaction date was not updated in the case of repetitive jounral entries in the non-finalized transactions.
SOLUTION DESCRIPTION:
Transaction date is updated in the non-finalized transactions in the case of repititive journal entries.

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

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

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

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

Solution: 125250
SITUATION IDENTIFIED IN:
"Link Invoices to Credit Notes" (tfacr2121m000)
SITUATION DESCRIPTION:
A normal credit note is assigned to the doubtful invoice.
Eventhough the message is given that the invoice is doubtful, the credit note is linked to the invoice.
SOLUTION DESCRIPTION:
A normal credit note is not assigned to the doubtful invoice.
A doubtful credit note is assigned to a doubtful invoice.

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

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

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

Solution: 125284
SITUATION IDENTIFIED IN:
"Closing Year" (tfgld6203m000)
SITUATION DESCRIPTION:
Japanese opening balance History tables were not updated correctly when you run the closing year process.
SOLUTION DESCRIPTION:
It is updating the opening balance history tables correctly when you run the closing year process now.

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

Solution: 125355
SITUATION IDENTIFIED IN:
"Terms of payment" (tcmcs0113s000)
SITUATION DESCRIPTION:
When assigning a financial rate code to terms of payment, the average number of days may not be greater than the range of
days covered by the financial rate. However the system would not allow an average number of days equal to that range
either.
Also when more than one line was entered on the financial rate, the system only checked the days of the first line.
SOLUTION DESCRIPTION:
When assigning a financial rate code to terms of payment, the average number of days is now compared with the total range of
days covered by all lines of the financial rate. Also an average number of days equal to the financial rate is allowed.

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

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

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

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

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

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

Solution: 125466
SITUATION IDENTIFIED IN:
"Generate Invoices by selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
Incase a "gross" tax code is used in the purchase order, then the invoice generated has the tax calculation based on the gross
amount. However it should still be calculated as if it is a Net tax code
SOLUTION DESCRIPTION:
Now, even when the tax code is of type gross, the tax calculation treats this as a tax code of type net.

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

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

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

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

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

Solution: 125517
SITUATION IDENTIFIED IN:
"Payment Advice" (tfcmg1120m000)
SITUATION DESCRIPTION:
The Amount paid in the Payment advice is not correct when you have the schedules are off, discount ' off' and trade note
parameter is ' on'.
SOLUTION DESCRIPTION:
The amount paid in the payment advice is displayed correctly now.

Solution: 125526
SITUATION IDENTIFIED IN:
"Assign unallocated /advance payments to invoices" (tfcmg2106s000)
SITUATION DESCRIPTION:
Two problems are reported:
1.Unable to see the invoice when only one invoice is paid and
2.Unable to reverse the assignment when multiple invoices are paid
SOLUTION DESCRIPTION:
Earlier,
1. it is not possible to see the invoice when only one invoice is paid and
2.Unable to reverse the assignment when multiple invoices are paid
Now,
1. Can see the invoice with assignment and is possible to reverse it
2. It is possible to reverse the assignment when multiple invoices are paid
SOLUTION
------------------------------------------- PLEASE DOWNLOAD 126663 ALSO AFTER DOWNLOADING THIS SOLUTION
VERSION(S):
B50_b, B50_c

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

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

Solution: 125538
SITUATION IDENTIFIED IN:
"Journal Voucher" (tfgld1103m000)
SITUATION DESCRIPTION:
Business partner field was not updated in the Non-finalized transaction when you create the transaction through the
transaction schedule in the Journal voucher.
SOLUTION DESCRIPTION:
Business partner field was updated correctly now in the Non-finalized transactions.

Solution: 125541
SITUATION IDENTIFIED IN:
"Assign Credit Note to Invoice" (tfacp2121s000)
SITUATION DESCRIPTION:
The following situations were noticed when the Localization parameter tccom936.pays.l is on .
1. The Paid amount (tfacp201.paia) is doubled.
2. In case payment schedule has multiple lines, then for each line, the linked amounts ( tfacp201.lamt.l ) is updated with
the total linked amount instead of the amount belonging to the line, during Assign default amounts.
3.Incase Assign default amount is done to an invoice which is fully assigned already ( invoice balance = 0 ) then the balances
gets updated incorrectly to there original balances.
SOLUTION DESCRIPTION:
The above situations have been solved.
1. The "Paid Amount" in table Payment schedule is correctly updated.
2. Incase of multiple payment schedule line, the linked amount corresponds to the Balance amount.
3.If the Invoice has been assigned completely, invoking Assign default amount option again does not update this invoice /
Payment schedule for the invoice anymore.

Solution: 125549
SITUATION IDENTIFIED IN:
"Anticipated Payments" (tfcmg2110s000)
SITUATION DESCRIPTION:
Description of pay-to business partner was wrongly displaying with name of the address instead of name of the business
partner.
SOLUTION DESCRIPTION:
Now the description of pay-to business partner is correctly displaying with name of the business partner.

Solution: 125553
SITUATION IDENTIFIED IN:
"Post Direct Debits" (tfcmg4257m000)
SITUATION DESCRIPTION:
No VAT is calculated on advance receipt when the payment method has no steps defined.
SOLUTION DESCRIPTION:
Now VAT is calculted and posted correctly on advance receipt when the payment hans no steps defined

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

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

Solution: 125575
SITUATION IDENTIFIED IN:
"Transfer payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
With the delivery of solution 123370 phase II of the IBAN functionality has been delivered for B40_c, B50_b and B50_c.
However, some components were not delivered correctly for the localisations of B50_b and B50_c.
SOLUTION DESCRIPTION:
With the components of this solution the IBAN functionality for phase II is complete in the localisations for B50_b
(B50_b_bgl0 and B50_b_jpn0) and B50_c (B50_c_bgl0).

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

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

Solution: 125607
SITUATION IDENTIFIED IN:
"Print Integration Transactions" (tfgld4410m000)
SITUATION DESCRIPTION:
Details of Inventtory ledger report was not correct
SOLUTION DESCRIPTION:
Now it is printing correctly

Solution: 125638
SITUATION IDENTIFIED IN:
"Print Statements Of Account" (tfacr3440m000)
SITUATION DESCRIPTION:
The Invoice amount, invoice received and amount open are wrong in case the box Use EURO instead of EMU currencies is
flagged
The problem appears only for the invoice in the EMU currency and if receipt Schedule parameter is "ON"
SOLUTION DESCRIPTION:
Now the invoice amount,invoice received and amount open are being calculated and displayed properly.

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

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

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

Solution: 125683
SITUATION IDENTIFIED IN:
"Write Off Currency Differences" (tfacr2250m000)
SITUATION DESCRIPTION:
In session "Write Off Currency Differences" (tfacr2250m000), the field "Bal In Inv Curr" on the report is not getting filled
with values.
SOLUTION DESCRIPTION:
The field "Bal In Inv Curr" is now getting printed with the correct values.

Solution: 125716
SITUATION IDENTIFIED IN:
"Creation of Recurring Transactions" (tfgld1202m000)
SITUATION DESCRIPTION:
The Fatal error is occurring while creating recurring transactions when the parent business partner bank differs from the
child business partner bank.
SOLUTION DESCRIPTION:
Now the fatal error is not occurring and recurring transactions were created.

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

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

Solution: 125752
SITUATION IDENTIFIED IN:
"Maintina receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Purchase order details were not filled in case of production subcontracting integration transactions
SOLUTION DESCRIPTION:
The problem is solved now

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

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

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

Solution: 125781
SITUATION IDENTIFIED IN:
"Open Entries" (tfacp2520m000)
SITUATION DESCRIPTION:
All Multiple control accounts were not displayed when this session is zoomed from any other sessions even when the
multiple control account parameter was ON.
SOLUTION DESCRIPTION:
Now Multiple control accounts are displayin when this session is zoomed from any other sessions when the multiple control
account parameter is ON.

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

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

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

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

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

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

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

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

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

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

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

Solution: 125862
SITUATION IDENTIFIED IN:
"Receipt Schedule" (tfacrl504m00l)
SITUATION DESCRIPTION:
Session should show only Open, Selected and Partially Paid schedule lines.
SOLUTION DESCRIPTION:
Session displays Open, Selected and Partially Paid schedule lines.
There is a toggle between the fully paid and Open ,Selected , Partially Paid schedule lines.

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

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

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

Solution: 125925
SITUATION IDENTIFIED IN:
"Billing Requests" (cisli2100s000)
SITUATION DESCRIPTION:
Even though the VAT Code is not linked to the transaction types defined in the SLI Parameters, the system is giving an error
message that series has to maintained for that Tax year.
SOLUTION DESCRIPTION:
Linking of VAT Code to the transaction type is not mandatory.
So if the user has not linked any, then the system will not check for the existence of the linkage between the Tax year and
the series used in the Transaction Types

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

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

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

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

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

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

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

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

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

Solution: 126047
SITUATION IDENTIFIED IN:
"Invoice- to Business Partners " (tccom4112s000)
SITUATION DESCRIPTION:
If Brazilian taxes are set to YES in Localization parameters, the Business Partner Category field in Invoice to Business Partner
session is enabled. This field is not used in Brazil, so it must not be part of tax defaults selection.
SOLUTION DESCRIPTION:
The Business Partner Category is disabled and not applicable for Brazilian Localization.

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

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

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

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

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

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

Solution: 126225
SITUATION IDENTIFIED IN:
"Print Control Account checklist" (tfacr2415m000)
SITUATION DESCRIPTION:
In "Print Control Account Checklist" and select " Print differences" only, Business Partners with no differences are printed.
SOLUTION DESCRIPTION:
In "Print Control Account Checklist" and select "Print differences" only, It prints " Total for Business Partner Group" and
"Total for Ledger Account " for the Business Partners with some differences.
SOLUTION "127275" IS POST-REQUISITE AND SHOULD BE DOWNLOADED ALONG WITH THIS SOLUTION.
VERSION(S):
B50_b, B50_c

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

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

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

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

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

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

Solution: 126288
SITUATION IDENTIFIED IN:
B50_b Customers please refer this : "Reprint Invoices" (cisli2405m000)
B50_c Customers please refer this : "Picking List" (whinh2525m100)
SITUATION DESCRIPTION:
B50_b Customers please refer this :
When reprinting the sales invoices from the Central Invoicing Module (cisli2405m000), the error 'Next Working Day is not
found' is encountered if the option 'Working days' is checked in the SLI parameters.
The system checks for the calender declared for the company to check & calculate the due dates for the payment. Even when
the due date is declared in the calender, this error is shown.
B50_c Customers please refer this :
1. Select all the lines for a Picking list sorted by 'Advised Quantity in Inventory Unit' in the session "Picking List"
(whinh2525m100)
2. When selecting the option of 'Confirm Advice Lines', Fatal Error 206 was popping up.
SOLUTION DESCRIPTION:
B50_b Customers please refer this :
The problem is now solved & if due dates are declared, this error will not be shown.
B50_c Customers please refer this :
Actually Shipments lines were not getting confirmed because of some insufficient data , In such case system should pop up
an error message , but it was giving a Fatal error . Now the Fatal error will not come up and error message comes up when
the user tries to confirm shipment lines.

Solution: 126292
SITUATION IDENTIFIED IN:
"Assign unallocated /advance payments to invoices" (tfcmg2106s000)
SITUATION DESCRIPTION:
When the payment schedule is "off", fatal error occurs when an unallocated payment is linked to 2 or more invoices
Fatal error 100 duplicate value when trying to allocate an UD to 2 invoices
SOLUTION DESCRIPTION:
Earlier, it is not possible to link one unallocated/advance payment to more than one invoice
Now, it is possible to link any number of invoices to one unallocated/advance payment

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

Solution: 126318
SITUATION IDENTIFIED IN:
"Link Invoices to Credit Notes II" (tfacr2121m000)
SITUATION DESCRIPTION:
It is not possible to unlink a credit note from a sales invoice.
Balance updating is wrong while linking a credit note to a Sales invoice.
SOLUTION DESCRIPTION:
It is possible to unlink a credit note from a sales invoice.
The balance updating of invoice and credit note while linking has been corrected

Solution: 126322
SITUATION IDENTIFIED IN:
"Posting Data per Bank & Payment/Receipt Method" (tfcmg0146s000)
SITUATION DESCRIPTION:
It was displaying an error message after defining posting data for all the steps with " Input" accounts.
SOLUTION DESCRIPTION:
Now, no error message will be displayed when the posting data is correctly defined for all the steps.

Solution: 126329
SITUATION IDENTIFIED IN:
"Open Entries" (tfacp2520m000 and tfacr2520m000)
SITUATION DESCRIPTION:
Fully paid invoices appear in the Open Entries.
SOLUTION DESCRIPTION:
Now the fully paid invoices don't appear in Open Entries.

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

Solution: 126338
SITUATION IDENTIFIED IN:
"Audit payments" (tfcmg1255m000)
SITUATION DESCRIPTION:
When paying to a factoring company the message comes up that "IBAN number is not filled".
SOLUTION DESCRIPTION:
When paying to a factoring company the message "IBAN number is not filled" won't come up anymore and the problem is
solved.
SOLUTION "126160" FOR THE STANDARD COMPONENT IN BAAN B50 b
*******************************************************************************************************
*****************************
VERSION(S):
B40_c, B50_b, B50_c

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

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

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

Solution: 126379
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
Fatal Error 205 is occurring while posting the EBS batch.
SOLUTION DESCRIPTION:
Now the Fatal error is not occurring.

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

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

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

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

Solution: 126414
SITUATION IDENTIFIED IN:
"Payment / Receipt Method" (tfcmg0140s000)
SITUATION DESCRIPTION:
Mandatory step "Document accepted/sent" was not checked when a new payment method was created.
SOLUTION DESCRIPTION:
Now the document accepted / sent is made mandatory when the trade note parameter is ON

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

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

Solution: 126427
SITUATION IDENTIFIED IN:
"Assign Credit Note to Payment Schedule Lines" (tfacpl103s001)
"Link Invoices to Credit Notes" (tfacp2121s000)
SITUATION DESCRIPTION:
After an unasignment, the field 'linked amount' remains the amount of the credit note. Also, when assigning a next invoice to
a credit note, the balance-amount of the first invoice becomes the balance of the second invoice.
SOLUTION DESCRIPTION:
After an unasignment, the field 'linked amount' becomes zero, like it should be. When assigning a next invoice to a credit
note, the balance-amount is the amount belonging to that invoice.

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

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

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

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

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

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

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

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

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

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

Solution: 126550
SITUATION IDENTIFIED IN:
"Business partner Purchase Invoices" (tfacp2521m000)
SITUATION DESCRIPTION:
Balance of business partner was not updated correctly and open invoice amounts of business partner were also wrong when
the trade notes were reconciled.
SOLUTION DESCRIPTION:
Now the business partner balances is updated correctly and also open invoices was shown correct balances after
reconciliation of trade notes.

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

Solution: 126653
SITUATION IDENTIFIED IN:
"Shipment Lines by Warehousing Order" (whinh4535m000)
"Shipment Lines by Warehousing Order" (whinh4131s000)
SITUATION DESCRIPTION:
Help text not clear for the check box 'Manual' in sessions "Shipment Lines by Warehousing Order" (whinh4535m000) and
"Shipment Lines by Warehousing Order" (whinh4131s000).
SOLUTION DESCRIPTION:
Now, the Help Text for the check box 'Manual' is changed according to the functionality.

Solution: 126663
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Message text is not displayed when the document line number is >99
SOLUTION DESCRIPTION:
Earlier, message text is not displayed
Now, message text is displayed
SOLUTION
VERSION(S):
B50_b, B50_c

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

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

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

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

Solution: 126741
SITUATION IDENTIFIED IN:
"Journal voucher for Offset Details" (tfgldl537s00l)
SITUATION DESCRIPTION:
The Offset document was not displayed in the session ' Journal vouches for offset accounts".
SOLUTION DESCRIPTION:
Now the Offset document is displayed in the session ' Journal vouches for offset accounts".

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

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

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

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

Solution: 126860
SITUATION IDENTIFIED IN:
"Manual Invoice Lines" (cisli2125s000)
SITUATION DESCRIPTION:
When Italian Localization Parameter "Vat Book" is ON, the user should not be able to enter a tax code which is of type "Not
Applicable". But the system allows the user to enter.
SOLUTION DESCRIPTION:
When Vat code is linked to the transaction type, then an error message is displayed when the user tries to enter a Vat code
of type "Not Applicable".
Similarly when Vat code is not linked to the Transaction type, then an error message will be displayed if the vat code
entered is of type "VAT"

Solution: 126877
SITUATION IDENTIFIED IN:
"Anticipated Document for Notifying" (tfcmgl104m00l)
SITUATION DESCRIPTION:
Unnecessary additional postings were made when the Anticipated document step status was changed from document issued to
accepted/sent status.
(Ex. when anticipated step status changed from Document issued to Document accepted/sent the postings for document
matured were also posted.)
SOLUTION DESCRIPTION:
Now no additional postings will be made when the anticipated document status is changed from document issued to
document accepted/sent.

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

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

Solution: 126900
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
It is not possible to handle 'Menu' and 'Option' items in the Purchase Order Lines. But the KIT items of type List can be
handled.
SOLUTION DESCRIPTION:
1. Now, the Menu and Options can be handled in the Purchase Order Lines.
2. The session that shows the components of the List item would appear once the List item is entered in the Purchase Order
Line.
3. If the user does not select any of the components, then the system would not allow proceeding further until some
component(s) is selected.
SOLUTION 127001 AFTER THIS SOLUTION 126900.

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

Solution: 126911
SITUATION IDENTIFIED IN:
"tfcmg0140s000" (Receipt Methods)
SITUATION DESCRIPTION:
It was not possible to define a payment method without any anticipated step.
SOLUTION DESCRIPTION:
Now it is possible to define a payment method without any anticipated step.

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

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

Solution: 126981
SITUATION IDENTIFIED IN:
"Link Invoices to Creditnotes" (tfacp2121s000)
SITUATION DESCRIPTION:
When linking a Credit note to a Invoice twice, the field 'linked amount' remains the amount of the credit note.
SOLUTION DESCRIPTION:
When linking a Credit note to a Invoice twice, the field 'linked amount' become zero, what it should be.

Solution: 126985
SITUATION IDENTIFIED IN:
"Print Terms of Payment" (tcmcs0413m000)
SITUATION DESCRIPTION:
In the report Terms of Payment, if a text is present for a record, some fields will be printed as "FFFFF" .
SOLUTION DESCRIPTION:
The report Terms of Payment contained some text in the part where the Text for Terms of Payment is printed, which looked as
if several fields were printed as "FFFFF". This text has been removed. The values for these fields are already printed in the
main body of the report.
If a text is entered for a Terms of Payment then only that text is printed on the report now.

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

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

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

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

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

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

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

Solution: 127111
SITUATION IDENTIFIED IN:
"Rebuild Ledger/Dim History - Final/Non Final Trans" (tfgld3203m000)
SITUATION DESCRIPTION:
Fatal error was occurring while rebuilding opening balance/history from transactions with the option of rebuild dimension
history.
SOLUTION DESCRIPTION:
Now Fatal error is not occurring while rebuilding the opening balance/history from transactions with the option of rebuild
dimension history.

Solution: 127133
SITUATION IDENTIFIED IN:
"Reconciliation Anticipated Payments/Receipts" (tfcmg2103s000)
SITUATION DESCRIPTION:
Fatal Error occurs while re-entering the session "Reconciliation of Receipts/Payments"
SOLUTION DESCRIPTION:
Earlier, fatal error was occurring while re-entering the session "Reconciliation of Receipts/Payments" and discount amount
was not filled properly in case of supplier reconciliation.
Now, Fatal error doesn't occur and the discount amount is properly filled in case of supplier reconciliation also.

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

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

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

Solution: 127158
SITUATION IDENTIFIED IN:
"Print Aging Analysis for Schedule Lines" (tfacrl404m00l)
SITUATION DESCRIPTION:
When opening the session " Print aging analysis for Schedule lines " for the first time, the first form gets the default
values. When these default values are changed with new values and after something is modified in the second form, the first
form retains only the default value and not the changed value.
SOLUTION DESCRIPTION:
When opening the session " Print aging analysis for Schedule lines " for the first time, the first form gets the default
values. When these default values are changed with new values and after something is modified in the second form, the first
form retains the changed value now and not the default value.

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

Solution: 127186
SITUATION IDENTIFIED IN:
"Write-off Payment Differences" (tfacr2240m000)
SITUATION DESCRIPTION:
Transaction Entry date is filled with today's date(i.e., the date when the batch is created) instead of Document date
specified.
SOLUTION DESCRIPTION:
Earlier, Transaction entry date is always today's date (i.e., the date when the batch is created).
Now, Transaction entry date is filled with the specified document date instead of batch-creation-date

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

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

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

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

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

Solution: 127242
SITUATION IDENTIFIED IN:
"Compose/Print/post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Gross amount and tax amount are not correct on sales invoice if tax code of type "Gross" is used.
This is applicable only for Manual Sales.
SOLUTION DESCRIPTION:
Now the tax amounts are calculated and printed correctly.

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

Solution: 127266
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
"Purchase- Requisition Lines" (tdpur2102s000)
SITUATION DESCRIPTION:
In Purchase Order lines, for cost or service items, while user is modifying 'Ordered Quantity' field to set units, the system
does not return correct units.
SOLUTION DESCRIPTION:
Now, System zooms to the correct session from the Ordered Quantity field in Purchase Order lines and also returns correct
unit.

Solution: 127339
SITUATION IDENTIFIED IN:
"Payment Advices" (tfcmg1120s000)
SITUATION DESCRIPTION:
Within session Payment Advices (tfcmg1501m000) no check is available on existence of Posting Data of Stand-alone
payments. Since session Posting Data (tfcmg1515s000) cannot be accessed directly from session Payment Advices
(tfcmg1120s000) entering posting data can easily be forgotten.
SOLUTION
DESCRIPTION:
When closing session 'Payment Advice' (tfcmg1501m000) warning message 'Posting data for
Stand-alone
Payment not
found'
will be given in
case no
Posting Data has been defined for the Stand-alone
payment within the payment
advice.

Solution: 127364
SITUATION IDENTIFIED IN:
"Generate Self Billed invoices" (tfacp2290m000)
SITUATION DESCRIPTION:
If in the common parameters "Destination Sales Tax" is set to applicable and the user processes a selfbilled order in session
tfacp2290m000 then whenever the debit receipt account is mapped to enterprise unit and the receipt integration transaction is
not yet posted, the user receives the error message that the debit expense account could not be determined.
SOLUTION
DESCRIPTION:
Whenver an integration transaction is posted the ledger account and dimensions are determined by the posting process and they can be used
immediately. If however the receipt integration transaction is not yet posted, the program tries to find the debit ledger account from the mapping
scheme. The user is able to map to Enterprise Unit, Department and Warehouse. It appears that for the debit mapping this is filled with the
enterprise unit of the warehouse and not with the enterprise unit of the purchase office. This same logic is now also used, so the enterprise unit
of the warehouse is used to search the mapping scheme.

Solution: 127372
SITUATION IDENTIFIED IN:
"Print Customer wise Aging Analysis" (tfacr2420m000)
SITUATION DESCRIPTION:
When the period for the invoice and the receipt are different then the Aging report is printed wrongly
SOLUTION DESCRIPTION:
Now the Aging Analysis report is printed correctly even when the periods for the invoice and the receipt are different

Solution: 127373
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
A)
1. There is an item with the purchase unit measured in length.
2. This item is entered in the purchase order lines, the 'Inspection' flag is not defaulted to the order line, when the
dimensions are entered.
B)
1. There is high conversion factor between the purchase unit and the price unit of the item.
2. A purchase order line is created with that item.
3. The order line amount of the Purchase Order Line and the amount shown in the session "Integration Transactions by
Project/Order" (tfgld4510m000) are different.
C)
1. The parameter 'Automatic confirmation of back orders' is YES in "Purchase Order Parameters" (tdpur0100s4000). There is a
Purchase Order Line with Inspection. The receipt is made for quantity lesser than ordered qty, with the 'Final receipt' flag
YES. This confirms the back order for the balance quantity. In the back order line the quantity is changed. Again, some
quantity is rejected in the approvals and the reduced quantity in the back order line is not considered and the quantity is
updated as a whole.
2. The back order line is created in the same way as it was done above. The back order line is cancelled and then some
quantity is rejected in the approvals and the rejected quantity is added in the cancelled back order line. Instead, it should
create a new back order line with sequence no 2. (Similar to the case where the original back order line has been deleted)
SOLUTION DESCRIPTION:
A)
The 'Inspection' flag would be defaulted once the item dimensions are entered.
B)
The difference between the amounts was due to the rounding of the received quantity in to the inventory unit of the item.
This has been solved and the amounts at both the places are same.
C)
1. The quantity to update in the back order line is determined as the difference between the current back order qty and the
original back order qty.
2. A new back order line with sequence number 2 is created now.

Solution: 127403
SITUATION IDENTIFIED IN:
"Change Price/Discounts after Receipts" (tdpur4122m000)
SITUATION DESCRIPTION:
An extra Receipt record with zero quantity is inserted in Finance table " Receipts by Packing Slip" table, if
Prices/Discounts are changed after Receipts through the session "Change Price/Discounts after Receipts".
SOLUTION DESCRIPTION:
Now, extra Receipt records with zero quantity are not generated if the prices/discounts are changed after Receipts.

Solution: 127404
SITUATION IDENTIFIED IN:
"Purchase-Invoice Transactions" (tfacp1120s000)
SITUATION DESCRIPTION:
If there are multiple purchase invoice transactions, then in session "Purchase-Invoice Transactions" (tfacp1120s000), when
only the reference field is updated, the amounts of all transactions are updated with amount from the first transaction line.
Hence the batch gets unbalanced and it is no longer possible to finalize the batch.
SOLUTION
DESCRIPTION:
The amounts are not changes when only the reference field is updated. Hence the batch remains balanced and it is now
possible to finalize the batch.

Solution: 127405
SITUATION IDENTIFIED IN:
"Link Invoices to Credit Notes II" (tfacr2121m000)
SITUATION DESCRIPTION:
The invoice, which has Advance Receipt Request (ARR) as yes, is not displayed in the session "Link Invoices to Credit Notes
II ". Hence it's not possible to assign a credit note to it when required.
SOLUTION DESCRIPTION:
Now the invoice with Advance Receipt Request (ARR) is also displayed if it has open balance & it is now possible to assign a
credit note to it from this session.

Solution: 127424
SITUATION IDENTIFIED IN:
"Posting Cash Management - Detail" (tfcmgl202m00l)
SITUATION DESCRIPTION:
Display of tax amount in home currency is not correct.
SOLUTION DESCRIPTION:
Display of tax amount in home currency is done correctly now.

Solution: 127449
SITUATION IDENTIFIED IN:
"Copy Item Data" (tcibd0205m000)
SITUATION DESCRIPTION:
When copying an item to a new item, the Item Production text is not copied to the new item
SOLUTION DESCRIPTION:
The system will copy the Item Production Text to the new item while copying the item.
While copying the item to a new Item, the system will copy the Item Production Text to the new Item.

Solution: 127450
SITUATION IDENTIFIED IN:
"Print Aging Analysis by Invoice-from Business Partner" (tfacp2420m000)
SITUATION DESCRIPTION:
In the session "Print Aging Analysis by Invoice-from Business Partner" (tfacp2420m000), the Business Partner name was
missing on all the reports.
SOLUTION DESCRIPTION:
The Business Partner name has been included in all the reports of the session "Print Aging Analysis by Invoice-from
Business Partner".

Solution: 127452
SITUATION IDENTIFIED IN:
"Posting Data by Bank/Payment Method" (tfcmg0146s000)
SITUATION DESCRIPTION:
Ledger account field is enabled if the account type is a Control account.
SOLUTION DESCRIPTION:
Ledger account field is disabled if the account type is a Control account and it is only enabled when the Account type is
"Input".

Solution: 127461
SITUATION IDENTIFIED IN:
"Item by Finance Company Details" (whinal132m00l)
SITUATION DESCRIPTION:
A)
1. Session "Market Price by Finance Company, Item" (whinal133m00l) is opened by means of the specific menu option of
the session "Item by Finance Company Details" (whinal132m00l).
2. The 'Year' is not properly displayed for the selected item, in the newly opened session.
B)
While zooming from the Item field of the session "Perform Inventory Valuation by LCM method" (whinal230m00l), system
pops up the session "Item Warehousing Data" (whwmd4500m000). Instead it should show the session "Item by Finance
Company Details" (whinal132m00l).
SOLUTION DESCRIPTION:
A)
The correct Year for the corresponding item is displayed in the session "Market Price by Finance Company, Item"
(whinal133m00l)
B)
The zoom now leads to the session "Item by Finance Company Details" (whinal132m00l).

Solution: 127470
SITUATION IDENTIFIED IN:
"Print Reminder Diary" (tfacr3430m000)
SITUATION DESCRIPTION:
Invoices fully settled with receipt steps "Document accepted by customer" or "Document sent to bank" are showing Zero
balance.
SOLUTION DESCRIPTION:
Invoices fully settled with receipt steps "Document accepted by customer" or "Document sent to bank" are not printed in
Reminder Diary.

Solution: 127489
SITUATION IDENTIFIED IN:
"Correct COGS Integrations" (cicor0111m000)
SITUATION DESCRIPTION:
When split deliveries are present the system removes the COGS for those lines, which are not selected within the given range
of invoice date.
SOLUTION DESCRIPTION:
Now the user can specify the range for posting date ("Transaction Entry Date") also. And COGS will be deleted within this
range only.
The reason for having a different range for "Transaction entry Date" is because of the fact that users can compose invoices
in one date and post them in another date.

Solution: 127492
SITUATION IDENTIFIED IN:
"Assignments on Advance / Unallocated Receipts" (tfacr2530m000)
SITUATION DESCRIPTION:
When the session "Assignments on Advance / Unallocated Receipts (tfacr2530s000)" is zoomed to, through the session
"Advance / Unallocated Details (tfacr2529s000)", the session comes up blank & no details are displayed.
The same session shows right details when zoomed from "Receipt Details (tfacr2524s000)".
SOLUTION DESCRIPTION:
Because of technical reasons the problem of the session coming up blank cannot be solved & hence details cannot be seen
through the session "Advance / Unallocated Details (tfacr2529s000)"
To view the details of Assignments made, the session "Assignments on Advance / Unallocated Receipts (tfacr2530s000)"
may be zoomed from "Receipt Details (tfacr2524s000)".

Solution: 127503
SITUATION IDENTIFIED IN:
"whinh3520m000" (Receipts)
SITUATION DESCRIPTION:
In case of an Intra Warehouse Item Transfer, which is created via a planned distribution order via Enterprise Planning, the
goods are received on a location of type 'receiving'. Since the inbound procedure cannot be executed for these kinds of
orders the inventory is stuck on the receiving location and can't be moved.
SOLUTION
DESCRIPTION:
In case of an Intra Warehouse Item Transfer, which is created via a planned distribution order via Enterprise Planning, the
receipt step is made mandatory. This is only applicable when both the 'to' item as well as the receiving warehouse are location
controlled. In this scenario now the user can define the receipt location on the receipt line. This location should be of type
'pick'/'bulk'. After confirming the receipt the rest of the inbound process will be performed automatically and the inventory
will be stored on the chosen 'pick'/'bulk' location.
The same functionality was already applicable in case of an item transfer (both transfer as well as transfer manual orders) to
a lot controlled item. In this scenario the maintain receipt step was already mandatory. This to be able to define the lot code
upon receipt.

Solution: 127507
SITUATION IDENTIFIED IN:
"Post Cash Management" (tfcmgl202m00l)
SITUATION DESCRIPTION:
Unallocated payment balance amount was not updated correctly when you delete the assignment records from the post cash
management session.
SOLUTION DESCRIPTION:
Unallocated payment header record balance is updating correctly when you delete the assignment records from the post
cash management session.

Solution: 127525
SITUATION IDENTIFIED IN:
"Print Goods Received Note" (whinh3412m000)
SITUATION DESCRIPTION:
Receipt of cost/service item gets stuck if order step "Print Goods Received Note" and parameter for inventory handling is set
to not printing cost/service items.
SOLUTION DESCRIPTION:
When inserting new inbound record for cost or service item and mandatory order step is 'print goods receipt note' and
parameter for inventory handling states this kind of item won't be printed then automatically next activity 'receipts' is
inserted and procedure mask also updated.

Solution: 127533
SITUATION IDENTIFIED IN:
"Correct COGS Integrations" (cicor0111m000)
SITUATION DESCRIPTION:
Checks should be present to prevent the user from accidentally entering dates belonging to 'closed' periods.
SOLUTION DESCRIPTION:
Some more additional checks built in the program.
1. If 'from' dates in the form are left blank, then an error message is displayed.
2. If within the range of dates, any of the period is not open, then also an error message is displayed.

Solution: 127556
SITUATION IDENTIFIED IN:
"Material costs" (tpppc2110s000)
SITUATION DESCRIPTION:
The actual costs and reversal of hard commitment are not being posted into the correct periods in projects. There is a
difference in periods in finance and periods in projects.
SOLUTION DESCRIPTION:
Now directly from finance tables the periods are obtained instead of calculating the periods from registration date.

Solution: 127590
SITUATION IDENTIFIED IN:
"Maintain Document Number Anticipated Payments" (tfcmg2114s000)
SITUATION DESCRIPTION:
When document series is 'zero', it is not possible to maintain posting data for the second line of the second document of
transaction types "Unallocated/Advance Receipts/Payments"
SOLUTION DESCRIPTION:
Earlier, for document series 'zero', Wrong Message - It is not possible to post an amount greater than the 'remaining
amount' - was given when trying to maintain posting data for the second line of the second document for the transaction
types "Unallocated/Advance Receipts/Payments"
Now, it is possible to maintain more than one line for any document series

Solution: 127601
SITUATION IDENTIFIED IN:
"Compose/Print/post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When Vat code is linked to the transaction type, then an error message is displayed when the user tries to enter a Vat code
of type "Not Applicable" in the Manual sales line.
But this needs to be checked only during Composing, as the Transaction Type used for the invoice was determined here
only.
SOLUTION DESCRIPTION:
Now the check is shifted to the Composing stage.

Solution: 127606
SITUATION IDENTIFIED IN:
"Select Invoices for Payment" (tfcmg1220m000)
SITUATION DESCRIPTION:
Financial department was not set to the settled invoices in the process of "Select invoices for payments (tfcmg1220m000)"
and select invoices for Direct debits (tfcmg4220m000) for payment batch and direct debit batch.
SOLUTION DESCRIPTION:
Now financial department is set to the settled invoices in the process of "Select invoices for payments (tfcmg1220m000)"
and "select invoices for direct debits (tfcmg4220m000)" for payment batch and direct debit batch.

Solution: 127610
SITUATION IDENTIFIED IN:
"Generate Invoices by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
The following situation were identified.
1. The check on batch balnce was done for each invoice created by this process. This caused performance problem due to
multiple reading of the same documents in the Nonfinalized transaction table (tfgld102 )
2. The error message when the ledger account was not maintained for the accrual account in teh Mapping scheme was
misleading in B50_b versions. The error message used to be "Ledger Account for the Expense Tax from the integration
mapp", whereas it should be " The ledger account for %s( Receipt / Direct delivery ) cannot be found in the integration
mapping scheme."
3. It was only possible to display error messages of upto 60 characters by the error report.
SOLUTION DESCRIPTION:
1. Now the batch balance, and the resetting of transaction type status are checked only when the transactions are written onto
the database.
2. The error message has been corrected to display the actual error.
3. The length of the error messages displayed on the error report has been increased ( to 136 characters , atleast ).

Solution: 127613
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When entered from the session 'Assign unallocated /advance receipts to invoices (tfcmg2130s000)', document date is not
saved properly.
SOLUTION DESCRIPTION:
Earlier, wrong Document date was saved in the tables.
Now, Document date is saved properly in the tables.

Solution: 127627
SITUATION IDENTIFIED IN:
"Maintain and Confirm Back Orders" (tdsls4125m000)
SITUATION DESCRIPTION:
A)
1. A sales direct delivery order line is maintained and purchase order is generated.
2. This purchase order is received partially. Purchase order is then processed.
3. Sales and Purchase backorder are created. The sales backorder is removed.
4. When this backorder is confirmed again, backorder is not created.
B)
1. There is cost item with the 'Release to Warehousing' option selected in the "Item Purchase Data" (tdipu0101s000).
2. This item is entered in the purchase order line and also a TP project is also entered along with Warehouse.
3. Then, there are many partial receipts are made in "Receipts" (whinh3520m000).
4. The creation and reversal of soft commitment and hard commitments in Projects is not consistent.
SOLUTION DESCRIPTION:
A)
It is possible to re-confirm the back order of a direct deliver sales order. At this time, the back order of the corresponding
purchase order is also created.
B) When the partial receipt s are made for a Cost item for a TP project in Warehousing, the creation and the reversal of the
soft and hard commitments are created correctly in Projects.

Solution: 127629
SITUATION IDENTIFIED IN:
"Purchase Invoice Corrections" (tfacp2110s000)
SITUATION DESCRIPTION:
Using session "Purchase Invoice Corrections" (tfacp2110s000), it is not possible to correct multiple tax lines for an invoice
with level of tax calculation as "Invoice Header".
SOLUTION DESCRIPTION:
It is now possible to make correction to multiple tax lines for an invoice with level of tax calculation as "Invoice Header".

Solution: 127631
SITUATION IDENTIFIED IN:
"Display Ledger History - Dim Type Wise Distribution" (tfgld3507m000)
SITUATION DESCRIPTION:
Dimension description was displaying incorrectly, if you have same dimension codes for different dimension types.
SOLUTION DESCRIPTION:
Dimension description is displaying correctly even when you have same dimension codes for different dimension types.

Solution: 127653
SITUATION IDENTIFIED IN:
"Integration Mapping Scheme (Manufacturing/Distribution)" (tfgld4101s000)
SITUATION DESCRIPTION:
The user was allowed to save complementary ledger account in the integration-mapping scheme
SOLUTION DESCRIPTION:
Now the system is not allowing the user to save complementary ledger account in the integration-mapping scheme

Solution: 127657
SITUATION IDENTIFIED IN:
"Print Aging Analysis by Invoice to Business partner" (tfacr2420m000)
SITUATION DESCRIPTION:
If you print the aging analysis report with the option based on 'due date' , Report is giving the error message "No data with in
selection" even though there is a valid data.
SOLUTION DESCRIPTION:
Report selects and puts the balance amount in right aging buckets as per the due date of the receipt schedule.

Solution: 127659
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When an unallocated receipt is linked to another unallocated receipt, it is not possible to reverse the assignment.
SOLUTION DESCRIPTION:
Earlier, when an unallocated receipt is linked to another unallocated receipt, it is not possible to reverse the assignment.
Now, it is possible to reverse the assignment made to the unallocated receipt.
SOLUTION 124880 ONLY
*********
VERSION(S):
B50_b, B50_c

Solution: 127667
SITUATION IDENTIFIED IN:
"Audit payments" (tfcmg1220m000)
SITUATION DESCRIPTION:
The system does not check the control accounts for posting data of anticipated document steps at the Audit level if the
Ledger accounts are not defined in the financial business partner group.
SOLUTION DESCRIPTION:
Now system checks the control accounts for posting data of anticipated document steps at the Audit level if the Ledger
accounts are not defined in the financial business partner group.

Solution: 127680
SITUATION IDENTIFIED IN:
"Archive/Purge Finance Transactions" (tfgld6205m000)
SITUATION DESCRIPTION:
Fatal error "Snap shot too old" occurred while archiving the finance transactions.
SOLUTION DESCRIPTION:
Now the error does not occur

Solution: 127683
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
When localization parameter "Not Zero Invoicing" is ON, the user gets an error while finalizing a batch consisting of a zero
invoice whose transaction type has an update mode as 'finalization'.
SOLUTION DESCRIPTION:
Now the batch could be finalized correctly.

Solution: 127694
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4120s000)
SITUATION DESCRIPTION:
When changing the Payment/Receipt method with the option "Planned Payment Date = Due Date" is checked "ON" to a
Payment method with the option "Planned Payment Date = Due Date" is checked "OFF", the Planned Debit Date remains the
Due date of the Previous payment method and not the date on which the Direct Debit Advice is created.
SOLUTION DESCRIPTION:
When changing the Payment/Receipt method with the option "Planned Payment Date = Due
Date" is checked "ON" to a Payment method with the option "Planned Payment Date =
Due Date" is checked "OFF", the Planned Debit Date won't remain the Due
date of the Previous payment method and now the date on which the Direct Debit Advice is created will be filled correctly.
SOLUTION 127815 TOGETHER WITH THIS
SOLUTION
*******************************************************************************************************
****************************************
VERSION(S):
B50_b, B50_c

Solution: 127705
SITUATION IDENTIFIED IN:
"Inventory by Warehouse and Item" (whwmd2515m000)
SITUATION DESCRIPTION:
When a completion for an order is over-reported and the over-reported quantity is returned back to the shopfloor, the
"On Order" value in the session "Inventory by Warehouse and Item" (whwmd2515m000) and the "Planned Inventory
Transactions by Order"(whinp1501m000) becomes incorrect.
SOLUTION
DESCRIPTION:
The "Planned Inventory Transactions by Order"(whinp1501m000) and "Inventory by Warehouse and Item" (whwmd2515m000)
are updated correctly when a completion for an order is over-reported and the over-reported quantity is backed out.

Solution: 127724
SITUATION IDENTIFIED IN:
"Audit Payments" (tfcmg1220m000)
SITUATION DESCRIPTION:
A fatal error was displayed in Notification process when both the sales and purchase invoices were composed in one
payment batch by selecting the payment method with option "Posting Scheme by financial BP" is yes.
SOLUTION DESCRIPTION:
Now an audit error will be printed on Audit report when both the sales and purchase invoices are composed in one payment
batch by selecting the payment method with option "Posting Scheme by financial BP" is yes.

Solution: 127725
SITUATION IDENTIFIED IN:
"Print Actual Cost Price by Item/Print Actual Cost Price by Project" (tipcs3452m000/tipcs3462m000)
SITUATION DESCRIPTION:
The subcontractor name is not printed in the 'Subcontracting Costs" of the report generated, when the sessions "Print
Actual Cost Price by Item" (tipcs3452m000) and "Print Actual Cost Price by Project" (tipcs3462m000) are started.
SOLUTION DESCRIPTION:
System prints the subcontractor name in the 'Subcontracting Costs" of the report generated, when the sessions "Print Actual
Cost Price by Item" (tipcs3452m000) and "Print Actual Cost Price by Project" (tipcs3462m000) are started.

Solution: 127736
SITUATION IDENTIFIED IN:
"Selection For Automatic Reconciliation" (tfcmg2123s000)
SITUATION DESCRIPTION:
Receipt status of the Invoice schedule lines changed to "Open" from "Selected, when its corresponding anticipated receipt is
not selected for Automatic reconciliation, as it does not fall within the selected Planned payment date range.
SOLUTION DESCRIPTION:
Now the Receipt status does not get changed when it is not selected in the given Planned payment date range.

Solution: 127741
SITUATION IDENTIFIED IN:
"Journal Vouchers" (tfgld1103m000)
SITUATION DESCRIPTION:
1. While entering dimensions for a ledger account in "Journal Vouchers" (tfgld1103m000) the dimension description is only
displayed in a flash and disappears from the form.
2. On the header tab user is not able to override document date.
3. Reporting year is user accessible
SOLUTION DESCRIPTION:
1. The description of a latest entered dimension is displayed correctly.
2. User is able to override the document date.
3. Reporting year is not user accessible

Solution: 127742
SITUATION IDENTIFIED IN:
"Selection for Automatic Reconciliation" (tfcmg2123s000)
SITUATION DESCRIPTION:
Wrong total amount is been displayed in the session "Selection for Automatic reconciliation's" Form.
SOLUTION DESCRIPTION:
This problem is solved now and the Correct Total amount will be displayed in the session "Selection for Automatic
reconciliation's" Form.

Solution: 127743
SITUATION IDENTIFIED IN:
"Print Cost Price Calculation by Item" (ticpr2410m000)
SITUATION DESCRIPTION:
When running the session "Print Cost Price Calculation by Item" (ticpr2410m000) more than once, without leaving the
session, the printed report gives wrong values.
SOLUTION DESCRIPTION:
The results of the report will be same for an item, even when it is run more than once without leaving the session.

Solution: 127763
SITUATION IDENTIFIED IN:
"Post Integration transactions to Finance" (tfgld4201m000)
SITUATION DESCRIPTION:
Session tfgld4201m000 "Post integration transactions to Finance" was creating finance transactions with different fiscal and
reporting year in case when transaction date is fall in last reporting and fiscal periods and one of these periods is closed.
SOLUTION DESCRIPTION:
Now when reporting and fiscal years are different program will create an error message tfglds2099 "Fiscal and reporting years
are inconsistent, please check session tfgld0107m000 "Period status" in the "Error log". User will have to close or open both
reporting and fiscal periods.

Solution: 127765
SITUATION IDENTIFIED IN:
"Print Specifications Delivered, Not yet Invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
In Job, Current year and period values are not taken, instead the values saved during creation of the job are picked.
SOLUTION DESCRIPTION:
Current year and period values are picked when the session is used in the Job.

Solution: 127774
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
Linking a credit note to a sales invoice by filling in the "original invoice" field when creating the credit note causes the
credit note to appear on the "Print Control Account Checklist" by the amount of the currency difference.
The credit note also appears on the aging report as having a balance when it does not.
SOLUTION DESCRIPTION:
Credit note is not displayed in the "Print Control Account Check list" and "Aging Report".

Solution: 127788
SITUATION IDENTIFIED IN:
"Purchase Order Receipts" (tdpur4101s3000)
SITUATION DESCRIPTION:
The Back Order quantity is enabled even after the back order is confirmed.
SOLUTION DESCRIPTION:
Once the back order is confirmed, the Back Order quantity fields would be disabled.

Solution: 127795
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
When running Calculate Cost and Valuation Prices (ticpr2210m000) and Actualize Cost and Valuation Prices (ticpr2220m000),
the system created more than 32000 sequence numbers for the items that were included in the update. This caused the process
to fail since the domain for tfgld.sern is defined as an integer, and limited to a range of 0 to 32000.
SOLUTION
DESCRIPTION:
Actualizing is now done per 400
items. Then a new
revaluation order and new
transaction date/time is
set. This prevents
the seq. nr for
overflow.

Solution: 127801
SITUATION IDENTIFIED IN:
"Transfer payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
For the "DTA" bank file used in Switzerland the IBAN numbers were not used. Only the bank account was taken.
SOLUTION DESCRIPTION:
The IBAN is implemented for the "DTA" bank file. In session "Payment/Receipt Method" (tfcmg0140m000) IBAN must be
activated. When that is done, IBAN numbers will be put in the "DTA" bank file.

Solution: 127804
SITUATION IDENTIFIED IN:
"Manual Sales Invoice Lines" (cisli2125s000)
SITUATION DESCRIPTION:
When creating
- Sales Orders (tdsls4500m000)
- Manual Sales Invoice Lines (cisli2525m000)
- Purchase Orders (tdpur4500m000)
- Sales Invoices (tfacr1110s000)
the Tax Exceptions (if any) are not always retrieved correctly, mainly due to incorrect or not enough information send from
the packages (ci, td or tf) to the Generic Tax determination procedure.
SOLUTION DESCRIPTION:
When creating
- Sales Orders (tdsls4500m000)
- Manual Sales Invoice Lines (cisli2525m000)
- Purchase Orders (tdpur4500m000)
- Sales Invoices (tfacr1110s000)
the Tax Exceptions (if any) are retrieved correctly. However, not in every situation the "Tax Exceptions" Logic is
applicable.
Example; when goods and invoice are both flowing from Spain to Portugal (both EU members), the Tax Exceptions routine
will not be used as it is part of the "Destination Sales Tax Logic" and not a part of the "EU Tax Handling".
Three functional situations could apply;
1) Your country has nothing to do with EU Tax Laws
2) Your country has to do with EU Tax Laws.
3) Your country has to do with EU Tax Laws, but because EU Tax is not applicable or when the Tax rules are Domestic,
the Destination Sales Tax Logic (and consequently the Tax Exceptions Logic) may apply, depending on the setting of the
parameter "Destination Sales Tax Applicable" in session tccom0000m000 (COM Parameters).
Summarized; Entering a "Tax Exception" in tcmcs1138m000 (Exceptions for Taxes) does not mean that always this Tax
Exception Code will be used. Please refer to the specific laws of your country to see whether Tax Exceptions are applicable
for your specific situation or not.

Solution: 127820
SITUATION IDENTIFIED IN:
"Calculate cost and valuation prices" (ticpr2210m000)
SITUATION DESCRIPTION:
An error report with message "Quantity of component is zero in the Bill of Materials of item" is printed, even though the
calculated net quantity of the component is not zero.
SOLUTION DESCRIPTION:
If the calculated net quantity of BOM component is not zero, then no error report will be printed for that item.

Solution: 127823
SITUATION IDENTIFIED IN:
"Print Receivable Invoices Checklist" (tfacp1438m000)
SITUATION DESCRIPTION:
Receipts (not for BAAN Project) for purchase orders are in finance posted with the internal rate type and with the rates of
each individual receipt. The session tfacp1438m000 does not take this into account. In this session every receipt and approval
is valuated with the rate information of the purchase order header. Because of this when there are only receipts for a certain
purchase orderline this session shows a difference between the financial and logistical values. This difference is not for real,
as the logistical values are wrongly calculated.
SOLUTION
DESCRIPTION:
Now the receipts do take the reality into account that receipts are calculated with the internal rate type and the rates of each
individual receipt.

Solution: 127836
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
While approving purchase invoices from session "Purchase Invoices" (tfacp1110s000), where the document date is different
from today's date, the approval transactions are created with document date set to today's date.
SOLUTION DESCRIPTION:
The approval document date is updated correctly with the document date of the invoice, when the purchase invoice is
approved from the session "Purchase Invoices".

Solution: 127848
SITUATION IDENTIFIED IN:
"Anticipated Payments (details)" (tfcmg2116s000)
SITUATION DESCRIPTION:
Anticipated unallocated payment record is updated with incorrect values and this leads to differences in control account
checklist after reconciliation.
SOLUTION DESCRIPTION:
Anticipated unallocated payment record updated with correct amounts and now there is no difference in control account
checklist after reconciliation.

Solution: 127882
SITUATION IDENTIFIED IN:
"Copy Purchase Orders" (tdpur4201s000)
SITUATION DESCRIPTION:
-1- It is not possible to copy any order in to a return order type.
-2- When the copy to order type is changed to non return order from a return order, the buy from BP field is not enabled.
SOLUTION DESCRIPTION:
-1- When the order type coped to is a Return Order, the user is prompted to enter the return reason code and the session for
the Return Reason pops up and the user can select the Return Reason from it.
-2- When the order type copied to is changed from a return order type to a non-return order type, the Buy-from BP is
enabled.

Solution: 127889
SITUATION IDENTIFIED IN:
"Audit Payments" (tfcmg1255s000)
SITUATION DESCRIPTION:
Two Problems are solved:
1. When 2 sub-contracting invoices are paid, then bank account of the first supplier's invoice is used for the second
supplier's invoice
2. When 'Bank Account Required' is set to 'yes' in Payment Method and the Supplier's Bank is empty in the Payment Advice,
no audit error is shown for the sub-contracting invoice
SOLUTION DESCRIPTION:
Earlier,
1. Wrong Bank Account is used while paying the second sub-contracting invoice
2. Even when supplier's bank is not filled in the payment advice, sub-contracting invoice can be paid
Now,
1. Correct Bank Account is used while paying any number of sub-contracting invoices
2. Audit error 'Bank of Business Partner not filled' is given and the invoice cannot be paid

Solution: 127892
SITUATION IDENTIFIED IN:
"Reconciliation of anticipated payments/receipts" (tfcmg2102)
SITUATION DESCRIPTION:
The anticipated receipt was not found to reselect for reconciliation if already reconciled document was opened.
SOLUTION DESCRIPTION:
Now, the anticipated receipt is found to reselect for reconciliation if already reconciled document is opened.

Solution: 127894
SITUATION IDENTIFIED IN:
"Post/Print Financial Transactions" (ticstdll0015)
SITUATION DESCRIPTION:
Zero-orders from Shopfloor should not result in inventory-variances.
SOLUTION DESCRIPTION:
No inventory-variance is created if the quantity-completed on the order is zero.

Solution: 127909
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance" (tfgld4201m000)
SITUATION DESCRIPTION:
When posting multiple period transactions like "Sales Invoicing (Service)- Revenue Service Contract", a fatal error occurs.
And moreover this happens only if the Integration Parameter "Compression" is defined as
"Compr. by Trans. Origin" and "Handling of Document numbers" is defined as "Document Number by Date"
SOLUTION DESCRIPTION:
Now the fatal error does not arise while posting the integration transactions.

Solution: 127932
SITUATION IDENTIFIED IN:
"Generate Invoices by Self Billing" (tfacp2290m000)
SITUATION DESCRIPTION:
Bath cannot be finalized due to the status was set as "in use".
SOLUTION DESCRIPTION:
Now, Batch status is set correctly and Batch can be finalized.

Solution: 127934
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
When printing Project WIP by order, the financial transaction "Warehousing (transfer) / Issue to Project" is not considered
for the report, thus prints wrong WIP.
SOLUTION DESCRIPTION:
When project WIP is printed by order, the financial transaction "Warehousing (transfer) / Issue to Project" will be
considered.

Solution: 127949
SITUATION IDENTIFIED IN:
""Print Invoice-to Business Partner Balance Report" " (tfacr2424m000)
SITUATION DESCRIPTION:
In Print Business Partner's Balance (tfacr2424m000) the column "Advance/Unallocated Receipts" is wrongly updated.
SOLUTION DESCRIPTION:
In Print Business Partner's Balance (tfacr2424m000) the column "Advance/Unallocated Receipts" is correctly updated.

Solution: 127957
SITUATION IDENTIFIED IN:
"Bank Transaction" (tfcmg2100s000)
SITUATION DESCRIPTION:
Not able to reverse the reconciliation of an Advance/Unallocated receipt when different transaction types are used in the
same batch.
SOLUTION DESCRIPTION:
Now the Reconciliation can be reversed.

Solution: 127968
SITUATION IDENTIFIED IN:
"Print Aging Analysis for customer" (tfacr2420m000)
SITUATION DESCRIPTION:
Some Receipts are not shown in aging analysis.
SOLUTION DESCRIPTION:
All valid Receipts are shown in aging analysis.

Solution: 127975
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Wrong balance in report "Invoice-to Business Partner Balances"
SOLUTION DESCRIPTION:
The reported problem is solved now and the report " Invoice-to Business Partner Balances" is printed correctly.

Solution: 128003
SITUATION IDENTIFIED IN:
"Print Purchase Orders" (tdpur4401m000)
SITUATION DESCRIPTION:
When we create a back order and print the back order , an EDI message is created for the original order along with the back
order
SOLUTION DESCRIPTION:
Now the EDI message is created for the original line with sequence 0 only once and when we print the back order , EDI
message for back order was only created

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

Solution: 128019
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
When Journal transactions involving bank or unallocated receipts transactions between two companies are posted, they are
posted to wrong Contra account
SOLUTION DESCRIPTION:
Now correct contra account is picked up

Solution: 128026
SITUATION IDENTIFIED IN:
"Posting Data of Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
Amount field in session 'Posting Data of Electronic Bank Statements' (tfcmg5106s000) is disabled at first entry of posting
data although user should be able to maintain this field when creating posting data.
SOLUTION DESCRIPTION:
Amount field can be accessed at first entry of posting data.

Solution: 128036
SITUATION IDENTIFIED IN:
"Transaction Sales Invoices" (tfacr1111s000)
SITUATION DESCRIPTION:
When the "Level of Tax calculation" is set on the Transaction line, the default vat code is not displayed
SOLUTION DESCRIPTION:
Now the default vat code is picked up and displayed.

Solution: 128039
SITUATION IDENTIFIED IN:
"Print Reminder Letters" (tfacr3420m000)
SITUATION DESCRIPTION:
No Reminder letter number is printed for Negative unallocated receipts and Negative advance receipts
SOLUTION DESCRIPTION:
Reminder Letter is printed for Negative unallocated receipts and Negative advance receipts

Solution: 128047
SITUATION IDENTIFIED IN:
"Maintain Posting Data for Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
When the changed amount is more than the defaulted amount, no warning message is given.
SOLUTION DESCRIPTION:
Earlier, no warning message was given.
Now, a warning message is given if the changed amount is more than the defaulted amount

Solution: 128049
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
1. A Sales return order is created.
2. The order quantity of the sales order is equal to the negative inventory present for the item in that warehouse.
3. Also the Warehouse Order type attached to the Sales Return order has "Approvals" (whinh3522m000) as an activity.
4. The Sales order is received in the warehouse and the Delivered quantity and the status of the Sales Order Line are not
updated due to this receipt.
SOLUTION DESCRIPTION:
Generally the Delivered quantity of the Sales order line would be updated at the time the Approval is done. In this case all
the received quantity has been consumed by the Negative Inventory that was already present. In this case no Inspection
record was created and hence the status of the Sales Order Line was not also updated. In such cases where the received
quantity is consumed by negative inventory, the delivery quantity and the status of the Sales Order Line is updated at the
time of Receipts confirmation.

Solution: 128065
SITUATION IDENTIFIED IN:
"Currency Rates" (tcmcs0108m000)
SITUATION DESCRIPTION:
In a Multi Site setup when table tcmcs008 (Currency Rates) is shared a problem may arise when the End User is trying to insert
new currency rates with an effective date before the last Cost Price calculation date.. This is due to the fact that the general
item data tables (tcibd001/tcibd007) are not shared over the same set of companies.
SOLUTION
DESCRIPTION:
From now onwards, the check for the last performed Cost
Price Calculation will not only check Item Costing Data (tcibd007) in
the current company, but also the other logistical companies in which tcmcs008 (Currency Rates) is shared.

Solution: 128095
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Receipts to Invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
The Balance amount is being calculated incorrectly once the user assigns Unallocated Receipt to an Invoice.
SOLUTION DESCRIPTION:
Now the user can assign an invoice to an Unallocated Receipt and the balance amount is being calculated perfectly

Solution: 128099
SITUATION IDENTIFIED IN:
"Assign unallocated / Advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
The control account checklist showed a difference when an unallocated receipt in home currency was linked to an invoice
with reference currency
SOLUTION DESCRIPTION:
No difference on the control account checklist when an unallocated receipt in home currency is linked to an invoice with
reference currency

Solution: 128107
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
When the amount in the sales credit note is modified, Wrong message "Credit note amount should not be greater than the
Original Invoice Amount" even though it is less than the original invoice amount
SOLUTION DESCRIPTION:
Now the message is not displayed if the Credit note amount is less than Original invoice amount

Solution: 128109
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
Receipt schedules gets deleted when the user changes the due date for the invoice
SOLUTION DESCRIPTION:
Now the schedules are not deleted when the due date of the invoice is modified

Solution: 128132
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
The system takes very long time to confirm the shipments.
SOLUTION DESCRIPTION:
The performance has been improved now and the time taken for the shipment confirmation is reduced now.

Solution: 128140
SITUATION IDENTIFIED IN:
"Selection for Automatic Reconciliation " (tfcmg2123s000)
SITUATION DESCRIPTION:
Auto Payment Reconciliation form gets the wrong total amount.
SOLUTION DESCRIPTION:
Now the Total Amount will be displayed correctly when saving the form and usage of the "Refresh (F5)" option is
recommended once after the "Saving" operation is carried out in the form.

Solution: 128167
SITUATION IDENTIFIED IN:
"Generate Inventory Commitments" (whinp2200m000)
SITUATION DESCRIPTION:
After generating an outbound advice , if we generate inventory commitment for a service order , duplicate commitments are
generated
SOLUTION DESCRIPTION:
Now the system checks for the existing outbound order line in warehousing and finds the related line with correct sequence
number and doesn't generate duplicate commitments

Solution: 128193
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
Document number was not printed on the posted EBS bank Statement Report after posting the EBS batch.
SOLUTION DESCRIPTION:
Now Document number is printed on the posted EBS bank Statement Report after posting the EBS batch.
SOLUTION 128528 AFTER THIS SOLUTION
=================================================
VERSION(S):
B40_c, B50_b, B50_c

Solution: 128197
SITUATION IDENTIFIED IN:
"Transactions" (tfgld1101m000)
SITUATION DESCRIPTION:
When transactions are maintained (Batch and transaction keys and the transaction lines) in financial company, it allows
deleting the transaction type, even though there are transactions present, when a Non-Finalized transactions (tfgld102) is
not shared between the Group Company and the financial company.
SOLUTION
DESCRIPTION:
When transactions are maintained (Batch and transaction keys and the transaction lines) in
financial company and if one of the transaction keys is deleted, then the system pops
up a error message, "Transactions present; first delete all transactions",
when a Non-Finalized transactions (tfgld102) is not shared between the Group company and the financial company.

Solution: 128213
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
It is possible to use a General Ledger account for which Integration Indicator is set to PCS Cost / Sales for Cost Item. This
should not be possible, as this will pose problems while posting the Integration Transactions. An Error Log "GL account is
set to PCS project cost' will be logged.
SOLUTION DESCRIPTION:
Now it is not possible to add a General Ledger Account for which Integration Indicator is set to PCS Cost / Sales for Cost
Item.
An Error Message "Ledger
account may not have
projects" is displayed and it is not possible to
enter such General Ledger Account.

Solution: 128224
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Status updated as "Paid" in Receipt Schedule after the document is "Partially paid" with Discount
SOLUTION DESCRIPTION:
The reported problem is solved now and the Status will get updated correctly as "Partially Paid" in Receipt Schedule after
the document is "Partially paid" with Discount and not with the status "Paid".

Solution: 128229
SITUATION IDENTIFIED IN:
"Report Operations Completed" (tisfc0130s000)
SITUATION DESCRIPTION:
When a reversal is made to an order to correct an over-reported quantity using session "Report operations
completed"(tisfc0130s000), the 'On Order' value becomes negative/incorrect in the session "Inventory by Warehouse and
Item" (whwmd2515m000).
SOLUTION DESCRIPTION:
The 'On Order' quantity of an item will never be a negative value at any point of time.

Solution: 128253
SITUATION IDENTIFIED IN:
"Payment Advice" (tfcmg1501m000)
SITUATION DESCRIPTION:
Problem of displaying document number and sequence number on the form. It was displaying sequence number next to the
document number instead of schedule line number.
SOLUTION DESCRIPTION:
Now the schedule line number is displayed next to the document number.

Solution: 128254
SITUATION IDENTIFIED IN:
"Display Payment Details" (tfacp2524s000)
SITUATION DESCRIPTION:
Session "Display Payment Details" (tfacp2524s000) is displaying a wrong value of check number, and is inconsistent with
the display of check number in session "Display Payments on Purchase Invoices" (tfacp2523s000) which is displaying a
correct value.
SOLUTION DESCRIPTION:
The session "Display Payment Details" displays correct value of check number and is consistent with the session "Display
Payments on Purchase Invoices".

Solution: 128258
SITUATION IDENTIFIED IN:
"Journal Voucher" (tfgld1103s000)
SITUATION DESCRIPTION:
1) Local currency rate was not picked up at the JV header transaction and due to this user can't add the records.
2) When you add the second line in the JV transaction lines, dimension description was not refreshed.
SOLUTION DESCRIPTION:
1) Local currency rate picked up correctly and user can add the records.
2) Dimension description was refreshed properly when you add the new line in Journal voucher.

Solution: 128285
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When running "Register Purchase Invoices (tfacp1110s000)"
The system allows user to save duplicate "Business Partner Invoice number".
SOLUTION DESCRIPTION:
When running "Register Purchase Invoices (tfacp1110s000)"
The system does not allow user to save duplicate "Business Partner Invoice number" anymore.

Solution: 128298
SITUATION IDENTIFIED IN:
"Copy Purchase Orders" (tdpur4201s000)
SITUATION DESCRIPTION:
1. There is a Purchase Order Line with back orders.
2. This Order is copied to a new order with the 'Cumulate Receipts' check box selected. The Detail line and the Back order
line are selected.
3. The Order Quantity of the newly copied line adds the order quantity of the Detail line and the Back order line.
SOLUTION DESCRIPTION:
The Quantity of the copies line is correct now.

Solution: 128303
SITUATION IDENTIFIED IN:
"Maintain Posting Data of Approved Invoices" (tfacp1141s000)
SITUATION DESCRIPTION:
When approving the average last purchase price is updated using the rate applicable at the date of approving. This is wrong
because the date of the invoice should be used.
SOLUTION DESCRIPTION:
When approving the date of the invoice is used determining the rate used for updating that average last purchase price.

Solution: 128314
SITUATION IDENTIFIED IN:
"Select Invoices for Direct Debits" (tfcmg4220m000)
SITUATION DESCRIPTION:
The System doesn't consider changes in the Customer Bank for the Receipt Schedule.
SOLUTION DESCRIPTION:
The problem is solved and now the System will consider changes in the Customer Bank for the Receipt Schedule.

Solution: 128369
SITUATION IDENTIFIED IN:
"Payment Advice" (tfcmg1120s000)
SITUATION DESCRIPTION:
Modified amount to be paid was not saved.
SOLUTION DESCRIPTION:
User able to save modified amount to be paid.

Solution: 128373
SITUATION IDENTIFIED IN:
"Lots" (whltc1500m000)
SITUATION DESCRIPTION:
Negative material issue overwrites a lot price of zero in the session Lots with standard cost.
SOLUTION DESCRIPTION:
Now the Lot price is not over written with the standard cost price when the Lot is received with zero prices.

Solution: 128380
SITUATION IDENTIFIED IN:
"Item Purchase Data" (tdipu0101s000)
SITUATION DESCRIPTION:
Calculation of the Average Purchase Price values goes wrong when the system takes return purchase orders into account when
calculating the Average Purchase Price for an item. This is incorrect
SOLUTION DESCRIPTION:
Return Purchase Orders will not be considered when calculating the Average Purchase Price
SOLUTION 128608 AFTER DOWNLOADING THIS SOLUTION. (128380)
VERSION(S):
B50_b, B50_c

Solution: 128386
SITUATION IDENTIFIED IN:
"Payment Advices" (tfcmg1120s000)
SITUATION DESCRIPTION:
Error message not given when an excess amount is entered the second time in the Payment Advice.
SOLUTION DESCRIPTION:
The reported problem is solved now and the Error message will be given even when an excess amount is entered the second
time in the Payment Advice.

Solution: 128397
SITUATION IDENTIFIED IN:
"Write of Currency Differences" (tfacr2250m000)
SITUATION DESCRIPTION:
When Currency Rate is "fixed" for invoice, currency difference is written off.
SOLUTION DESCRIPTION:
If Currency Rate is "fixed" for the invoice, then message "no data within selection" appears.

Solution: 128408
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
When the user re-enters the session for modifying and if he changes the amount, then the system gives an error message
"Terms of Payment not found". This is when the localization Parameter "Receipt schedule" is ON. If it is OFF, no error
message is displayed, but the terms of payment becomes blank.
SOLUTION
DESCRIPTION:
Now the error message does not appear.

Solution: 128414
SITUATION IDENTIFIED IN:
"Release to Warehousing (batch)" (tdpur4246m000)
SITUATION DESCRIPTION:
1. There are many lines in a purchase order.
2. All the lines of this order are copied to a new order.
3. When this new order is Released to Warehousing, all the lines are released under different warehousing order.
SOLUTION DESCRIPTION:
The problem was the Planned Delivery date of all the purchase order lines of the copied order were not the same. Now, the
Planned Delivery Date would be same for all the lines of the copied order.

Solution: 128420
SITUATION IDENTIFIED IN:
"General Actual Project Costs" (tipcs3140s000)
SITUATION DESCRIPTION:
Erroneous postings to finance for 'Project (PCS)/Costs Goods Sold (General)' combination, when the Key Definition in the
integration mapping scheme is set as 'Financial Business Partner Group' and the same business partner is attached to the
project. This is because, the 'Financial customer group PCS' will not be considered as the Key Definition 'Financial
Business Partner Group' in the finance integration mapping scheme for the above combination.
SOLUTION
DESCRIPTION:
The Financial Customer Group PCS will be considered as Financial Business Partner Group in the Integration mapping
scheme for Project (PCS)/Costs Goods Sold (General) combination.

Solution: 128426
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2500m000)
SITUATION DESCRIPTION:
Consignment replenishment sales orders are not processed automatically when returning goods from consignment (owned)
warehouse to own warehouse.
The flow stops at Receipts step, waiting for a receipt to be created manually.
SOLUTION DESCRIPTION:
This situation is corrected. Processing is done automatically if the warehouse procedure is set up that way.

Solution: 128428
SITUATION IDENTIFIED IN:
"Purchase order Receipts" (tdpur4101s300)
SITUATION DESCRIPTION:
The 'Automatic Confirmation of Back orders' is YES. In combination with multiple receipt and Approval, the 'Confirm Back
Order' button is enabled in the session "Purchase order Receipts" (tdpur4101s300). When the button is pressed, system
creates some wrong back orders.
SOLUTION
DESCRIPTION:
The 'Confirm Back Order' button is not enabled now.

Solution: 128434
SITUATION IDENTIFIED IN:
"Commitments and actual costs" (tpppc2110s000)
SITUATION DESCRIPTION:
The date in the reversed soft commitment entry is wrong when the purchase order is received.
SOLUTION DESCRIPTION:
Now the registration date for the reversed soft commitment during receipts is filled with the receipt date

Solution: 128450
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When creating a Purchase Invoice related to orders and if the Purchase Invoice and the Order has different "Terms of
Payment", then the "Terms of Payment" should default to the one defined at Purchase Order Header. But after entering the
amount, the "Terms of Payment" was changing to the one defined for Business Partner.
When a Cost Purchase Invoice is created with "Level of Tax Calculation" as Header
level, a temporary tax transaction is created in table "Tax transactions" (tfgld107). If no transactions is entered and the level of tax calculation is
changed to "Transaction Line", the tax transaction record
in the Header Level is not
deleted.
For the following Tax Localization parameters setting (Generic Taxes = "Yes,
Singular Tax = "No"), a Purchase
cost invoice is entered with tax
calculation at the header level. After
the Tax amount is filled, when
the form is changed, the amount gets
reset to
zero.
SOLUTION
DESCRIPTION:
The "Terms of Payment" on the invoice defaults to the one that is
defined at the Purchase Order Header. And it doesn't
change when the amount field is updated.
When the tax transaction changes from header to transaction line
level and there is no transactions present, the records from table tfgld107 is deleted.
The tax amount doesn't
change when the form is changed; hence it
has the correct value always.

Solution: 128462
SITUATION IDENTIFIED IN:
"Generate Inventory Commitments" (whinp2200m000)
SITUATION DESCRIPTION:
After generating an outbound advice, if we generate inventory commitment for a production order, duplicate commitments
are generated this was because of the difference in the sequence numbers between warehousing and production.
SOLUTION DESCRIPTION:
Now the system checks for the existing outbound order line in warehousing and finds the related line with correct sequence
number and doesn't generate duplicate commitments

Solution: 128465
SITUATION IDENTIFIED IN:
"Sales Corrections" (tfacr2110m000)
SITUATION DESCRIPTION:
BP Balance getting wrongly updated in tfacr2533m000 (BP totals) when Sales Invoice is corrected through tfacr2110m000
(Sales Correction).
SOLUTION DESCRIPTION:
BP Balance getting correctly updated in tfacr2533m000 (BP totals).

Solution: 128476
SITUATION IDENTIFIED IN:
Print Payment Advice (tfcmg1401m000)
SITUATION DESCRIPTION:
IBAN: Wrong Account is printed on the Report "Print Payment Advices by Pay - to Business Partner" (tfcmg140117000)
SOLUTION DESCRIPTION:
The reported problem is solved now and now the correct bank account will get printed on the Report. (Either IBAN or the
Normal Bank Account depending on the option chosen)
SOLUTION 128766 (POST-REQUISITE) TOGETHER WHEN DOWNLOADING THIS SOLUTION
128476
*******************************************************************************************************
**********************************************
VERSION(S):
B50_b, B50_c

Solution: 128486
SITUATION IDENTIFIED IN:
"Generate Invoice by Self-Billing" (tfacp2290m000)
SITUATION DESCRIPTION:
When running session "Generate Invoice by Self-Billing - tfacp2290m000", a fatal error occurs with the message :
"Dynamic Link failure external symbol 'desc.l' in DLL object 'otfglddll4002' "
SOLUTION DESCRIPTION:
The fatal error no longer occurs.

Solution: 128517
SITUATION IDENTIFIED IN:
"Assign unallocated / Advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When more than one unallocated receipt was used within the same transaction to be linked to invoices, the balance amounts
went wrong.
Problems in balances were also encountered when trying to assign one unallocated receipt to another using the same
transaction type in the same batch.
SOLUTION DESCRIPTION:
Now there are no problems with balances on assigning unallocated receipts to invoices.
Problems with balances when trying to assign two unallocated receipts with each other are also taken care of.
It is not possible to directly allocate two unallocated receipts now (using "Bank Transactions"). A separate transaction type
needs to be used for allocating unallocated receipts to each other. This restriction has been implemented to prevent problems
in balances while linking unallocated receipts to invoices.

Solution: 128519
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
The Tax country in the Sales Invoice Transactions (tfacr1111s000) becomes zero once the Invoice date is changed in the
Sales Invoices. (tfacr1110s000)
SOLUTION DESCRIPTION:
The Tax country in the Sales Invoice Transactions does not become blank even though the Invoice date is changed in the
Sales Invoices.

Solution: 128528
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
Document number was not printed on the posted EBS bank Statement Report after posting the EBS batch.
SOLUTION DESCRIPTION:
Now Document number is printed on the posted EBS bank Statement Report after posting the EBS batch.

Solution: 128532
SITUATION IDENTIFIED IN:
"Assign Credit Notes to Invoices" (tfacr2121m000)
SITUATION DESCRIPTION:
The document number of the Assignment document created when a credit note is linked to an invoice is not shown after the
assignment is done.
SOLUTION DESCRIPTION:
A message is displayed with the document number after a credit note is linked to an invoice.

Solution: 128535
SITUATION IDENTIFIED IN:
"Remove Fully Paid Sales Invoices" (tfacr2260m000)
SITUATION DESCRIPTION:
Cannot archive the data for the Receipt Document after Archiving the Sales Invoices.
SOLUTION DESCRIPTION:
Now the Receipt transactions can be archived

Solution: 128536
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
Transactions created from EBS were not displayed in the "Display Bank Balances By Document Number" Report when the
common parameter multiple control account is ON.
SOLUTION DESCRIPTION:
Now Transactions created from EBS are displayed in the "Display Bank Balances By Document Number" Report when the
common parameter multiple control account is ON

Solution: 128543
SITUATION IDENTIFIED IN:
"Sales Credit Note" (tfacr1110m000)
SITUATION DESCRIPTION:
Late Payment Surcharge Code and Payment Method Code are wrongly defaulted for Sales Credit Note.
SOLUTION DESCRIPTION:
Correct Late Payment Surcharge Code and Payment Method Code are defaulted for Sales Credit Note.

Solution: 128550
SITUATION IDENTIFIED IN:
"Assign Credit Notes to Invoices" (tfacp2120m000)
SITUATION DESCRIPTION:
The sessions "Assign Credit Notes to Invoices" (tfacp2120m000) and "Assign Invoices to Credit Notes" (tfacp2121s000) take
a long time to start.
SOLUTION DESCRIPTION:
The performance of the above sessions has been improved.

Solution: 128553
SITUATION IDENTIFIED IN:
"Report Orders Completed" (tisfc0120s000)
SITUATION DESCRIPTION:
When trying to complete a rework production order for an item having 'Lot control- By Unit', an error message "Lot %s for
item %s already exists" pops up and it is not possible to complete the order. This happens if the initial lot code and the
rework order's lot code are the same.
SOLUTION DESCRIPTION:
Users can now close the rework production order with the same lot code as the original production order's lot code.

Solution: 128561
SITUATION IDENTIFIED IN:
"Print Payment Advice" (tfcmg1401m000)
SITUATION DESCRIPTION:
'Reason for Payment' is not printed in any of the 'Detailed Reports' because that field is not present in those reports
SOLUTION DESCRIPTION:
Earlier, 'Reason for Payment' is not printed in the 'Detailed Reports'
Now, new field is added to the report so that 'Reason for Payment' is also printed in the Reports

Solution: 128569
SITUATION IDENTIFIED IN:
"Anticipated Payments(Details)" (tfcmg2116s000)
SITUATION DESCRIPTION:
Error message displayed when entering Journal check.
SOLUTION DESCRIPTION:
The reported problem is solved now and now the Error message won't get popped up when entering Journal check

Solution: 128599
SITUATION IDENTIFIED IN:
"Compose Payments" (tfcmg1240m000)
SITUATION DESCRIPTION:
The IAB and PAYE numbers are currently printed at the end of the 'Reference' field, for the report group selected in
'Payment Methods' (tfcmg0140m000). The social contribution and tax authorities are only reading the first 30 characters of
this 'Reference'; therefore, these numbers are not read completely.
SOLUTION
DESCRIPTION:
The order of the 'Reference' field has been changed. The IAB and PAYE subcontracting numbers are printed at the beginning of
the 'Reference' to be properly read by the social contribution and tax authorities.
The IAB- and PAYE-
subcontracting numbers is actually filled at the first 30 positions.

Solution: 128608
SITUATION IDENTIFIED IN:
"Generate Invoice by Self Billing" (tfacp2290m000)
SITUATION DESCRIPTION:
It was not possible to generate the self-billing invoice, as the system shows the below fatal error.
FATAL ERROR: Illegal number of args (11) for function tfint.dlltdpur.update.average.purchase.price expected 12.
it appears because of the reason that an argument was missing
SOLUTION DESCRIPTION:
The argument is added for the called function. Now, it is possible to process the self-billing invoice.
SOLUTION AFTER DOWNLOADING THE SOLUTION 128380.
VERSION(S):
B50_b, B50_c , B52_a

Solution: 128625
SITUATION IDENTIFIED IN:
"Item Costing Data" (tdisa0107s000)
SITUATION DESCRIPTION:
When Standard Cost Price is calculated for a new item the fatal error "Index out of dimension" occurs.
SOLUTION DESCRIPTION:
The fatal error doesn't occur now.

Solution: 128635
SITUATION IDENTIFIED IN:
"Item Costing Data" (tdisa0107s000)
SITUATION DESCRIPTION:
When Standard Cost Price is calculated for a new item the fatal error "Index out of dimension" occurs.
SOLUTION DESCRIPTION:
The fatal error doesn't occur now.

Solution: 128637
SITUATION IDENTIFIED IN:
"Purchase Order lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1) When the Purchase order is generated for a Sales Order, the unit in the purchase order line is always in the Inventory unit
of the item. Instead, it should be converted and created in the Purchase unit of the item.
2) Suppose that there are two planned purchase orders in Projects. When these two planned orders are transferred together
to Purchase Orders for the same Buy-from-BP, they are created under two different Purchase Orders
SOLUTION DESCRIPTION:
1) Now, the purchase order would be generated in the Purchase Unit of the item.
2) The two planned orders will be clubbed together in a single purchase order.

Solution: 128647
SITUATION IDENTIFIED IN:
"Finalization Run Numbers" (tfgld1110m000)
SITUATION DESCRIPTION:
Automatic transactions added to postings of opening balance batch and to the transaction type of "Automatic balancing of
P&L Accounts"
SOLUTION DESCRIPTION:
Automatic transactions are not added to postings of opening balance batch and to the transaction type of "Automatic
balancing of P&L Accounts"

Solution: 128654
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Discount amount is subtracted twice from the Amount to be paid and a wrong Cash discount is getting defaulted in the
Swiss Localization
SOLUTION DESCRIPTION:
The reported problem is solved now and the Discounts are calculated and displayed correctly in the Swiss Localization

Solution: 128655
SITUATION IDENTIFIED IN:
"Print Statements of Account" (tfacr3440m000)
SITUATION DESCRIPTION:
When anticipated receipts with step "Doc sent to customer" were attached to an invoice, the invoice amounts and receipt
amounts were not being calculated correctly for such invoices in the statement of account .
SOLUTION DESCRIPTION:
Now the invoice and receipt amounts for such invoices are correctly calculated in the statement of account .

Solution: 128657
SITUATION IDENTIFIED IN:
"Complete Production Orders" (tisfc0520m000)
SITUATION DESCRIPTION:
1. There are two operations attached to the production order and the operations are carried out in work centers that belong
to different Financial Companies.
2. While completing the order in partial quantities, the fatal error "Duplicate value 100" occurs.
SOLUTION DESCRIPTION:
The error 100 no longer appears and the Production order can be completed.

Solution: 128660
SITUATION IDENTIFIED IN:
"Assign Credit Notes to Invoices" (tfacr2121m000)
SITUATION DESCRIPTION:
Wrong updating of balance amount after assigning a Credit note to an invoice with schedule lines.
The invoice balance becomes 0 even if the amount assigned doesn't correspond to the entire invoice amount
SOLUTION DESCRIPTION:
The Balance amount of the invoice and the receipt schedules is updated as per the assignment amount.

Solution: 128662
SITUATION IDENTIFIED IN:
"Select Invoices for Reminder" (tfacr3210m000)
SITUATION DESCRIPTION:
1. Invoices getting selected without Reminder Method attached to Business Partner
2. Default not working for representative.
3. Though Business Partner balance is negative, Reminder are sent to customer when range of sale representatives are
entered.
SOLUTION DESCRIPTION:
1. Business Partner without Reminder Methods is not selected.
2. Proper defaults of Representatives are done.
3. If BP balance is negative and Parameter "Do Not Send" is ON then reminders are not sent to the Business Partner.

Solution: 128703
SITUATION IDENTIFIED IN:
"Write off payment differences" (tfacr2240m000)
SITUATION DESCRIPTION:
When a payment difference document is created through this session "Write off payment differences", it is observed that for
this record, the document date in the "Non-finalized transactions" table and the table "open entries" are not the same.
If the receipt schedule parameter in General Localization parameters is OFF, the date of this document in the "Non-finalized
transactions" table picks up the document date of the original invoice, where as the date of this document in the "open
entries" table picks up the date entered in the second form of the session.
SOLUTION DESCRIPTION:
The document dates of the newly created payment difference records in both "Non-finalized transactions" table and the "open
entries" table will now be the same i.e., they will be the date entered in the second form of the session "Write off payment
differences".

Solution: 128716
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
The materials retuned from service to warehousing are logged with the FTP price in "Integration Transactions by
Project/Order" (tfgld4510m000). This should be done with the actual inventory value depending on the 'Inventory
Valuation Method' for the Item and Warehouse combination.
SOLUTION
DESCRIPTION:
The return Service/Issue type of integration is logged with the actual inventory value and not the with the FTP price of the
item.

Solution: 128717
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
While EBS batch posting was done, it was posting the GLD batch transaction type with a new document number for every
document in the EBS batch.
SOLUTION DESCRIPTION:
Now the new document number will be created only when there is a change in the Bank transaction type or EBS batch.

Solution: 128752
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
After entering the original invoice in the credit note, the Late Payment Surcharge, Terms of Payment and Due date are
defaulted as that of the original invoice and are able to modify.
SOLUTION DESCRIPTION:
After entering the original invoice in the credit note, the Late Payment Surcharge, Terms of Payment and Due date are
defaulted as that of the original invoice and are not allowed to modify.

Solution: 128764
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1111s000)
SITUATION DESCRIPTION:
Default tax code not displayed when the tax is defined based on GEO Codes in the session "Tax Codes by GEO Code"
(tcmcs1136m000).
SOLUTION DESCRIPTION:
Now Tax code is defaulted if defined based on GEO Codes

Solution: 128782
SITUATION IDENTIFIED IN:
"Enter amounts for assignment" (tfcmg2119s000)
SITUATION DESCRIPTION:
When 'Schedule' parameter is 'on', the balance of the unallocated/advance document selected for linking is zero while
entering the session
SOLUTION DESCRIPTION:
Earlier, balance of the unallocated/advance document is always zero instead of its original balance
Now, the balance is shown correctly

Solution: 128784
SITUATION IDENTIFIED IN:
"Remove Fully Paid Sales Invoices" (tfacr2260m000)
"Remove Fully Paid Purchase Invoices" (tfacp2250m000)
SITUATION DESCRIPTION:
No session available to archive the Anticipated Payment/Receipts tables (tfcmg110 till tfcmg112).
SOLUTION DESCRIPTION:
Via session(s) "Remove Fully Paid Sales Invoices" and "Remove Fully Paid Purchase Invoices" , all Anticipated
Payments/Receipts (including Cash Journals) can be archived and deleted from Anticipated Payments/Receipts tables
(tfcmg110 , tfcmg111 and tfcmg112) .

Solution: 128811
SITUATION IDENTIFIED IN:
"Trade Notes Payable" (tfcmgl170s00l1/tfcmgl170s00l2)
SITUATION DESCRIPTION:
Some words are hard-coded in the forms and a label "Actual Maturity Date " is misleading.
SOLUTION DESCRIPTION:
Now, the hard-coded words are replaced with labels and the Misleading label description is modified with "Maturity Date".

Solution: 128812
SITUATION IDENTIFIED IN:
"Select Invoices for Payment" (tfcmg1220s000)
SITUATION DESCRIPTION:
Incorrect message that the selection is complete when invoice has not been selected
SOLUTION DESCRIPTION:
The reported problem is solved and now a correct message "No Invoices Selected" will be given when the Invoice has not
been selected.

Solution: 128825
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
1. When registering a purchase invoice of an order the actual currency rate is taken and can only be adjusted to the original
rate of the order by manually changing the currency rate.
2. Project transactions are not removed even when after the question "Remove existing transactions?" "YES" is pressed.
3. When changing the amount in an Invoice header to the amount of the Invoice lines after entering a cost invoice, with an
amount of 0.00 in the Invoice header and an amount <> 0.00 in the Invoice lines the invoice status never changes to
"transactions entered".
SOLUTION DESCRIPTION:
1. When registering a purchase invoice of an order the original rate of the order is taken in account.
2. Project transactions are removed after the question "Remove existing transactions?" "YES" is pressed because a matched
order has to be unmatched before changes can be made.
3. When changing the amount of an Invoice header to the amount of the Invoice lines after entering a cost invoice, with an
amount of 0.00 in the Invoice header and an amount <> 0.00 in the Invoice lines the invoice status will change to
"transactions entered".

Solution: 128851
SITUATION IDENTIFIED IN:
"Print Multi-level cost price calculation" (ticpr2420m000)
SITUATION DESCRIPTION:
When printing Multi-level cost price calculation of an item by 'Details by cost component' flag checked, the operation time
is printed wrongly if man time or machine time is zero for the operations.
SOLUTION DESCRIPTION:
When printing the operation costs for an item in session "Print Multi-level cost price calculation" (ticpr2420m000), if man
hours or machine hours for an operation are zero, then system will consider the non zero hours for printing operation time.

Solution: 128852
SITUATION IDENTIFIED IN:
"Remove Fully Paid Trade Notes Payable" (tfcmgl270m00l)
SITUATION DESCRIPTION:
On removing the fully paid trade note numbers the Trade number was not made null in the Payment advice.
SOLUTION DESCRIPTION:
Now after removing the fully paid trade note numbers the Trade note numbers is made null in the payment advice.

Solution: 128893
SITUATION IDENTIFIED IN:
"Generate Invoices by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
The session Generate Invoices by selfbilling was designed as one huge logical transaction because which the following
problems were noticed.
1. The batch number was locked too long , because which other process trying to create batch numbers resulted in Fatal
error.
2. Performance loss due to retries.
3. When something goes wrong with the particular receipt ( for example missing ledger account in mapping scheme for invoice
accrual account ), then all the previously processed receipts were reverted back.
SOLUTION DESCRIPTION:
Now the session is designed into smaller logical transaction.
1, Batch is created in the beginning of process. If no transaction is created in the batch, then the batch status set to deleted.
2. The transactions are committed into the tables after each Invoice is created.

Solution: 128895
SITUATION IDENTIFIED IN:
"Currency Rates" (tcmcs0108m000)
SITUATION DESCRIPTION:
In a Multi Site setup when table tcmcs008 (Currency Rates) is shared a problem may arise when the End User is trying to insert
new currency rates with an effective date before the last Cost Price calculation date. This is due to the fact that the general
item data tables (tcibd001/tcibd007) are not shared over the same set of companies.
SOLUTION
DESCRIPTION:
From now onwards, the check for the last performed Cost
Price Calculation will not only check Item Costing Data (tcibd007) in
the current company, but also the other logistical companies in which tcmcs008 (Currency Rates) is shared.

Solution: 128902
SITUATION IDENTIFIED IN:
"Print WIP" (ticst0450m000)
SITUATION DESCRIPTION:
Performance problem
SOLUTION DESCRIPTION:
Improved 2 queries

Solution: 128909
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
No VAT Postings are found for Journal Transactions When EBS batch is posted.
SOLUTION DESCRIPTION:
Now VAT postings are posted for Journal Transactions when EBS batch is posted.

Solution: 128949
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Payments to Invoices" (tfcmg2105s000, tfcmg2106s000, tfcmg2107s000, tfcmg2119s000 )
SITUATION DESCRIPTION:
1.The assignment of an unallocated or advanced receipt to an invoice or a credit note does not work correctly.
2. Impossible to unlink a negative unallocated payment to a Credit Note once the allocation has been processed
SOLUTION DESCRIPTION:
Now the assignment works properly and it is possible to unlink a negative unallocated payment to a Credit Note once the
allocation has been processed .

Solution: 128984
SITUATION IDENTIFIED IN:
"Correct COGS Intgrations" (cicor0111m000)
SITUATION DESCRIPTION:
User needs the flexibility to correct transactions even present in the closed period.
SOLUTION DESCRIPTION:
The user is now given the flexibility to correct the transactions booked in a closed period also.
Now if the option "Correct transactions of Closed Period" is enabled, then the user can give the date range falling in the
closed periods also.
So the wrong transactions booked in those periods will be deleted and new transactions will be booked in the next available
open period.

Solution: 128987
SITUATION IDENTIFIED IN:
"Integration transaction" (tfgld4510m000)
SITUATION DESCRIPTION:
1) Using triangular invoicing, the amount of the generated financial transaction Warehouse order/Transfer price is not
correctly rounded.
2) For the financial transaction Sales/General costs, the amount is always "0" though the cost of goods sold (general)
appears correctly in the item master data. This is specific to the B50_c_bgl0 (Localization) VRC.
3) Amounts are posted with Wrong transaction origin and financial transaction for Production return when more than issued
quantity is returned. (DF 129377)
SOLUTION DESCRIPTION:
1) Now the amounts are correctly rounded before generating the invoice.
2) The Sales/General costs financial transactions are posted correctly with the cost price of the cost item.
3) Amounts for Production return are posted with correct transaction origin and financial transactions in finance.
SOLUTION 129446 AFTER DOWN
LOADING THIS SOLUTION *********************
*************************************************************** THIS IS MANDATORY
*********************************************************************************
VERSION(S):
B50_b, B50_c

Solution: 128990
SITUATION IDENTIFIED IN:
"Payment Advice" (tfcmg1120s000)
SITUATION DESCRIPTION:
In Dependent Currency System, currency rate was picked up from the currency rate table when you gave ' Fixed hard' rate
determiner in the invoice.
SOLUTION DESCRIPTION:
In Dependent Currency System, currency rate is picked up from the invoice when you give ' Fixed hard' rate determiner in
the invoice.

Solution: 128995
SITUATION IDENTIFIED IN:
"Trade notes Payable" (tfcmgl570m00l)
SITUATION DESCRIPTION:
The label "Actual Maturity Date" on Form is misleading in Japanese Language.
SOLUTION DESCRIPTION:
Now, the label on the form is modified as "Maturity Date".

Solution: 129026
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4120s000)
SITUATION DESCRIPTION:
In Dependent Currency System, currency rate was picked up from the currency rate table when you gave ' Fixed hard' rate
determiner in the invoice.
SOLUTION DESCRIPTION:
In Dependent Currency System, currency rate is picked up from the invoice when you give ' Fixed hard' rate determiner in
the invoice.

Solution: 129056
SITUATION IDENTIFIED IN:
"Generate Project Structure for Product Variant" (tipcs2220m000)
SITUATION DESCRIPTION:
When a project structure is generated for a product variant of a generic item, if the component is also generic item, then the
sales price of the customized component is getting updated with purchase price of the original generic item.
SOLUTION DESCRIPTION:
The customized item derived from a generic item, which is a component of another generic item, will have the default sales
price.

Solution: 129058
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
It is not possible to go to Detail session once the single occurrence session is closed and opened again as the Detail button
is removed from the form during this condition.
SOLUTION DESCRIPTION:
Now it is possible to go to detail line session from the first form of the purchase order line session even if the single
occurrence session is closed and opened again.

Solution: 129098
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Receipt cannot be made for an item that is blocked for purchase in the time interval between the order line creation and
receipts.
SOLUTION DESCRIPTION:
The receipts can be maintained now even if the item is blocked for purchase after the purchase order line entry.

Solution: 129107
SITUATION IDENTIFIED IN:
"Post Payments" (tfcmg1257m000)
SITUATION DESCRIPTION:
There was a difference in Control account checklist after payment of multiple control account purchase invoice. It was not
updating the correct multiple control account for the payment documents.
SOLUTION DESCRIPTION:
There is no difference in Control account checklist after payment of multiple control account purchase invoice. It is
updating multiple control account correctly for the payment documents.

Solution: 129123
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When the currency rate changes at the time of invoicing, then the cash discount amount in home currency is not recalculated
again. It retains the old value itself.
SOLUTION DESCRIPTION:
Now the home currency amounts are correctly calculated.

Solution: 129134
SITUATION IDENTIFIED IN:
"Process Inspection Orders" (qmptc1204m000)
SITUATION DESCRIPTION:
While processing an inspection order in QMS Module for Sales origin, the system gives a fatal error "Index out of range".
SOLUTION DESCRIPTION:
The inspection orders can be processed and the order can be closed.

Solution: 129136
SITUATION IDENTIFIED IN:
"Print Specifications delivered but not invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
Report shows a delivered quantity of zero (0) even though there is a delivered quantity
SOLUTION DESCRIPTION:
Report does not show a delivered quantity of zero (0) if there is a delivered quantity

Solution: 129199
SITUATION IDENTIFIED IN:
"Assign unallocated /advance payments to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
Invoices from child Business Partner which have been already linked to an unallocated receipt are not shown while
re-entering the session.
SOLUTION DESCRIPTION:
Now, the linked invoices of Child Customers are shown with the proper balances.

Solution: 129204
SITUATION IDENTIFIED IN:
"Purchase Invoice Corrections" (tfacp2110s000)
SITUATION DESCRIPTION:
When a correction was done for the second time in session "tfacp2110s000 - Purchase Invoice Corrections" on an amount
including vat after a correction which did not influence any amount the batch got unbalanced with the old vat amount.
SOLUTION DESCRIPTION:
Corrections are done properly for the second time on the same invoice now as well.

Solution: 129216
SITUATION IDENTIFIED IN:
"Selection for Automatic Reconciliation" (tfcmg2123s000)
SITUATION DESCRIPTION:
Session reconciles the document that has not been selected for Automatic Reconciliation.
SOLUTION DESCRIPTION:
Session won't reconcile the document that has not been selected for Automatic Reconciliation and only the documents that
are selected for Automatic Reconciliation will be reconciled now.

Solution: 129223
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When confirming receipt in session "Receipts" (whinh3520m000) for a zero quantity order with inventory valuation method as
"Lot Price" and if the order amount is different from the lot amount then the error message 'Price in CPR does not match lot
price' pops up and it is not possible to confirm the receipt.
SOLUTION DESCRIPTION:
No error message comes up when confirming a receipt of zero quantity.

Solution: 129229
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation by LCM Method" (whinal230m00l)
SITUATION DESCRIPTION:
When running session "Perform Inventory Valuation by LCM Method" (whinal230m00l), the error message "Illegal number
of arguments" pops up and the session aborts.
SOLUTION DESCRIPTION:
No error message pops up and the session runs properly.

Solution: 129234
SITUATION IDENTIFIED IN:
"Assign Credit Note to Invoices" (tfacp2121s000)
SITUATION DESCRIPTION:
During the assignment of the Credit Note to Invoice(s) the document is set to deleted and batch to free. The result is that
Linking is not possible.
SOLUTION DESCRIPTION:
Linking is possible again.

Solution: 129246
SITUATION IDENTIFIED IN:
"Maintain Purchase Invoice Corrections" (tfacp2110s000)
SITUATION DESCRIPTION:
When correcting a Purchase Invoice for the amount in sesison "tfacp2110s000 - Maintain Purchase Invoice Corrections" and
the session is closed and saved by the x-button. The amounts in home currecny are changed on the screen but the table is
not updated.
SOLUTION DESCRIPTION:
The amounts are updated correctly now

Solution: 129284
SITUATION IDENTIFIED IN:
"Payment details" (tfacp2524s000)
SITUATION DESCRIPTION:
When in session "Payment details" (tfacp2524s000), on clicking option "Check Doc. Data" the error message "Fatal Error
506" appears and the session doesn't open.
SOLUTION DESCRIPTION:
No error messages appear on choosing the option "Check Doc. Data" and the session opens properly.

Solution: 129328
SITUATION IDENTIFIED IN:
"Actualize Cost and Valuation Prices" (ticpr2220m000)
SITUATION DESCRIPTION:
Actualize cost price failed but no report is printed with the reason why.
SOLUTION DESCRIPTION:
In some cases actualizing the cost price failed due to a timing problem caused by sol 127795. Besides, an error report was
missing so problems were never showed to the user, giving a lot of confusion. Now both the timing problem and the report
handling have been solved.

Solution: 129336
SITUATION IDENTIFIED IN:
"Item Inventory by Warehouse" (whwmd2115s000)
SITUATION DESCRIPTION:
When inserting a purchase order line for a combination of item (controlled as Average Costs (aavg)) and warehouse which
does not yet exist in |Item Inventory by Warehouse" (whwmd2115s000), the average costs is not filled. The result is wrong
financial transactions.
SOLUTION DESCRIPTION:
The program script has been corrected. The values are now calculated properly. The functionality of calculating Average
Cost is as follows:
- When entering a new record for an item and a warehouse, either directly in session |Item Data by Warehouse",
(whwmd2510m000) or indirectly (via entering e.g. a purchase order), the average cost for materials and operations are taken
from the Item by Warehouse information from the default warehouse (defined in General Item Data). If that information is
not available, the FTP values must be taken. For Surcharges, the normal calculated values are used.
- When updating the Item Data by Warehouse via cost price calculations, average costs will only be updated if there is no
inventory (On Hand, On Order, Allocated).

Solution: 129340
SITUATION IDENTIFIED IN:
"Commitments(material)" (tpppc2110s000)
SITUATION DESCRIPTION:
Soft Commitments generated in Project for cost items always gets quantity 0 and unit has an empty value when inventory
unit of that item is empty.
SOLUTION DESCRIPTION:
Now purchase unit would be used instead of inventory unit if inventory unit is blank in item data. So now correct quantity
and unit would be displayed.

Solution: 129359
SITUATION IDENTIFIED IN:
"Write off Currency Differences" (tfacp2240m000)
SITUATION DESCRIPTION:
After running session "Write off Currency Differences" (tfacp2240m000) for Unallocated Payments, the new rate and the new
balance in home currency is not updated for the Unallocated Payments, even though the currency difference transaction is
created correctly.
SOLUTION DESCRIPTION:
The rates and new balance in home currency is updated correctly for the Unallocated Payment document.

Solution: 129374
SITUATION IDENTIFIED IN:
"Match Purchase Order Lines" (tfacp2541m000)
SITUATION DESCRIPTION:
In session "Match Purchase Order Lines" (tfacp2541m000), the option "Match All" is chosen. Now if there are many items
still not received in the warehouse then the error message "Received quantity 0 of order minus quantity already matched 0 is
less than or equal to zero" appears, as many times as there are non-received orders in the warehouse.
SOLUTION DESCRIPTION:
When the option "Match All" is chosen, the message comes up
once. And then a question is asked, whether the user wants to continue
running the session. If the option "Yes" is chosen then no more messages pops up, but further orders are processed.

Solution: 129378
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2500m000)
SITUATION DESCRIPTION:
Consignment replenishment sales orders are not processed automatically when returning goods (using a negative quantity)
from consignment (owned) warehouse to main warehouse, even when process direct is set to true.
SOLUTION DESCRIPTION:
Processing is done automatically if process direct is set to true (for this situation, a receipt needs to be created manually
only when process direct is set to False and Receipt is an activity included in the warehouse procedure).

Solution: 129399
SITUATION IDENTIFIED IN:
"Selection for Automatic Reconciliation" (tfcmg2123s000)
SITUATION DESCRIPTION:
After automatic reconciliation via session "Selection for Automatic Reconciliation" (tfcmg2123s000), the reconciliation
batch cannot be finalized when both a purchase invoice and a standing order for advance payment with VAT are included
within this batch. An error report has been created about wrong balances on the VAT account.
SOLUTION
DESCRIPTION:
The reconciliation batch with both a purchase invoice and a standing order for advance payments with VAT can be finalized
successfully.

Solution: 129403
SITUATION IDENTIFIED IN:
"Sales Invoice Transactions" (tfacr1111s000)
SITUATION DESCRIPTION:
If VAT amount is changed in the transaction line level, batch is not in balance; Maintain Interim Tax table (tfgld107) is
not updated with the new changed amount
SOLUTION DESCRIPTION:
If VAT amount is changed in the transaction line level, Maintain Interim Tax table (tfgld107) is updated with the new
changed amount.

Solution: 129412
SITUATION IDENTIFIED IN:
"Warehouse Tools Transfer" (titrp0108m000)
SITUATION DESCRIPTION:
It is not possible to transfer tools within session "Warehouse Tools Transfer" (titrp0108m000) in case the parameter
"Over Delivery" in session "Inventory Handling Parameters" (whinh0100s000) is set lower than 100%.
The message " Advised quantity in Inventory Unit cannot be greater than Ordered quantity in Inventory Unit + Rejected
Quantity in inventory UNIT" occurs.
SOLUTION DESCRIPTION:
Changes made so the functionality of Parameter "Over Delivery" is handled correctly.

Solution: 129419
SITUATION IDENTIFIED IN:
"Close Service Orders and Post to History" (tssoc2201m000)
SITUATION DESCRIPTION:
A) When the Purchase Order Line generated from Service order is split, the service order can not closed by running the
session. System gives the error report
+++++++++++++++++++++++++++
Active Purchase Orders are present
+++++++++++++++++++++++++++
B) When the planned purchase order is transferred as purchase order, the order quantity is not converted in to the Purchase
Unit of the item. But, it is creating in the inventory unit.
SOLUTION DESCRIPTION:
A) It is possible to close the production order, which has split purchase order lines attached to that.
B) The order quantity is converted to the purchase unit of the item and it is no longer in the inventory unit.

Solution: 129428
SITUATION IDENTIFIED IN:
"Write off Currency Difference" (tfacp2230m000)
SITUATION DESCRIPTION:
When payment schedules are used and if the purchase invoice is paid, then the "Write off Currency Difference"
(tfacp2230m000) session doesn't write off any difference between the purchase invoice and the allocated payment.
SOLUTION DESCRIPTION:
The session now creates a payment difference document even if the invoice is paid.

Solution: 129434
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
Swift code is not filled for Report S, Bankgiro, Foreign (code 29)
SOLUTION DESCRIPTION:
Swift code is filled correctly now for Report S, Bankgiro, Foreign (code 29)

Solution: 129446
SITUATION IDENTIFIED IN:
"Integration Transactions by Project / Order" (tfgld4510m000)
SITUATION DESCRIPTION:
Postings in finance were done with wrong 'Transaction origin' and 'Financial transaction', when more than the issued
quantity is returned to warehouse for a production order and meanwhile FTP has changed.
SOLUTION DESCRIPTION:
Now the postings are done with correct 'Transaction origin' and 'Financial transaction' for the extra returned quantity.

Solution: 129460
SITUATION IDENTIFIED IN:
"Correct COGS Integrations" (cicor0111m000)
SITUATION DESCRIPTION:
If the correction program is run from a different company other than the logistic company in which the sales order was
raised, then the correction program did not pick up the order.
SOLUTION DESCRIPTION:
Now the program works correctly in a multi-site environment

Solution: 129468
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When the user tries to terminate the composing process by clicking 'Stop' button, he gets a fatal error "Error 506 (Table does
not exist).
SOLUTION DESCRIPTION:
Now the fatal error does not occur. The process gets terminated correctly.

Solution: 129497
SITUATION IDENTIFIED IN:
"Print goods received note" (whinh3412m000)
SITUATION DESCRIPTION:
While printing the report for 'Print goods received note' (whinh3412m000) of a Purchase order, then the report does not print
the subcontracting details of the order. The problem occurs when there are more than one operation linked to the routing and
the first operation is not the subcontracting operation.
SOLUTION
DESCRIPTION:
The subcontracting details of the production orders are printed in the report, when 'Print goods received note'
(whinh3412m000) for the Purchase order are printed.

Solution: 129519
SITUATION IDENTIFIED IN:
"Maintain Posting Data for Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
When an invoice (for part amount) was already in 'audited' status and is selected again in the same or another batch
for 'maintaining posting data', message 'Document already selected in company , batch '
was shown (For example, for company 550, Batch 100, Message was 'Document already selected in company 550, batch
100'), which was confusing.
SOLUTION DESCRIPTION:
Now, message is changed as 'Document was already selected
in batch . Post batch to finance, remove posted data and
try again.' For the above example, if invoice ACR 19980172 is selected again,
the message would be - 'Document ACR 19980172 was already
selected in batch 100. Post batch 100 to finance, remove posted data and try again.'
SOLUTION 129801 ALSO ***
VERSION(S):
B40_c, B50_b, B50_c, B52_a

Solution: 129530
SITUATION IDENTIFIED IN:
"Maintain Currency Rates" (tcmcs0108m000)
SITUATION DESCRIPTION:
It was possible that a currency rate was entered on the form with more than 6 decimals. Example, an End User could enter
"1,23456789012" on the form as the currency rates. When tabulating over this field, the newly entered rate was shown as
"1,234568". This was due to the fact that this formfield was displayed according its format; 6 digits. However on Database
level still the "1,23456789012" was stored. When calculating with large amounts, these 7th-11th decimals could lead to
differences in Finance, which is incorrect.
SOLUTION
DESCRIPTION:
It is still possible that a currency rate on the form is entered with more than 6 decimals, but only the first rounded 6
decimals will be stored in the Database. If the 7th-11th digit are still important, the field "Rate Factor" should be used. In
this way, the currency rate "1,23456789012" will be stored as "123456,789012" with rate factor "100000".

Solution: 129533
SITUATION IDENTIFIED IN:
"Remove Fully Paid Purchase Invoices" (tfacp2250m000)
SITUATION DESCRIPTION:
When running session "Remove Fully Paid Purchase Invoices" (tfacp2250m000) it doesn't archive the data from table "One
time supplier address" (tfacp202).
SOLUTION DESCRIPTION:
The data from table "One time supplier address" (tfacp202) is archived in the history company, but the data is not deleted
as many other modules make use of the information from this table.

Solution: 129535
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When user terminates the Composing process in the middle of it's run, the status of the Billing Request remains as "Posted"
even though only one of the order line has been posted.
The user will not be able to use that Billing Request again.
SOLUTION DESCRIPTION:
Now the process is terminated immediately and the status of the Billing Request remains as "Composed" only. So the user
can process the remaining order lines easily.

Solution: 129551
SITUATION IDENTIFIED IN:
"Print Supplier Aging Analysis" (tfacpl402m00l)
SITUATION DESCRIPTION:
The payment document is not printed when a payment is done for a schedule line.
SOLUTION DESCRIPTION:
The payment document is now printed when a payment was done for a schedule line.

Solution: 129563
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
In session "tfacp1110s000 - Purchase Invoices" it is possible to link an invoice to a credit note with a bigger amount. This
will create a negative balance on the invoice.
This happens when a negative invoice is entered to be used as a credit note.
SOLUTION DESCRIPTION:
It's impossible to link an invoice with a lower balance than the credit note to this credit note.

Solution: 129564
SITUATION IDENTIFIED IN:
"Release to Invoicing" (tdsls4247m000)
SITUATION DESCRIPTION:
When user processes a collect order with more than one line, the tax calculated is wrong. It gets rounded for each line. The
rounding has to be for the entire order.
SOLUTION DESCRIPTION:
Now the tax is calculated correctly.

Solution: 129578
SITUATION IDENTIFIED IN:
"Invoices for Payment" (tfcmg1220m000)
SITUATION DESCRIPTION:
In session "Invoices for Payment - tfcmg1220m000", in case payments are done in "Group Company" (tfcmg000.pall set to
"yes"), the original companies of the invoices should be printed.
SOLUTION DESCRIPTION:
Now the original companies of the invoices are printed.

Solution: 129587
SITUATION IDENTIFIED IN:
"Display Purchase Invoices" (tfacp2520m000)
SITUATION DESCRIPTION:
When running session "Display Purchase Invoices - tfacp2520m000" the displayed due date is not the same as the last date
of the payment schedules when there are payment schedule lines present.
SOLUTION DESCRIPTION:
When running session "Display Purchase Invoices - tfacp2520m000" the displayed due date is the same as the last date of
the payment schedules when there are payment schedule lines present.

Solution: 129589
SITUATION IDENTIFIED IN:
"Confirm Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Cannot confirm a Purchase Receipt cross-docked to a Sales Consignment Replenishment Order.
The Confirmed flag of the Purchase Receipt remains to "No" whereas the Purchase/Receipt Integration Transactions are
being created.
When confirming the Purchase/Receipt for the second time, the Confirmed flag of the Purchase Receipt is properly set to
"Yes" and the Purchase/Receipt Integration Transactions are created.
As a consequence, the Purchase/Receipt Integration Transactions are created twice.
SOLUTION DESCRIPTION:
The Purchase Receipts cross-docked to a Sales Consignment Replenishment Order can now be properly confirmed.

Solution: 129611
SITUATION IDENTIFIED IN:
"Generate Invoices by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
When a receipt is flagged as final receipt is made, and the backorder is changed and then confirmed, a receipt line with zero
quantity is recorded in Finance. Because of this, during the selfbilling process, only the zero receipt line is invoiced, and the
original receipt is not invoiced.
SOLUTION
DESCRIPTION:
Now, a check is also done on the receipt sequence number, to make sure all the receipt lines belonging to a receipt are
invoiced.

Solution: 129623
SITUATION IDENTIFIED IN:
"Print Specification Delivered Not Invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
When user selects "Sales" transaction origin, "Warehousing (consignment)" transactions are printed along with "Sales"
orders.
SOLUTION DESCRIPTION:
When "Sales" transaction origin is selected, only sales order details are printed.

Solution: 129630
SITUATION IDENTIFIED IN:
"Confirm Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When receiving a Sales Return Order, the Financial Integration created for the Sales Item or Warehouse Issue Surcharges and
the Inventory Receipt Transactions (as registered in the table whinr112) could be created with an incorrect amount.
This happens when a Variance (as registered in the table whinr116) was assigned to the original Receipt (from which the
returned Issue was consumed) after the Issue had been processed.
This only happens if the Item Valuation Method is FIFO or LIFO.
The Inventory Receipt Transactions and the Surcharges included the assigned Variances. This is not correct.
Example:
01-01-2002
Receipt created for 19 pcs.
02-01-2002
Issue 11 pcs (that will consume the receipt above)
03-01-2002
Match and Approve the Receipt in Finance.
A Variance is created for the price difference
04-01-2002
Assign the variance to the Receipt.
05-01-2002
Return the Sales Order.
SOLUTION DESCRIPTION:
The assigned Variances will be deducted from the Receipt Amounts.

Solution: 129636
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When re-entering, after reversing one of the 2 assignments, the balances of the invoices are wrong. The 'write-off' status is
also not changed even after reversal. It is because the line number of the assignment document is ignored while deleting
assignments resulting in non-deletion of assignment record of the cancelled-invoice.
SOLUTION
DESCRIPTION:
Now, line number is also used to read and delete the assignments.
Therefore, determination of the 'write-off' status and
the balances of the invoices are
done
correctly
.

Solution: 129644
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When localization parameter 'Multiple Tax' and 'Cash Discount' is ON, rounding differences accumulated over many lines in
an invoice cause the batch to be unbalanced. So the user cannot finalize the batch.
SOLUTION DESCRIPTION:
Now the batch is posted correctly.

Solution: 129645
SITUATION IDENTIFIED IN:
"Approve Purchase Invoices" (tfacp1140s000)
SITUATION DESCRIPTION:
The creation of costs and commitment lines in projects for project-related Purchase-Invoices are depending, during the
approval, on the fact if the
last invoice is processed. Sometimes this is NOT coming to projects. So the projects cann't be processed.
SOLUTION DESCRIPTION:
The detemination, in the approval-process, if it is the 'last'-invoice (for project related Purchase Orders) is changed in such a
way that there is not looked at the 'order'-quantity but at the 'approved'- AND the 'rejected'-quantity.

Solution: 129648
SITUATION IDENTIFIED IN:
"Process Cycle Counting / Adjustment Orders" (whinh5201m000)
SITUATION DESCRIPTION:
Actual amounts are calculated with FTP even if aavg has to be used while processing inventory adjustment.
SOLUTION DESCRIPTION:
In case of positive adjustment and valuation method AAVG the annual average price will be used. In case of negative
adjustment old AAVG value will be saved and used for Finance before overwriting AAVG with FTP when reducing stock to
zero quantity.

Solution: 129661
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
For a Collect Return Purchase Order, user is not able to change the warehouse in case of insufficient inventory because the
warehouse field is disabled. Also, the warehouse is not defaulted for this type of Purchase Order.
SOLUTION DESCRIPTION:
Now the default warehouse is found and defaulted on to the purchase order line even for a collect return purchase order. Also,
the warehouse field is enabled so that user can change it to a different warehouse in case of insufficient inventory.

Solution: 129708
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When an invoice with subcontracting and shifted vat was directly linked to a credit note in session "Purchase Invoices -
tfacp1110s000" the approval batch got unbalanced when you have to set the field subcontracting to "yes" and the vat code to
shifted after saving. This could happen when entering the credit note a mistake was made regarding those fields..
SOLUTION
DESCRIPTION:
The batch is now balanced also when the subcontracting field is changed to yes and the vat code is changed to shifted on the
credit note.

Solution: 129720
SITUATION IDENTIFIED IN:
"Reconciliation of Receipts/Payments" (tfcmg2103s000)
SITUATION DESCRIPTION:
In session "Reconcile Receipts/Payments - tfcmg2103s000", when rejecting a partial reconciliation, the batch is not in
balance. Furthermore, the part of the payment that is still open cannot be reconciled either.
SOLUTION DESCRIPTION:
A partial reconciliation can now be rejected without creating an unbalanced batch. The part of the payment that remains open
can also further reconciled.
Reconciliation batch not is balanced after rejecting a partial payment

Solution: 129729
SITUATION IDENTIFIED IN:
"Print Aging Analysis" (tfacr2420m000)
SITUATION DESCRIPTION:
Wrong Assigned documents for unallocated receipts are shown.
SOLUTION DESCRIPTION:
Correct Assigned documents for unallocated receipts are shown.

Solution: 129748
SITUATION IDENTIFIED IN:
"Business patner's invoices in a company" (tfacr2535m000)
SITUATION DESCRIPTION:
The footer fields are overlapped in detail lines if the window size is changed.
SOLUTION DESCRIPTION:
Now footer is moved to the top of the detail lines. Hence the date and period line is not overlapping on the details.

Solution: 129760
SITUATION IDENTIFIED IN:
"Process Periodical Depreciation Calculation" (tffas2200m000)
SITUATION DESCRIPTION:
If a disposal journal entry which is not posted is deleted, it is no longer possible to depreciate the asset further in session
"Process Periodical Depreciation Calculation" (tffas2200m000).
SOLUTION DESCRIPTION:
It is now possible to depreciate the asset further, if the asset disposal is reversed.

Solution: 129766
SITUATION IDENTIFIED IN:
"Generate Invoices by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
When a selection is processed twice, during the second processing a message "tcempty" is displayed. This doesnt create any
additional problem otherwise.
SOLUTION DESCRIPTION:
This message is no longer displayed.

Solution: 129801
SITUATION IDENTIFIED IN:
"Maintain Posting Data for Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
Fatal error when selecting an invoice, which was already selected in another batch, in the payment advice.
It is because same message code with different parameters is used in Electronic Bank Statements (EBS)
SOLUTION DESCRIPTION:
Now, fatal error doesn't occur in the payment advice even when an invoice is reselected again. A message "Document
already selected in company %s, batch %d" is given.

Solution: 129863
SITUATION IDENTIFIED IN:
"Import Actual Costs from GLD" (tfcat2210m000)
SITUATION DESCRIPTION:
When the data, required for the session "Import Actual Costs from GLD" is very high, the session will aboort with a
Roll-back Error. This has to be changed.
SOLUTION DESCRIPTION:
Now the transaction handling has been changed, so that very large amounts of data can be handled by the system

Solution: 129876
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
A)
1. The Order Balance of a purchase order increases in "Purchase Order Lines" (tdpur4501m000) when the order line is
created.
2. It comes down once the invoice of the purchase order line is approved. This does not happen to the cost items.
3. The Order Balance does not reduce for the cost items, even when the invoice is approved.
B)
1. A self-billing subcontracting purchase order is partially received with out 'Final Receipt' check box selected in
"Receipts" (whinh3520m000)
2. Self-billing invoice for this receipt is generated in Finance package.
3. Now the Final Receipt is done for the purchase order with zero quantity.
4. It is not possible to close the production order, as the linked purchase order is not considered as fully invoiced.
C)
1. A self-billing purchase order is partially received.
2. The back order quantity is changed for this line.
3. When the self-billing invoice is generated for this order, two invoices are generated while the second invoice is for zero
quantity and zero amounts.
SOLUTION DESCRIPTION:
A) The Order Balance will come down for the Invoice From Business Partner once the purchase invoice is approved. The sum
of the Order Balances displayed for the all the orders in "Purchase Order Lines" (tdpur4501m000) is the total Order Balance
of the Invoice From BP.
B) It is possible to close the production orders even when the Final Receipt of the linked purchase order is for zero quantity.
C) The extra self-billing invoice for zero amounts is not generated while changing the back order quantity of the purchase
order line.

Solution: 129883
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
The backorder of a consignment replenishment order cannot be deleted. whinhs0458 "Deleting an inbound order line can
only be done by deleting the outbound order line." comes up.
SOLUTION DESCRIPTION:
The problem was caused by an incorrect check on existing outbound lines. The check is corrected.

Solution: 129888
SITUATION IDENTIFIED IN:
"Write off Currency Differences" (tfacr2250m000)
SITUATION DESCRIPTION:
Even though nothing is found to write off, batch and document number are created, the status of the document is deleted
but the locking status of document should be FREE -instead of IN USE.
SOLUTION DESCRIPTION:
When nothing is found to write off, the status of the document is deleted and locking status of document is FREE -instead
of IN USE.

Solution: 129892
SITUATION IDENTIFIED IN:
"Ledger Accounts by Business Partner Group" (tfacr0111m000)
SITUATION DESCRIPTION:
System is allowing selecting trade notes related ledger accounts defined in Financial Business Partner Group while
creating Manual Journal Voucher
SOLUTION DESCRIPTION:
Now, Trade notes related ledger accounts defined in Financial Business Partner Group are treated as Control Accounts.
Hence these ledger accounts will not be allowed to select while creating manual Journal Vouchers.

Solution: 129905
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When the "Amounts Entered" option for the tax code is defined as "Gross Over Hundred", then the tax is calculated
wrongly when a 100% tax rate is defined. Also the Goods Amount has to be zero, but the invoice shows some value.
SOLUTION DESCRIPTION:
Now the tax is calculated correctly and the invoice is printed correctly.

Solution: 129941
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
In case the order has a fixed rate the current rate is used when entering the order in an invoice. The order rate should be
used.
SOLUTION DESCRIPTION:
After installing this solution the fixed rate of the order is used when entering the order in an invoice.

Solution: 129942
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2100s000)
SITUATION DESCRIPTION:
When outbound lines or inbound lines for a Production (manual) order are released, the system seems to be busy for a
moment but does nothing.
SOLUTION DESCRIPTION:
One of the dll's that is used returned an incorrect value.
Lines can now be released.

Solution: 129954
SITUATION IDENTIFIED IN:
"Maintain Posting Data For Electronic Banks Statements" (tfcmg5106m000)
SITUATION DESCRIPTION:
Amount in home currency is wrongly calculated for unallocated Receipts or unallocated payments.
SOLUTION DESCRIPTION:
Now, home currency amount is calculated correctly for unallocated Receipts or payments.

Solution: 129956
SITUATION IDENTIFIED IN:
"Select Invoices for Payment" (tfcmg1220m000)
SITUATION DESCRIPTION:
Running a job with session 'Select Invoices for Payment' (tfcmg1220m000) on daily basis is not possible. When activating
the job again the system tries to use same batch number again.
SOLUTION DESCRIPTION:
When an already created job with session 'Select Invoices for Payment' is activated again, a new batch number has been
created.

Solution: 129967
SITUATION IDENTIFIED IN:
"Import Actual Costs from GLD" (tfcat2210m000)
SITUATION DESCRIPTION:
When the data, required for the session "Import Actual Costs from GLD" is very high, the session will aboort with a
Roll-back Error. This has to be changed.New changes were added because of the large amount of data
SOLUTION DESCRIPTION:
Now the transaction handling has been changed, so that very large amounts of data can be handled by the system

Solution: 129997
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When entering an invoice with shifted vat in session "Register Purchase Invoices - tfacp1110s000" the shifted vat amount in
home currency isn't filled.
SOLUTION DESCRIPTION:
The shifted vat amount in home currency is filled now when a shifted vat code is entered.

Solution: 130002
SITUATION IDENTIFIED IN:
"Print Aging Analysis" (tfacr2420m000)
SITUATION DESCRIPTION:
When aging analysis code with type days is changed to months.
Re-initialization of values have been taken care, But the re-enabling and disabling of the fields is not done.
When Aging Analysis code with period type "month" is used, "as on year/period" fields are disabled.
SOLUTION DESCRIPTION:
When aging analysis code with type days is changed to months.
Re-initialization of values and the re-enabling and disabling of the fields is done.
When Aging Analysis code with period type "month" is used, "as on year/period" fields should be enabled.

Solution: 130067
SITUATION IDENTIFIED IN:
"Service Order: Actual Material Costs" (tssoc2121s000)
SITUATION DESCRIPTION:
1. When changing the status of a Service Order or a Service Order Activity from 'Released' to 'Completed', return lines are
generated automatically (based on Service Order Control parameters). When all materials have been issued (From Lines) or
received (To Lines) the order can be set to 'Costed'.
When changing the status of a Service Order or a Service Order Activity from 'Released' to 'Costed', return lines are generated automatically
(based on Service Order Control parameters), Obviously it is not possible to receive these items in the same
step in the warehouse, as
this requires a logistical
receipt. This situation leads to
an unbalanced work in
process as long as the item(s) on the return
line(s) are not received in the
warehouse
.
2. A service order material line can generate financial transaction
'Approved for Invoicing' although it is not consumed,
i.e. the material is returned to
the
warehouse
.
This happens in the following
situation:
After a return line is generated for a material (receipt line is present in Warehousing), the
actual quantity is put back from zero to the quantity for which it has been issued
before. As a result of this, the receipt line in
Warehousing is deleted and the 'To Be Delivered
Quantity' on the return line is changed to
zero automatically. Subsequently, the
'To Be Delivered Quantity' on the return line is changed from
zero to the former value and the material is
received in Warehousing.
This results, after setting the
order to 'Costed', in a negative
issue booking as well as a
approved for invoicing booking as can
be seen in session "Integration Transactions by
Project/Order"(tfgld4510
m000)
3. Changing the cost component on a service order
actual material line after the materials have
been issued / received, the original
issue transaction should be
reversed and a new booking
should be made using the new cost component.
This does not happen anymore.
4. When the service order (or activity) has got the status "Released" or "Completed" and a new material line with delivery type "From
Warehouse in Car" or "From Warehouse by Transport" is updated, the warehouse
transactions (inventory commitments) will not be done
during the update of the line. Instead, the error message " Item
'xxxx' not found in warehouse ' '. " is shown
although a correct
warehouse was
defined on the material line.
This error is shown because
the estimation warehouse is used
in order to check and update the
warehouse transactions, but in this case, no
estimation is present.
SOLUTION DESCRIPTION:
1. When changing the status of a Service Order or a Service Order Activity from 'Released' to 'Costed', the service order actual material cost lines
are checked. All material should be issued/received completely. If there are quantity differences, i.e. more material is issued then on the 'From' line
is specified as 'Actual Quantity (tssoc220.adqt), the service order or service order activity first needs to be set to status 'Completed', so return
lines can be generated and can be handled correctly.
2. If non-consumed materials need to be returned to the warehouse, automatically a return line can
be generated (based on Service Order Control parameters). However, the quantity, prices, discounts and/or surcharges regarding the material are
based
on the original line ('From Warehouse' line or 'By Purchase Order' -line). This means that any change of quantity on the original line will result in
a change of quantity on the return line. Therefore, only the fields Warehouse, Planned Delivery and Return Reason are updateable on returns
line that have a line number greater than 5000 (B50b and B50c) or that have the related line number filled (B52a).
3. Changing the cost component on a material line, for which an issue or receipt had already taken place, will result in a negative issue booking
using the old cost component and a positive issue booking for
the new cost
component.
4. Warehouse transactions will be updated in case the
service order/activity is "Released" or "Completed" and
- A new
material line is created
- A material line
with cost line
status "Free" is
updated with a
new - Planned
delivery time (return deliveries),
- Item
code
-
Actual warehouse
code
- Sales
unit
- Sum of
the quantity
delivered &
subsequent
delivery
- A material line is
deleted
- The planned times on the service order or
activity have been changed.
In all these situations, the
estimated warehouse
defined on the material line is
used to check and
update the warehouse
transactions.
In case no estimation is
present for this line,
the actual warehouse
defined on the material
line will be used
in order to check
and update warehouse
orders.

Solution: 130068
SITUATION IDENTIFIED IN:
"Sales Order Line Details" (tdsls4101s200)
SITUATION DESCRIPTION:
When canceling a consignment replenishment backorder in sales the incorrect error message "Warehouse
order/pos.number.seq.number "XX/YY/Z" of origin Sales not found." is shown
SOLUTION DESCRIPTION:
A consignment replenishment backorder can be cancelled or deleted without error messages if the advice for this backorder
is not yet released. The inbound and outbound order line for the corresponding transfer order in warehousing are deleted.

Solution: 130098
SITUATION IDENTIFIED IN:
"Match/Approve purchase invoices" (tfacp2107s000)
SITUATION DESCRIPTION:
The problem occurs when destination sales tax is applicable in the common parameters and an invoice related to orders is
entered with on header level an expensed tax code If not any orderline is matched but the entire amount is posted as costs
in tfacp1133s000 to a ledger account with integration's to for example project, the total cost posted as an integration is
the amount without VAT however the vat is expensed. This creates a difference between Finance and Project for the
expensed VAT amount.
SOLUTION
DESCRIPTION:
The handling is as follows:
In case of an expensed vat with an invoice related to orders and no match is done then if the entire amount is added as a
cost, Baan is posting all expensed VAT to the cost account. In general Baan is posting all vat to the Tax Variance account in
case of an invoice related to order. Now in case a cost account with integrations is used Baan should also post the VAT to the
tax variance account. If the total expensed vat should also be posted to the integrations, a cost invoice should be created.

Solution: 130109
SITUATION IDENTIFIED IN:
"Ledger Accounts By Business Partner Group" (tfacr0111m000)
SITUATION DESCRIPTION:
The session does not allow using the Same Ledger Account for more than one time even though it is not defined as Control
account
SOLUTION DESCRIPTION:
Now the Same General Ledger can be used more than once if not defined as a Control Account

Solution: 130120
SITUATION IDENTIFIED IN:
"Maintain Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Calculation and the posting of VAT are wrong. Wrong VAT code is picked up during Receipt Transaction with Discount.
SOLUTION DESCRIPTION:
The system will now pick up the correct VAT code and so the calculation and posting of VAT will be correct during
Receipt Transaction with Discount.

Solution: 130137
SITUATION IDENTIFIED IN:
"Reconcilaition of payments/receipts" (tfcmg2103s000)
SITUATION DESCRIPTION:
Batch was not balanced when you reconcile the unallocated payment. This problem happens only while selecting the trade
note parameter and in the payment method, if you choose the 'paym.doc.contra' account for document paid step.
SOLUTION DESCRIPTION:
Batch is balanced after reconciliation of the unallocated payment document.

Solution: 130288
SITUATION IDENTIFIED IN:
"Anticipated Receipt Details" (tfcmg2117s000)
SITUATION DESCRIPTION:
It not possible to create manual anticipated receipt document with blank bank code and it is giving ' Fatal Error'.
SOLUTION DESCRIPTION:
-- It is possible to create manual anticipated receipt document with blank bank code.
-- This functionality has been restricted by giving warning message at the time of creation of manual anticipated payment
document with blank bank code. The reason for restricting this functionality is it's not possible to assign the bank code
later to the manual anticipated payment document and not possible to reconcile the document.

Solution: 130334
SITUATION IDENTIFIED IN:
"Reconcile Payments/Receipts" (tfcmg2103s000)
SITUATION DESCRIPTION:
In session "Reconcile Payments/Receipts - tfcmg2103s000", the batch is not balanced in the following situation:
-The payment advice contains negative standing orders
-The parameter "Calculate Tax on Advance Payments/Receipts is set to "yes".
SOLUTION DESCRIPTION:
Now the reconciliation batch is balanced.

Solution: 130610
SITUATION IDENTIFIED IN:
"Post Direct Debits" (tfcmg4257s000)
SITUATION DESCRIPTION:
It is not possible to create new batch during the process of post payments
SOLUTION DESCRIPTION:
Now it is possible to create a new batch during the process of post payments.

Solution: 130667
SITUATION IDENTIFIED IN:
"Post Debits" (tfcmg4257s000)
SITUATION DESCRIPTION:
Reference doesn't appear in the session "Display receipt details"
SOLUTION DESCRIPTION:
Reference will now appear correctly in the session "Display receipt details"
SOLUTION 131313 TOGETHER WITH THE SOLUTION 130667
*******************************************************************************************************
*****************************************
VERSION(S):
B40_c, B50_b, B50_c, B52_a

Solution: 130752
SITUATION IDENTIFIED IN:
"Payment Advices" (tfcmg1120s000)
SITUATION DESCRIPTION:
Tax amount not calculated in Payment Advice for Standing Order of type Advance Payment.
SOLUTION DESCRIPTION:
Tax amount will get calculated now in Payment Advice for Standing Order of type Advance Payment.

Solution: 130754
SITUATION IDENTIFIED IN:
Posting 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:
"Contra-post previous step" can be set as "document cancelled" step.
The error message is not displayed.
Journalizing of Document Cancelled is created correctly.
SOLUTION 131228 AFTER THIS SOLUTION
========================================================
VERSION(S):
B50_b, B50_c

Solution: 130756
SITUATION IDENTIFIED IN:
"Sales invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
Wrong error message when entering a tax code which does not have Posting Data.
SOLUTION DESCRIPTION:
Correct error message will pop up now when entering a tax code, which does not have Posting Data.

Solution: 130933
SITUATION IDENTIFIED IN:
"Reconciliation Payments/Receipts" (tfcmg2103s000)
SITUATION DESCRIPTION:
When the application is locked during reconciliation, message 'Reconciliation in process for this bank and document' is
given. This message is misleading because the reconciliation will not be processed in this case.
SOLUTION DESCRIPTION:
When the application is locked during reconciliation, message 'Reconciliation in process by other user' will be given. This
message indicates clearly that the reconciliation will not be processed.

Solution: 131094
SITUATION IDENTIFIED IN:
"Reconciliation Payments/Receipts" (tfcmg2103s000)
SITUATION DESCRIPTION:
Rejected anticipated documents do not get the status 'Rejected', when the previous status was 'open'.
SOLUTION DESCRIPTION:
Rejected anticipated documents now correctly get the status 'Rejected'.

Solution: 131155
SITUATION IDENTIFIED IN:
Reconciliation of Receipts/Payments (tfcmg2103s000)
SITUATION DESCRIPTION:
1) Currency difference calculated during reconciliation for invoice with Fixed hard
2) Fatal error occurring when reconciling receipt anticipated document for sales and Purchase Invoice adjustment.
3) Reconciliation amount in foreign bank currency is wrong for manual anticipated receipt document.
SOLUTION DESCRIPTION:
1) Currency difference not calculated anymore during reconciliation for invoice with Fixed hard
2) Fatal error is not occurring when reconciling Receipt anticipated document for sales and Purchase Invoice adjustment.
3) Reconciliation amount in foreign bank currency is correct for manual anticipated receipt document.
SOLUTION 131356 ALONG WITH THIS SOLUTION
=============================================================================
VERSION(S):
B50_b, B50_c, B52_a

Solution: 131228
SITUATION IDENTIFIED IN:
"Anticipated document for Notifying" (tfcmgl104s00l)
SITUATION DESCRIPTION:
Empty batch is generated when the document status changed from Document Matured to Document accepted/sent
SOLUTION DESCRIPTION:
Now Batch is created with the correct posting data for the document status changed from "Matured" to "Accepted/sent".

Solution: 157501
SITUATION IDENTIFIED IN:
"Report Orders Completed" (tisfc0120s000)
SITUATION DESCRIPTION:
When completing production orders, Production/Price Variance currency amounts of zero were being posted to finance
although these transactions should be suppressed.
SOLUTION DESCRIPTION:
Production/Price Variance transactions of currency amount zero are no longer posted to finance.

Solution: 157952
SITUATION IDENTIFIED IN:
"Delete WIP Transactions by Project/Order" (tcfin1200m000)
SITUATION DESCRIPTION:
When deleting Work in Process (WIP) transactions using deleting method 'horizon' the session performance was not good.
SOLUTION DESCRIPTION:
When deleting WIP by horizon, the program checks to make sure all the transactions for the project/order are within the
year/period range entered by the user. If any transactions for the project/order lie outside the user entered period range then
the transactions related to it cannot be deleted. This check has been changed to work more efficiently.
It is recommended that deleting method 'project, order' be used whenever possible as this will be faster than using deleting
method by 'horizon'.

Solution: 157979
SITUATION IDENTIFIED IN:
"Rebuild Ledger / Dimension History of Period" (tfgld3206m000)
SITUATION DESCRIPTION:
Ledger account history was not being updated correctly for parent accounts. If a ledger account contained both a statutory
and complementary parent, history was only rebuilt for one of the parent accounts. Also in the same case the dual accounting
indicator was sometimes filled incorrectly.
SOLUTION DESCRIPTION:
The program has been changed so that:
#1 dual accounting indicator is always filled correctly
#2 processing will now be done for both parent accounts and
their parents as well all the way up until
the highest
level.

Solution: 157983
SITUATION IDENTIFIED IN:
"Background Process For Real-Time Document Level Update" (tfgld1201s000)
"Background Process For End Of Session Update" (tfgld1203s000)
"Termination Mode Update (Background)" (tfgld1201s000)
"Rebuild Opening Balance/History from Transactions" (tfgld3203m000)
SITUATION DESCRIPTION:
History tables are updated in transaction currency although the currency analysis of the ledger account is "not required".
According to the table field help text, when a ledger account has currency analysis 'not required' history is only stored in
home currency.
SOLUTION DESCRIPTION:
The programs that update ledger account and dimension history have been modified to store history only in home currency if
the ledger account has currency analysis 'not required'. This will help reduce the size of history tables and improve the
performance of sessions that use history information.

Solution: 157985
SITUATION IDENTIFIED IN:
"Standard Subcontracting Items" (tppdm0513)
SITUATION DESCRIPTION:
When adding a new standard subcontracting item and then deleting it, the same item in the general item data was not
removed.
SOLUTION DESCRIPTION:
Now when adding a new standard subcontracting item and then deleting it, the same item in the general item data is
removed.

Solution: 158006
SITUATION IDENTIFIED IN:
"Display Ledger History - Dim Type Wise Distribution" (tfgld3507m000)
SITUATION DESCRIPTION:
When a ledger account was linked to a multi-dimension budget, and one drilled down from session tfgld3501s000 (Ledger
History) to tfgld3507m000 (Distribution by Dimension type for Ledger Account) one could only see data for one of the
ledger's dimensions. Even though there was data for other dimensions, it was not displayed. This generally happened when
one changed the default selection range values in the session tfgld3503s000 (Change Default Values).
SOLUTION DESCRIPTION:
This problem happened because of incorrect usage of memory within the program. Each time the defaults were changed more
memory was used up. Also, when the budget data was read the dimension type for which it was read was incorrect.
Therefore, between the two problems the session sometimes failed to show any data for a dimension type. Both problems
have been corrected.

Solution: 158098
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
In case of warehouse transfer orders with no shipment procedures, when generate outbound advice is done, the confirm
shipment is done automatically. If there is shortage on outbound quantity during generation of outbound advice, the error
messages are not displayed.
SOLUTION DESCRIPTION:
Now, the error messages are not suppressed. When there is a
shortage on outbound quantity, the error messages are displayed.

Solution: 158099
SITUATION IDENTIFIED IN:
"Maintain Last Used Document Number by Transaction Type Series" (tfgld0114m000)
SITUATION DESCRIPTION:
After a series has been used, it should not be possible to modify the tax year that it has been linked to.
SOLUTION DESCRIPTION:
Now if this session shows a last entered transaction date for a series, it will not be possible to change the tax year.

Solution: 158104
SITUATION IDENTIFIED IN:
"Rebuild Ledger/Dim History - Final/Non Final Trans." (tfgld3203m000)
SITUATION DESCRIPTION:
When using 'Rebuild Ledger/Dim History - Final/Non Final Trans' session (tfgld3203m000), the session does not support the
rebuilding of the general ledger history for individual periods types (fiscal and reporting) independently of each other's period
status. If a fiscal period(s) is 'finally' closed and the reporting period is open - the session does not allow the individual
rebuilding of only the reporting period.
SOLUTION DESCRIPTION:
The 'Rebuild Ledger/Dim History - Final/Non Final Trans" session (tfgld3203m000) has been enhanced to support the
individual rebuilding of fiscal or reporting periods independent of their closing status.

Solution: 158135
SITUATION IDENTIFIED IN:
"Automatic Balancing of Profit and Loss Accounts" (tfgld6202m000)
SITUATION DESCRIPTION:
The session generates an error message, showing that Ledger Account is not in balance, while actually Ledger Account is
in balance. This problem occurs because Opening Balances distributed among Dimensions have not been considered during
checking of Ledger Account.
The session generates a float exception
error. The reason why this error occurs is a division
by zero during calculation of
currency rate.
SOLUTION DESCRIPTION:
Opening Balances distributed among Dimensions have been included in the checking of Ledger Account.
Calculation of currency rate has
been changed to
exclude
situation of division be
zero.

Solution: 158139
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
Item receipt surcharges are posted incorrectly resulting in a positive Work-in-Process under the following conditions:
- The production order was created before the installation of solution 157837 (NB B50_b and B50_c only)
- Item receipt surcharges are added to the ordered item (after order completion and prior to closing).
- The Reset Production-Order Status and the Close Production Orders sessions are then run for the order.
SOLUTION DESCRIPTION:
The session has been corrected and now production orders created with the above conditions are reset and re-closed with
item receipt surcharges posted properly.

Solution: 158168
SITUATION IDENTIFIED IN:
"Global Selection of Batches for Finalization" (tfgld1210m000)
SITUATION DESCRIPTION:
If a user runs the session tfgld1210m000 (Global Selection of Batches for Finalization) and aborts at the device acceptance
screen and then attempts to finalize the created run number in tfgld1111s000 "Select Batches for Finalization", the batch or
batches attached to the run number created from the global finalization will show as selected i.e. the check box "Selected
for Finalization" against these batches will be checked. But if one tabs through the check boxes without doing anything these
boxes get un-checked even though the batches are still selected for finalization in that run number.
SOLUTION
DESCRIPTION:
This problem occurred because when placing the selected batches within a run, the table field to
indicate the batch is 'selected' was not changed to 'yes' by the global finalization session.
Thus when a user tabbed thorugh the form, the displayed value got reset to the value in the table. To correct this problem, now when attaching
batches to a run number in the global finalization process the batches will now have the 'selected' field = 'yes'. Thus the flag will correctly display
when looking/tabbing through the screen containing the batches selected for finalization in (tfgld1111s000) "Select Batches For Finalization"

Solution: 158180
SITUATION IDENTIFIED IN:
"GL Account Matching- Automatic" (tfgld1216m000)
"Close Year" (tfgld6203m000)
SITUATION DESCRIPTION:
When running the session "GL Account Matching Automatic" (tfgld1216m000), it would abort with an error message if a
complementary matching ledger account was not defined in the company parameters even though the company does not use
Complementary ledger accounts.
When running the session (tfgld6203m000) "Close Year", it would give an error message if the complementary currency
translation account was not filled in the company parameters even though the company does not use Complementary ledger
accounts.
SOLUTION DESCRIPTION:
Use of complementary accounts is an option used for accounting for management
information. It is not mandatory to use complementary accounts
so the error checks should only be done if
complementary accounts are used.
The error checks for complementary ledger accounts from the company
parameters are now only done if there are complementary accounts defined in the chart of accounts that will be processed by
the session.

Solution: 158183
SITUATION IDENTIFIED IN:
"Terms of Payment" (tcmcs0113s000)
SITUATION DESCRIPTION:
It is possible to link a Financial Surcharge to a Term of Payment with incoherent dates. As a result, no financial surcharge is
calculated in Central Invoicing.
Terms of Payment has a field 'Average Days'. If a Financial Rate Code is linked to the Terms of Payment, the last date of the
financial rate must be checked with the 'Average Days' field.
SOLUTION DESCRIPTION:
The session will no longer allow a financial rate code to be linked to a payment term when the average days field of the
payment term does not fall within the range of days specified by the financial rate code.

Solution: 158193
SITUATION IDENTIFIED IN:
"Delete WIP Transactions by Project/Order" (tcfin1200m000)
SITUATION DESCRIPTION:
WIP transactions are left behind when archiving shopfloor production orders. This is inconvenient and causes excess storage
of unnecessary data.
SOLUTION DESCRIPTION:
WIP transactions for archived shopfloor production orders are now deleted using the session "Delete WIP Transactions by
Project/Order(tcfin1200m000)".

Solution: 158233
SITUATION IDENTIFIED IN:
"Nonfinalized Transaction Lines" (tfgld1508m000)
"Finalized Transaction Lines" (tfgld1509m000)
"Nonfinalized Transaction" (tfgld3508m000)
"Finalized Transaction" (tfgld3509m000)
SITUATION DESCRIPTION:
The text button was disabled on some forms and enabled in read-write mode on others.
SOLUTION DESCRIPTION:
The text buttons that were disabled have been enabled. Since all the sessions in this solution are display only sessions, all
text buttons have been set to read only mode.

Solution: 158244
SITUATION IDENTIFIED IN:
"Print Chart of Accounts" (tfgld0408m000)
SITUATION DESCRIPTION:
The headings for the columns "Currency Analysis" and "Fixed Asset Integration" are printing too high on the report. They
are printing above the box set up for the column headings.
SOLUTION DESCRIPTION:
The text for the column headings for "Currency Analysis" and "Fixed Asset Integration" have been moved so that they will
print within the box set up for the column headings.

Solution: 158266
SITUATION IDENTIFIED IN:
"Conversion Factors" (tcibd0103m000)
SITUATION DESCRIPTION:
When adding a new conversion factor to an item with inventory, the user cannot change or delete this newly added conversion
factor, even though there have been no transactions on this conversion factor.
SOLUTION DESCRIPTION:
New conversion factors can now be added to an item with inventory and then changed or deleted, if there is no inventory
structure on the item and unit combination.

Solution: 158311
SITUATION IDENTIFIED IN:
"Print Trial Balance - Dimension Code/Ledger Accounts" (tfgld3406m000)
SITUATION DESCRIPTION:
--Parent level ledger accounts have been included in the "Budget Variances" reports grouped by dimensions. Parent ledger
accounts can not have dimensions and thus they can not have actual amounts linked to a specific dimension. But parent
ledger account can have a budget that is distributed among dimensions. Therefore, on the reports grouped by dimensions,
the variance between actual and budgeted amounts of the parent ledger account is always 100%. Moreover, budgeted amounts
of the parent ledger accounts have been added to the totals thus making budgeted totals incorrect.
--On the form there are fields named "Sublevel from" and "Sublevel to" which are used to enter a range of dimension
sublevels. Dimension sublevels can only be one digit long (0-9) but these form fields were two digits in length which gives
users the impression that these fields are ledger account sublevels.
--The Grand Totals of the report "Budget Variances (Dimension/Ledger Account)" (tfgld340612000) were incorrect.
SOLUTION DESCRIPTION:
--Now parent ledger accounts will not be included in the reports, which are grouped by dimensions. However, actual and
budgeted amounts of the parent level ledger account can be seen and compared using the report "Print Trial Balance"
(tfgld3402m000) that is not grouped by dimensions.
--Form fields for dimension sublevels have been changed to contain one only digit.
--Calculation of the dimension totals have been changed on the report "Budget Variances (Dimension/Ledger Account)"
(tfgld340612000) so that the Grand Totals of the report are correct.

Solution: 158330
SITUATION IDENTIFIED IN:
"Close Year" (tfgld6203m000)
SITUATION DESCRIPTION:
If a ledger account has a credit balance then the quantity stored on the ledger account is reported as a negative figure. When
the year is closed and again the quantity on the ledger account is checked it is now reported as a positive figure.
SOLUTION DESCRIPTION:
When writing the opening balance of ledger accounts with a credit balance, the year end session wrote the quantity
incorrectly in the non-finalized transactions table (tfgld102). Thus, wrong figures got stored in the history tables of the
GLD module which would cause financial reports to display the wrong quantity. This has been corrected.

Solution: 158331
SITUATION IDENTIFIED IN:
"Cancel Production Orders" (tisfc0203m000)
SITUATION DESCRIPTION:
When cancelling production orders, instead of being cancelled and deleted, production orders were left with status 'To Be
Deleted'.
SOLUTION DESCRIPTION:
When cancelling production orders, production orders are now correctly cancelled and deleted.

Solution: 158345
SITUATION IDENTIFIED IN:
"Audit Batches" (tfgld1211s000)
"Maintain Journal Vouchers" (tfgld1103s000)
"Maintain Journal Vouchers (Multiple Lines)" (tfgld1115s000)
SITUATION DESCRIPTION:
While finalizing a batch, the check to make sure no blocked dimensions are used in the document, is carried out on the wrong
date. The document date is used to make the check instead of the batch transaction entry date.
SOLUTION DESCRIPTION:
The transaction entry date is now used to check for blocked dimension. This date was already used correctly to check for
blocked ledger accounts.
The same problem existed in the Journal Vouchers sessions. This too has been corrected.

Solution: 158382
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When posting integration transactions to finance, negative amounts are posted to non-finalized transactions when the
transaction type does not allow negative amounts. This happens when posting intercompany integration transactions, where
the two companies have different number of currencies.
SOLUTION
DESCRIPTION:
When posting intercompany transactions, the correct number of home currencies for each company is now determined.
Transactions that do not allow negative amounts now get converted properly in all home currencies.

Solution: 158398
SITUATION IDENTIFIED IN:
"Termination Mode Update (Background)" (tfgld1213s000)
SITUATION DESCRIPTION:
When finalizing a document where the debit and credit lines belong to different reporting periods and the update mode of the
transaction type used is "finalization", the finalization of the batch fails with an error because the batch is un-balanced.
SOLUTION DESCRIPTION:
The background program is invoked during finalization for several tasks one of which is to create inter-period lines so that
the debit and credit balance in each period individually. However, it fails to write one of the lines which creates an
un-balanced batch which cannot be finalized. The problem has been corrected and now inter-period lines are created
correctly.

Solution: 158401
SITUATION IDENTIFIED IN:
"Post Integration Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When posting integration transactions with session (tfgld4201m000) within a company that is setup to not use reporting
periods and is setup to use transaction compression, posted transactions are not compressed in the non-finalized transaction
table tfgld102 (Non-finalized Transactions).
SOLUTION
DESCRIPTION:
The session "tfgld4201m000" (Post Integration Transactions) was erroneously populating the
reporting year on the transaction with the fiscal year. If a company does not use
reporting periods, the reporting year should be 0. This caused a mismatch when
determining if transactions could be compressed as reporting year is
part of the compression criteria. The result was
that transactions would never
compress.
To correct this situation the reporting year will now be written correctly in tfgld102 (Non finalized transactions) if the
company does not use reporting periods.

Solution: 158430
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
When the Print Project Work In Process session is run either for 'By Project' or 'By Project / Department' retroactive
warehouse value adjustment transactions posted against either the project calculation office or against a department were
ignored. Additionally when running the session for 'By Project / Order', price variances posted against a warehouse (in the
case of actual costing) were ignored. Both of these situations resulted in an incorrect amount work in process on the report.
SOLUTION
DESCRIPTION:
The session has been corrected so that all relevant transactions are included in the session's reports.

Solution: 158435
SITUATION IDENTIFIED IN:
"tfgld1440m000" (Print Finalized Transactions by Date)
"tfgld1441m000" (Print Journal)
SITUATION DESCRIPTION:
When printing reports, the total amounts are not printed if they are amounts greater than 16 digits in length . The reports,
instead, print a format overflow sign like "################" for total amounts.
SOLUTION DESCRIPTION:
The totals have been extended to now print 18 digits.

Solution: 158461
SITUATION IDENTIFIED IN:
"Calculate Currency Differences" (tfgld5201m000)
SITUATION DESCRIPTION:
While running the session Calculate Currency Differences, it was possible for transactions to be created in the
Non-finalized Transactions table (tfgld102) for GL accounts and dimensions which have a blocking status of "blocked for all
purposes." This should not be possible as the created batch will give errors when attempting to finalize.
SOLUTION DESCRIPTION:
Checks have been added in the session "Calculate Currency Differences" so that no transactions will be created for any
ledger accounts/dimensions that are blocked for all purposes. An error message will be displayed on the report for these
ledger accounts/dimensions that are blocked.

Solution: 158493
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance" (tfgld4201m000) and "Transactions" (tfgld1101m000)
SITUATION DESCRIPTION:
When posting integration transactions to finance using sessions "Post Integration Transaction to Finance" (tfgld4201m000)
or "Transactions" (tfgld1101m000), sometimes the integration transactions are posted into a non-integration batch.
SOLUTION DESCRIPTION:
The solution prevents the session "Post Integration Transaction to Finance" (tfgld4201m000) from using batch number not
created by integrations in Baan 5c and 5b. In Baan 4c, an additional check has been added to prevent users sharing a
common login from acquiring the same batch number.

Solution: 158504
SITUATION IDENTIFIED IN:
"Create Recurring Transactions" (tfgld1202m000)
SITUATION DESCRIPTION:
When finalizing a batch that was created from 'Create Recurring Transactions (tfgld1202m000)' , the error message "period
status not defined" was always given.
SOLUTION DESCRIPTION:
This error occurred because the tax year was not filled in the batch header information (table tfgld100).
This information is now filled when creating recurring transactions and these transactions can now finalize without error.

Solution: 158526
SITUATION IDENTIFIED IN:
"Journal Vouchers (Multiple Lines)" (tfgld1115m000)
SITUATION DESCRIPTION:
In cases where more than one transaction schedule is used per batch in session Journal Vouchers (Multiple Lines), the user
is always taken back to the first journal after transactions have been created with session Create Transactions from Schedule
(tfgld1204s000).
SOLUTION DESCRIPTION:
Journal Vouchers (Multiple Lines) has been modified to display the newly created transactions.

Solution: 158535
SITUATION IDENTIFIED IN:
"Delete WIP Transactions by Project/Order" (tcfin1200m000)
SITUATION DESCRIPTION:
When deleting WIP transactions for already archived production orders and projects, the project and production order
numbers do not appear on the report.
SOLUTION DESCRIPTION:
For all projects and production orders where WIP transactions are being deleted, the production order and project numbers
will appear on the report.

Solution: 158536
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
When an item receipt surcharge is added to a production item, after a production order is created for the item and materials
are issued for the order without backflushing, the surcharge is incorrectly posted for a quantity of one instead of the entire
ordered quantity upon closing the order. This results in incorrect variance postings during closing.
SOLUTION
DESCRIPTION:
The Close Production Orders session has been corrected and item receipt surcharges are now posted for the entire quantity
ordered, providing correct variance postings.

Solution: 158561
SITUATION IDENTIFIED IN:
"Journal Vouchers" (tfgld1103s000)
SITUATION DESCRIPTION:
When entering a Journal Voucher via the session "Journal Vouchers" (tfgld1103s000), the system does not pick up the
default document series set for the Transaction Type. This happens when the localization parameter "VAT Book" is turned
ON.
SOLUTION DESCRIPTION:
The session now picks up the correct default document series when creating a new document.

Solution: 158589
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
Although a Production/Price Variance transaction of amount zero is not posted to the finance Integration Lines Debit table
(tfgld410), a posting is incorrectly made to the Additions to Integration Transactions table (tfgld415) with errant data.
SOLUTION DESCRIPTION:
The financial integration between manufacturing and finance has been corrected and now Production/Price Variance
transactions of amount zero do not result in an incorrect finance record in the Additions to Integration Transactions table
(tfgld415).

Solution: 158596
SITUATION IDENTIFIED IN:
"Display Ledger History - Dim Type Wise Distribution" (tfgld3507m000)
SITUATION DESCRIPTION:
The session tfgld3507m000 (Display Ledger History - Dim Type Wise Distribution) is not displaying budget information.
SOLUTION DESCRIPTION:
The session had a problem while querying for budget data. It has been corrected.

Solution: 158599
SITUATION IDENTIFIED IN:
"Inventory-Inspection Data" (whinh3122s000)
SITUATION DESCRIPTION:
Unable to reject part of receipt quantity for project warehouses
SOLUTION DESCRIPTION:
System no longer requires that approved and rejected quantites comprise the entire receipt.

Solution: 158621
SITUATION IDENTIFIED IN:
"Print Finalized Transactions by Ledger Account" (tfgld1406m000)
"Print Finalized Transactions by Dimension/Ledger" (tfgld1407m000)
"Print Finalized Transactions by Date" (tfgld1440m000)
"Print Journal " (tfgld1441m000)
SITUATION DESCRIPTION:
When the session is run as a Job, the rotate currency functionality does not work. The reports are printed in the home
currency instead of the currency set when creating the job.
SOLUTION DESCRIPTION:
Changes have been made to get the proper currency when printing in job mode.

Solution: 158666
SITUATION IDENTIFIED IN:
"Process Commission/Rebate" (tdcms2201m000)
SITUATION DESCRIPTION:
When running session "Process Commission/Rebate"(tdcms2201m000) getting the following:
FATAL ERROR: Illegal number of args (48) for function tfint.dlltfgld.write.integr.transactions.easy expected 57.
SOLUTION DESCRIPTION:
Changed the integration librarys to send the necessary number of arguments between functions. This will stop the Fatal
Error from happening.

Solution: 158683
SITUATION IDENTIFIED IN:
"Print Trial Balance - Dimension Code/Ledger Accounts" (tfgld3406m000)
SITUATION DESCRIPTION:
Problem # 1: Reports have been ordered neither by ledger account sequence number nor by dimension sequence number.
Problem # 2 (Only in Baan5c):During running of the session "Print Trial Balance - Ledger Account/Dimensions"
(tfgld3404m000) progress indicator has never reach 100%.
SOLUTION DESCRIPTION:
Problem # 1: Reports are ordered by sequence numbers.
Problem # 2: Maximum value of the progress indicator is set to 100%.

Solution: 158692
SITUATION IDENTIFIED IN:
"Integration Transactions by Document Line" (tfgld4512m000)
"Non-Finalized Transations" (tfgld3508m000)
"Finalized Transations" (tfgld3509m000)
SITUATION DESCRIPTION:
When running the session Ledger History (tfgld3501s000) in a company and on the default parameters one specifies a
different company, then it is not possible to mark a finalized line in session Finalized Transactions (tfgld3509m000) or
Non-Finalized Transactions (tfgld3508m000) and view the integration details in session Integration Transactions by
Document Line (tfgld4512m000).
SOLUTION DESCRIPTION:
This problem happened because the current company number was sent to the session Integration Transactions by Document Line
(tfgld4512m000) instead of the one specified by the user in the defaults session (tfgld3503s000). Thus, the session was not
able to retrieve the correct data for display. This has been corrected.

Solution: 158757
SITUATION IDENTIFIED IN:
"General Item Data" (tcibd0101s000)
SITUATION DESCRIPTION:
When changing the item group in "General Item Data", the item group is not updated in the "Item Supplier Info". This is
working correctly in standard, but is not working in the Japanese Localization.
SOLUTION DESCRIPTION:
The Japanese Localization of "General Item Data" is now properly working, such that when the item group is changed, it is
also updated in the "Item Supplier Info".

Solution: 158811
SITUATION IDENTIFIED IN:
"Ledger Accounts by Bussiness partner Group" (tfacp0111m000) / (tfacr005m000 )
SITUATION DESCRIPTION:
Even when the dimensions are present in tfacp005, they were not visible in this session , when the dimension usage is
switched off in Maintain Ledger Accounts.
SOLUTION DESCRIPTION:
Now, when the dimension usage is switched off in the Maintain Ledger Accounts ( tfgld008 ), then the dimensions present in
the Bussiness partner group table will still be visible, but will not be accessible.

Solution: 158838
SITUATION IDENTIFIED IN:
"Journal Vouchers (Multiple Lines)" (tfgld1115m000)
SITUATION DESCRIPTION:
The form field "D/C" (Debit/Credit) did not get updated automatically while working with BI interface. Because of this, the
user had to select the correct value manually. This problem occurred because BAAN changed the value of the field but did
not refresh the form.
SOLUTION DESCRIPTION:
Now the form field "D/C" (Debit/Credit) is updated explicitly each time its value changes.

Solution: 158849
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When running the Compose/Print/Post Invoices session (cisli2200m000) for Service-Material, the source type for the invoice
was being set to Sales rather than to Service when updating the Vertex register. This led to incorrect tax amounts being
written to the register.
SOLUTION
DESCRIPTION:
The source type for the invoice is now being set correctly to Service so that the Vertex register is updated correctly.

Solution: 158916
SITUATION IDENTIFIED IN:
"Global Approval of Commissions/Rebates" (tdcms0250m000)
SITUATION DESCRIPTION:
Poor performance has been found in the "Global Approval of Commissions/Rebates" (tdcms0250m000) session. This due to
the way the history records are updated/created.
SOLUTION DESCRIPTION:
The "Global Approval of Commissions/Rebates" (tdcms0250m000) session has been modified to more efficently update the
history records, therby increasing the overall performance of the session.

Solution: 158917
SITUATION IDENTIFIED IN:
"Create Transactions from Scheme" (tfgld1204s000)
SITUATION DESCRIPTION:
In case of VAT "Partially Undeductible" the system doesn't take the right account. This happens only in case the lines are
prepared using Transaction Schedules and if the Tax calculation is at the line level. If the lines are manually entered on the
lines the cost account is picked up correctly.
SOLUTION
DESCRIPTION:
The problem was being caused because the session
tfgld1204s000 did not have any code in there to check
& assign the cost account for non deductible
VAT. This code has been added to the script for both
Singular as well as Multiple VAT
code lines.

Solution: 158920
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When running the Compose/Print/Post Invoices session (cisli2200m000) for a billing request which contains both sales and
service orders, the source type for the sales order will be incorrect if the Vertex register is updated for the service order
first. This led to incorrect tax amounts being written to the register for the sales order.
SOLUTION
DESCRIPTION:
The source type for the invoice is now being set correctly for both types of orders, so that the Vertex register is updated
correctly.

Solution: 158944
SITUATION IDENTIFIED IN:
"Rebuild Opening Balance/History from Transactions" (tfgld3203m000)
SITUATION DESCRIPTION:
The non-finalized credit amount in home currency was not being updated correctly in the History - Dimension/Ledger Account
Totals table (tfgld202). The debit amount was being updated when the transaction line was a debit or a credit.
SOLUTION DESCRIPTION:
The non-finalized amount in home currency is being updated correctly in the History - Dimension/Ledger Account Totals
table (tfgld202) for both debits and credits.

Solution: 158961
SITUATION IDENTIFIED IN:
"General Item Data" (tcibd0101s000)
SITUATION DESCRIPTION:
>>Problem: The item signal is not displayed.
>>Location: In the single occurrence session of "General Item Data".
>>Conditions: While accessing general item data from DEM (dynamic enterprise modeler) in "display only" mode.
>>Cause: Signals are only displayed in "maintain" mode for general item data. There is no provision for displaying item
signals when in "display only" mode.
SOLUTION DESCRIPTION:
>>Resolution: The item signal is now shown properly in either "maintain" or "display" mode.
>>Location: In the single occurrence session of "General Item Data".
>>Conditions: While accessing general item data from DEM (dynamic enterprise modeler) in "display only" mode.

Solution: 158977
SITUATION IDENTIFIED IN:
"Tax Code Lines" (tfgld1109s000)
SITUATION DESCRIPTION:
1) The ledger account and dimension fields are disabled if Destination Tax (tccom999.dstx) = No.
2) If the tax amount is changed in the Tax Code Lines (tfgld1109s000) then the Tax amount in Purchase Invoice Transaction
Lines (tfacp1120s000) was getting set to zero.
The second issue is only valid for the localization VRC's where the parameter "Generic Taxes" (tccom936.gtcd.l) is turned
on.
SOLUTION DESCRIPTION:
1) The session has been changed to allow the user to edit the Ledger Account field irrespective of the Destination tax
parameter value.
2) If the user changes the tax amount in the tax code lines then the change will be reflected in the calling session.

Solution: 158979
SITUATION IDENTIFIED IN:
"Journal Vouchers (Multiple Lines)" (tfgld1115m000)
SITUATION DESCRIPTION:
The following applies to a company having a dependent currency system with the local currency not equal to the reference
currency and a rate factor not equal to 1. When a journal voucher is entered in the local currency, an error message
(Document Currency and Home Currency are the same, so Rate must be 1.0) is displayed saying that when the document
currency and the home currency are the same, the rate factor should be 1.
SOLUTION DESCRIPTION:
The check on the rate factor is now performed only
when the currency system is not dependent.

Solution: 159037
SITUATION IDENTIFIED IN:
"Create Transactions from Schedule" (tfgld1204s000)
SITUATION DESCRIPTION:
Documents are not balanced when generating transactions using a transaction schedule. The message: "Document not
balanced" is given when attempting to exit the session.
SOLUTION DESCRIPTION:
Rounding was not being done when there were multiple lines on the transaction schedule and the total for these lines was less
than the entered transaction amount. Rounding was only being done if the total of the lines was greater than the entered
transaction amount and was ignoring if the total was less than the transaction amount. Now amounts will be rounded in both
cases (where the total of the lines is either greater than or less than the entered transaction amount) to ensure the document is
balanced.

Solution: 159115
SITUATION IDENTIFIED IN:
"Purchase-Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
When trying to delete a PO line with status 'Awaiting Receipts' in warehousing, fatal error 111 is generated.
SOLUTION DESCRIPTION:
Altered the manner in which deletions of the order advice line is handled to ensure proper deletion without errors.

Solution: 159128
SITUATION IDENTIFIED IN:
"Print Tax Analysis" (tfgld1420m000)
SITUATION DESCRIPTION:
Transactions with multiple tax were not printed correctly on the reports. A single line was being printed for the total of the
taxes and the net amount in home currency was incorrectly printed as zero.
SOLUTION DESCRIPTION:
The report layout has been modified so that transactions with multiple tax will generate a separate line for each tax and the
correct amount in home currency will be displayed.

Solution: 159135
SITUATION IDENTIFIED IN:
"Perform Rounding Difference Adjustment" (tfgldl233m00l)
SITUATION DESCRIPTION:
When running the session or compiling the program script an illegal number of arguments error was given. This occured
after installing solution 124194.
SOLUTION DESCRIPTION:
The script has been changed to be able to work with the changes made by solution 124194.

Solution: 159136
SITUATION IDENTIFIED IN:
"Addresses" (tccom4130m000)
SITUATION DESCRIPTION:
When using a tax provider, the user was constantly prompted to provide a valid GEO code even if a valid one was already
present.
SOLUTION DESCRIPTION:
When using a tax provider, a user is only prompted for a GEO code if the country, city, state or postal code is changed or if
the user chooses to change.

Solution: 159139
SITUATION IDENTIFIED IN:
"Chart of Accounts" (tfgld0108s000)
SITUATION DESCRIPTION:
Problem #1- The user is unable to change the sublevel of a ledger account once the account has been used. This
functionality was present in prior BAAN versions (B40_c).
Problem #2- There was an error message that indicated that a parent and child ledger account can not have the same sublevel
but the program was allowing this.
Problem #3- There was an error check to make sure that a ledger account can not have its sublevel changed to be less than any
of its children's sublevel. There was no check to make sure that an account sublevel can not be changed to greater than its
parent.
SOLUTION DESCRIPTION:
-Changes have been made to allow ledger account sublevels to be changed if the account is used. It is not allowed to change
a 0 level account or change a parent to a 0 level if the account has been used. Also extra checks have been added so that
this process will work with complementary accounts.
-Programming has been added so it is no longer allowable to put a parent and its child with the same sublevel.
- A check has been added to make sure that when changing an account sublevel that the new sublevel can not be more than or
equal to its parent's sublevel.

Solution: 159248
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
Erroneous financial integration entry was created for a cost component of type operation when shipping more than one line
for consignment inventory.
SOLUTION DESCRIPTION:
Changes made so that only the proper financial integration entries are create for type operation.

Solution: 159298
SITUATION IDENTIFIED IN:
"Finalization Run number" (tfgld1519m000)
SITUATION DESCRIPTION:
In case when transaction type update mode is "Real time" or "End of session" and document contains Tax, it was not
possible to finalize the batch because document was not balanced in one of the home currencies.
SOLUTION DESCRIPTION:
Now user will be able to finalize batch and finalization process will generate the correct rounding difference lines to
balance document in all home currencies.

Solution: 159334
SITUATION IDENTIFIED IN:
"Addresses" (tccom4130m000)
SITUATION DESCRIPTION:
When there is only one GEO code for a country, city, postal code, and state, no check is done to see if the GEO code is for
sales and use.
SOLUTION DESCRIPTION:
When only one GEO code exists for a country, city, postal code, and state, a check is done to see if the GEO code is fro
sales and use. If the GEO code is not valid for sales and use, the record cannot be saved.

Solution: 159354
SITUATION IDENTIFIED IN:
"Automatic Balancing of Profit and Loss Accounts" (tfgld6202m000)
SITUATION DESCRIPTION:
#1- Error messages were given when attempting to balance profit & loss accounts because there were opening balance
transactions to these accounts.
#2- If the process aborted because of errors, there was no way to run the session again without the use of general table
maintenance to remove the batch created before the errors were encountered.
SOLUTION DESCRIPTION:
#1 Profit & Loss accounts should never have an opening balance. It was found that if there was a rounding difference on an
opening balance batch that this rounding difference was posted into the account specified in the company parameters which is
a P&L account. Now the rounding difference account will not be used for opening balance transactions instead the last account
of the transaction will be used to store the rounding difference.
#2- Changes have been made to the session (tfgld6202m000) "Autobalancing of profit and loss" so that if the program errors
out that it can be rerun and the prior aborted batch will be removed automatically.

Solution: 159356
SITUATION IDENTIFIED IN:
"Calculate Currency Differences" (tfgld5201m000)
SITUATION DESCRIPTION:
When running the session tfgld5201m000 (Calculate Currency Differences) if the report is executed a second time without
exiting and re-entering the session, the ledger account description may be incorrect.
SOLUTION DESCRIPTION:
The session will now produce the correct ledger account description with multiple runs.

Solution: 159439
SITUATION IDENTIFIED IN:
"Post Integration to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When using session tfgld4201m000 (Post Integration Transactions to Finance) or other sessions that are capable of creating
transactions to finance, if the integration parameter (tfgld4150s000) "Posting to Next Open Period Allowed" is set -
transactions can be posted into closed periods.
SOLUTION
DESCRIPTION:
The process tfglddll4010 (Write transactions in integration tables)
has been modified to properly handle posting
transactions to the correct period.

Solution: 159507
SITUATION IDENTIFIED IN:
"Print Integration Transactions" (tfgld4410m000)
SITUATION DESCRIPTION:
The following problems were reported in the session.
1. (B40c only) If a non-existing company is entered in the session and one tries to zoom on the order field then a
runtime BW error 506 Table tfgld000XXX does not exist is given where XXX is the company entered.
2. When (Graphical User Interface only) no 'from' and 'to' Transactions Origin are specified and a user tries to zoom on the
order field, a message is given saying "No Zoom Session defined". After the "OK" button is clicked, the mouse pointer
remains at hourglass indicating that the system is busy when actually it is waiting for customer input.
3. When zooming on order number, orders for the wrong company were displayed. This happens when the original company
specified is not the company from which the session is being run in.
SOLUTION
DESCRIPTION:
1. A check has been added to the program to make sure a valid company is entered by the user. If the user does not have
authorizations to the company or the company does not exist then an error message is displayed.
2. It is only possible to zoom on the order field of this session if the from original company = to original company and from
transaction origin = to transaction origin. When these conditions are not satisfied, the session will not zoom.
3. Changes have been made to the program so that it will now
display orders/projects from the 'from
company' on the form.

Solution: 159526
SITUATION IDENTIFIED IN:
"Import Journal Vouchers by Batch ID Number" (tfgld2215m000)
SITUATION DESCRIPTION:
When importing journal vouchers with session tfgld2215m000 (Import Journal Vouchers by Batch ID Number), if any of the
transaction lines have errors, then only lines which do not have errors are imported into the General Ledger. In such a
situation the interim tables were also cleared forcing the user to re-import data into Baan and cleaning up the data which
was successfully imported into the General Ledger.
SOLUTION DESCRIPTION:
An audit capability has now been implemented in this session. The audit will
allow users to validate an import batch before the journal voucher
transactions are actually loaded into the General Ledger. The
audit will produce a detailed error report and allow
users to make corrections to import data.
Further, a progress indicator has been added to
provide visual feedback on the
import process.

Solution: 159546
SITUATION IDENTIFIED IN:
"Print Trial Balance" (tfgld3402m000)
SITUATION DESCRIPTION:
Additional flexibility is needed in the Trial Balance session to allow the user to input both a complementary and statutory
sublevel print range.
SOLUTION DESCRIPTION:
With Solution 159546, modifications have been made to the sessions Print Trial Balance (tfgld3402m000) and Print Trial
Balance by Currency (tfgld3403m000), which will increase the flexibility of the reports. These modifications will only
directly impact those customers that are utilizing the dual accounting functionality in their general ledger set up. This
functionality allows users to define their accounts as either statutory(for fiscal reporting) or complementary(for management
reporting).
The following are the characteristics of these accounts: complementary
accounts defined as sublevel 0 can only be linked to a complementary
parent. Statutory accounts defined as sublevel 0 can be linked to either a
complementary or a statutory parent (or both). This means that a parent level complementary account can carry a balance
that is made up of both complementary and statutory activity.
When running these sessions, it is possible for the user to indicate that they want to print
statutory balances, complementary balances, or both balances for specified ledger accounts.
With this enhancement, when the user specifies that they want to print both, it is now
possible for them to specify a sublevel range for both complementary and
statutory accounts. The link below is to an Excel document that
contains examples of the output you can expect when printing both, complementary only, or statutory only.
ftp://ftp.support.baan.com/updates/Documents/SOL159546Examples

Solution: 159615
SITUATION IDENTIFIED IN:
"Period Status" (tfgld0107m000)
SITUATION DESCRIPTION:
When using session tfgld0107m000 (Period Status) to modify a period status, it was possible to set the status of ACR, ACP,
CMG, or INT to "open" and then set the status of GLD to "closed " and save. The session allowed this if the module status
was not saved between individual module status changes.
SOLUTION DESCRIPTION:
The session tfgld0107m000 (Period Status) will now prevent a module status from being set to "open" if the GLD status has
been set to "closed".

Solution: 159625
SITUATION IDENTIFIED IN:
"Business Partners" (tccom4500m000)
SITUATION DESCRIPTION:
In the specific multi company setup, where the 'Business Partners' (tccom100) table is shared between the logistical and
finance companies and some or all of the roles by business partner tables are not shared, the 'Search Key' (seak) field was
not updated in all linked companies in the roles by business partner tables when changing it for a business partner.
SOLUTION
DESCRIPTION:
The 'Search Key' (seak) field is now updated in all linked companies in the role by business partner tables when changing it
for a business partner.

Solution: 159635
SITUATION IDENTIFIED IN:
"Chart Of Accounts" (tfgld0108s000)
SITUATION DESCRIPTION:
It was not possible to change the print sequence for parent ledger accounts when transactions existed for the account. An
error was given 'Ledger account present in history'.
The error was given because of an incorrect check on sublevel even though the account sublevel was not changed.
SOLUTION DESCRIPTION:
It its now possible to change print sequence even if there are transactions made to the ledger account.

Solution: 159638
SITUATION IDENTIFIED IN:
"Generate Subcontracting Purchase Orders" (tisfc2250m000)
SITUATION DESCRIPTION:
When processing a production order for an item, that includes in its bill of materials a phantom item with a subcontracted
operation, the session Generate Subcontracting Purchase Orders (tisfc2250m000) incorrectly creates a purchase order for
the quantity of the end item and not the quantity of the phantom component.
SOLUTION
DESCRIPTION:
Now when the Generate Subcontracting Purchase Orders session is run under the conditions above, the resulting purchase order is correctly
created for the quantity of the phantom item in the production item's bill of materials. Additionally, estimated end item unit costs, operation
costs, completion and variance posting calculations have been modified to reflect the correct subcontracting quantity.

Solution: 159646
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When Vertex is unable to calculate tax during the compose process, no exception report is given or the error message given
in the exception report is incorrect. This was due to the error message not being populated when tax cannot be calculated.
SOLUTION DESCRIPTION:
The error message is now populated with a message indicating tax cannot be calculated, so the exception report is generated
with the correct message.

Solution: 159735
SITUATION IDENTIFIED IN:
"Saes-Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Allocated quantity for item with lot by unit allow to exceed one.
SOLUTION DESCRIPTION:
Changed to reject order lines that would increase either the allocated or on order values beyond one for an item which is lot
controlled by unit.

Solution: 159746
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
For Baan 5b customers in Japan, the Work Center and Main Work Center fields need to be filled for all production variance
transactions posted to finance, regardless of the inventory valuation method used.
SOLUTION DESCRIPTION:
All production variance transactions posted to finance will now have the fields Work Center and Main Work Center filled
within the Japanese localization of Baan 5b.

Solution: 159816
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
In finance you can choose which ledger accounts you want to map your financial integrations to. It is possible to map the
production/completion integration to the warehouse. The warehouse is not being populated when logging financial
integrations for production/completion. Therefore, the user receives and error message when posting to finance.
SOLUTION
DESCRIPTION:
The warehouse is now being populated with the main warehouse of the SFC production order on the integration. This allows
for proper mapping when posting to finance.

Solution: 159850
SITUATION IDENTIFIED IN:
"Create Transaction Schedules" (tfgld1204m000)
SITUATION DESCRIPTION:
Tax amounts are incorrect for invoices generated via transaction scehdules. This happens only if the invoice has multiple tax
lines.
SOLUTION DESCRIPTION:
Wrong amount was being passed to the function calculating tax amount. This has been fixed.

Solution: 159887
SITUATION IDENTIFIED IN:
"General Item Data Defaults" (tcibd0502m000)
SITUATION DESCRIPTION:
When copying the general item data defaults, the existing sub entity defaults are not copied.
SOLUTION DESCRIPTION:
Now when copying the general item data defaults, the existing sub entity defaults are copied.

Solution: 159888
SITUATION IDENTIFIED IN:
"Maintain Transactions" (tfgld1101m000)
SITUATION DESCRIPTION:
Batch numbers are not incremented correctly which can lead to a couple of problems
1. Batches belonging to different users could get combined into a single batch.
2. Error message "Transaction already finalized" is given while trying to insert a transaction type for a new batch.
This problem would occur if a user enters a batch header then chooses to change to a different batch header, but does not
have permissions for any other batch. The control would stay with the newly entered batch header. If the user creates
transactions in this batch, the system does not recognize it as a new batch.
SOLUTION DESCRIPTION:
Changes have been made in the program so that batch numbers are incremented correctly.

Solution: 159889
SITUATION IDENTIFIED IN:
"Print Tax Summary by Tax Authorities" (tfgld8401m000)
SITUATION DESCRIPTION:
Transactions with multiple shifted tax are not printed properly on the report. The amount in home currency is sometimes
showing as a negative, and the transaction lines are not sorted correctly by tax authority.
SOLUTION DESCRIPTION:
Made modifications to ensure that the amounts are written as positive in the tax analysis table (tfgld110) and have added logic
to find the correct tax authority for each transaction line. Also added a field to enable the user to specify whether or not they
want to see the contra for shifted tax in the report.

Solution: 159903
SITUATION IDENTIFIED IN:
"Rebuild Opening Balance/Dimension History form Transactions" (tfgld3203m000)
SITUATION DESCRIPTION:
The Opening Balances - Combination of Dimension/Ledger/Currency table (tfgld206) is not generated for certain ledger
accounts. The cause of the problem was that the fiscal year of the non-finalized transactions was being used when updating the
table for the finalized transactions.
SOLUTION DESCRIPTION:
The fiscal year of the finalized transactions is now being used when updating The Opening Balances - Combination of
Dimension/Ledger/Currency table (tfgld206) for the finalized transactions.

Solution: 159948
SITUATION IDENTIFIED IN:
"Print Tax Report by Tax Position/Country Group" (tfgldl407m00l)
SITUATION DESCRIPTION:
1) The "Net Amount" totals in the layout "Total for tax Position Line" in the "Document Detail" report was incorrect .
2) The "Tax Amount" field did not print entirely on the reports "Tax Report by Tax Position/Country Group" & "Tax
Report by Tax Position/Country Group (Document Detail)" .
SOLUTION DESCRIPTION:
1) The total field was getting reinitialized before the tax position line changed and this was causing the total to be incorrect.
This has been fixed in the program script.
2) The report width for the above 2 reports was 132 but the layouts lengths were more than that. The report width has been
changed to 145.

Solution: 159958
SITUATION IDENTIFIED IN:
"Archive / Purge Finance Transaction " (tfgld6205m000)
SITUATION DESCRIPTION:
The internal memory of session "Archive / Purge Finance Transaction" (tfgld6205m000) may become full and cause the session
to hang. This can occur when a large number of transaction lines are processed within a single batch. The session held the
entire batch in memory until the archive / purge process was complete before doing a database update.
SOLUTION
DESCRIPTION:
The session now updates the archived / purged
transactions more frequently within the database.
This reduces the amount of memory required by the archiving
process and allows large batches to be archived successfully.

Solution: 159975
SITUATION IDENTIFIED IN:
"Rebuild Opening Balance/History From Transactions" (tfgld3203m000)
SITUATION DESCRIPTION:
When rebuilding history the following problems occurred:
Problem #1 (Japanese Specific)- When rebuilding finalized transactions, the history tables for "Daily Balance Monitoring"
were updated without filling the date.
Problem #2(Japanese Specific)- When rebuilding non-finalized transactions the history tables for "Daily Balance
Monitoring", were updated with the wrong date. Records were created based on the batch date when history should be
based on the document date.
Problem #3 (Japanese Specific)- History tables for 'Inventory Ledger Management' were updated without filling fields
warehouse, item, and department.
Problem #4- The session displays information on the screen to indicate to the users what information is being processed.
When processing finalized transactions, the batch number was always printed on the screen as 0 .
SOLUTION DESCRIPTION:
#1- Localization specific history tables for daily balance monitoring are now updated with the correct date when rebuilding
history.
#2- Non-finalized transactions are now placed in the daily balance history tables based on the document date and not the
batch date.
#3- Inventory Ledger history is now created with the warehouse, item, and department.
#4- Batch number is now displayed correctly on the screen when rebuilding finalized transactions.

Solution: 159984
SITUATION IDENTIFIED IN:
"Recurring Transaction Details" (tfgld1517s000)
SITUATION DESCRIPTION:
When creating Recurring Transaction Instructions in a multi-site environment, the check for whether a period is defined
and not finally closed is done for the group company. The check should be done for the current company.
SOLUTION DESCRIPTION:
The check is now performed for the current company.

Solution: 160046
SITUATION IDENTIFIED IN:
"Print Tax Analysis" (tfgld1420m000)
SITUATION DESCRIPTION:
The report totals for some of the layouts for "Tax Analysis by Tax Authority", "EU Tax Handling by Tax Period", "EU Tax
Handling by Fiscal Period" and "EU Tax Handling by Tax Authority" were printing incorrect values.
SOLUTION DESCRIPTION:
The "aggregate conditions" on the reports has been changed so that all the total fields have consistent conditions. The totals
will print correct values.

Solution: 160059
SITUATION IDENTIFIED IN:
"Rebuild Ledger/Dimension History of Period" (tfgld3206m000)
SITUATION DESCRIPTION:
When running the rebuild session, unnecessary history records are being created for the tax period type.
SOLUTION DESCRIPTION:
The functionality to rebuild tax period history has been removed. History is not stored for tax period types, it is only stored
for Financial and Reporting period types. Unnecessary records will no longer be created in the history tables by this session.

Solution: 160072
SITUATION IDENTIFIED IN:
"Maintain Transactions" (tfgld1101m000)
SITUATION DESCRIPTION:
When the session is started but there is not a batch in the current fiscal year to display, the session automatically begins the
process of creating a new batch header. If the user hits the previous group key at this point, the header of a new batch is
created rather than displaying an existing batch in the previous year should one exist. The group keys are not functioning
properly.
SOLUTION
DESCRIPTION:
If the user hits a group action key when starting the session with no batches to display for the current fiscal year, the group
action key will work as it should.

Solution: 160172
SITUATION IDENTIFIED IN:
"Print Tax Analysis" (tfgld1420m000)
SITUATION DESCRIPTION:
1) If the report "Print Tax Analysis by Tax Authority" is printed for a multiple tax code only the first line prints the "Net
Amount in HC". All the subsequent lines print 0.
2) The tax authority field was not printing in reports Print Tax Analysis by Tax Code, Print Tax Analysis by Fiscal Year and
Print Tax Analysis by Tax Authority in case of multiple tax codes.
3) In report Print Tax Analysis by Fiscal Period, the Grand Total was not printing the correct total for the field "Net
Amount in HC". This problem was only in B50_b version.
SOLUTION DESCRIPTION:
1)The net amnt in HC will now be printed for all the tax code lines, but only the first line (tfgld110.sern = 1) amount will be
included in the total. The other lines will be marked with an asterisk (*) on the report and a note will be added in the footer
denoting that those lines are not included in the calculation of the total.
2) The tax authority will print correctly on all the reports.
3) Necessary changes have been made to calculate the grand total correctly.

Solution: 160245
SITUATION IDENTIFIED IN:
"Audit Batches" (tfgld1211s000)
SITUATION DESCRIPTION:
#1- When closing the year (tfgld6203m000) if the created batch contained an entry to a dimension that was blocked for all
input, the created opening balance batch would give an error 'dimension is blocked' when attempting to finalized the batch.
#2- When closing the year (tfgld6203m000) if the update mode of the transaction is 'real time' or 'end of session' and the
year-end-close batch contained an entry to a ledger account that was blocked for all input, the created opening balance
batch could not be finalized as the message 'background process not complete' was given when selecting the batch. This
occurred because the background program would not finish due to the blocked ledger account.
#3- Transactions created by the "Automatic Balancing of Profit and Loss Accounts" (tfgld6202m00) could not be finalized if
the created batch contained entries to ledger accounts or dimensions that were blocked for all input.
SOLUTION DESCRIPTION:
#1- The audit program that is run when finalizing batches (tfgld1211s000) has been changed so that the error check for
blocked dimensions is not done for opening balance transactions. The reasoning behind this is that these entries are simply
transfering the existing balances to the new year, and are not a result of any new activity on the dimension.
#2- The background programs called for update mode "end of session" (tfgld1203s000) and update mode "real
time"(tfgld1201s000) have been modified so that error checks for blocked ledger accounts are no longer done for opening
balance transactions.
#3- The audit program that is run when finalizing batches (tfgld1211s000) has been changed to not check for ledger account or
dimension blocking when the transaction type is equal to the transaction type for autobalancing in the company parameters
(tfgld004.taut). This part of the solution does not apply to versions lower than B40_c as this field did not exist prior to
B40_c.

Solution: 160271
SITUATION IDENTIFIED IN:
"Print Periodic Journal Report" (tfgld1411m000) in B40_c, B50_b, B50_c
"Print Journal Report - Belgium" (tfgld1442m000) in B52_a
SITUATION DESCRIPTION:
When printing Journal Report for Belgium, it is not possible to print the report for more than one finance company
belonging to the same finance group.
SOLUTION DESCRIPTION:
Now it is possible to print the Journal Report for Belgium either for the current company or for all companies belonging to
the same finance group, with the new option "Print All Companies". The reports print the finance company number on the
detail line.

Solution: 160280
SITUATION IDENTIFIED IN:
"Generate Invoice by Self Billing" (tfacp2290m000)
SITUATION DESCRIPTION:
When generating self-billed invoices for a packing slip range, if one of the orders in the range has an error no invoices are
generated for the orders without errors.
SOLUTION DESCRIPTION:
Now invoices will be generated for the orders in the range which do not have errors.