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

Solution: 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: 120949
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260m000)
Report group 3, "Checks" (rtfcmg126031000) - [B40L_c_fre0]
Report group 22, "Check printout for France" (rtfcmgL2521100L) - [B50_b and B50_c]
"Print Forwarding Notes" (tdsls4421m000)
SITUATION DESCRIPTION:
Two main sessions exist that display amounts in words:
* In the subsession 'Transfer Payments' (tfcmg1260m000), payments can get transferred to cheques. On these cheques, the
amount is presented both in digits and in words.
* In the session "Print Forwarding Notes" (tdsls4421m000), bills of lading can be printed. When "Cash on Delivery" has been
selected as the type of bill of lading, the amount to be received is printed in words as well.
In the sessions mentioned above, the following things go wrong:
1. With the French language selected, the word 'sept' in front of the hundreds is missing in the amount on the cheque and the
bill of lading.
2. For the amount in words on the cheques in France, it is required to have the currency printed together with the decimals in
words. Currently the decimals are printed in figures only, without currency notation.
SOLUTION DESCRIPTION:
1. For the French language, all amounts are printed correctly now.
2. Since this is a bank requirement in France, ONLY FOR THE FRENCH LOCALIZATION (B40L_c_fre0) a separate report
"Checks (Euro)", report group 3 (tfcmg126031000), has become available in which the decimals are printed in words as
well. The amount on the cheque also contains the currency, which will ALWAYS be 'Euro'. The amount EUR 6.9063,50 will
be printed on the cheque as:
* SEIZE MILLE NEUF CENT SOIXANTE TROIS EUROS ET CINQUANTE CTS *

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

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

Solution: 122793
SITUATION IDENTIFIED IN:
"Inventory Receipt Transaction Consumptions" (whina1514m000)
SITUATION DESCRIPTION:
When confirming a shipment a financial integration transaction of type 'issue' is created. This transaction will debit the
'Interim delivery' account. At the moment the invoice is posted a financial integration transaction of type 'COGS' is created.
This transaction will credit the 'Interim delivery' account. Both transactions are created in two separate processes and due
rounding it can happen that the 'issue' amount is unequal to the 'COGS' amount.
A side aspect of this rounding issue is that the MAUC value which is displayed in session whwmd2515m000 "Inventory by
Item and Warehouse" is updated incorrectly.
COGS = Cost Of Goods Sold
MAUC = Moving Average Unit Cost
SOLUTION
DESCRIPTION:
The rounding of the calculated issue amounts has been changed. This will prevent the 'issue' amount 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: 123058
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
A new version 3 of the payment file format exists for the BG Bank (Denmark) -Foreign Payments.
SOLUTION DESCRIPTION:
In part 2 of the report the supplier's country description was added.
New part was added: for SWIFT - part 5, for GIRO - part 3.
In this part there is information about the reason for payment and the description of the reason for payment.
In session "Maintain ACP Parameters" (tfacp0100m000) the parameter "Add Reasons for Payments" should be "Yes", because
only in this case there is a check whether the code of reason for payment is filled.

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

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

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

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

Solution: 123607
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
"Cost of Goods sold cannot be determined" error when trying to confirm shipments for components.
SOLUTION DESCRIPTION:
In case of 'issue to components' the delivered quantity must be corrected by the actual ratio of the component.
SOLUTION 123607 PLEASE ALSO INSTALL SOLUTION 128772.
VERSION(S):
B50_b, B50_c

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

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

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

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

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

Solution: 123801
SITUATION IDENTIFIED IN:
"Process Inventory Variances" (whina1200m000)
SITUATION DESCRIPTION:
Integration transaction "Warehousing(Valuation)/Value Correction" is not generated, If "Process Inventory Variance
(whina1200m000)" is executed for the production order of 0 quantity. But if the session "Process Inventory Variance
(whina1200m000)" is run for the second time, the transaction is posted to finance.
The same problem occurs while processing any Inventory Variance record with zero quantity and with the 'Assigned to Inventory' flag selected
as YES. While running for the first time, the 'Assigned to Inventory' flag is reset to NO and in the second run it is processed.
SOLUTION
DESCRIPTION:
The posting to financing would be done in single step. The user need not
run the session again to make the
"Warehousing(Valuation)/Value Correction" transaction to be posted to Finance.

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

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

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

Solution: 123854
SITUATION IDENTIFIED IN:
"Generate invoice by selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
It can happen that a batch is generated with session tfacp2290m000 (generate selfbilled invoices) and that that batch can not
be finalized. The user will get the message "batch header record missing". If you look with table maintenance (ttaad4500) to
the related tables then indeed a record is missing in tfgld101, whereas all the other tables are populated correctly.
SOLUTION
DESCRIPTION:
A batch header record has to be written once in the selfbilling batch as the transaction
type is the same for all documents. Because of this a certain DLL (dynamic link
library) is called to create this record and for performance reasons the creation of a batch header record is only done once.
However when (because of the locking of a table) the process gets into its retry.point() this record will because of this
mechanism never be created again. Now it is also checked whether a db.retry.hit has 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: 123885
SITUATION IDENTIFIED IN:
"Release to Invoicing" (tdsls4501m130)
SITUATION DESCRIPTION:
When entering a delivered quantity (tdsls401.dqua) = zero for a Cost Item on a Sales Order of type "Return Order" in
session "Release to Invoicing" (tdsls4501m130), the line could not be processed any further in session "Process Delivered
Sales Orders" (tdsls4223m000).
SOLUTION
DESCRIPTION:
From now on Sales Order Lines of type
"Return Order", with "delivered quantity" = zero for Cost Items,
can be processed in "Process Delivered Sales Orders" (tdsls4223m000).

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

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

Solution: 123907
SITUATION IDENTIFIED IN:
"Convert Electronic Bank Statements" (tfcmg5202m000)
SITUATION DESCRIPTION:
Can not import MultiByte fb file.
SOLUTION DESCRIPTION:
Re-fix for badfix SOL123606 only for 123606bgl0

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

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

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

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

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

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

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

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

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

Solution: 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: 124143
SITUATION IDENTIFIED IN:
"Additional Object for SOL119504" (whinh211)
SITUATION DESCRIPTION:
SOL119504 does not include engough objects for bgl0 VRC. This cause some object mismatch when the customer installed
this solution.
SOLUTION DESCRIPTION:
Release additional objects for B50L_b_bgl0 & B50L_c_bgl0

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

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

Solution: 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: 124190
SITUATION IDENTIFIED IN:
"Print Purchase Orders" (tdpur4401m000)
SITUATION DESCRIPTION:
For a Purchase Order line,if we have more than one tax code for a tax code group, the total value of the purchase order was
being repeated that many times.So the total value printed for the Purchase Order was wrong.
SOLUTION DESCRIPTION:
Now, correct order value is printed on the purchase order, ir-respective of no. of tax codes for the tax group.

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

Solution: 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: 124226
SITUATION IDENTIFIED IN:
"Receipt Schedule" (tfacrl1504m001)
SITUATION DESCRIPTION:
From session Receipt schedules, when zoomed to 'Sales invoices receipts', the BP code displayed is wrong. Other details are
right.
SOLUTION DESCRIPTION:
Now all the details including the BP Code & Description is rightly displayed.

Solution: 124265
SITUATION IDENTIFIED IN:
"Print Collected Suspended Vat" (tfgldl415m00l)
SITUATION DESCRIPTION:
When printing the report the VAT Amount and Taxable Amount are not showed with the decimals however the currency and
display format are correctly setup for printing decimals
SOLUTION DESCRIPTION:
When the currency and display format are correctly setup for printing decimals the report will show the decimals now.

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

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

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

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

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

Solution: 124325
SITUATION IDENTIFIED IN:
"purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1. A purchase order line is created and released to warehousing. The receipts are not yet made.
2. In finance, an invoice is created and matching is done by order.
3. Now the order line is deleted in the session "Purchase Order Lines" (tdpur4501m000) session. The deletion is not done and
also there is no message given to the user as to why the order line not deleted.
SOLUTION DESCRIPTION:
Now, a message
-----------------------------------------------------------------------------------------------------------------
There are invoice(s) matched against this order line. Deleting not possible.
--------------------------------------------------------------------------------------------------------------------
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: 124352
SITUATION IDENTIFIED IN:
"Print Purchase Orders" (tdpur4401m000)
SITUATION DESCRIPTION:
The 'Alternative item code' is printed only for the first line of the Purchase Orders. It is not printed for the other lines.
SOLUTION DESCRIPTION:
Now the 'Alternative item code' would be printed for all the appropriate lines.

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

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

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

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

Solution: 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: 124427
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
1) Fields "Tax Country /Code" only available when saving or changing to the second form.
2) When using Receipt transaction it isn't possible to select the invoice through zoom.
SOLUTION DESCRIPTION:
1) Fields "Tax Country /Code" will be available in the first form itself and before saving or changing to the second form
2) When using Receipt transaction it is now possible to select the invoice through zoom.

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

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

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

Solution: 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: 124449
SITUATION IDENTIFIED IN:
"Domains" (ttadv4500m000)
SITUATION DESCRIPTION:
When in the session ttadv4500m000(Domains) the domain tfcmg.tran is selected and for this domain via Specific the enum/Set
data, the translation in German in the localisation is quit different from the standard, which causes problems and confusions.
SOLUTION DESCRIPTION:
Now the translations for the standard and the localisations are the same.

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

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

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

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

Solution: 124473
SITUATION IDENTIFIED IN:
"whinal210m000" (Calculate LIFO by Year)
SITUATION DESCRIPTION:
The average price and the total value are not converted in the report currency, if the report currency is not the local
currency.
SOLUTION DESCRIPTION:
The LIFO amounts are now converted to the report currency.

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: 124492
SITUATION IDENTIFIED IN:
"Sales and Warehousing Order Invoice Lines" (cisli2545m000)
SITUATION DESCRIPTION:
There is a bilateral invoicing relationship between the warehouses used in the "Warehousing Orders" (whinh2500m000) for
Transfer manual orders. The cutoff date in the session "Sales and Warehousing Order Invoice Lines" (cisli2545m000) is
blank when the shipment is confirmed for the outbound line of the above order.
SOLUTION DESCRIPTION:
The cutoff date is now filled in central invoicing when the shipment is confirmed.

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

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

Solution: 124535
SITUATION IDENTIFIED IN:
"Print Sales Order Line History by Sold-To BP and Item" (tdsls5401m000)
SITUATION DESCRIPTION:
When Swiss rounding is used, and a report from session "Print Sales Order Line History by Sold-To BP and Item"
(tdsls5401m000) is printed, the currency of a sales order history line is not converted to the home currency. Also the
currency code is printed on top of the amount on all reports which can be printed from this session.
SOLUTION DESCRIPTION:
The amounts are converted to the home currency and rounded according to the Swiss rounding method. The currency code is
correct displayed.

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

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

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

Solution: 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: 124579
SITUATION IDENTIFIED IN:
"Journal Report for Date" (tfgldl421m00l)
SITUATION DESCRIPTION:
The opening balance amount of all transactions for the specified ledger account for the given date is not correct.
SOLUTION DESCRIPTION:
Now it is showing correctly the opening balance amount of all transactions related to specific ledger account on the specific
date.

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 124743
SITUATION IDENTIFIED IN:
"Print Libro Giornale" (tfgldl402m00l)
SITUATION DESCRIPTION:
As the Libro Giornale is a legal report and it has to be printed on legal paper, the final print-out should come without the
header, because the legal paper has already headers on each page pre-printed (company name, page number, etc). Instead the
report header is useful when you print the preliminary report (not legal), because it is printed on common paper.It should
provide the option to choose header or not.
SOLUTION DESCRIPTION:
The option is provided to choose header or not in the report.

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: 124778
SITUATION IDENTIFIED IN:
"Print Purchase Order Reports" (tdpur4405m000)
SITUATION DESCRIPTION:
When all the options are used, the system doesnot print the output.
SOLUTION DESCRIPTION:
Now when all the options are used also, the system prints the output.

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

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

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

Solution: 124807
SITUATION IDENTIFIED IN:
"Print VAT Book" (tfgldl408m00l)
SITUATION DESCRIPTION:
As the VAT Book is a legal report and it has to be printed on legal paper, the final print-out should come without the
header, because the legal paper has already headers on each page pre-printed (company name, page number, etc).
Instead the report header is useful when you print the preliminary report (not legal), because it is printed on common
paper.It should provide the option to choose header or not.
SOLUTION DESCRIPTION:
The option is provided to choose header or not.

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 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: 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: 125060
SITUATION IDENTIFIED IN:
"Manual Sales Invoice Header" (cisli2120m000)
SITUATION DESCRIPTION:
It is possible to enter into the fields of Manual Sales Invoice Header, when it has one or more lines with the status other
than ON HOLD. But the user cannot change any values of the fields in the Manual Sales Header. He can only navigate
through the fields.
SOLUTION DESCRIPTION:
Now the functionality is kept the same but the user is not allowed to navigate through the fields as they are now made as
display fields, when it contains one or more lines in status other than ON HOLD. The values in the fields can be changed
only when the status of the respective lines are in status ON HOLD.

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

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

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

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

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

Solution: 125132
SITUATION IDENTIFIED IN:
"Assign invoices to credit notes" (tfacp2121s000)
SITUATION DESCRIPTION:
Incase no change has been made to the linked amount and Process assignment is done again, the 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: 125155
SITUATION IDENTIFIED IN:
"Print Sales Invoices" (cisli2400m000/cisli2405m000)
SITUATION DESCRIPTION:
Order discount not printed in the invoice. But in Baan4c, it does get printed.
Line discount amount is printed wrongly if a sales order has more than one line and the line discount of the first line alone is
empty. In that case, the line discount amount of the last line is printed in the first line.
In localization VRCs, Tax percentage and description is not printed. This is printed in the standard reports
SOLUTION DESCRIPTION:
Now the Order discount for Sales orders is printed in the invoice
Now the line discount amounts are printed correctly.
Now in localization VRCs also, tax percentage and description is printed in the invoice.

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

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

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

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

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

Solution: 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: 125253
SITUATION IDENTIFIED IN:
"Print Sales Invoices" (cisli2400m000/cisli2405m000)
SITUATION DESCRIPTION:
Sales Order Lines Details with different prices are aggregated in same invoice line. Actually a seperate invoice line has to
be printed when the price changes
SOLUTION DESCRIPTION:
Now the detail lines are not aggregated if price changes. It is printed seperately

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

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

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

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

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

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

Solution: 125299
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
When a payment is transferred. On report 'S, Bankgiro Domestic' (tfmcgl2571400l), the payment date is not printed on the
'Payment assignment TC 14', position 50-55.
SOLUTION DESCRIPTION:
Payment Date is printed on the report 'S, Bankgiro Domestic'. Payment assignment TC 14 is showing the payment date on
position 50-55.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 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 Aging Analysis by Customer" (tfacr2420m000)
SITUATION DESCRIPTION:
Aging Analysis gives wrong report in the Following cases:
1. Negative Anticipated Receipt is linked to a Sales Invoice.
2. When a Negative Sales Invoice used as a credit note to link it to another sales invoice
SOLUTION DESCRIPTION:
Now the Aging Analysis shows correct amounts both in the balance column and gives correct classification of the age of the
invoices

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

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

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

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

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

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

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

Solution: 125558
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
"Belgian Bank File for Payments in FC" (tfcmgL2571100L)
SITUATION DESCRIPTION:
In the session "Transfer Payments" (tfcmg1260s000), the payment data gets transfered to the chosen payment file. When
the "Belgian Bank File for Payments in FC" (tfcmgL2571100L, report group 37) has been chosen, the IBAN code is not yet
available.
SOLUTION DESCRIPTION:
With this solution, the IBAN functionality will come available for this report, when the field "Use IBAN account" in the
session "Payment/Receipt Methods"(tfcmg0140m000) has been set to 'Yes'.

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

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

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

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

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

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

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

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

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

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

Solution: 125700
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
When credit notes with case discount and with option "Negative amounts allowed" as NO are
posted, an unbalanced btach is created.
SOLUTION DESCRIPTION:
Now the transactions are booked correctly and the batch is also balanced.

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

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

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

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

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

Solution: 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: 125819
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
The Swiss DTA is not correct in case of foreign payments.
SOLUTION DESCRIPTION:
The Swiss DTA is correct in case of foreign payments now.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 125974
SITUATION IDENTIFIED IN:
"Open Entries" (tfacp2520m000)
SITUATION DESCRIPTION:
When the session Open Entries(tfacp2520m000) is started for the localization, fatal errors occurs because of a lack of a
former solution, which was not dumped in the localization VRC.
SOLUTION DESCRIPTION:
Now the fatal errors do not occur anymore

Solution: 125980
SITUATION IDENTIFIED IN:
"Receipts" (tdpur4531m000)
SITUATION DESCRIPTION:
Purchase order details were not filled in the integrations when confirming receipts via session Receipts ("tdpur4531m000")
for subcontracting orders.
SOLUTION DESCRIPTION:
Order details are filled now in the integrations.

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: 126006
SITUATION IDENTIFIED IN:
"Manual Sales Invoice Details" (cisli2125m000)
SITUATION DESCRIPTION:
When the Manual sales invoice has zero quantity and zero price but has amount, the Invoice is printed with ZERO amounts.
SOLUTION DESCRIPTION:
Now the Invoice gets printed correctly taking into account the amount entered in the Manual sales invoice lines

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

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

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

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

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

Solution: 126079
SITUATION IDENTIFIED IN:
"Payment Advice" (tfcmg1120m000)
SITUATION DESCRIPTION:
It is selecting the paid standing order in the payment advice when you select it through manually.
SOLUTION DESCRIPTION:
It is not possible to select already paid standing order in the payment advice manually.

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

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

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

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

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

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

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

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

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

Solution: 126167
SITUATION IDENTIFIED IN:
"Process Quotations" (tdsls1200m000)
SITUATION DESCRIPTION:
The inventory check was not properly executed when processing a quotation line.
This only applied to items for which an ATP (Available to Promise) did not need to be executed.
SOLUTION DESCRIPTION:
The inventory check is now properly executed.

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

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

Solution: 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: 126254
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Intra warehouse item transfer goes wrong when warehouse with locations and item is not location-controlled.
SOLUTION DESCRIPTION:
Solution 122844 ported to localizations "bci1" and "bgl0".

Solution: 126258
SITUATION IDENTIFIED IN:
"Payment Methods" (tfcmg0140s000)
SITUATION DESCRIPTION:
Belgian Payment report 42 (B50L_b and B50L_c) and report 6 (B40L_c4_blg0) not IBAN compatible.
SOLUTION DESCRIPTION:
Belgian Payment report 42/report 6 is IBAN compatible now.

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

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

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

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

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

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

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

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

Solution: 126360
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
In session Business Partners, the role of a business partner is set to Invoice-from.
Then on the second tab of session Invoice-from Business Partner, the Business Partner Category can be set.
Start session Transactions and insert a new batch.
Now session Purchase Invoices is started.
Fill in a business partner, whose Business Partner Category is set to e.g. AGENT.
The VAT-Code for the used category is set to e.g. 20%.
Tab to the field VAT and the wrong VAT-Code is displayed.
SOLUTION DESCRIPTION:
Now when tabbing to the VAT-Code field, the VAT-Code belonging to the role of the business partner (namely 20%) is
displayed, which is the correct code.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 126575
SITUATION IDENTIFIED IN:
"Compose/Print/post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When Italian Localization parameter "Vat Book" is ON, the form fields on the session are not disabled/enabled properly.
When the user enters a Billing Request set, all the other fields like "Compose", Print", "Post" etc are disabled.
SOLUTION DESCRIPTION:
Now the form fields are correctly enabled.

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

Solution: 126592
SOLUTION DESCRIPTION:
D
ear Customer,
We are pleased to enclose a delivery of porting set 7.1c.04.
Porting set 7.1c.04 has been released for the following platforms: NT, UNIX, AS/400 and S/390, and is suitable for use
by iBaan ERP 5.0b and iBaan ERP 5.0c customers. However, there are differences in the level of platform/database
support provided for these Baan applications. Therefore, separate Technical Notes documents have been created for
iBaan ERP 5.0b and iBaan ERP 5.0c customers, which can be downloaded from the DOWNLOADS section at the bottom of
this page.
IMPORTANT:
From portingset 7.1c.02 onward it is not possible to use BaanSafari FSR (Financial Statement Reporting) on iBaan ERP 5.0c and iBaan ERP 5.0b.
Because of technical reasons
it is no longer possible to
integrate BaanSafari FSR with
Baan. The alternative is to use
Crystal Reporting
"Crystal
Enterprise Solutions for
Baan
2.0".
Note 1. On iBaan ERP 5.0b, only the
BDB driver will work; XML
reporting is not available on iBaan ERP 5.0b.
Note 2. Besides purchasing Crystal Reporting, some solutions must be installed, which can be downloaded from the Baan
Support web, at solution number 123595.
Note for customers running an Oracle database: Oracle has de-supported a
number of database versions, for which reason Baan will desupport them as well. It concerns the following versions:
8.0.4 - de-supported
since Apr 1, 2000 - succeeded by
terminal release 8.0.6.3
8.0.5 -
de-supported since
July 1, 2000 -
succeeded by terminal release 8.0.6.3
8.1.5 -
de-supported
since Jan 1,
2001 - succeeded
by terminal release
8.1.7.x
8.1.6 -
de-supported since
Oct 31, 2001 -
succeeded by terminal
release
8.1.7.x
There are some known problems in the bdbreconfig, this is
especially the case when developing new domains and tables.
if the error message:
Serious Error
is occuring the old version of bdbreconfig can be used from
portingset 7.1c. the problem will be fixed
in a newer release: 7.1d
DOWNLOADS:
With the following link you can download the
"Technical Notes Porting Set 7.1c.02, doc nr U7699A
US" which contains essential information for B50c specific.
Please read these notes first before you install the portingset:
ftp://ftp.support.baan.com/updates/port/7.1c.02/U7699aus%20Tech%20Notes.pdf
With the following link you can download the
"Technical Notes Porting Set 7.1c.02, doc nr U7697A
US" which contains essential information for B50b specific.
Please read these notes first before you install the portingset:
ftp://ftp.support.baan.com/updates/port/7.1c.03/U7697bus%20Tech%20Notes.pdf
With the following link you can download the
release notes for portingset 7.1c.04:
ftp://ftp.support.baan.com
/updates/port/7.1
c.04/bugfi
xes71c
04.txt
With solution 123645 you can find the link
to the portingset components
We hope that using this product will enhance the continued success of your business.
For further assistance, please contact
your Baan Support Center.
Yours truly,
Baan
VRC package component comp_type comp_code servicepack
B50L b bgl0 tf tfacrl505m00l Script/Library Source acrl505 spb50b_14
B50L b bgl0 tf tfacrl505m00l Script/Library Object acrl505 spb50b_14

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

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

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

Solution: 126631
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
When session 'Transfer Payments' (tfcmg1260s000) is run, the 'S, Bankgiro. Domestic' payment file (tfcmg126081000) is not
printing the due date, although, the option 'Planned Pmt Date/Due Date' is set to 'Yes' for the selected payment method in
session 'Payment Method' (tfcmg0140m000).
In this case, the payment file is showing the
payment date (date when session 'Transfer Payments',
tfcmg1260s000, has been run) instead of the due date.
SOLUTION DESCRIPTION:
Due date is printed on payment file 'S, Bankgiro.
Domestic' (tfcmg126081000), when transfer
a payment and the payment method selected has
active the option 'Planned Pmt
Date/Due Date'.
Other issue has been solved through
this solution:
When the due date or planned date is overdue, this
means that the due date or the planned date is smaller than
the payment date (date when session 'Transfer
Payments' has been run), the payment date will be printed on the
payment file 'S, Bankgiro, Domestic' instead of the due date or planned date.

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

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

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

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

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

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

Solution: 126715
SITUATION IDENTIFIED IN:
"Print Purchase Invoices" (tfacp2421m000)
SITUATION DESCRIPTION:
When running session "Print Purchase Invoices" tfacp2421m000 with the field "Invoices to be Printed" set to "Approved
Invoices", the report prints also the purchase credit notes 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: 126775
SITUATION IDENTIFIED IN:
"Inventory by Item and Warehouse" (whwmd2515m100)
SITUATION DESCRIPTION:
1. A Sales Order is created for 10 pcs and the 'Allocated Quantity' goes up by 10 in the session "Inventory by Item and
Warehouse" (whwmd2515m100).
2. For this sales order a quantity more than the Order Quantity is shipped (Say 12 pcs).
3. When the Shipment is confirmed, the Allocated Quantity becomes -2 pcs.
SOLUTION DESCRIPTION:
When the Over Delivery is done with the shipped quantity being more than the order quantity, the reduction of the
Allocated Quantity would be equal to the Order Quantity and not more than that.

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

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

Solution: 126787
SITUATION IDENTIFIED IN:
"Import / Export Statistics" (tccom7571m000)
SITUATION DESCRIPTION:
New functionality concerning Intrastat regulations.
SOLUTION DESCRIPTION:
On form "Process Import/Export Statistics" an extra field named "Region" is introduced.
Here the values "Flemish", "Walloon" and "Brussels" can be chosen when the sequential imp/export file (B) is selected.
Only one region can be chosen at the same time.
To this file the fields region and Incoterm are added.
In order to activate the new report, namely "Seq. Imp/export File (B)", it is necessary to mark the Intrastat Reporting -
Belgium checkbox in session General Localization Parameters (tccoml100s00l).

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

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

Solution: 126806
SITUATION IDENTIFIED IN:
"Exceptions for Taxes" (tcmcs1138m000)
SITUATION DESCRIPTION:
In session "Exceptions for Taxes" (tcmcs1138m0000) the field 'Business Partner Category' is opened for the Brazilian
Localization. This field is not used in Brazil, so it must not be part of tax defaults selection.
SOLUTION DESCRIPTION:
In session "Exceptions for Taxes" (tcmcs1138m0000) the field 'Business Partner Category' is now disabled for the Brazilian
Localization.

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

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

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

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

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

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

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

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

Solution: 126992
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
When PCS Project is used in a Bilateral Invoicing Transaction, and if the Calculation office of the PCS Project is linked to a
different finance
company other than the supplying warehouse, then the "Credit" line of the COGS booking is wrongly booked to the finance
company of the warehouse. It has to be the finance company of the Calculation Office. Also, the Enterprise units are
populated wrongly in the Integration Tables.
SOLUTION DESCRIPTION:
Now the COGS Bookings are posted correctly
SOLUTION <128526> ALSO
VERSION(S):
B50_b, B50_c, B52_a

Solution: 127000
SITUATION IDENTIFIED IN:
"Print Sales Contract Acknowledgements" (tdsls3405m000)
SITUATION DESCRIPTION:
Contract line text is not printed in case contract line applies to all items in price group
SOLUTION DESCRIPTION:
The printing of contract line texts was determined based on the field "Apply Contract for all Items in Price group" in
session Sales-Contract Lines (tdsls3101s000).
Contract texts are now printed (when available) for all lines regardless if the contract line applies to all items in the
pricgroup or not.

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 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: 127151
SITUATION IDENTIFIED IN:
"Release to warehousing (batch)" (tdsls4246m000)
SITUATION DESCRIPTION:
A sales order line with a cost item with quantity =0 is not transferred to the warehouse by session Release to Warehousing
(batch).
SOLUTION DESCRIPTION:
Functionnality for Cost and Service Item is slightly different than for a normal Item. Now, in case of Cost or Service Item,
Sales Order Line will be transfer to warehouse.
SOLUTION #127384 AFTER INSTALLING THIS SOLUTION
VERSION(S):
B50_b, B50_c

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

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

Solution: 127203
SITUATION IDENTIFIED IN:
"Approve Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When a project related purchase order is matched and approved with an Invoice, and there is is currency rate difference
between the time of Receipt and Approval, the currency difference is not posted as a Purchase price variance.
SOLUTION DESCRIPTION:
Now, when a project related order line is matched totally and all other invoices linked with the order have been approved,
the difference in home currency between the Receipt and Approval, 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: 127204
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
1. The receipt procedure of the Inbound Order does not have Generate Inbound and Put away Inbound as activities, meaning
that the inbound would be done automatically when the receipt is confirmed.
2. There is a lot-controlled item.
3. Many unit of this item is entered in the Purchase Order Lines.
4. It is released to Warehousing and the order is linked to a Receipt.
5. While confirming the linked receipt, it takes lot of time.
SOLUTION DESCRIPTION:
The changes have been made in such a way that time taken for the complete process of confirming the receipt is reduced
considerably. Even in cases where the Generate Inbound is a separate activity, the changes will be applicable and the
performance of the advice generation.

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

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

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

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

Solution: 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: 127265
SITUATION IDENTIFIED IN:
"Print Claims" (tdpur4420m000)
SITUATION DESCRIPTION:
1. A subcontracting purchase order is generated from the sub contracting operation of a production order.
2. While receiving the subcontracting item of this purchase order, the received quantity is less than the packing slip
quantity.
3. But it is not possible to print the claims even if the activity "Print Claims" (tdpur4420m000) is part of the order step.
SOLUTION DESCRIPTION:
It is possible to print the claim for the subcontracting item when the packing slip quantity is greater than the received
quantity.

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

Solution: 127269
SITUATION IDENTIFIED IN:
"Print Invoices" (cisli2400m000)
SITUATION DESCRIPTION:
When Invoices of Collect Orders are printed, the correct Invoice report specific to Swiss Localization is not picked up.
SOLUTION DESCRIPTION:
Now the correct invoice is printed.

Solution: 127274
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
In Sales Order Header, it is not possible to change the tax code country in the 'Invoicing' tab from the default to any other
country.
SOLUTION DESCRIPTION:
It is now possible to change the tax code country, to other countries, apart from the default one in Sales Order Header.

Solution: 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: 127413
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
1. In the session "Master Data Parameters" (whwmd0100s000), the parameter "Only Unoccupied Locations" is set to NO.
2. All the bulk/pick locations of the warehouse are occupied with some quantity and due to the parameter setting the
occupied location could also be advised.
3. The Receipt procedure has only one the activity "Receipt" (whinh3520m000).
4. The inbound should be done automatically, at the time the receipt were confirmed. The inbound is not made and the item is
left in receiving location.
SOLUTION DESCRIPTION:
The goods are advised to the Bulk or Pick location at the time the receipt is confirmed.

Solution: 127419
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
"Process Delivered Sales Orders" (tdsls4223m000)
SITUATION DESCRIPTION:
System allows the user to delete the purchase and sales orders created for PCS Project Items, even though the status of the
Project is not "Archived".
SOLUTION DESCRIPTION:
Now, changes are made such that system doesn't allow the deletion of purchase and sales orders if the corresponding linked
Projects don't have the status of "Archived". Only when the status of the PCS Project is "Archived", system allows the
deletion of the purchase and sales orders.

Solution: 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: 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: 127460
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When receiving an order acknowledgment with a different item for a direct delivery purchase order line, the item was being
updated. This is not allowed, even if the |Field Action" in the conversion setup is set to |Update".
SOLUTION DESCRIPTION:
In case of direct delivery purchase orders, it is not allowed to change the item code, similarly as in the manual order entry
process (in the user interface, the item field is disabled). This has been corrected. The |Differences between Purchase
Order and Order Acknowledgment" report shows that the incoming data is different from the existing item code, but the item
code is not being updated on the order. Some other purchase order line fields could also be updated in case of direct
delivery, which is also impossible in the user interface. Corrections have been made for the following fields: Ordered
Quantity (tdpur401.oqua), Purchase Unit (tdpur401.cuqp), Lot Selection (tdpur401.lsel) and Lot (tdpur401.clot).

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

Solution: 127477
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2125s100)
SITUATION DESCRIPTION:
An Outbound Order line is created for some quantity and advice is done. Then, the quantity is reduced and "Re-advise
Remaining" is done. The system goes into loop and hangs.
SOLUTION DESCRIPTION:
Now, on invoking the "Re-advise Remaining" option system doesn't hang and quantities are advised properly.

Solution: 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: 127510
SITUATION IDENTIFIED IN:
"Update Sales Statistics" (tdsst0201m000)
SITUATION DESCRIPTION:
When a sales order line is cancelled and if the updates are done for the same. Then while printing the sales statistics, the
quantity and amounts values are getting doubled.
SOLUTION DESCRIPTION:
Now the values are shown correctly and the sales updating also done correctly.

Solution: 127514
SITUATION IDENTIFIED IN:
"Picking List" (whinh2525m100)
SITUATION DESCRIPTION:
Shipment lines get sometimes a wrong weight when confirming several lines from picking list with different items.
SOLUTION DESCRIPTION:
Before creating a new shipment line the related item base data is re-read.

Solution: 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: 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: 127564
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000).
SITUATION DESCRIPTION:
Consignment Replenishment Orders could be linked to Sales Contracts.
Afterwards several problems would occur.
When for example the ordered quantity (tdsls401.oqua) was changed, message "Price cannot be changed" (tdisa001.00)
appeared and saving of the record was impossible.
SOLUTION DESCRIPTION:
From now on Consignment Replenishment Orders cannot be linked to Sales Contracts anymore. This type of order was never
meant to be used this way.
According to the concept, the only purpose of this type of order is to transfer goods from one warehouse to another. Note that
this transfer does not affect the ownership of the goods.
As a consequence no financial transactions should take place, like for example linking to sales contracts.
When goods are actually issued from a replenished warehouse, a Consignment Invoicing Order should be used. This type of
order can actually be linked to a Sales Contract. That way the financial transactions are handled the right way.

Solution: 127567
SITUATION IDENTIFIED IN:
"Inbound Order Lines" (whinh2510m000)
SITUATION DESCRIPTION:
When an order line is tried to block/unblock an unnecessary error message pop up saying that "Order line not found ".
SOLUTION DESCRIPTION:
The error message will not pop up and blocking / unblocking operation will be performed and a message will also be shown
saying that " Line is blocked " or Line is unblocked" depending upon the operation.

Solution: 127574
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
"Report & Remittance Bank File for Belgian Banks" (rtfcmgL2571300L)
SITUATION DESCRIPTION:
The report "Report & Remittance Bank File for Belgian Banks" (report 42, rtfcmgL2571300L) cannot handle bank accounts that
consist of more than 17 positions. In France, for instance, the bank accounts have 23 positions. This cannot be printed on
the report and the account number will be truncated.
The value for 'Total Credit Bank
Accounts' does not summarize
correctly. This is because the value is outside the system boundaries.
SOLUTION DESCRIPTION:
The field in the column
'Bank Type' has been
adjusted to display these
accounts also. The value in the
field 'Total Credit
Bank Accounts' is now also
visible.

Solution: 127583
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Enter a Sales Order Line with a specific revision of an Engineering Item. When the line a split delivery line, the E-revision
field is disabled, and it is not possible to change the e-revision for the item.
SOLUTION DESCRIPTION:
Since, e-item revision can become outdated, change in e-revision is necessary.
Change has now been made to allow change the e-revision till one of the detail line is advised. Changing the e-revision would
be applicable to all the detail lines.

Solution: 127586
SITUATION IDENTIFIED IN:
"Print Remittance Letters" (tfcmg1270m000)
SITUATION DESCRIPTION:
Language of Supplier was not taken into account when printing the Remittance Advice.
SOLUTION DESCRIPTION:
The Problem is solved now and the Language of Supplier will be taken into account when printing the Remittance Advice.
SOLUTION 127808 WITH THIS SOLUTION
*******************************************************************************************************
**********************
VERSION(S):
B40_c, B50_b, B50_c

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: 127598
SITUATION IDENTIFIED IN:
"Quotation Lines" (tdsls1101s000)
SITUATION DESCRIPTION:
When the user is maintaining Sales quotation line and save the record. Without closing the session user press 'ctrl n', to
maintain another Quotation line for the same item. Here the system is not picking the correct price.
SOLUTION DESCRIPTION:
The system will pick the correct price even if the user maintains the new Quotation line for the same item by pressing 'ctrl n'.

Solution: 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: 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: 127633
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
A Sales Order is raised with a line which has a Contract attached to the Business Partner and Item. A second line is raised
with a different Item that is not linked to any contract.
When the Shipment is confirmed, the second Order line which does not have any contract attached is also attached to the
contract, which is attached to the first line.
SOLUTION DESCRIPTION:
Now, the link is made to only to the Sales Order lines, which have Contracts, attached.

Solution: 127641
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
Two issues were discovered when receiving an incoming purchase order acknowledgment via EDI (Field Action set to
Update):
1. When purchase order lines had items for a Baan Project, and the items on the incoming message were different (but for the
same project), the item of the first line was not updated.
2. The item could be changed on purchase order line details via the incoming order acknowledgement. This is not allowed.
SOLUTION DESCRIPTION:
The program script has been corrected.
1. The project information was not read properly, so the update of the Baan Project item went wrong. Now all items are
updated.
2. There was no check if a normal line was going to be changed or a detail line. Such a check has been introduced, in order
to make sure that only those fields can be updated, which can be updated in the User Interface, like Ordered Quantity. Item
cannot be changed on the details.

Solution: 127647
SITUATION IDENTIFIED IN:
"Sales Quotations" (tdsls1100s000)
"Sales Contracts" (tdsls3100s000)
SITUATION DESCRIPTION:
When entering the Sold To Business Partner on a new Sales Quotation (session tdsls1100s000) or Sales Contract header (session
tdsls3100s000), the default sales office is picked up. But the default quotation or contract series for this sales office is not
picked up.
SOLUTION
DESCRIPTION:
The way of defaulting the order series for Sales
Orders (tdsls4100s000), Sales Quotations (tdsls1100s000)
and Sales Contracts (tdsls3100s000)
is the same
now.
First the default series of the order
type (session tdsls0194s000) is read.
If there is no default, the series of
the user profile (session
tdsls4123s000) is read. If
empty, finally the
series of the sales office is taken (session tdsls0212s000).

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

Solution: 127656
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
When changing the sales order type to consignment invoicing the warehouse is changing immediately but the warehouse
name is not.
SOLUTION DESCRIPTION:
The name of the warehouse is now updated as well when in case the warehouse changes because of a change of sales order
type

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

Solution: 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: 127661
SITUATION IDENTIFIED IN:
"Sales Order Line Details" (tdsls4501m200)
SITUATION DESCRIPTION:
When new text is created for a Sales Order Detail line (in session tdsls4101s200) and the detail session is closed, a
"recursion not yet implemented" fatal error can pop up when many lines already exist for the same Sales Order Line
Position.
SOLUTION DESCRIPTION:
Sales Order Detail Lines with text can be added and saved without fatal errors now. Session Sales Order Line Details
(tdsls4501m200) gets correct refreshed.

Solution: 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: 127693
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When entering lot controlled items to Collect Return Orders, the system would automatically create a lot number, without
notifying the user about it.
SOLUTION DESCRIPTION:
A message is implemented that informs users that they may provide a lot number.
If no lot number is provided the system will automatically generate one.
This only applies when adding a lot controlled item to a Sales Order of type 'Collect Return Order'.

Solution: 127694
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4120s000)
SITUATION DESCRIPTION:
When changing the Payment/Receipt method with the option "Planned Payment Date = Due Date" is checked "ON" to a
Payment method with the option "Planned Payment Date = Due Date" is checked "OFF", the Planned Debit Date remains the
Due date of the Previous payment method and not the date on which the Direct Debit Advice is created.
SOLUTION DESCRIPTION:
When changing the Payment/Receipt method with the option "Planned Payment Date = Due
Date" is checked "ON" to a Payment method with the option "Planned Payment Date =
Due Date" is checked "OFF", the Planned Debit Date won't remain the Due
date of the Previous payment method and now the date on which the Direct Debit Advice is created will be filled correctly.
SOLUTION 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: 127715
SITUATION IDENTIFIED IN:
"Initialize Parameters" (tcmcs0295m000)
SITUATION DESCRIPTION:
The End User was not updated on the current progress of this (process) session. Therefor it was difficult to see if the
process was hanging or still runing in the background.
SOLUTION DESCRIPTION:
A progress bar has been added to the session, so that the End User stays updated on the current progress of this (process)
session.

Solution: 127721
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
When a user maintains an installment line for a sales order and then releases the installment line to invoicing, he is still
allowed to delete the sales order header. Because of this, the released installment line remains forever in Central Invoicing.
It cannot be posted or purged. This problem is applicable both to B50_b and B50_c
Moreover when the user tries to post that installment line, the open batch created for that day consisting of the transactions
of previous billing requests posted, gets the status of 'deleted'. So the batch cannot be finalized. This problem is applicable
to B50_c only.
SOLUTION DESCRIPTION:
Now the user will not be able to delete the header, if the installment linked to it is already released to Central Invoicing.
Also, the batch will never be set to 'deleted' in B50_c as it can be re-used by a Billing Request processed later.

Solution: 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: 127727
SITUATION IDENTIFIED IN:
"Print Bills of Lading" (whinh4470m000)
SITUATION DESCRIPTION:
-1- The Volume printed in the Bill of Lading is wrong. The system prints the unit volume of the item and it is not total
volume of the goods shipped.
-2- The Alternative item code of the Sales Order Line is not printed in the Bill of lading.
SOLUTION DESCRIPTION:
-1- The Volume printed in the report is the total volume of the goods shipped and it is not the unit volume of the item.
-2- The alternative item code of the item from the Sales Order is printed in the Bill of Lading now.

Solution: 127732
SITUATION IDENTIFIED IN:
"Generate Picking List" (whinh4415m000)
SITUATION DESCRIPTION:
For a Warehouse using Zones but not locations, it is not possible to sort the Picking List using Zones.
SOLUTION DESCRIPTION:
Now, the user can add one more Sort option. That is "Zone" mentioned in Item Data by Warehouse. This option can be
included in the Sort list & System sorts the Picking List by Zone as mentioned in Item Data by Warehouse.

Solution: 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: 127752
SITUATION IDENTIFIED IN:
"Print Packing Slip" (whinh4475m000)
SITUATION DESCRIPTION:
1. There are 2 outbound lines of two different Sales Orders.
2. They are shipped with the same shipment.
3. When the packing slip is printed, the data for the two lines are printed in two separate pages and the Shipment Header data
is printed twice.
4. They have to be printed one by one in the same page with the header data printed only once.
SOLUTION DESCRIPTION:
Now the Shipment header is not printed in two separate pages and the shipment header data is not printed twice.

Solution: 127766
SITUATION IDENTIFIED IN:
"Item Sales Data" (tdisa0101s000)
SITUATION DESCRIPTION:
1. Item defaults are maintained for an item group with item type 'List.
2. The 'Release to Warehousing' check box is not selected in the default Item Sales Data.
3. A KIT item is created for this item group and the Release to Warehousing field in the "Item sales Data" (tdisa0101s000)
is NO for this item.
4. Due to this it is not possible to release the sales order of a KIT item to warehousing.
SOLUTION DESCRIPTION:
The Release to Warehousing field in the "Item sales Data" (tdisa0101s000) is YES for KIT items irrespective of the value in
the Item Data Defaults. This would enable the user to release the KIT items to warehousing.

Solution: 127771
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
A Sales Order has 2 lines. The lines are released to Warehousing & Outbound advice has been created. Now, if user tries to
cancel the Header, system gives error that position 1 cannot be modified. User doesn't press OK to this error and goes and
deletes the outbound advice for this position. Now, on saying OK to the error, system cancels that position and header also.
SOLUTION
DESCRIPTION:
Now, on following the above procedure system doesn't cancel the
Header and lines. It gives the error
corresponding to the next
position.

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

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

Solution: 127794
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
When a purchase order line is having detail line and if any one of the detail line is received with zero quantity, then the
total line become enabled and it is possible to save the data by changing the item.
SOLUTION DESCRIPTION:
Now it is not possible and the total line will be disabled even after the zero quantity line is received at the receipts session.

Solution: 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: 127815
SITUATION IDENTIFIED IN:
"Payment Advice/Direct Debit Advice" (tfcmg1120s000/tfcmg4120s000)
SITUATION DESCRIPTION:
Field Order Sequence is not correct in the Payment Advice and the Direct Debit Advice Session
SOLUTION DESCRIPTION:
Field Order Sequence is corrected now in the Payment Advice and the Direct Debit Advice Session and the problem is
solved.

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: 127849
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
In session Sales Order Lines, no message appears for a dimension item when the quantity entered in Sales Order Lines is
less than quantity entered in session Sales Item Data ("Order quantity less than minimum quantity of item")
SOLUTION DESCRIPTION:
For a dimension item the check on quantity was missing in the Sales Order Lines session. This function follow the quantity
entered in the Sales Order Lines and display the existing warning message ( Note: order quantity less than minimum order
quantity of item is less than the quantity entered in the Sales Item Data session) if quantity is less than the minimum ordered
quantity store in Maintain Item Data.

Solution: 127864
SITUATION IDENTIFIED IN:
"cprrp1210m000" (Simulate Orders)
SITUATION DESCRIPTION:
When planning a Generic- or To-Order Item, customized stock which is consumed by a Salesorder is simultaneously
consumed by 'anonymous' demand for the Generic- or To-Order Item from which the customized item is derived.
The customized stock is consumed twice; once for the customized item and once for the Generic- or To-Order Item.
Insufficient Planned Orders are generated as a result.
In session In session "Time Phased Planning Overview" (cprrp0520m000) the total stock (stock of the generic + stock of
customized items) is shown and there is no simple way of telling what part of that stock is customized.
SOLUTION DESCRIPTION:
Customized stock is not available for a Generic- or To-Order item (customized stock is only available for the customized
item).
When planning a Generic- or To-Order Item Item, first all customized demand and supply is processed. Customized demand
will consume customized supply/stock (for the same project).
Any remaining demand (customized or 'anonymous') will be planned for the Generic- or To-Order Item itself (customized or
anonymous demand will result in a planned order for the Generic- or To-Order Item when the inventory of the Generic- or
To-order Item itself is insufficient)
Customized demand outside the Orderhorizon is not seen during "Simulate Orders" and will therefore not consume
customized stock when planning the Generic- or To-Order Item.
Outside of the Orderhorizon the customized stock is handled as 'anonymous' stock.
In session "Time Phased Planning Overview" (cprrp0520m000) for Generic- or To-Order Items the stock per project is shown
in 'detail-view'. These "stock"-lines have no 'date'

Solution: 127865
SITUATION IDENTIFIED IN:
"Reconciliation Payments/Receipts" (tfcmg2103s000)
SITUATION DESCRIPTION:
Reconciliation Aborts with the message "Out of dimension" when trying to reconcile the anticipated document of a Purchase
Invoice which has more than 10 lines and having a Vat code for each of them
SOLUTION DESCRIPTION:
Now the reconciliation is completed successfully

Solution: 127869
SITUATION IDENTIFIED IN:
"Link Invoices to Credit Notes" (tfacr2120m000)
SITUATION DESCRIPTION:
The session takes lot of time to open.
SOLUTION DESCRIPTION:
Now the performance is improved.

Solution: 127879
SITUATION IDENTIFIED IN:
"Settlement by Installment" (tdsls4513s000)
"Process Delivered Sales Orders" (tdsls4223m000)
"Installment Orders" (tdsls4506m000)
SITUATION DESCRIPTION:
A. The settlement is incorrect when a sales order is returned in the same order.The settlement becomes negative when the
following procedure is followed:
1. A sales order line (session tdsls4101s000) is entered for amount 1000
2. The first installment (session tdsls4506m000) for amount 100 is entered, processed and invoiced
3. The sales order line is processed and invoiced
4. The installment is settled with an amount of 100 which is correct
5. A second installment of 100 is made and invoiced
6. A second orderline is created to return the goods of orderline one. The amount is -1000
7. This orderline is processed and invoiced
8. The second orderline is settled with an amount of -1000 which is incorrect.
B. When an installment line is already invoiced, but the sales order line is not, the installment line cannot be processed
with session 'Process Delivered Sales Orders' (tdsls4223m000).
C. An installment is already invoiced and processed. Then the goods are shipped and the sales order line is invoiced and
processed. The installment is not counter booked, giving incorrect sales statistic data. Normally when an installment is
processed a record is entered in the Sales Order Line History of type 'Turnover'. When the goods are invoiced a settlement is
created. When the order is processed, this settlement is written to the Sales Order Line History with negative amount and of
type 'Turnover'. This 'settlement history line' is not entered in the History as the procedure as above is followed.
SOLUTION DESCRIPTION:
A. When following the procedure as described in the situation description, the second installment is now settled with an
amount of 100 which is correct.
B. Installments can be processed although the Sales Order itself is not ready for processing yet.
C. All settlement records are correct entered in the Sales Order Line History. Total turnover amounts for a sales order line are
correct now, giving correct sales statistics.

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

Solution: 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: 127895
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When the option "Inventory by Item and Warehouse" (whwmd2515m100) is activated from the shortage menu and a different
warehouse is selected the tax country and code is not updated correctly.
SOLUTION DESCRIPTION:
The functionality similar to manually changing the warehouse of the sales order line is also implemented in case the
warehouse is changed when handling the shortage.

Solution: 127901
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
1. The Rounding factor of the currency used is 1.
2. A purchase order is created. The ordered quantity of the purchase order is very precious in terms of number of digits after
the decimal point.
3. The purchase order is received and the amount posted as the Purchase/Receipt entry in "Integration Transactions by
Project/Order" (tfgld4510m000) is slightly wrong due to the rounding.
SOLUTION DESCRIPTION:
The amount posted to "Integration Transactions by Project/Order" (tfgld4510m000) is correct.

Solution: 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: 127913
SITUATION IDENTIFIED IN:
"Copy Purchase Contracts" (tdpur3801m000)
SITUATION DESCRIPTION:
1. There is a Purchase Contract and in the contract lines, there is a valid Contact filled in.
2. This contract is copied to a new contract for another Business Partner and the Ship-from Business partner of the new
contract does not have the Contact mentioned in the source contract.
3. The system gives the following fatal error and it is not possible to copy the contracts.
++++++++++++++++++++++++++++++++++++++++++++++
Error 606 (Reference does not exist) on tdpur301300 in select
++++++++++++++++++++++++++++++++++++++++++++++
SOLUTION DESCRIPTION:
The Contact of the new Contract lines is taken from the Ship-from Business partner of the new contract and the fatal error
no more pops up.

Solution: 127920
SITUATION IDENTIFIED IN:
"Generate Order Advice" (whina3200m000)
SITUATION DESCRIPTION:
When running session whina3200m000 ("Generate Order Advice") for a SIC item assigned to a signal that is blocked for
Requisition (and free for everything else), the following message is returned "Item is blocked for production issue".
SOLUTION DESCRIPTION:
A new message has been created with the following text: "Item is blocked for requisition from production".
Session whina3200m000 ("Generate Order Advice") now shows "Item is blocked for requisition from production" instead of
"Item is blocked for production issue"

Solution: 127935
SITUATION IDENTIFIED IN:
"Manual Invoice Lines" (cisli2125s000)
SITUATION DESCRIPTION:
When the user tries to enter a blank tax code in the Manual sales line and if a tax code has been defined for a geocode of the
ship-to address, then the tax code will always be defaulted, even if the user does not want it.
SOLUTION DESCRIPTION:
Now the tax code will be defaulted only for the first time. When the user changes it, then it will remain so.

Solution: 127940
SITUATION IDENTIFIED IN:
"tdsls4247m000" (Release to Invoicing (batch))
SITUATION DESCRIPTION:
Amounts in home currency are incorrect in case of COGS transaction.
SOLUTION DESCRIPTION:
Amounts requested from "Get Costs Of Goods Sold" are rounded in Warehousing before returning to Sales.

Solution: 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: 127965
SITUATION IDENTIFIED IN:
"Manual Sales Invoice Headers" (cisli2120s000)
SITUATION DESCRIPTION:
When zooming on payment method, session displays both Receipt method and Payment method. But the session accepts
only Receipt methods.
SOLUTION DESCRIPTION:
Now instead of showing both Payment methods and the Receipt methods, the zoom shows only the Receipt methods.

Solution: 127967
SITUATION IDENTIFIED IN:
"Print Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When Italian Invoice Report (cislil4501300l) is picked up for printing the Invoice, the discount amounts for the schedules
are not printed when localization parameter "Receipt Schedule" is ON.
Also when "Discount Including Tax" Parameter is OFF in the "Terms of payment" the discount is not being calculated
correctly. Tax should be deducted before the discount is calculated. This works correctly for standard. But in Localization,
when Receipt schedule is ON, the discounts are wrongly calculated.
SOLUTION DESCRIPTION:
Now the discounts are printed correctly for the schedules. Also it is calculated correctly.

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: 127993
SITUATION IDENTIFIED IN:
"Copy Purchase Contracts" (tdpur3801m000)
SITUATION DESCRIPTION:
When a Purchase Contract is copied from one supplier to another. The ship from address is taken from the source contract
rather than taking the default address of the new ship from BP.
SOLUTION DESCRIPTION:
Now the problem is solved, the system will pick up the correct address when the user is coping the contracts from one
business partner to another.

Solution: 127999
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation by Item and Warehouse " (whina1210m000)
SITUATION DESCRIPTION:
System gives the float exception fatal error when running the Inventory valuation for a warehouse with negative stock.
SOLUTION DESCRIPTION:
The float exception does not come now.

Solution: 128001
SITUATION IDENTIFIED IN:
"Purchase Change Order Sequence Numbers (tdpur4114m000)" (tdpur4114m000)
SITUATION DESCRIPTION:
When user zooms from "Purchase Orders (tdpur4500m000)" session to the session "Purchase Change Order Sequence
Numbers (tdpur4114m000)", system doesn't zoom to the correct purchase order number.
SOLUTION DESCRIPTION:
Now, system zooms to the session "Purchase Change Order Sequence Numbers (tdpur4114m000)" from "Purchase Orders
(tdpur4500m000)" session and displays the correct purchase order number and its details.

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

Solution: 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: 128030
SITUATION IDENTIFIED IN:
"Display Composed Direct Debits" (tfcmg4504s000)
SITUATION DESCRIPTION:
When tabbing through the second form of the session, Error "tfcmg403.refr index 68 out of dimension" is thrown .
SOLUTION DESCRIPTION:
When tabbing through the second form of the session the Fatal Error won't occur anymore and the problem is solved.

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: 128044
SITUATION IDENTIFIED IN:
"whinh4275m000" (Confirm Shipments/Loads)
SITUATION DESCRIPTION:
-1- When confirming an over-delivery shipment (the quantity shipped is greater than the ordered quantity of the outbound line
linked to the warehouse order), the following data should have been updated as well so that the over-delivered quantity
(over-delivered quantity = delivered quantity - original order quantity) could be taken into account:
- the sales order history
- the contract called quantity
- the order balance
-2- When running the session "Process Delivered Sales Orders" (tdsls4223m000) with the option "Delete Order Data" ON,
some Sales Order Line Records for a specific Sales Order Line could be deleted even if some of the records linked to the
same Sales Order Line had not yet been processed in the session "Process Delivered Sales Orders" (tdsls4223m000).
-3- When a Sales Order Line is split when processing a partial shipment (in this case the status of the corresponding
Outbound Line remains "Adviced/Staged" as an Outbound Advice Line should still be shipped), the Sales Order History is
not updated.
The following updates would then
be
expected
:
Sales Order Line Order Quantity
Sequence Number
(tdsls401.sqnb) (tdsls401.oqua)
0 10 (inserted when creating the Sales Order Line)
0 -10 (when the Detail line becomes a Total line due to the "Split Sales Order Line")
1 4 (when inserting the Sales Order Line with the sequence 1 --> if 4 has been delivered)
2 6 (for the remaining order quantity)
SOLUTION DESCRIPTION:
-1- The sales order history, the contract called quantity and the the order balance will now be properly updated.
-2- A Sales Order Line can only be deleted if ALL the Sales Order Line Records linked to a specific Sales Order Line have
been processed in the session "Process Delivered Sales Orders" .
-3- The Sales Order History will now be properly
updated (according to the
above
example).

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

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

Solution: 128050
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
If a bilateral invoicing relation is set up between the warehouses of a Manual Transfer Order and the transfer price is
defined as the Commercial Price, it is not possible to add more than 1 Outbound Order Line to the Warehouse Order (even if
the Transfer Price in the Warehouse Order Header is set to 0).
SOLUTION DESCRIPTION:
It is now possible to add a more than 1 Outbound Line to the Manual Warehouse Transfer Order, as long as the Transfer
Price in the Warehouse Order Header is not filled in.

Solution: 128051
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
The 'N, Norske Bank, Domestic' payment file (tfcmgL2601600L) does not shows the House Number, neither the Postal
Code.
For the 'N, Norske Bank, Foreign' payment file (tfcmgL2601500L) the same House Number and Postal Code are missing,
the Country Code is also not displayed.
SOLUTION DESCRIPTION:
The Norwegian Domestic file is printing the house number and the postal code. The same applies for the Norwegian Foreign
payment file (house number and postal code printed), the missing country code is displayed as well.
Other modifications have been introduced to update both payment files to the new format.

Solution: 128052
SITUATION IDENTIFIED IN:
"Purchase Change Order Sequence Numbers (tdpur4114m000)" (tdpur4114m000)
SITUATION DESCRIPTION:
When user zooms from "Purchase Order Lines (tdpur4501m000)" session to the session "Purchase Change Order Sequence
Numbers (tdpur4114m000)", system doesn't zoom to the correct purchase order number.
SOLUTION DESCRIPTION:
Now, system zooms to the session "Purchase Change Order Sequence Numbers (tdpur4114m000)" from "Purchase Order
(tdpur4501m000)" session and displays the correct purchase order number and its details.

Solution: 128061
SITUATION IDENTIFIED IN:
"Link Credit Notes to Receipt Schedules" (tfacrl102m000)
SITUATION DESCRIPTION:
The Linked amount is incorrect when the option "Assign Default Amount to Schedule Lines" is selected.
SOLUTION DESCRIPTION:
When the option "Assign Default Amount to Schedule Lines" is selected, the lesser amount among credit note balance and
schedule line is defaulted.

Solution: 128071
SITUATION IDENTIFIED IN:
"Item Purchase Data" (tdipu0101s000)
SITUATION DESCRIPTION:
The Buy-From Business partner in the session "Item Purchase Data" (tdipu0101s000) is a mandatory field. But the system
allows the user to save the record with out filling this field.
SOLUTION DESCRIPTION:
The user should enter the Buy-from BP. Other wise, the system is not allowing the user to save the record.

Solution: 128077
SITUATION IDENTIFIED IN:
"maintain address info" (tccom4130s000)
SITUATION DESCRIPTION:
Extra fields required for local Tax number for Germany and Swift-nr + Bankid
SOLUTION DESCRIPTION:
New table defined (Extra address info (tccom133)) and software is modified/added to handle this new table and fields.

Solution: 128088
SITUATION IDENTIFIED IN:
"Quotation Lines" (tdsls1101s000)
SITUATION DESCRIPTION:
For generic item, system is giving the message "Configure product variant now?" twice.
SOLUTION DESCRIPTION:
Now the problem is solved, the system will give the message "Configure product variant now?" only once.

Solution: 128094
SITUATION IDENTIFIED IN:
"Financial Institution Codes" (tfcmgl139m00l)
SITUATION DESCRIPTION:
Error Message in Session Financial Institution Codes displayed partially
SOLUTION DESCRIPTION:
Properly display the Error Message in Session Financial Institution Codes for MB language

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: 128100
SITUATION IDENTIFIED IN:
"Link Credit Notes to Receipt Schedules" (tfacrl102m000)
SITUATION DESCRIPTION:
Invoice balance is wrongly displayed.
SOLUTION DESCRIPTION:
Invoice balance is correctly displayed.

Solution: 128104
SITUATION IDENTIFIED IN:
"Billing Request Template" (cisli2101s000)
SITUATION DESCRIPTION:
"Record Already Exists" error, while saving a Billing Request Template.
It happens in the following situation.
1. The user copies an existing template to a new template and clicks the 'Save' button.
2. A question is asked whether the user wants to change the priority or not.
3. The user selects the option 'Yes', and then select the 'Priority' field and change it.
4. Now if he saves the record, the error message appears.
SOLUTION DESCRIPTION:
Now the error message does not appear.

Solution: 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: 128129
SITUATION IDENTIFIED IN:
"Print Project Costs and Revenues" (tipcs3490m000)
SITUATION DESCRIPTION:
When changing the price of a customized item after delivery, but before invoicing the delivery, the changed price was not
reflected when running session "Print Project Costs and Revenues" (tipcs3490m000).
Instead the calculation would always be based on the item 's price as it was at order entry.
SOLUTION DESCRIPTION:
When calculating and printing the Project Costs and Revenues the calculation was done on the total ordered amount of a
particular order line.
When partially delivering a given order line, and changing the involved item 's price afterwards, before the order was
released to invoicing, this changed price would not be reflected by a changed expected revenue.
From now on the calculation will be done per order line detail. When a given order had not been released yet to invoicing the
price will be updated on the order line detail. As a result the calculation of the project costs and revenues now will reflect
this changed item price.

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

Solution: 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: 128146
SITUATION IDENTIFIED IN:
"Release Outbound Advice" (whinh4202m000)
SITUATION DESCRIPTION:
For two (or more) different Sale Orders with the same Business Partner, same delivery date etc but with different Motive
(tdsls400.cdis.l), the system groups them together in the same Shipment, when running session Release Outbound Advice
(whinh4202m000), Picking List (whinh2525m100)... (the session to run depends on the Order Type used)
Due to only one Shipment Header is created, the field Motive of that grouped Shipment is the Motive specified for the first
Sales Order, and the other Motive information is lost.
SOLUTION DESCRIPTION:
For every order it is checked:
-if this order can be added to an
existing shipment (then the system will only add
a shipment line to that shipment)
-or if this order needs a new shipment
header to be created (because the order does not
match with any other existing
shipment)
But the field Motive was not checked, causing that two different orders with same data but different Motive were considered
to be part of the same shipment.
A check on Motive has been added. Now only if also the Motive matches the order can be processed in the same Shipment.

Solution: 128149
SITUATION IDENTIFIED IN:
"Manual Invoice Headers" (cisli2520m000)
SITUATION DESCRIPTION:
When user inserts a "Delivery note" in the Manual sales line and then tries to do a "Direct Processing", then the system does
not process it.
SOLUTION DESCRIPTION:
'Direct Processing' is now possible when the 'Delivery Note' is filled.

Solution: 128156
SITUATION IDENTIFIED IN:
"Clear Corrupted Inventory" (whcor0200m000)
SITUATION DESCRIPTION:
When running session "Clear Corrupted Inventory" (whcor0200m000), for all lot controlled items a check was performed on the
allocated and on order quantity. A message is displayed if one of these quantities is greater then 1.
The following message is printed: 0030 "Lot size of lot XXXX is not allowed to be greater then 1.0".
SOLUTION DESCRIPTION:
This check is now only executed for lot-by-unit items.

Solution: 128166
SITUATION IDENTIFIED IN:
"Price Calculator" (tdpcg0200m100)
SITUATION DESCRIPTION:
1. The 'Update Default Price Book' is NO in "Pricing Parameters" (tdpcg0100s000)
2. Due to this the default price book is not created when an item is created.
3. The price calculator displays the default price book when calculated for the above item, even though the price is not
retrieved from the default price book. The price is actually retrieved from the "Item Purchase Data" (tdipu0501m000)
SOLUTION DESCRIPTION:
When the 'Update Default Price Book' is NO in "Pricing Parameters" (tdpcg0100s000) and there is no other price book for the
item, then the Price book and Price book description are shown as blank in the Price Calculator.

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

Solution: 128172
SITUATION IDENTIFIED IN:
"Interest Invoice details" (cisli2110s000)
SITUATION DESCRIPTION:
Zooming on the Payment method displays both the receipt methods and the Payment methods.
SOLUTION DESCRIPTION:
Now the zooming displays only the receipt methods.

Solution: 128182
SITUATION IDENTIFIED IN:
"Tax Transactions" (tfacp1112m000)
SITUATION DESCRIPTION:
In session "Tax Transactions" (tfacp1112m000), it is possible to enter both positive and negative tax transactions. But when
a combination of positive and negative tax transactions are entered and the records are saved, the error message "Enter
Negative Amounts" comes up and asks to skip the positive tax transaction record. But later it is possible to enter the same
again and save the record.
SOLUTION
DESCRIPTION:
It is now possible to enter both negative and positive tax
transactions for a credit note and save the
records without any error
message.

Solution: 128187
SITUATION IDENTIFIED IN:
"Maintain Lots" (whltc1100s000)
SITUATION DESCRIPTION:
The lot Date could not be calculated under a very specific condition.
If the item is :
-1- lot controlled and
-2- has a shelf life that is in MONTHS or YEARS and
the date on which the lot is created is the 29th, 30th or 31st (of any month) and
the number of months or years ( in the field "shelf life") would make the calculated month equal to February,
then the date field is cannot be calculated
SOLUTION DESCRIPTION:
The lot date will now be properly calculated.

Solution: 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: 128211
SITUATION IDENTIFIED IN:
"Print Control Account Checklist" (tfacr2415m000)
SITUATION DESCRIPTION:
Ledger Account selection ignored in Print Control Account Checklist. This works correctly in the standard.
SOLUTION DESCRIPTION:
Now the report is printed correctly taking into account the ledger account selection.

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: 128242
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
The system takes lot of time in Printing the invoice.
SOLUTION DESCRIPTION:
The time taken for printing the invoice is less now and the performance is improved.

Solution: 128252
SITUATION IDENTIFIED IN:
"Maintain Quotation Lines" (tdsls1101m000)
SITUATION DESCRIPTION:
It is not possible to create a quotation line without item.
SOLUTION DESCRIPTION:
It is now possible to create a quotation line without an item.
The message "Item not filled. Please enter a text for this quotation line" will appear.

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

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

Solution: 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: 128306
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When the user uses the Swiss Localization Parameter "Payment Slip", the payment slip will be printed in the invoice.
The payment slip has 3 parts:
- The processing slip
- The receipt stub
- The code line
In the code line, the unused spaces should be left aligned and filled with zeros. Now it is blank.
In the receipt stub, the complete reference is not printed. Only the invoice document is filled. It should print the complete
reference.
SOLUTION DESCRIPTION:
Now the invoice is printed correctly.

Solution: 128309
SITUATION IDENTIFIED IN:
"Archive Warehousing Order History" (whinh2255m000)
SITUATION DESCRIPTION:
1. The Production order had Warehousing orders of transaction type Issue and Receipt.
2. While Archiving the history of such Warehouses orders, the history of the Inbound Data is not archived.
SOLUTION DESCRIPTION:
Now both the Inbound Data and the Outbound Data are archived.

Solution: 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: 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: 128375
SITUATION IDENTIFIED IN:
"Payment Schedule" (tfacp1103m000)
SITUATION DESCRIPTION:
1) Unable to close session "Payment Schedules - tfacp1103m000" when a Purchase-Invoice is overpaid.
2) While zooming from the Invoice to the Payment schedule, the schedule of another
invoice is shown.
SOLUTION DESCRIPTION:
1) When running session "Payment Schedules - tfacp1103m000" with an overpaid Purchase-Invoice the user is able to close
this session without changing anything.
2) While zooming from the Invoice to the Payment schedule, the schedule of the
invoice is shown.

Solution: 128377
SITUATION IDENTIFIED IN:
"Audit Posting Data of Electronic Bank Statement" (tfcmg5203m000)
SITUATION DESCRIPTION:
EBS batch reference and Bank Relation description was not printed correctly on the "Audited Electronic Bank Statements"
Report when more than one EBS batch or bank relation was audited.
SOLUTION DESCRIPTION:
Now EBS batch reference and Bank Relation description is printed correctly on the "Audited Electronic Bank Statements"
Report when more than one EBS batch or bank relation is audited

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

Solution: 128384
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101m200)
SITUATION DESCRIPTION:
When a subcontracting purchase order line is split into two detail deliveries the price is recalculated.
SOLUTION DESCRIPTION:
Now the system does not recalculate prices and discounts for subcontracting purchase orders

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

Solution: 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: 128406
SITUATION IDENTIFIED IN:
"Sales Order Line Details" (tdsls4501m200)
SITUATION DESCRIPTION:
When the user uses the sales order type as automatic, and maintains a detail line for existing position, which has been
already processed, then system is not processing the newly entered detail line automatically.
SOLUTION DESCRIPTION:
Now, when the user uses the sales order type as automatic, and maintains a detail line for an existing position, which has
been already processed, then system will process the new entered detail line automatically.

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

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

Solution: 128415
SITUATION IDENTIFIED IN:
"Interest Invoice Lines" (cisli2110s000)
SITUATION DESCRIPTION:
User can change the Pay-from BP in the interest invoice lines even though there is no relation between the new pay-from BP
and the Invoice-to BP.
SOLUTION DESCRIPTION:
Now a warning message will appear if the Pay-from and the Invoice-to BP's are not related to each other.

Solution: 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: 128447
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
A return sales order is created and the line is copied from the original order. This line has a to-order item (make customized
= yes). The order line is not copied.
SOLUTION DESCRIPTION:
When the sales order line quantity is negative, the make-customized checkbox cannot be on yes. When entering a normal sales
order line for a customized item, and making the quantity negative, the 'make customized' checkbox is set to 'no'. This was
not done when copying such a sales order line to a return order.
Now the copied line has a negative order quantity and the 'make customized' checkbox is set to 'no'.

Solution: 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: 128471
SITUATION IDENTIFIED IN:
"Print Remittance Letters" (tfcmg1270m000)
SITUATION DESCRIPTION:
The IBAN number is not printed although "IBAN" is specified in the payment method and the Business Partner has an
IBAN account.
SOLUTION DESCRIPTION:
The IBAN functionality has been included in the "Print remittance Letter" session (tfcmg1270m000).
When "IBAN" is specified in the payment method and the Business Partner has an IBAN account this account is printed in
the "Bank Account" column..

Solution: 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: 128491
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
In session "Sales Order Lines" (tdsls4501m000), there is inconsistency in enabling - disabling mechanism of the specific
menu option "Recalculate Price/Discounts Entire Order".
When starting the session the option is disabled and no lines are marked.
When any order line is marked, this option is be disabled.
If an empty order line is selected, this option should also be enabled because the same situation is created as when starting
the session.
SOLUTION DESCRIPTION:
The enabling and disabling of the option is correctly executed

Solution: 128513
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
The specific option |Receipt Correction" in the Receipts session (whinh3520m000) was enabled for sales return orders for a
very short time due to slow performance of the system or long client-server response times. However, during this short
period of time, the option could be used for this type of orders, which is not allowed. Under normal conditions, this
phenomenon would not have been noticed.
SOLUTION
DESCRIPTION:
The |Receipt Correction" must always be disabled for a sales return order. The enabling/disabling of this specific option has
been modified to avoid the enabling of this option under a scenario of slow performance or long response times.

Solution: 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: 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: 128593
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1. There are two purchase order lines and the first order line is created from a Sales Order, while the second one is manually
created.
2. While deleting the second line, the system asks the following question
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
"The purchase order line is linked to a sales order line. This link will be disconnected. Continue?"
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SOLUTION DESCRIPTION:
The question will not pop up when the Purchase order line is not linked to any sales order.

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

Solution: 128602
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4500m000)
SITUATION DESCRIPTION:
A Non-Warehouse Item is used in Sales Order lines. It doesn't have valid Cost structure. If this Sales Order line is to be
released to invoicing, the "Release to Invoicing (batch)" session doesn't serve the purpose as delivered quantity & Cost Of
Goods Sold have to be entered while releasing to Invoicing. Hence, the session "Release to Invoicing"(tdsls4501m130) has to
be used. How ever, this session is not accessible from the Sales Order Header.
SOLUTION
DESCRIPTION:
Since the Delivered Quantity and Cost of Goods Sold for the Non-Warehouse Items
need to be entered in "Release to Invoicing"(tdsls4501m130)
session, the zoom to this session is provided from
Sales Order Header via the Specific menu.

Solution: 128604
SITUATION IDENTIFIED IN:
"Match Purchase Receipt Line" (tfacp2544m000)
SITUATION DESCRIPTION:
In session "Match Purchase Receipt Line" (tfacp2544m000), the "Sort By" option under "View" in the main menu is not
clear.
SOLUTION DESCRIPTION:
The "Sort By" option has been changed to give a more meaningful explanation.

Solution: 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: 128617
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
It is not possible to process the Direct Delivery purchase order received with zero quantity. The system gives the error
report "No linked Purchase Order found for Sales Order".
SOLUTION DESCRIPTION:
It is possible to process the purchase order and the back order is also confirmed.

Solution: 128621
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
1. The commitment policy of the item is 'Line Entry'. The Inventory on hand is less that the Minimum Quantity to commit. A
sales order is created for this item with a quantity higher than the on hand and minimum quantity to commit. The line
can be saved and the user gets the message
+++++++++++++++++++++++++++++++++++++++++++++
"Cannot commit less than minimum allocation quantity: XX pcs"
+++++++++++++++++++++++++++++++++++++++++++++++++
After this is order quantity is reduced and saved. At this time, the
line cannot be saved with the system giving the error
message "Back order quantity
not possible"
2. At Order Entry is was possible to end up with a Sales Order Line
with a different Sold-to Business Partner then on
the Sales Order Header it belongs to.
As a result changing the Ship-to Business
Partner on the Line afterwards is not possible, since no
relation exists between the Line' s and
Header' s business partner.
Also the wrong Business Partner would be invoiced.
4. For Cost Items with No
Release to Warehousing,
the Warehouse gets
defaulted in Sales Order
lines, if the
"Split
Deliveries"
box is
checked.
5. Alternative Item that is already expired can
also be chosen, without any problem.
SOLUTION DESCRIPTION:
1. The order quantity can be reduced and the line can be saved.
2. From now on it is impossible to enter different Sold-to
Business Partners on Line and Header at order entry.
A check was built in that
compares both Sold-to Business Partners
of Line and Header.
When a difference is found, the
user will be notified by a message "Sold-to
Business Partner of Line does not match with Sold-to
Business Partner of Header." (tdslss401.4).
4. If Items do not have Release to
Warehousing mentioned in Item Sales
Data, the Warehouse doesn't get defaulted
in Sales Order lines.
5. Check has now been
added to check whether the
Alternative Item chosen is expired on
the Order Date.
If the expiry date falls before the
Order Date, then a warning message
"Alternative Item Expired" is
popped up.
If the Order Date falls before the Introduction date of the alternative item, a
warning "Alternative Item not yet introduced" is popped up, and it is
not possible for the user to choose alternative items
that are 'Expired' or 'Not
Introduced' anymore.

Solution: 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: 128667
SITUATION IDENTIFIED IN:
"Release to Central Invoicing" (tdsls4247m000)
SITUATION DESCRIPTION:
When releasing a Sales Order Line to Central Invoicing the Cost of the Goods Sold was set to 0.0 if the corresponding
Warehousing Order Outbound Line had been removed.
SOLUTION DESCRIPTION:
1. It will not be possible to remove the Warehousing Order Outbound Line as long as the Sales Order Line has not be fully
processed.
2. In case the corresponding Shipment Line or Warehousing Order Outbound Line has been removed, it will not be possible to
release the Sales Order Line to Central Invoicing.

Solution: 128673
SITUATION IDENTIFIED IN:
"Reminder Advice" (tfacr3420m000)
SITUATION DESCRIPTION:
Reminder Advice does not include Interest if the reminder advice is printed for the first time with the option "Update
Letter number" = No.
SOLUTION DESCRIPTION:
Now the interest is calculated when the reminder advice is printed for the first time with the option "Update Letter number"
= No

Solution: 128683
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
According to the calendar the warehouse is closed every Saturday and Sunday.
Entering an ATP controlled item on a sales order.
When accepting an ATP-Schedule proposal that resulted in a delivery date on Saturday or Sunday the order line details are
inserted with the suggested delivery dates without a warning. It should the calendar attached to the warehouse and adjust the
delivery date according to that calendar if needed
SOLUTION DESCRIPTION:
When accepting the proposal the delivery date is checked to
see if it fits the calendar linked to the delivery warehouse. If the
suggested date is incorrect automatically the first possible delivery date is calculated based on the calendar.

Solution: 128685
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
A sales order line is delivered from more than one stock point. This results in splitting of the sales order line into several
details. This order is returned back. The original order is linked to this new return order. Now the button "Select Orig.
Lines is pressed and all order lines are selected via session "Select Sales Order Lines for Copying" (tdsls4535m000). When
the copying process is executed two new lines are added but with the total order line quantity for each new line. This is
incorrect because the return order quantity is now doubled.
SOLUTION DESCRIPTION:
Modifications inserted to make sure the copying will result in two lines with the correct quantity and with the correct link to
the original sales order.

Solution: 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: 128704
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2125s000)
SITUATION DESCRIPTION:
1. There is an Outbound Order Line for an item with issue status 'Issue Components'.
2. From the specific menu option of the session "Issue Components" (whinh2520m000), the session "Outbound Advice by
Order Line" (whih2525m200).
3. A new advice is created here for the component, which is a LOT controlled item. The Lot field is enabled for input.
4. With out closing the item, one more advice line is created for the same item and now, the lot field is not enabled.
SOLUTION DESCRIPTION:
The Lot field is enabled now even if the user creates a new advice for the same item with out closing the session.

Solution: 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: 128724
SITUATION IDENTIFIED IN:
"Post payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
A Swiss DTA file can be created with various payments. For the 830 payment (payments to financial institutions) in Record 3
the bank identification is not inserted in the bank file. This happens when no SWIFT code is entered for the receiving bank.
SOLUTION DESCRIPTION:
The bank identification entered in session "Banks-by-pay-to Business partner" (tccom4125s000) is inserted in the file in
Record 3.

Solution: 128748
SITUATION IDENTIFIED IN:
"Import / Export Statistics" (tccom7571m000)
SITUATION DESCRIPTION:
New functionality concerning Intrastat regulations.
SOLUTION DESCRIPTION:
Instead of one sequential file named Sequential Imp/export File (B), two sequential files have been introduced,
namely Sequential Import File IDEP (Belgium) and Sequential Export File IDEP (Belgium).
The old sequential file has been deleted.

Solution: 128749
SITUATION IDENTIFIED IN:
"Generate Inbound Advice " (whinh3201m000)
SITUATION DESCRIPTION:
Inbound Advice line with the line status " Put away " gets deleted by doing "Undo" in session whinh3201m000 (Generate
Inbound Advice)
SOLUTION DESCRIPTION:
System will not delete lines that are already put away while doing Undo advice.

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

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

Solution: 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: 128772
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
Wrong starting value of total quantity.
SOLUTION DESCRIPTION:
Starting value adapted.

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: 128791
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
When session "Confirm Shipments/Loads" (whinh4275m000) is run for shipments having multiple shipment lines for the same
item, having inventory valuation method as "LIFO" and the Order is a transfer order from warehouse to project, then the
actual cost booking is booked incorrectly in Projects. This happens when the item has different order price in the orders.
SOLUTION DESCRIPTION:
The price is updated correctly in Projects based on the inventory valuation method used.

Solution: 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: 128817
SITUATION IDENTIFIED IN:
"Warehouse Orders" (whinh2500m000)
SITUATION DESCRIPTION:
1. There is a Manual (Transfer Order) Order present in the system.
2. This order is copied to a new order. If the sum of the Maximum Quantity percentage of the source order and the Over
Delivery percentage defined in "Inventory Handling Parameter" (whinh0100s000) exceeds 999.99, the system gives 'Fatal
error 205 in insert'.
SOLUTION DESCRIPTION:
The Maximum Quantity percentage of the source order would be simply copied to the new order and the Over Delivery
percentage is not added to that. It is possible to save the copied orders.

Solution: 128823
SITUATION IDENTIFIED IN:
"Purchase Order Header" (tdpur4100s000)
SITUATION DESCRIPTION:
A Purchase Order type has input controls. When the user comes from lines to header by clicking the "Header" button, the
'Save' and 'Text' buttons are not enabled.
SOLUTION DESCRIPTION:
Now, during the Second Pass of the Header the 'Save' and 'Text' buttons will be enabled though the Order type has Input
Control defined.

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

Solution: 128829
SITUATION IDENTIFIED IN:
"Print VAT Books" (tfgldl408m00l)
SITUATION DESCRIPTION:
1) Amount in transaction is not correct when you give EEC type VAT code
2) In the case of multi-finance company setup, it is printing other finance company VAT transactions.
SOLUTION DESCRIPTION:
1) Now it is printing VAT amount is correctly when you give EEC type of VAT code.
2) In the case of multi-finance company setup, it is printing current finance company VAT transactions only now.

Solution: 128880
SITUATION IDENTIFIED IN:
"Subcontracting Invoices" (tfacp3160s000)
SITUATION DESCRIPTION:
For a subcontracting invoice, the wage part in invoice currency is getting calculated using the purchase rate, instead of the
rate type used in the purchase invoice.
SOLUTION DESCRIPTION:
For a subcontracting invoice, the wage part in invoice now is getting calculated using the rate type used in the purchase
invoice.

Solution: 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: 128897
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4500m000)
SITUATION DESCRIPTION:
When creating a Sales Order Line with these properties;
Invoice goes: from the Netherlands to the Netherlands (or any other EU member), and
Goods go: from Switzerland to Switzerland (or any other NON EU member),
a message "EU tax code not defined." could appear. However, as Switzerland is the leading country for Tax determination
but not part of the EU, this message is not correct. The result was that the wrong VAT country was shown on the form
"Invoicing".
SOLUTION DESCRIPTION:
The situation when a Sales Order line is created and the;
Invoice goes: from the Netherlands to the Netherlands (or any other EU member), and
Goods go: from Switzerland to Switzerland (or any other NON EU member),
the correct default VAT country is derived and shown on the form "Invoicing" in case of a Sales Order Line.

Solution: 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: 128937
SITUATION IDENTIFIED IN:
"Release To Invoicing" (tdsls4501m130).
SITUATION DESCRIPTION:
Error: "Combination of Country ... and Tax Code ... not found; please add this combination" can occur when releasing Sales
Orders to Invoicing.
This can happen when the Ship-to Address on a detail is changed and tax of the current detail line is recalculated.
Although the calculated country / tax combination may be invalid, the record can can be saved and released to Warehousing
without any problem.
When the order is released to Invoicing the error will occur.
SOLUTION DESCRIPTION:
A check is implemented that assures a valid tax code / country combination is available for a given destination, after the
Ship-to Address of an Order line Detail has been changed and the tax code has been recalculated.
Composing of invoices in Central Invoicing is done using the following fixed aggregation criteria:
(see session help-text of session: "Global Confirmation of Future Invoices" (cisli2219m000).
invoice-to bp
sold-to bp
ship-to bp
pay-from bp
invoice-to addresss
rate determinator
sold-to address
ship-to address
pay-from address
invoice currency
terms of payment
late-payment surcharge
tax country
financial company
As a consecuence of this it is checked from now on that for a given order number, position number, ship-to business partner,
ship-to address, country combination all detail lines contain the same vat code.
(Note that of all the above mentioned fields only these can be changed manually when entering sales order line details,
therefore the other fields are irrelevant with respect
to this issue).
Otherwise, although a certain country / tax combination itself could be valid, when composing / printing the invoices, due to
the fixed aggregation criteria, there would
not be a breakdown per vat code.
The form, used to enter Sales Order Line Details (tdsls4101s200) is modified in a way that from now on it is possible to
enter / change the country and vat code manually.

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

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

Solution: 129028
SITUATION IDENTIFIED IN:
"Purchase Order Header" (tdpur4100s000)
SITUATION DESCRIPTION:
When the 'Delivery Date' field is changed in the purchase order header, the price is recalculated for the cancelled purchase
order lines also.
SOLUTION DESCRIPTION:
The Price of the cancelled order lines would remain the same and it is not recalculated now.

Solution: 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: 129087
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
When doing an internal sale from one "company" to another the system books tax even though the internal business partner
have all tax flags deactivated. When the session "Confirm Shipments/Loads" (whinh4275m000) is run, it creates an invoice
for the warehouse order. When this invoice is confirmed the tax amounts are filled and posted to finance.
SOLUTION DESCRIPTION:
No tax amounts are calculated if the tax flags are deactivated.

Solution: 129097
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4500m000)
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
1. Having a Sales Order (tdsls4500m000) with more lines. One line is advised. When changing the Ship To Address on the
Sales Order header, the Ship To address on the advised line is not changed and no message is shown.
2. B50_c_bgl0 environment only.
For the following set up a Cost / Service Item can not be released to Invoicing
"whinh0100s000" (Inventory Handling Parameters) "cost/service item on packing slip" Both
"tdisa0101s000" (Item Sales Data) "release to Warehouse" No
The message "'Packing slips should be printed before releasing to invoicing" comes up. This cannot be correct because the
Item is never released to warehousing so no Packing slip could have been printed
3. The sales price is not adjusted when linking a sales order line to a contract which conversion factor differs from the
current conversion factor.
4. When a Cross Docking Sales Order is over delivered, the new created detail line does not have the link to the Purchase
Order.
SOLUTION DESCRIPTION:
1. When a change is made on the header and a line cannot be changed, a correct error message is shown. The way of giving
through modifications from header to lines is restructured.
2. B50_c_bgl0 environment only.
For the mentioned set-up no longer the message appears and the order line is released to Invoicing
3. A check has been added which will allow the system to adjust the sales price by using the current conversion factor. A new
message called has been created to indicate the user that the sales order line has been linked to a contract and that he must
be aware that the sales price will be adjusted since the current conversion factor has been changed.
4. An over delivered Cross Docking Sales Order has the correct link to the Purchase Order. This can be seen in the Linked
Order Line Data.

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

Solution: 129101
SITUATION IDENTIFIED IN:
"Print Packing Slips" (whinh4475m000)
SITUATION DESCRIPTION:
When printing the packing slip from session "Print Packing Slip" (whinh4475m000), if the "Ship to" language of the business
partner is not English and if a unit description is maintained in the "Ship to" language, then a float exception error occurs and
the report is not printed.
SOLUTION
DESCRIPTION:
The report prints
data correctly
without any
errors.

Solution: 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: 129111
SITUATION IDENTIFIED IN:
"Items - Service" (tsmdm2100m000)
SITUATION DESCRIPTION:
When entering prices in the Item Service Data of an Item (session "Items - Service (tsmdm2100m000)") the prices are
converted to the Reference Currency and stored in the default Service Price Book as specified in parameters (session
"Pricing Parameters (tdpcg0100m000)"). Unfortunately, the conversion is done using the Purchase Rate (as specified in
session "Companies (tcemm1170m000)") instead of the Sales Rate. Particularly as the Service Price Book is considered a
Sales Price book, this is clearly incorrect. The results of this conversion can be seen in session "Price Book
(tdpcg0131m000)". The problem occurs for default sales price book also.
SOLUTION
DESCRIPTION:
Now, the Sales Rate will be used to
update the price for the default sales and service price books.

Solution: 129116
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
On form 'General' of session 'Sales Order Lines' (tdsls4101s000) the field 'Hold Back Quantity' is not visible.
SOLUTION DESCRIPTION:
The field 'Hold Back Quantity' is available and can be filled according to the Hold Back Quantity Functionality as described
in solution 126042.

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: 129125
SITUATION IDENTIFIED IN:
"VAT Books" (tfgldl408m00l)
SITUATION DESCRIPTION:
Transaction category was overlapping by business partner name when you print the report.
SOLUTION DESCRIPTION:
Transaction category is not overlapping by business partner name when you print the report.

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: 129152
SITUATION IDENTIFIED IN:
"Sales Order Line Details" (tdsls4101s200)
SITUATION DESCRIPTION:
It is not possible to add new Detail lines in the sales order, if some other Detail line of the same position has been already
been delivered. The system gives the error message "Delivery date not allowed"
SOLUTION DESCRIPTION:
It is possible to create new detail lines.

Solution: 129155
SITUATION IDENTIFIED IN:
"Transfer Direct Debits" (tfcmg4260s000)
SITUATION DESCRIPTION:
No company name is getting printed in the Direct Debits Bank File (Clieop EUR/NLG)
SOLUTION DESCRIPTION:
Now the company name is getting printed correctly in the Direct Debits Bank File (Clieop EUR/NLG)

Solution: 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: 129220
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. This is
corrected by solution 127736. But the status of those schedule lines, which are wrongly updated prior to this solution, is not
corrected.
SOLUTION
DESCRIPTION:
The correction program corrects the Receipt status of the Invoice
Schedule lines, updated with Wrong status prior
to stalling solution 127736.

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: 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: 129256
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
Two problems are reported in the report of 'Belgian Bank file for Payments in FC':
1. There should be one blank space between the amount and the currency
2. And the amount is shown without decimals
SOLUTION DESCRIPTION:
Now, the above problems are solved by:
1. Inserting a blank space between the amount and the currency
2. Amount is printed up to 2 decimal places

Solution: 129276
SITUATION IDENTIFIED IN:
"Generate Order Advice" (whina3200m000)
SITUATION DESCRIPTION:
When a Transfer (manual) order is created using session "Generate Order Advice" (whina3200m000), the field "Route" does
not get defaulted in the newly generated warehousing order.
SOLUTION DESCRIPTION:
The value of field "Route" is defaulted in the warehousing order.

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

Solution: 129286
SITUATION IDENTIFIED IN:
"Receipt Correction" (whinh3121s000)
SITUATION DESCRIPTION:
Corrupt inventory after receipt correction, especially when changing from original receipt unit to another unit.
SOLUTION DESCRIPTION:
New structure for receipt corrections prevents data corruption.
Changing the receipt unit while correcting the quantity is only possible when total stock is still available.

Solution: 129296
SITUATION IDENTIFIED IN:
"Release to warehousing (Batch)" (tdsls4246m000)
SITUATION DESCRIPTION:
Create a sales order where the Shipping Constrain is set to "Order Complete"
Create two order lines
Process the order lines until the status within Warehousing is "Staged"
Now add a new line to this sales order.
In this situation it is not possible to release the newly created line to warehousing. The message "Set Could not be released
completely" appears.
It is possible to ship the two lines within warehousing. This is not correct because there is still another order line present
that should be part of the shipment because of the shipping constraint "Order Complete"
After the two lines are shipped it still is not possible to release the new line to warehousing.
SOLUTION DESCRIPTION:
For shipping constraint "Order Complete" a check is done when confirming the shipment to see if there still are lines within
sales that are not yet released to warehousing.
If there are still lines present within sales the order lines within warehousing are not shipped.
New order lines can be released to warehousing even if there are other lines for the same order that are already released to
warehousing.

Solution: 129300
SITUATION IDENTIFIED IN:
"Matched Purchase Invoice Transactions" (tfacp1133s000)
SITUATION DESCRIPTION:
When on the second form of session "tfacp1133s000 - Matched Purchase Invoice Transactions" the reporting period is changed
this is not updated. When you get into the session again you can see the old value is displayed again.
SOLUTION DESCRIPTION:
The transaction is updated with the changed value now

Solution: 129325
SITUATION IDENTIFIED IN:
"Copy Received Purchase Invoices" (tfacp1210s000)
SITUATION DESCRIPTION:
After solution 119986, when the session "Copy Received Purchase Invoices" (tfacp1210s000) is started the order of the data
displayed is using index 2 (supplier, document). It is now not possible to customize the default order of the index during
startup of the session as the changes are in the script.
SOLUTION
DESCRIPTION:
It is now possible to customize the session, so that the starting "sort by" of session can be changed.

Solution: 129335
SITUATION IDENTIFIED IN:
"Change Prices/Discounts after Receipts" (tdpur4122m000)
SITUATION DESCRIPTION:
The Name of the Business Partner is not displayed in the session and only the Business Partner title is displayed.
SOLUTION DESCRIPTION:
Now, the name of the Business Partner is correctly displayed.

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

Solution: 129352
SITUATION IDENTIFIED IN:
"Release to Invoicing (batch)" (tdsls4247m000)
SITUATION DESCRIPTION:
When releasing an orderline without quantity to invoicing, error "cannot determine COGS" appears.
SOLUTION DESCRIPTION:
System was trying to read the cost of goods sold for such a line. But, because the sales order line with qunatity zero is not
known in Warehousing, the error appears.
Now a sales order line without quantity can be released to invoicing without errors.

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

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

Solution: 129383
SITUATION IDENTIFIED IN:
"Generate Purchase Order Advice for Sales Order" (tdsls4240m000)
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
It is not possible to create a Purchase Order Advice for a Direct Delivery Sales Order although the parameter "Refuse
Blocked Direct Deliveries" is set to no. The option "Generate Purchase Order Advice for Sales Order" in session "Sales
Order Lines" (tdsls4501m000) is disabled for all blocked orders. Session "Generate Purchase Order Advice for Sales Order"
(tdsls4240m000) cannot be run for blocked orders.
SOLUTION DESCRIPTION:
For Direct Delivery Sales Order Lines that are blocked, a Purchase Order Advice can be generated (session tdsls4240m000). Also the option in
the Specific menu of "Sales Order Lines" (tdsls4501m000) is enabled. During the Transfer of the Purchase Order Advice the parameter "Refuse
Blocked Direct Deliveries" is checked. If 'yes', no Purchase Order is generated. If 'no' a Purchase Order is generated.
For cross docking orders that are blocked no Purchase Order Advice can be generated.

Solution: 129394
SITUATION IDENTIFIED IN:
"Print Warehousing Order History" (whinh2450m000)
SITUATION DESCRIPTION:
1) When option "Order lines" alone is chosen, the transaction date is printed incorrectly in the line records.
2) When Order set range is given, the details of the first Order set is not printed.
SOLUTION DESCRIPTION:
1) Now, the Transaction date is printed correctly when the option "Order lines" alone is chosen.
2) The information about all the Order sets are printed including the first Order set when a range of Order sets are specified.

Solution: 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: 129409
SITUATION IDENTIFIED IN:
"Archive Inventory Transactions by Item and Warehouse" (whinr1210m000)
SITUATION DESCRIPTION:
When archiving/deleting is done, inventory receipt transaction consumptions with a date greater than the entered date can be
deleted.
This is because only the date of the inventory receipt transactions is checked and not the date of the related inventory
receipt transaction consumptions.
Example:
100 Pieces of item A are received on 31-12-2000
Complete consumption of this receipt takes place on 01-01-2002
If session "Archive Inventory Transactions by Item and Warehouse" (whinr1210m000) is executed for this item with cutoff date
01-01-2001, both the inventory receipt transaction and the inventory receipt transaction consumption are deleted despite of
the fact that the consumption date is greater then the cutoff date. This is wrong, in this case nothing must be deleted.
SOLUTION DESCRIPTION:
The date of the inventory receipt transaction consumptions is checked properly, so that only inventory transactions within
the date boundary are deleted.

Solution: 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: 129447
SITUATION IDENTIFIED IN:
"Generate Outbound Advice" (whinh4201m000)
SITUATION DESCRIPTION:
This situation only applies in case a package definition is involved and the requested unit is not "binding".
Different outbound advices are generated for corresponding quantities/units of the same item.
In case a package definition is involved and the requested unit is not "binding", the outbound advice should be similar for
corresponding quantities.
Example:
Item "A" has inventory unit "pcs" and package definition "B".
Levels of package definition "B":
Level 1 pcs
Level 2 box = 10 pcs
Level 3 pal = 10 box = 100 pcs
Generating an outbound advice for 10 "box" and generating an advice for 1 "pal" does not always give the same result, even
though the quantities are corresponding (100 "pcs").
The outbound advice for 10 "box" sometimes advises picking from different stock points, while the outbound advice for 1
"pal" would advise to pick 1 "pal".
The outbound advice for 10 "box" should also advise to pick 1 "pal".
SOLUTION DESCRIPTION:
In case a package definition is involved and the requested unit is not "binding", the same logic is used for every requested
unit. This results in identical outbound advices.

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

Solution: 129472
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
If the warehouse field is filled for the ship-to BP (tccom4111s000) the defaulting of the Warehouse on the order lines is
incorrect for Consignment Invoicing orders. It defaults with the warehouse set in the Ship-To BP data and not with the
Consignment Owned Warehouse
SOLUTION DESCRIPTION:
The process of determining the default
warehouse is adjusted. In case of
Consignment Invoicing always the Consignment
Owned warehouse is selected.

Solution: 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: 129532
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
When creating a Purchase Order Line, the VAT Country was determined incorrect in this case;
When both Goods and Invoice are flowing from one EU country to another (f.i. from the Netherlands to Germany) this
situation can be characterized as an ICT; Intra Community Transaction. In this ICT situation, the country where the
Ship-From Business Partner is located, is leading for VAT determination. It was based, however, on the Ship-To country.
This was incorrect.
SOLUTION DESCRIPTION:
In an ICT Situation, where both Goods and Invoice flow from one EU country to another (f.i. from the Netherlands to
Germany) the default VAT country will be the country of the Ship-From Business Partner.

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

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

Solution: 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: 129555
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When the 'Rounding factor' of the Purchase Order Currency is very high, there is a difference between Invoice Accrual
amount and the amount posted with 'Purchase/result' integration transaction entry.
SOLUTION DESCRIPTION:
The difference has been eliminated and both the amounts are same now.

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

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

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

Solution: 129582
SITUATION IDENTIFIED IN:
"Item Purchase Data" (tdipu0101s000)
SITUATION DESCRIPTION:
When the session "tipcs2220m000" (Generate Project structure for Product Variant) is run, error message "Buy From
business Partner not present".
It is not possible to generate the product structure for a product variant for a generic item. You are forced to enter a Buy -
From business partner.
The same applies when copying a standard product structure to customized structures.
Customer will be forced to enter Buy-from BP's in all their manufactured and generic components to carry on with these and
related process.
It should be possible for generic and manufacturing item project structures to be created without entering a value in the Buy
from Business Partner as they are usually manufactured internally.
SOLUTION DESCRIPTION:
Now the above-mentioned problem is solved when generating project structure or when copying a standard product structure
to a customized structure.

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

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

Solution: 129596
SITUATION IDENTIFIED IN:
"Inbound Advice" (whinh2515m000)
SITUATION DESCRIPTION:
When compiling any of the following scripts:
whinh2515
whinh3122
whinh3200 and
whinh3520, following error appears:
Error: 5 arguments expected for function 'whinh.dll4275.confirm.shipment'.
SOLUTION DESCRIPTION:
Number or arguments has been corrected.

Solution: 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: 129629
SITUATION IDENTIFIED IN:
"Copy Sales Orders" (tdsls4201s000).
SITUATION DESCRIPTION:
When copying a sales order to another Sold-to Business Partner, the country field (tdsls401.ccty) of the new Sales Order Line
is the same as on the original line.
SOLUTION DESCRIPTION:
When copying a Sales Order to another Sold-to Business Partner the country field (tdsls401.ccty) will be filled with the
right value. The value will be the same as when a line is added to the new created Sales Order manually.
During copy, the right country is determined when defaulting the country field belonging to the Sold-to Business Partner
that is on the new created Order Header. The same country will be used on the lines.
When the original lines are split, (so details exists), the details are all totalized per line. Although the original details
may have different Ship-to Addresses and therefore different countries, when copying them to another Sold-to Business
Partner (having another Ship-to Address) this is not relevant anymore.

Solution: 129630
SITUATION IDENTIFIED IN:
"Confirm Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When receiving a Sales Return Order, the Financial Integration created for the Sales Item or Warehouse Issue Surcharges and
the Inventory Receipt Transactions (as registered in the table whinr112) could be created with an incorrect amount.
This happens when a Variance (as registered in the table whinr116) was assigned to the original Receipt (from which the
returned Issue was consumed) after the Issue had been processed.
This only happens if the Item Valuation Method 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: 129637
SITUATION IDENTIFIED IN:
"Generate Picking List" (whinh4415m000)
SITUATION DESCRIPTION:
1. Revision number not printed on Picking list.
2. When multiple sequence number exists for the same position of a warehouse order outbound line, and for each sequence
number
if different text is maintained, only the last text is printed and only once per position number.
SOLUTION DESCRIPTION:
1. Now Revision number is printing in both the reports of picking list.
2. Now text is correctly printed for each sequence number.

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

Solution: 129669
SITUATION IDENTIFIED IN:
"Confirm Shipment" (whinh4275m000)
SITUATION DESCRIPTION:
-1- A shipment line with a Cost Item (that is thus released to Warehousing) and an Ordered Quantity and a Shipped Quantity
of 0.0 could not be confimed.
The session Confirm Shipment (whinh4275m000) displayed the error message "Confirm Shipment Failed".
-2- When Sales Order Lines were split when confirming a shipment, an Order Header Discount could be calculated for a
Cost Item.
SOLUTION DESCRIPTION:
-1- It is now possible to confirm the shipment
-2- No Order Header Discount will be calculated for a Cost Item.

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

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

Solution: 129713
SITUATION IDENTIFIED IN:
"Print Order Acknowledgments" (tdsls4401m000)
SITUATION DESCRIPTION:
When printing a Sales Order with 'Order Line Types to Print' on 'All Lines', the title of the contact is incorrect printed.
SOLUTION DESCRIPTION:
The correct title is printed on the Order Acknowledgment.

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: 129749
SITUATION IDENTIFIED IN:
"Sales Quotation Price Inquiry" (tdsls1501s110)
SITUATION DESCRIPTION:
When zooming from session "Sales Quotation Lines" (tdsls1501m000) to session "Sales Quotation Price Inquiry"
(tdsls1501s110), the Gross Margin Percentage is incorrect calculated.
The same happens with session "Sales Contract Price Inquiry" (tdsls3501s110)
SOLUTION DESCRIPTION:
To make sessions "Sales Quotation Price Inquiry" (tdsls1501s110) and "Sales Order Price Inquiry" (tdsls4501s110) more
comparable the cost price is displayed in the sales price unit now.
The Gross Margin is displayed as Gross Profit as that is what is calculated. The Gross Profit is calculated correct.
The same is done with session "Sales Contract Price Inquiry" (tdsls3501s110)

Solution: 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: 129802
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1. A the Purchase Order Line is created.
2. The order line is received.
3. The price of the Purchase Order Line changes if the Recalculate Price and Discounts is done for this purchase order line.
4. The price should not be recalculated if the order line has been received already.
SOLUTION DESCRIPTION:
The Price and Discount of the purchase order line will not be recalculated, if the order line has been partially (or) fully
received already.

Solution: 129806
SITUATION IDENTIFIED IN:
"Change Prices/Discounts after Receipts" (tdpur4122m000)
SITUATION DESCRIPTION:
Some Purchase Order Lines that are received, and not processed are not displayed in the above session.
SOLUTION DESCRIPTION:
All the relevant Purchase Order Lines are displayed, now.

Solution: 129811
SITUATION IDENTIFIED IN:
"Quotations" (tdsls1100s000)
SITUATION DESCRIPTION:
For languages 1 and 3 the description of the second sales representative is missing
SOLUTION DESCRIPTION:
Enlarged the available space of the label on the form so now a description is available for all 3 main languages.

Solution: 129821
SITUATION IDENTIFIED IN:
"Convert Electronic Bank Statements" (tfcmg5202m000)
SITUATION DESCRIPTION:
During conversion of an Electronic Bank Statement (EBS) file, the "Reference" and the "Description" text is not put in the
first line, but in the second line.
SOLUTION DESCRIPTION:
The "Reference" and the "Description" text are stored, starting from the first line.

Solution: 129835
SITUATION IDENTIFIED IN:
"Print Open Entries" (tfacp2421m000)
SITUATION DESCRIPTION:
On form 3 of session "Print Open Entries" (tfacp2421m000), a label is missing in German language.
SOLUTION DESCRIPTION:
The label is present in form 3 for German language.

Solution: 129847
SITUATION IDENTIFIED IN:
"Print Sales Contract Reminders" (tdsls3406m000)
SITUATION DESCRIPTION:
When printing the reminder during the effective period no output will be created.
SOLUTION DESCRIPTION:
The calculation needed when checking the percentage of the elapsed period with the "Minimum Time Required for
Evaluation" was incorrect. Changed the calculation to make the comparison working correctly.

Solution: 129850
SITUATION IDENTIFIED IN:
"Reprint Invoices" (cisli2405m000)
SITUATION DESCRIPTION:
When printing a Sales Invoice in case of a Bilateral or Triangular setting, the message "Do Not Print" is printed on the Inv.
Header.
SOLUTION DESCRIPTION:
This message will not appear on the Invoice Header anymore.

Solution: 129866
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation (LIFO by Year)" (whinal201m00l)
SITUATION DESCRIPTION:
The report did not show any values when the Currency System of the company was set to "INDEPENDENT".
SOLUTION DESCRIPTION:
The report will now show the correct values.

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: 129904
SITUATION IDENTIFIED IN:
"Print sales contract reminders" (tdsls3406m000)
SITUATION DESCRIPTION:
Item Sales Text added in Item Sales Data (tdisa0101s000) and contract lines linked to sales orders cause the report details
from 'Print Contract Reminders' (tdsls3406m000) to be moved up. This occurs when the report is printed the second time,
without closing the session.
SOLUTION
DESCRIPTION:
The variable used for printing the report details: item code, description, text, etc. is being used for sorting the report. The
program script as well as the report has been modified so this variable will get the right value so it can used to sort the data.

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

Solution: 129908
SITUATION IDENTIFIED IN:
"Reprint Invoices" (cisli2405m000)
SITUATION DESCRIPTION:
It was not possible to reprint the sales invoice from archiving company and it is giving an error message stating that ' No
Data within selection'.
SOLUTION DESCRIPTION:
It is reprinting the sales invoice from archiving company.

Solution: 129925
SITUATION IDENTIFIED IN:
"Release to Warehousing (Batch)" (tdsls4246m000)
SITUATION DESCRIPTION:
When releasing a range to warehousing with in the range one borderline cannot be released because the quantity is partially
committed and the Shipping Constraint is 'Ship Complete, an error message is given and nothing is released.
SOLUTION DESCRIPTION:
For the line that cannot be released to Warehousing a line is printed on the error report ("Quantity not yet fully committed.
Release to warehousing not allowed"), the other lines in the range that can be released to Warehousing are released.

Solution: 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: 129948
SITUATION IDENTIFIED IN:
"Re-Print Sales Invoices" (cisli2405m000)
SITUATION DESCRIPTION:
In Italian Invoices, the tax total printed in the summary box and the invoice tax amount printed in the VAT section box are
different. They are rounded differently.
SOLUTION DESCRIPTION:
Now the same amounts are printed on both the places.
SOLUTION <130064> ALSO.
VERSION(S):
B50_b, B50_c

Solution: 129953
SITUATION IDENTIFIED IN:
"Sales Orders below/above allowed margin" (tdsls4518m000)
SITUATION DESCRIPTION:
Cancelled sales order lines still appear in "Sales orders below/above Margin" (tdsls4518m000) mixed with active sales
orders that are below or above the margin.
SOLUTION DESCRIPTION:
It is preferred to see the cancelled lines in the session "Sales orders below/above Margin" (tdsls4518m000). But to make the
session more user friendly two specific options are introduced that gives the user the possibility to show all the lines or to
see the not cancelled order lines only.
Also the deleted order lines were visible in session tdsls4518m000. This is of no use so these lines are no longer visible.
This also applies to the session "Quotations below/above Margin" (tdsls1518m000)

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

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

Solution: 129977
SITUATION IDENTIFIED IN:
"Archive Inventory Transactions by Item and Warehouse" (whinr1210m000)
SITUATION DESCRIPTION:
Message "Error 206 (record is not locked) on whinr110 in db_delete(51)" is shown and the archiving process is aborted.
SOLUTION DESCRIPTION:
This situation is corrected and the process completes without giving this message.

Solution: 129989
SITUATION IDENTIFIED IN:
"Release to Invoicing" (tdsls4247m000)
SITUATION DESCRIPTION:
Error message "Error 205 (Out of range)", when "Release to Invoicing" is done. This happens when the cost price holds more
than 13 digits.
SOLUTION DESCRIPTION:
Now the error does not occur.

Solution: 129990
SITUATION IDENTIFIED IN:
"Manual sales Invoice Headers" (cisli2120m000)
SITUATION DESCRIPTION:
While entering the information in Text editor, it is considering the default language as the language, which has been defined
by the user in user data.
SOLUTION DESCRIPTION:
While entering the information in Text editor, it is considering the default language as the language, which has been defined
at the business partner roles not the language that is defined in the user data.

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: 130045
SITUATION IDENTIFIED IN:
"Direct Network Communication" (tcedi7205m000/ecedi7205m000)
SITUATION DESCRIPTION:
When reading an order acknowledgment and an order change acknowledgment in one run, no differences report is generated
for the order change acknowledgment. When these message are processed in different processes, a is generated properly,
for both messages being the |Differences Between Purchase Order and Order Response" (B40_c) or |Differences Between
Purchase Order and Order Acknowledgment" (B50_b/c)".
SOLUTION
DESCRIPTION:
Due to incorrect initialization, the report was not generated
in the described situation. In order to be able to distinguish between
the order acknowledgment and the order change acknowledgement,
a new report has been created for the latter message:
|Differences Between Purchase Order & Order
Change Response" (B40_c) and |Differences Between
Purchase Order & Order Change
Acknowledgment" (B50_b/c)".

Solution: 130064
SITUATION IDENTIFIED IN:
"Print Invoices" (cisli2400m000)
SITUATION DESCRIPTION:
When multiple tax codes exist for an invoice, then the tax amounts are not rounded properly. The tax amounts printed per
tax code in the VAT section box, is wrong. This happens only for the Italian Invoices.
SOLUTION DESCRIPTION:
Now the tax amounts are printed correctly.

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: 130082
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
In Report N 43 - Sweden, Bankgiro Domestic, in the closing report, the number of lines should be mentioned, but in the
report the numbers of payments, which is shown is always zero.
SOLUTION DESCRIPTION:
Now the report shows the number of lines.

Solution: 130085
SITUATION IDENTIFIED IN:
"Sales and Warehouse Order Invoice Lines" (cisli2545m000)
SITUATION DESCRIPTION:
For bilateral or triangular invoicing a price type is defined in session "Entity-Entity relationship" (tcemm2510m000). If the
price type is "Commercial Price", the invoice amount is not rounded according to the rounding of the invoice currency.
If the price type is "Transfer Price", the amounts are calculated and rounded correctly.
SOLUTION DESCRIPTION:
Before assigning the amounts to session "Sales and Warehouse Order Invoice Lines" (cisli2545m000), the amounts are rounded
according to the invoicing currency. A check is inserted to perform this only in case the price type is 'Commercial Price".

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

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

Solution: 130115
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
Enter a sales order (tdsls4100s000). Change the order type so the BP/Order type combination triggers input control. The field
"Sales Office" (tdsls400.cofc) is in the Sales Input Control fields (tdsls0195m000). The user is not automatically taken to
the Sales Office field, the Order Lines session (tdsls4101s000) will not open and user seems stuck on last form.
SOLUTION DESCRIPTION:
The above situation happens because after the input control is triggered (after changing the Sales Order Type) the field "Sales Office" is not
visited again. When the Sales Office field is not empty it will now not be necessary to visit this field again. The Order Lines session
(tdsls4101s000) will
automatically open when all other Sales Input
Control fields are
visited.

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

Solution: 130125
SITUATION IDENTIFIED IN:
"Maintain and Confirm Backorders" (tdsls4125m000)
"Release to Warehousing" (tdsls4501m140)
"Release to Invoicing" (tdsls4501m130)
SITUATION DESCRIPTION:
When 'new group' button is used to search for an order in session "Maintain and Confirm Backorders" (tdsls4125m000) the
message "Sold-to-Business Partner of Line does not match with Sold-to-Business Partner of Header" is displayed.
This also happens in session "Release to Invoicing" (tdsls4501m130) and "Release to Warehousing" (tdsls4501m140)
SOLUTION DESCRIPTION:
When searching for a Sales Order no incorrect messages are shown.

Solution: 130127
SITUATION IDENTIFIED IN:
"Remove Confirmed Shipments" (whinh4250m000)
SITUATION DESCRIPTION:
Run session "Remove Confirmed Shipments" (whinh4275m000) with checkbox "Print error report" checked. When one of the
shipments in the range cannot be removed the job fails in a runtime error whereas a report should be printed.
SOLUTION DESCRIPTION:
When an error occurs in session "Remove Confirmed Shipments" (whinh4275m000) when this session is placed in a job, the
functionality is as follows:
1. The checkbox "Print error report" is checked on session "Remove Confirmed Shipments" (whinh4275m000): the job is
completed and an error report is printed.
2. The checkbox "Print error report" is not checked on session "Remove Confirmed Shipments" (whinh4275m000): the job
fails in a runtime error.

Solution: 130154
SITUATION IDENTIFIED IN:
"Compose/Post/Print Invoices" (cisli2200m000 )
SITUATION DESCRIPTION:
Page number is not correct, while printing the copy of the original invoice.
SOLUTION DESCRIPTION:
Page number is correct, while printing the copy of the original invoice.

Solution: 130201
SITUATION IDENTIFIED IN:
"Post Sales/Warehouse Order Invoice Data" (cisli3200m000)
SITUATION DESCRIPTION:
Two Problems:
1. In a single currency system, wrong rate is filled in Finace for the Integration transactions "Cost of Goods sold"
2. When a single order has many lines (> 15,000) then fatal error "Out of range" occurs while posting the invoice.
SOLUTION DESCRIPTION:
The rates are filled correctly in the Finance.
The Fatal Error Out of Range does not occur

Solution: 130214
SITUATION IDENTIFIED IN:
"Print Purchase Order Report" (tdpur4405m000)
SITUATION DESCRIPTION:
The report "Print Purchase Order Report " is showing the wrong back order quantities, when it printed with the option "order
lines" only is checked.
SOLUTION DESCRIPTION:
Now the problem is solved the report "Print Purchase Order Report " will show the correct back order quantities, even when it
printed with the option "order lines" only.
SOLUTION 130214, PLEASE DOWNLODE SOLUTION 130544
**********************************************************************
*********** A NEW SOLUTION IS GIVEN FOR THE DEFECT 130414, BECAUSE AN ADDITIONAL ISSUE IS
ADDED TO THE SAME DEFECT **************************
*******************************************************************************************************
**********************************************************************************************
VERSION(S):
B50_b, B50_c

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: 130301
SITUATION IDENTIFIED IN:
"Process Delivered Sales Orders" (tdsls4223m000)
SITUATION DESCRIPTION:
When deleting a range of Cancelled Sales Orders, the value of the field "Delete up to (Date)" is not taken into account. All
cancelled sales orders in the range are deleted.
SOLUTION DESCRIPTION:
For Sales Orders that are not cancelled the invoice date is checked. If the invoice date of a Sales Order Line lies before the
value of the "delete up to (date)" field the Sales Order Line can be deleted.
Cancelled orders are not invoiced so do not have an invoice date. For Cancelled Orders the order date is checked now: If the
order date of a Cancelled Sales Order Line ilse before the value of the "delete up to (date)" field the Sales Order Line can be
deleted

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: 130544
SITUATION IDENTIFIED IN:
"Print Purchase Order Report" (tdpur4405m000)
SITUATION DESCRIPTION:
The report "Print Purchase Order Report " is showing the wrong back order amounts, when it printed with the option "order
lines" only is checked.
SOLUTION DESCRIPTION:
Now the problem is solved the report "Print Purchase Order Report " will show the correct back order amounts, even when it
printed with the option "order lines" only.
SOLUTION 130544, PLEASE DOWNLODE SOLUTION 130214
********************************************************************
*********** A NEW SOLUTION IS GIVEN FOR THE DEFECT 130414, BECAUSE AN ADDITIONAL ISSUE IS
ADDED TO THE SAME DEFECT *************************
*******************************************************************************************************
*********************************************************************************************
VERSION(S):
B50_b, B50_c

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: 130740
SITUATION IDENTIFIED IN:
"Process Delivered Sales Orders" (tdsls4223m000).
SITUATION DESCRIPTION:
When running session "Process Delivered Sales Orders" (tdsls4223m000) for an order that is not suited to be processed
(yet), message "Process Completed" pops up, although the order has not been processed at all.
Steps to take:
1. Start session "Sales Orderlines Overview" (tdsls4510m000).
2. Select tab "Status".
3. Select an order not having "Process Delivered Sales Orders" in column "Description".
4. Start session "Process Delivered Sales Orders" (tdsls4223m000).
5. Check "Process Order Data" and enter the Order number, as selected in step 3.
6. Choose "Continue".
7. Message "Process completed" pops up, suggesting the order has been processed which is wrong.
SOLUTION DESCRIPTION:
Correct message is being displayed when Processing Delivered Sales Orders.
If order(s) could be processed message "Process completed" pops up.
If nothing could be processed message "Sales: No Data within Selection" is displayed.

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

Solution: 130848
SITUATION IDENTIFIED IN:
Print Purchase Order Reports (tdpur4405m000)
SITUATION DESCRIPTION:
While printing the Purchase Orders by Currency in the session, system doesn't print the Purchase Order Total in Home
Currency. It is shown as 0.
SOLUTION DESCRIPTION:
Now, the amounts for the Purchase Order Total are correctly printed for Home Currency Total.

Solution: 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: 131095
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
One label each is missing in the sessions mentioned below:
"Purchase Order Lines" (tdpur4501m000)
"Purchase Order Line Details" (tdpur4501m200)
"Sales Statistics Parameters" (tdsst0100m000)
"Sales order lines overview" (tdsls4510m000)
"Addresses" (tccom4130s000)
SOLUTION DESCRIPTION:
Missing labels are available via this solution.

Solution: 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: 157178
SITUATION IDENTIFIED IN:
"Receipts via DDC" (whinh3520b000)
SITUATION DESCRIPTION:
The user is unable to compile the script used for receiving via DDC.
SOLUTION DESCRIPTION:
Solution 122071 changes needed to be added to DDC script. This eliminates an unresolved reference.

Solution: 157949
SITUATION IDENTIFIED IN:
"Print Sales Order Acknowledgment" (tdsls4401m000)
SITUATION DESCRIPTION:
When printing the sales order acknowledgement with the flag "Option Descriptions" selected, the process run time is taking
much too long.
SOLUTION DESCRIPTION:
Now when printing the sales order acknowledgement with the flag "Option Descriptions" selected, the process run time has
been reduced.

Solution: 157961
SITUATION IDENTIFIED IN:
"Print Finalized Transactions by Ledger Account" (tfgld1406m000)
"Reprint Journal Report" (tfgld1410m000)
"Print Finalized Transactions by Date" (tfgld1440m000)
"Print Journal" (tfgld1441m000)
SITUATION DESCRIPTION:
The Reference column on the report was not wide enough to display the entire reference text.
SOLUTION DESCRIPTION:
The Reference column has been widened so all of the reference text will be displayed. This problem also existed in other
sessions. The sessions which have been corrected are listed above this section.

Solution: 157973
SITUATION IDENTIFIED IN:
"Intergroup Transactions" (tfgld2102s000)
SITUATION DESCRIPTION:
If journal transaction changes from debit to credit the intergroup transaction doesn't change automatically. Moreover, error
message doesn't appear and transaction can be finalized. The remaining amount is calculated incorrectly and that's why error
doesn't occur when original transaction changes from debit to credit.
SOLUTION
DESCRIPTION:
The calculation of the remaining amount has been changed. If original transaction changes from debit to credit or from credit
to debit intergroup transaction has to be changed as well. Otherwise, error message appears. The debit/credit field of
intergroup transaction has been changed from Display field to Input field. Now user doesn't have to delete and insert new
intergroup transaction if the posting of the original transaction was changed.

Solution: 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: 158036
SITUATION IDENTIFIED IN:
"Print Sales Orders" (tdsls4405m000)
SITUATION DESCRIPTION:
The amounts shown in the report aren't always correct for a certain combination of parameters and if the amount is based on
either 'Delivered quantity' or 'Outstanding quantity' and backorders exist for an order line.
SOLUTION DESCRIPTION:
When the amount is based on 'Delivered quantity' or 'Outstanding quantity' and a backorder exist for the order line the
amounts displayed in the report are correct.
See below figure for an explanation.
Orderlines/sub-details | Amnt based on | Backorder delivered | Backorder conf? | Show only backorders | Result | Comment
--------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------
Orderline | ordered | No | No | -- | 600 |
| delivered | No | No | -- | 360 |
| outstanding | No | No | -- | 240 |
--------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------
Sub details | ordered | No | No | No | 600 |
| delivered | No | No | No | 360 |
| outstanding | No | No | No | 240 |
| ordered | No | No | Yes | 600 |
| delivered | No | No | Yes | 360 |
| outstanding | No | No | Yes | 240 |
--------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------
Orderline | ordered | No | Yes | -- | 600 |
| delivered | No | Yes | -- | 360 |
| outstanding | No | Yes | -- | 240 |
| ordered | Yes | Yes | -- | 600 |
| delivered | Yes | Yes | -- | 600 |
| outstanding | Yes | Yes | -- | 0 |
--------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------
Sub details | ordered | No | Yes | No | 600 | 1)
| | | | | 240 |
| delivered | No | Yes | No | 360 |
| | | | | 0 |
| outstanding | No | Yes | No | 0 |
| | | | | 240 |
| ordered | No | Yes | Yes | 240 | 2)
| delivered | No | Yes | Yes | 0 |
| outstanding | No | Yes | Yes | 240 |
| ordered | Yes | Yes | No | 600 | 3)
| | | | | 240 |
| delivered | Yes | Yes | No | 360 |
| | | | | 240 |
| outstanding | Yes | Yes | No | 0 |
| ordered | Yes | Yes | Yes | no data |
| delivered | Yes | Yes | Yes | no data |
| outstanding | Yes | Yes | Yes | no data |
1) The system shows the subdetails of the order line. Because you've confirmed the backorder there's are two records with sub
details. The order line itself has an amount of 600. Because you've confirmed the backorder there's also a record for the
backorder. This backorder consists of an amount of 240. The system prints both sub detail lines, e.g.: the order line itself
and the backorder line, which exists after confirmation of the backorder.
2) Because the system only shows the backorder lines here and the sub details of the order line are shown separately the
system shows an amount of 240 here for the backorder.
3) Originally there's an order line for a total amount of 600. After receiving a part of the goods, there's also a backorder,
which is another sub detail of the total orderline. That means the system shows both the amount of the original order line
(600) as the backorder (with amount 240) when you choose to display the amounts by ordered quantity.

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: 158116
SITUATION IDENTIFIED IN:
"Print Journal" (tfgld1441m000)
SITUATION DESCRIPTION:
Two separate problems are occuring on this report.
1.) The amount field is not printing for transactions with negative amounts.
2.) No totals are not printing when the localization parameter periodical journal is set to no.
SOLUTION DESCRIPTION:
Both problems have been solved.
1.) An incorrect restriction was in the report. The condition only allowed amounts that were greater than zero to print. This
restriction was removed,
and now the amounts will print even when they are less than zero.
2.) The report used when the localization parameter "periodical journal" is set to No did not make use of the value of the
parameter. The report has
been changed to make use of this parameter and now the totals will be printed.

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: 158154
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
System allows the receipt of more quantity than was shipped when performing an item-transfer.
SOLUTION DESCRIPTION:
System changed to ensure receipt quantity cannot exceed the shipment quantity.

Solution: 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: 158195
SITUATION IDENTIFIED IN:
"Print Trial Balance" (tfgld3402m000)
"Print Trial Balance by Currency" (tfgld3403m000)
"Print Trial Balance - Ledger Account/Dimensions" (tfgld3404m000)
"Print Trial Balance - With Dimensions" (tfgld3405m000)
"Print Trial Balance - Dimension Code/Ledger Accounts" (tfgld3406m000)
"Print Trial Balance - Dimension Type/Dimension Code" (tfgld3408m000)
SITUATION DESCRIPTION:
Session and form field help texts were not present in some cases and inadequate in some cases. This caused confusion about
the functionality of some of the form options and the report output.
SOLUTION DESCRIPTION:
For the trial balance sessions, field and session help texts have been refined/added.

Solution: 158215
SITUATION IDENTIFIED IN:
"Adresses" (tccom4130s000)
SITUATION DESCRIPTION:
The check on VAT numbers for Ireland did not accept all possible control codes.
SOLUTION DESCRIPTION:
Since 2001 new Irish VAT numbers have been issued by http://www.revenue.ie.
However no official document has been issued with its specification.
Since we did not receive any information, Baan tried to figure from new VAT numbers what could likely be the difference,
and changed the check.
The check on VAT numbers for Ireland does now accept all possible control codes known.

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: 158247
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When reading in an EDI sales order acknowledgement(855) the warehouse field on the Direct Delivery purchase order line is
updated. It should not be updated since this is a direct delivery purchase order.
SOLUTION DESCRIPTION:
The EDI script has been modified to not update or fill the warehouse field on a direct delivery purchase order. If the
purchase order is direct delivery then the purchase order lines warehouse field should remain blank.

Solution: 158262
SITUATION IDENTIFIED IN:
"Print BLWI-Declaration" (tccom9430m000)
"Print BLWI-Declaration" (tccoml405m000)
SITUATION DESCRIPTION:
Layout of the front page after change per January 1st of this year no longer according official layout.
SOLUTION DESCRIPTION:
Layout is changed in accordance to the offical layout.

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: 158305
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2420m000)
SITUATION DESCRIPTION:
When printing a commission invoice. The total field for Total Net Amount is missing.
SOLUTION DESCRIPTION:
Added the field Total Net Amount to the report.

Solution: 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: 158414
SITUATION IDENTIFIED IN:
"Calculate Commissions/Rebates" (tdcms0240m000)
SITUATION DESCRIPTION:
When calculating commissions for orders that were delivered from multiple lots within warehousing, the commissions are
not being calculated.
SOLUTION DESCRIPTION:
When delivering a single sales order from multiple lots in warehousing, new sales order lines are added in the system to
handle the individual deliveries. When this happened, the commission relations linked to the original sales order line were
not getting linked to the new lines. Because of this, the commissions were not being calculated completely.

Solution: 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: 158452
SITUATION IDENTIFIED IN:
"Inventory Commitment" (whinp2100s000)
SITUATION DESCRIPTION:
Inventory commitment acts as though the full amount has been committed from previous, partial commitments.
SOLUTION DESCRIPTION:
Changed Inventory Commitments not to consider backorder quantities when determining the amount that can be committed.

Solution: 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: 158497
SITUATION IDENTIFIED IN:
"Report Production Schedules Complete" (tirpt1201m000)
SITUATION DESCRIPTION:
For each completion of a SFC production order, there will be two inbound lines. When printing the inbound lines at the
time of completing a SFC production order, both inbound lines were printing confusing the user.
SOLUTION DESCRIPTION:
Only the last inbound line of the sequence is important for the report. Therefore, only the last record of each sequence is
printed on the inbound report.

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

Solution: 158532
SITUATION IDENTIFIED IN:
"Print Journal" (tfgld1441m000)
SITUATION DESCRIPTION:
When printing journal vouchers with session tfgld1441m000 using any of following of print options: "Print Period Totals" or
'Print Day Totals' with 'Print Protocol Codes' the sub totals and closing totals are incorrect.
Only two reports within session are affected: the tfgld144112000 (Daybook Finalized Trans with Prot Codes
(date/type/doc) and tfgld144132000 (Daybook Finalized Trans with Prot (type/doc/date).
SOLUTION DESCRIPTION:
The functionality used to calculate the totals has been properly implemented to generate the correct totals.

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: 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: 158620
SITUATION IDENTIFIED IN:
"Maintain Sales Order Line Details" (tdsls4101s200)
SITUATION DESCRIPTION:
When using commissions and having a default relation set up for a business partner, the session gets an error 100 when the user
tries to enter detail lines for a sales order.
SOLUTION DESCRIPTION:
When entering detail lines for a sales order line, the default commission/rebate relations where not being linked correctly.
This caused the fatal error to occur. The linking will now be done correctly and no errors will result.

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

Solution: 158641
SITUATION IDENTIFIED IN:
"Picking List" (whinh2525m100)
SITUATION DESCRIPTION:
When trying to confirm a picking list for an item transfer within the same warehouse, we get message: "Some of the selected
lines have not been confirmed." followed by: "Received quantity should not exceed shipped quantity for a transfer order"
SOLUTION DESCRIPTION:
System now allows the picking list to be processed for item transfers within the same warehouse.

Solution: 158645
SITUATION IDENTIFIED IN:
"Integration Mapping Scheme (Service)" (tfgld4103s000)
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When setting up Integration Mapping Scheme (Service) for Sales Invoicing (Service) / Revenues Analysis using the session
"Integration Mapping Scheme" (tfgld4103s000), the combination of Financial Business Partner Group A/R and Cost
Component is not allowed. When this combination is entered the system gives error message "Invalid combination of
selected fields for Key Definition". This new combination should be allowed.
SOLUTION
DESCRIPTION:
This combination is now added as one of the valid combinations for Key Definition. The system now accepts this
combination.
Further, when Integration Transactions are posted to Finance using the session "Post Integration Transactions to Finance
Transactions" (tfgld4201m000), system obtains the ledger account set up for the combination and posts the integration
transaction to finance.
Help text is updated showing the latest
search priorities for Service.

Solution: 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: 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: 158722
SITUATION IDENTIFIED IN:
"Receipts via DDC" (whinh3520b000)
SITUATION DESCRIPTION:
When you have an item that is fifo and you recieve first item through DDC then receive the second item. It will keep the
inventory date of the first item that was received
SOLUTION DESCRIPTION:
Any previous date is now cleared durring receiving.

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

Solution: 158773
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2402m000)
SITUATION DESCRIPTION:
When printing commission invoices for a sales order line with multiple details, only the first detail line is included on the
invoice.
SOLUTION DESCRIPTION:
The session has been modified to print all detail lines on the invoice. The totals will also be updated correctly.

Solution: 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: 158814
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2402m000)
SITUATION DESCRIPTION:
The following errors are displayed when running the session "Print Commission/Rebate Invoices" (tdcms2402m000):
- unable to determine invoice number for relation 005
- no data within selection
SOLUTION DESCRIPTION:
Problem is due to having the "link with Finance" flag set to no withing the commission parameters. The "Print
Commission/Rebate Invoices" (tdcms2402m000) session has been modifed to correctly determine the next invoice number. This
will stop the error message from being displayed and allow the process to continue. If the "link with Finance" flag is set to
yes everything functions as it did before.

Solution: 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: 158899
SITUATION IDENTIFIED IN:
"Print Libro Giornale" (tfgldl402m00l)
SITUATION DESCRIPTION:
Amounts for compressed ledger accounts did not get printed when the amount was negative.
SOLUTION DESCRIPTION:
This problem happened because the report suppressed all amounts that were less than zero for the ledger accounts which had
compression on. This has been changed so that any non-zero amount will print i.e. positive or negative.

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

Solution: 158971
SITUATION IDENTIFIED IN:
"Journal Vouchers" (tfgld1103s000)
SITUATION DESCRIPTION:
When searching for a dimension in session tfgld1103s000 (Journal Vouchers) by entering a "," in the dimension field -
the zoom session tfgld0510m000 (Dimension Master) only shows information for dimension type 1.
SOLUTION DESCRIPTION:
When searching for a dimension via "," in a dimension field the correct dimension information will be displayed.

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

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

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

Solution: 159215
SITUATION IDENTIFIED IN:
"Generate Project Structure for Sales Order" (tdsls4244m000)
SITUATION DESCRIPTION:
On entering a generic item on a sales order line and then generating the project structure for this item, and then deleting
this sales line and re-entering another generic item and generating project structure for this item; the error message 'Project
X exists without being used in Sales Order X.' is received which blocks the entry of this new item.
This functionality as described above would effectively be the same as entering a second line on the sales order for another
generic item and then generating project structure for the second item, this second method is allowed.
SOLUTION
DESCRIPTION:
The process of entering a new generic item on a sales order, generating structure, removing the item and re-entering the item
again on the same sales order and again generating project structure is now allowed.

Solution: 159224
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When posting integration transactions, using the session "Post Integration Transactions to Finance Integrations"
(tfgld4201m000), some transactions erred with messages "Dimension XXX must be filled for ledger account YYYYYY" or
"Ledger Account not defined".
SOLUTION DESCRIPTION:
Integration transactions are now
posted
successfully
.
After installing this Solution, install the solution 159697. Then, post integration transactions using the session "Post
Integration Transactions to Finance Transactions" (tfgld4201m000).
Next, the Solution 159254 must be
installed for all versions prior to B52_a. See the
Solution 159254 for more details.

Solution: 159227
SITUATION IDENTIFIED IN:
"Print Goods Received Note" (whinh3412m000)
SITUATION DESCRIPTION:
Request for a more convenient way to display the appropriate variant information when receiving goods.
SOLUTION DESCRIPTION:
Option added to the Print Goods Received Note Session to allow for the printing of a new report that displays the variant
product information appropriate for an Inbound document

Solution: 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: 159288
SITUATION IDENTIFIED IN:
"Material to Issue for Production Orders" (ticst0101s000)
SITUATION DESCRIPTION:
Under the following conditions:
1. The Inventory Handling Parameter, 'Correct SFC Production Order till' is set to 'Generate Outbound Advice' or 'Release
Outbound Advice'
2. In the Material to Issue for Production Orders (ticst0101s000) session the 'To Issue' field is updated to a negative value.
A Planned Inventory Receipt line for the material is created when the Planned Inventory Issue line should be updated
instead.
SOLUTION DESCRIPTION:
Under the above conditions, if a negative 'To Issue' quantity is processed, the Planned Inventory Issue line will be updated
accordingly.

Solution: 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: 159355
SITUATION IDENTIFIED IN:
"Change Default Values for Finalization" (tfgld1113s000)
SITUATION DESCRIPTION:
When finalizing a batch using a run number it is not possible to include the text in the journal output. A facility similar
to the one when re-printing journals (tfgld1410m000) should be made available.
SOLUTION DESCRIPTION:
After selecting a batch for finalization in session Select Batches for Finalization (tfgld1111s000) the user has the option to
over-ride the default values by zooming to session Change Default Values for Finalization (tfgld1113s000). In this session, a
new field has been added to the form to accept the user option of whether the text is to be printed in the journal report or not.
The default value of this field is "No". The user has the option of changing it to "Yes" and saving defaults if they always want
to print the associated text at finalization time.

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

Solution: 159394
SITUATION IDENTIFIED IN:
"Print Packing Slips" (whinh4475m000)
SITUATION DESCRIPTION:
Unable to print all lines on Packing Slip
SOLUTION DESCRIPTION:
Due a technical problem sometimes not all lines where printed on a packing slip which has been adapted.

Solution: 159412
SITUATION IDENTIFIED IN:
"Integration Transactions by Project/Order" (tfgld4510m000)
SITUATION DESCRIPTION:
Service item and service item group cannot be mapped to the debit side of a transaction when a subcontracting item is used
on the service order.
SOLUTION DESCRIPTION:
When the user has a subcontracting cost on a service order, a mapping scheme can now be created where service item and
service item group are on the debit side of the transaction and regular item and item group is on the credit side.

Solution: 159428
SITUATION IDENTIFIED IN:
"Global Selection of Batches for Finalization" (tfgld1210m000)
SITUATION DESCRIPTION:
Focus is missing after the start-up of the session. A mouse click on an input field is required to enable processing in this
session.
SOLUTION DESCRIPTION:
The cursor defaults to the "Year" field when the session is started.

Solution: 159446
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
"Sales Order Line Details" (tdsls4501m200)
SITUATION DESCRIPTION:
It is not possible to link manually a relation "Relations by Order Line" (tdcms041m000) to a sales order detail line
(tdsls4501m200) via specific from the menu bar.
SOLUTION DESCRIPTION:
In the session "Sales Order Lines" (tdsls4501m000), the zoom option for the session |Relations by Order Line"
(tdcms0141m000) will be disabled if the sales order line is a split delivery line. In this situation, the zoom option for
"Relations by Order Line" (tdcms0141m000) is added to the session "Sales Order Line Details" (tdsls4501m200).

Solution: 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: 159578
SITUATION IDENTIFIED IN:
"DDC Monitor" (tuddcmonitor)
SITUATION DESCRIPTION:
The ddc monitor was not shutting down when the function server went away.
SOLUTION DESCRIPTION:
Changed how monitor was processing events along with how function servers sent events to the monitor.

Solution: 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: 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: 159655
SITUATION IDENTIFIED IN:
"Select Batches For Finalization" (tfgld1111s000)
SITUATION DESCRIPTION:
The session starts very slowly. This is caused by an inefficient query on the Batch Status (tfgld100) and the Transaction
Type Batch Status (tfgld101) tables when initializing the form.
SOLUTION DESCRIPTION:
The inefficient query has been rewritten.

Solution: 159695
SITUATION IDENTIFIED IN:
"Archive Project" (tipcs2260m000)
SITUATION DESCRIPTION:
When archiving projects, the sales and purchasing orders related to the project are automatically removed. This is
incorrect. The removal of the sales and purchasing project related orders should be handled within "Process Delivered
Sales Orders" and "Process Delivered Purchase Orders".
SOLUTION
DESCRIPTION:
Now sales and purchasing orders are not automatically removed when archiving projects.
The reason for not removing sales and purchase orders via session "Archive Project" is the fact that those orders might be
needed for analysis of GRINYA (Goods Received, Invoice Not Yet Approved) or for reconciliation of logistical and
financial data.

Solution: 159715
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When a mapping scheme is defined in session Integration Mapping Scheme (CMS) (tfgld4104s000) and one of the key
definitions is for field "Relation", the posting program is not able to use this mapping scheme. This happens when the field
"Relation" contains a value 9 characters in length.
SOLUTION
DESCRIPTION:
This problem happened because one of the internal variables in the program could only receive values up to 8 characters in
length. Thus the value of "Relation" got truncated and when reading the mapping scheme the truncated value was being
checked for, leading the posting session to believe that no mapping was defined. The program variable has been corrected to
receive 9 character values.

Solution: 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: 159743
SITUATION IDENTIFIED IN:
"tfgld2102s000" (Maintain Intergroup Transactions )
SITUATION DESCRIPTION:
When creating intergroup transactions if the user does not have permission in the target company the following errors
occurred:
#1- The created transactions use the currency rates from the source company instead of target company. (B40_c Only)
#2- The dimension type description displayed on the form was for the source company instead of target company.
#3- The group company of the target company was not read correctly.
#4- The session would give a no permission error when zooming to display a ledger account but would allow zooming ( to
the wrong company) on select dimensions types.
SOLUTION DESCRIPTION:
Changes have been made to get the correct currency rates, dimension type descriptions, and target group company when the
user does not have permissions in the target company. Also the zoom functionality for selecting dimensions has been
modified to work the same as on ledger account in that the zoom will be done in the target company and an error 'no
permission' will be given if a user attempts to zoom when having no permission in the target company.

Solution: 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: 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: 159994
SITUATION IDENTIFIED IN:
"Banks by Pay-by Business Partner" (tccom4115s000)
"Banks by Pay-to Business Partner" (tccom4125s000)
SITUATION DESCRIPTION:
The K11 check on the bank account number for a French bank did not allow leaving this field blank, even if the IBAN was
defined for the bank account.
SOLUTION DESCRIPTION:
The K11 check on the bank account number for a French bank does now allow leaving the bank account number blank.

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: 160048
SITUATION IDENTIFIED IN:
"Print Tax Report by Tax Position/Country Group" (tfgldl420m00l)
SITUATION DESCRIPTION:
When the session is run in language 1 (Dutch) the fields "Include Expensed Tax in Net Amount" and "Print Selection
Details" were not showing up on the form.
SOLUTION DESCRIPTION:
The form has been recompiled and the fields should now be visible when the session is run.

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: 160080
SITUATION IDENTIFIED IN:
"Journal Vouchers (Multiple Lines)" (tfgld1115m000)
SITUATION DESCRIPTION:
The defaults on the form fields were over-ridden with user defaults stored from the last time the user used this session.
This happened because of the wrong start command of the session.
SOLUTION DESCRIPTION:
The start command of the session has been changed.

Solution: 160090
SITUATION IDENTIFIED IN:
"Print Tax Report" (tfgldl416m00l)
SITUATION DESCRIPTION:
"Tax Declaration" report does not report the amounts correctly; the amounts are divided per 1000 and then reported.
The session, sometimes, issues the error message "Error in reading sort file record: xx fields scanned, yy expected".
SOLUTION DESCRIPTION:
The amounts are now reported correctly, without dividing per 1000.
The error message is no longer issued now.

Solution: 160122
SITUATION IDENTIFIED IN:
"Maintain Customers" (tccom1101m000)
SITUATION DESCRIPTION:
The Canadian province code for Newfoundland has changed from 'NF' to 'NL' for Newfoundland and Labrador. The new code
has become effective on October 21, 2002, and the old code will still be accepted for a period of six months. Baan did not
accept the new code before.
SOLUTION DESCRIPTION:
Baan is now accepting the new Canadian province code 'NL' for Newfoundland and Labrador. The old code 'NF' can still be
used until April 20, 2003.

Solution: 160149
SITUATION IDENTIFIED IN:
"Intergroup Transactions" (tfgld2102s000)
SITUATION DESCRIPTION:
1. While maintaining the intergroup transactions, the transaction reference of the document in the source company is not
copied to the transaction reference of the document being created in the target company. It is, instead, left blank.
2. After creating the document in the target company, if the user tries to modify the document (without re-starting the
session), the data just created disappears. The only way the user can modify the information is to exit and re-start the
session.
SOLUTION DESCRIPTION:
1. The transaction reference of the document in the source company is now copied into the transaction reference of the
document in the target company.
2. User is now able to modify the data without re-starting the session.

Solution: 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: 160210
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2402m000)
SITUATION DESCRIPTION:
When the Commission Parameter, Exchange Rate Type has been entered in session "Commissions/Rebates Parameters"
(tdcms0100s000), it is not used to convert the Business Partner's currency to the company's reference currency.
SOLUTION DESCRIPTION:
When the Commission Parameter, Exchange Rate Type has been entered in session "Commissions/Rebates Parameters"
(tdcms0100s000), it will be used to convert the Business Partner's currency to the company's reference currency.

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

Solution: 160302
SITUATION IDENTIFIED IN:
"Commissions Calculated by Order/Schedule" (tdcms0550m000)
SITUATION DESCRIPTION:
When deleting a record in "Commissions Calculated by Order/Schedule" (tdcms0550m000) after saying "yes" to the question "Set
the relation status to free or not?" and deleting the record, the status stays in "processed" rather than being set to "free".
This only happens when the "Relation" field (tdcms050.reln) is the full 9 characters in length. If it is less than 9 characters
it works fine.
SOLUTION
DESCRIPTION:
The relation field(s) size has
increased between BaanIV and iBaanERP
versions. The CMS and Finance
areas of iBaanERP have been updated to
correctly use the new domain.