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

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

Solution: 129187
SITUATION IDENTIFIED IN:
"Projects" (tppdm6100s000)
SITUATION DESCRIPTION:
When inserting a project and the parameter "Use Project Archive" in session tppdm0100m000 ("General Parameters") is
switched on, the wrong logistic company was filled in table tppdm790 "Archived Projects". This caused reference-error
206 when deleting the project. This only occurred in a multi-finance setup.
SOLUTION DESCRIPTION:
The correct company is now being used to fill table "Archived Projects".

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

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

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

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

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

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

Solution: 130044
SITUATION IDENTIFIED IN:
"Maintain Projects" (tppdm6100m000)
SITUATION DESCRIPTION:
The following functional enhancement was requested:
When linking a sub-project to a main-project a question should come up asking if the customer data should be copied
from the main project.
SOLUTION DESCRIPTION:
The requested functionality is built in. When a sub-project is linked to a main-project the question comes up. When
answered with "Yes" the customer-data from the main-project is copied.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 130765
SITUATION IDENTIFIED IN:
Calls (tsclm1100s000)
SITUATION DESCRIPTION:
When transferring a Call to a Service Order where the Sold Business Partner has no default Invoice To Business Partner
linked, it is not possible to transfer the Call. It is not possible to create a Service Order without a default Invoice To
Business Partner.
SOLUTION DESCRIPTION:
It is now possible to create an External Service Order without an Invoice-to Business Partner or a Pay-by Business
Partner. This is possible until the Service Order or its Activity are being set to Costed. During the process of setting
one of them to Costed a check is made whether the Invoice-to Business Partner and Pay-by Business Partner are present on
the Service Order header. Also when creating an actual costline for an External Service Order, a Invoice-to Business
Partner and a Pay-by business partner have to be present. These changes make it possible to "transfer" or "emergency
transfer" a Call without having defined a default Invoice-to Business Partner.
When actual costlines are created, changes are limited. The following fields cannot be changed in that case, also when
they are derived from fields which are allowed to change.
Fields:
Location Address (tssoc200.lcad)
Service Area (tssoc200.csar)
Currency (tssoc200.ccur)
Exchange rate type (tssoc200.rtyp)
Rate determiner (tssoc200.fcrt)
Country (tssoc200.ccty)
For example when the Invoice-to Business Partner changes, default values are retrieved for for example the currency. This
will be blocked when one or more actual costline exist.
Note:
With this solution it is not yet possible to Invoice a Service Call via Service Orders without default Invoice-to Business
Partner. For this a seperate solution will be profided.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 130827
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
The standard cost price of a manufacturing item is not getting updated, if the calculated cost price is zero. If the BOM
(Bills of material) and routing get expired for a manufacturing item, even though the system calculates the cost price, the
standard cost price sessions will not be updated.
SOLUTION DESCRIPTION:
When the calculated cost price of a manufacturing item is zero, the standard cost price sessions will be updated.
SPECIAL INSTRUCTIONS:
None.

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

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

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

Solution: 130894
SITUATION IDENTIFIED IN:
"Project Status" (tppdm6107m000)
SITUATION DESCRIPTION:
When changing the project status from 'Free' to 'Active', the system will give an error 'Transaction is on, can't continue'.
This only happens when already installments or advances are created for this project.
SOLUTION DESCRIPTION:
The error occurred due to locking mechanisms. The check on whether the new status is allowed for the project or not, was
moved to the point of actually saving the record. This changed the point at which records are locked and removed the
error.
SPECIAL INSTRUCTIONS:
None.

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

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

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

Solution: 130981
SITUATION IDENTIFIED IN:
"Generate Cycle Counting Orders" (whinh5200m000)
SITUATION DESCRIPTION:
In a location controlled warehouse for a location controlled item , a cycle counting order can be generated and processed
with an empty location .When there is inventory in the warehouse , the location is filled correctly during generation of
cycle counting order lines .The problem occurs only in the case of non- existing stock points and we force cycle counting
during generating of cycle counting orders .
SOLUTION DESCRIPTION:
The System will not generate cycle counting order lines for a location controlled item in a location controlled warehouse
with empty location for non existing stock points .
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

Solution: 131061
SITUATION IDENTIFIED IN:
Calculate Cost and Valuation Prices (ticpr2210m000)
SITUATION DESCRIPTION:
The standard cost price of a manufacturing item is not getting updated, if the calculated cost price is zero. If the BOM
(Bills of material) and routing get expired for a manufacturing item, even though the system calculates the cost price, the
standard cost price sessions will not be updated.
SOLUTION DESCRIPTION:
When the calculated cost price of a manufacturing item is zero, the standard cost price sessions will be updated.
SPECIAL INSTRUCTIONS:
Please download this solution along with solution 130827.

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

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

Solution: 131161
SITUATION IDENTIFIED IN:
"Inventory Inspection Data" (whinh3122s000)
SITUATION DESCRIPTION:
Two users can approve the same inspection line, using the " Approve remaining " and "Save" buttons. After approvals, the
status of the outbound order line is still " To be Inspected " and the
quantities are doubled in the shipment lines.
SOLUTION DESCRIPTION:
Now a check is made whether the inspections are done and if its done already a message " Approval line is not saved,
Inspection is already done " is displayed, the same record cannot be saved two times. This check is made for both "
Approve remaining " and " Reject Remaining " buttons.
SPECIAL INSTRUCTIONS:
None.

Solution: 131190
SITUATION IDENTIFIED IN:
"Project" (tppdm6100s000)
SITUATION DESCRIPTION:
Problem 1: Whenever the value of enterprise unit is changed, a check is done on the user type & if the user is a "Normal
User", then a check is done to see if the Fin. company of first enterprise unit & second are different. If they are
different an error message is returned. But, next time when the same enterprise unit value is passed, no error message is
returned. The check on Authorizations is not consistent.
Problem 2: When a new project record is opened, keeping the old one open, the enterprise unit field of the new project has
the value of old project instead of it's own value.
SOLUTION DESCRIPTION:
Solution 1: Whenever the value of enterprise unit is changed, a check is done on the user type & if the user is a "Normal
User", then a check is done to see if the Fin. company of first enterprise unit & second are different. If they are
different an error message is returned. But, even when an error has occurred, the financial company gets the value of new
financial company. So, next time when the same enterprise unit value is passed, the check on financial company fails & no
error message is returned.
Now, the financial company will be assigned a new value only if there are no errors. So, the check will always be
consistent.
Solution 2: Now, always the enterprise unit of current project will be found & displayed.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

Solution: 131377
SITUATION IDENTIFIED IN:
"Project" (tppdm6100s000)
SITUATION DESCRIPTION:
When a user (located in timezone A) was trying to create a project and the periods in tcccp060 (Period Table) was created
with timezone B, an error message would popup that "periods in Project are not equal to periods in Finance". This message
was technically correct, but functionally incorrect.
SOLUTION DESCRIPTION:
When user 1 (located in timezone A) and user 2 (located in timezone B) are trying to create the same project there
should be no difference when the Project periods are matched with the Finance periods, even when the periods were
created in timezone C.
However, it is strongly recommended to create the Periods in the Periods table (tcccp0560m000) with the same timezone
as the timezone of the Financial company to which they are going to be linked.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

Solution: 131597
SITUATION IDENTIFIED IN:
"Standard labor" (tppdm0511m000)
SITUATION DESCRIPTION:
When the labor is used in both element & activity budgets, the error message duplicates. This has to be corrected.
SOLUTION DESCRIPTION:
Now the error message is displayed only once even when labor is used in both element and activity budgets.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 131632
SITUATION IDENTIFIED IN:
"Cycle Counting/Adjustment order lines" (whinh5101s000)
SITUATION DESCRIPTION:
Problem in Inventory adjustment if Package definition not used on a stock point and inventory is not available directly in
base unit (but only in higher levels) and in the session "Cycle Counting/Adjustment order lines" (whinh5101s000), if user
enters the storage unit as the base unit.
The Actual inventory defaulted should be zero, but a non-zero value is defaulted. This confuses the user and moreover,
when the user modifies it to zero (so that the 'Variance' is a negative value), and stock point inventory goes wrong.
SOLUTION DESCRIPTION:
The quantity defaulted for the field 'Actual Inventory' will be equal to the quantity that is available in the warehouse for
the 'Storage unit' entered by the user.
For example, if there is one box of an item which contains ten pieces of the same item, then if the user enters the 'Storage
unit' as box, the 'Actual inventory' defaulted will be 1. But, if the user enters the 'Storage unit' as pieces, the 'Actual
inventory' defaulted will be 0.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 131766
SITUATION IDENTIFIED IN:
"Item Production Data" (tiipd0101s000)
SITUATION DESCRIPTION:
System is not changing the Critical in Master Planning flag to NO in the session "Item Production Data"
(tiipd0101s000), when the order system is changes from planned to manual in the session "Item Ordering Data"
(tcibd2100s000).
SOLUTION DESCRIPTION:
System will change the Critical in Master Planning flag to NO in the session "Item Production Data" (tiipd0101s000),
when the order system is changes from planned to manual in the session "Item Ordering Data" (tcibd2100s000).
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

Solution: 131885
SITUATION IDENTIFIED IN:
"Calculate cost and valuation prices" (ticpr2210m000)
SITUATION DESCRIPTION:
The updation of standard cost price is not correct, if the cost price of manufacturing item is zero.
SOLUTION DESCRIPTION:
The standard cost price will be updated correctly, if the calculated cost price of manufacturing item is zero.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

Solution: 132131
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices " (ticpr2210m000)
SITUATION DESCRIPTION:
Performance problem in the session "Calculate Cost and Valuation Prices" (ticpr2210m000) when calculating the cost price
of a single item, if the item group range is wide open.
SOLUTION DESCRIPTION:
Performance improvement while calculating cost prices of the Item, when the Item Group is wide open (without filling up
the range).
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

Solution: 132232
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
Error index out of dims 250[251], during cost price calculation and inventory revaluation for an item. The item has
multiple cost price components defined and the item is present in large number of warehouses.
SOLUTION DESCRIPTION:
Inventory revaluation is done without any errors, If multiple cost price components are defined for an item present in
large number of Warehouses.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

Solution: 132396
SITUATION IDENTIFIED IN:
"Service Order Actual Material Costs" (tssoc2120s000)
SITUATION DESCRIPTION:
1. When a Service Order is linked to a PCS project and the actual cost lines for this order are split into an "Invoicing"
part and an "Internal(other)" part, then when costing the order, only the "Invoicing" part will be booked as "Approved for
Invoicing" financial integration, but the financial integration posting "Internal Service Costs" is not booked.
2. When a Service Order is linked to a PCS project, the WIP-reversal postings for Service Order Material Costs, pass the
wrong entity type(from). It is "Warehouse" but it should be "Department". The entity should be the calculation office of
the project.
3. When changing the Cost Component of an Actual Material Line, Baan exits completely without saving the change. This
does not always happen, it depends on the number of Cost Components linked to the Item. See session "Cost Component
Details" (tcibd0110m000). If this number exceeds 3 the problem occurs (only in B50c).
4. When changing the Cost Component of an Actual Material Line and the at number 3 mentioned problem does not occur,
then the new issue integration bookings are all linked to the project. So the credit Issue integration booking from
Warehousing which was originaly not linked to the project is now counterbooked with a negative issue amount but linked to
the project and then newly booked with a positive amount but then also with a link to the project.
SOLUTION DESCRIPTION:
1. When a Service Order is linked to a PCS project the Financial Integration postings "Internal Service Costs", "Warranty
Costs" and "Field Change Order Costs" are taken into account when costing the cost line.
2. When a Service Order is linked to a PCS project, the WIP-reversal postings for Service Order Material Costs, will have
the entitype from as 'Department' and use the calculation office of the project.
3. When changing the Cost Component of an Actual Material Line, the Cost Component is changed where necessary. The
System keeps running without errors.
4. When changing the Cost Component of an Actual Material Line the following steps are performed.
A. The existing credit issue booking is counterbooked with the same amount but then negative. With the old Cost
Component. Without a link to the project.
The existing debit issue booking is counterbooked with the same amount but then negative. With the old Cost
Component. With a link to the project.
B. A new credit issue booking is created with the same amount but now positive. With the new changed Cost Component.
Without a link to the project.
A new debit issue booking is created with the same amount but now positive. With the new changed Cost Component.
With a link to the project.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

Solution: 132599
SITUATION IDENTIFIED IN:
"Print Multi-level Cost Price Calculation" (ticpr2420m000)
SITUATION DESCRIPTION:
When the session "Print Multi-level Cost Price Calculation" (ticpr2420m000) is run to print the report for standard items
with EOQ (Economic order quantity) sub item flag set to NO, then system takes the BOM quantity as order quantity for sub
item cost calculations, instead of end item's order quantity.
SOLUTION DESCRIPTION:
If EOQ (Economic order quantity) Sub item flag set to NO for standard items, then the order quantity for sub item will be
BOM quantity times the end item's order quantity, for operation cost calculation in the report.
SPECIAL INSTRUCTIONS:
None.

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

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

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

Solution: 132650
SITUATION IDENTIFIED IN:
"Standard Subcontracting" (tppdm0113s000)
SITUATION DESCRIPTION:
If a new Subcontracting / Equipment record is opened, without closing the old record, all changes made in the second
record are updated in the first record.
SOLUTION DESCRIPTION:
The above problem is solved and now all values will be properly updated in their respective records.
SPECIAL INSTRUCTIONS:
None.

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

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

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

Solution: 132783
SITUATION IDENTIFIED IN:
"Sold-To Business Partners" (tccom4110s000)
SITUATION DESCRIPTION:
When Contract Module is not implemented in SLS Parameters, While entering a New Sold-To B.P, an irrelevant message "
Orders and/or contracts present; changing status not allowed." pops up
SOLUTION DESCRIPTION:
Now the system doesn't give irrelevant error message while entering a new Sold- o Business partner.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

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

Solution: 133120
SITUATION IDENTIFIED IN:
"Project" (tppdm6100s000)
SITUATION DESCRIPTION:
An Enterprise Unit (EU) is always linked to financial Company & all the project related financial transactions are always
posted in the financial company linked to this EU. So, when a EU is changed to one, which has a different financial
Company, it will carry lot of consequences with it. Normal users are not allowed to change a EU with different financial
co. Only Super User can. But if the super user adds a EU with different financial co by mistake, he/she will have no
information about it.
SOLUTION DESCRIPTION:
Now, if a Super User tries to change an Enterprise Unit, linked to a different financial co., a warning message will be
shown.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

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

Solution: 133550
SITUATION IDENTIFIED IN:
"Calculate cost prices by Project" (tipcs3250m000)
SITUATION DESCRIPTION:
When cost price of a project is calculated, system generates an error report with message "Cost price of the item is zero",
even if the calculated cost price of customized item is non-zero.
SOLUTION DESCRIPTION:
If the calculated cost price of the customized item is zero, then only system generates an error report with message "Cost
price of the item is zero".
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

Solution: 133905
SITUATION IDENTIFIED IN:
"Service Order Actual Labor Costs" (tssoc2531m000)
SITUATION DESCRIPTION:
1) Cost Amounts on a Service Order Actual Labor line are doubled in case the end user executes the following steps:
- Enter an Hours Accounting Line in session Service Hours Accounting (tssoc2135s000 or tssoc2136s000).
- Without leaving the session change the Hourly Labor Type (tssoc235.chlt) or the Cost Component (tssoc235.ccmp).
- Without leaving the session change the Hourly Labor Type (tssoc235.chlt) or the Cost Component (tssoc235.ccmp)
again.
- The total cost amount in the Service Order Actual Labor Line is now doubled.
2) Cost Amounts on a Service Order Actual Labor line are wrong in case the end user executes the following steps:
- Enter Hours Accounting Lines in session Service Hours Accounting (tssoc2135s000 or tssoc2136s000) for 2 or more
Service Orders.
- Change the status of one of the Service Order Actual Labor Lines to status 'Costed'.
- In session Service Hours Accounting, change the Service Order Number of the Hours Accounting lines related to the
Service Order Actual Labor Lines with status 'Costed', to the another Service Order Number (status should not be costed).
- On the Service Order with the Labor Line on Costed, a new, corrective, Labor line is created with a wrong Cost
Amount.
3) Only B50_c: When coping an Hours Accounting Line for a Service Order (tssoc2136s000), and saving the data, error
message pops up: Service Center not allowed.
SOLUTION DESCRIPTION:
1) and 2) Changes in Service Order Hours Accounting lines are now properly reflected on the Service Order Actual Labor
Lines.
3) When coping an Hours Accounting Line for a Service Order (tssoc2136s000), and saving the data, an error message
does not pops up anymore. Data is properly saved.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

Solution: 134217
SITUATION IDENTIFIED IN:
"Projects" (tcmcs0152s000)
SITUATION DESCRIPTION:
The implementation of a tools variable was changed/corrected. Prior to the change, changing the project search key from
session 'Projects' (tcmcs0152s000) did not update the search key in Manufacturing (module tipcs) or in Project (module
tppdm).
SOLUTION DESCRIPTION:
After the change of the tools variable, changing the project search key from session 'Projects' (tcmcs0152s000) does
update the search key in Manufacturing (module tipcs) or in Project (module tppdm).
SPECIAL INSTRUCTIONS:
None.

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

Solution: 134301
SITUATION IDENTIFIED IN:
"Generate Cycle-Counting Orders" (whinh5200m000)
SITUATION DESCRIPTION:
The fatal error 606 can occur when several count numbers within 1 order exist. This is due to the fact that the needed order
header doesn't exist.
SOLUTION DESCRIPTION:
The check on the existence of the order header is changed so that if the header doesn't exist it will be created.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

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

Solution: 134733
SITUATION IDENTIFIED IN:
"Cycle Counting / Adjustment Orders" (whinh5500m000)
SITUATION DESCRIPTION:
Quantities in inventory unit are calculated wrongly when entering adjustment order lines.
This happens if first a line is entered for an existing stock-point, and then a new line for a not existing stock-point is
entered via "CTRL-N" without leaving the session.
SOLUTION DESCRIPTION:
This situation is corrected and values are calculated properly.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 160755
SITUATION IDENTIFIED IN:
"Conversion Factors DAL" (tcibd003)
SITUATION DESCRIPTION:
When inserting conversion factors via the EXCHANGE product, the error message "Unit is not a base unit" is received,
even for valid base unit values.
This was also demonstrated by inserting a valid base unit via general table maintenance tool and receiving the error.
SOLUTION DESCRIPTION:
Now conversion factors can be inserted via EXCHANGE product without receiving the "Unit is not a base unit" error
message for valid base unit values.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 162384
SITUATION IDENTIFIED IN:
"Item Costing Data" (tcibd0507m000)
SITUATION DESCRIPTION:
It is currently possible to delete the item costing data when there is existing inventory or orders against the item.
SOLUTION DESCRIPTION:
Now item costing data cannot be deleted when there is existing inventory or orders against the item.
SPECIAL INSTRUCTIONS:
None.

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