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

Solution: 118032
SITUATION IDENTIFIED IN:
"Print Item Production Data" (tiipd0401m000)
SITUATION DESCRIPTION:
Session takes a long time to print the item production data when the session runs with a range of Item Group or Item Type
SOLUTION DESCRIPTION:
Now the performance is improved with the modification of select queries.

Solution: 121385
SITUATION IDENTIFIED IN:
"Bill of Material" (tibom1110s000)
SITUATION DESCRIPTION:
It should be possible to copy a non-customized component to a customized component in session tibom1110s000 when a
non-customized "to order" item is found in the BOM of a custmized parent item.
SOLUTION DESCRIPTION:
A button to copy from standard to customized is added to session tibom1110s000.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 124131
SITUATION IDENTIFIED IN:
"Purchase Contracts" (tdpur3100s000)
SITUATION DESCRIPTION:
1. It is possible to have expiry date before contract date.
2. It is possible to have expiry date before current date.
SOLUTION DESCRIPTION:
Now it is not possible to have expiry date before contract date.
Now it is not possible to have expiry date before current date.

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

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

Solution: 124227
SITUATION IDENTIFIED IN:
"(Un)Block Lots" (whinh6120m000)
SITUATION DESCRIPTION:
While blocking or unblocking a lot, Inventory on hold for planning is wrongly updated
SOLUTION DESCRIPTION:
The inventory on hold for planning is updated correctly

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

Solution: 124352
SITUATION IDENTIFIED IN:
"Print Purchase Orders" (tdpur4401m000)
SITUATION DESCRIPTION:
The 'Alternative item code' is printed only for the first line of the Purchase Orders. It is not printed for the other lines.
SOLUTION DESCRIPTION:
Now the 'Alternative item code' would be printed for all the appropriate lines.

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

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

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

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

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

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

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

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

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

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

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

Solution: 124778
SITUATION IDENTIFIED IN:
"Print Purchase Order Reports" (tdpur4405m000)
SITUATION DESCRIPTION:
When all the options are used, the system doesnot print the output.
SOLUTION DESCRIPTION:
Now when all the options are used also, the system prints the output.

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

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

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

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

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

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

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

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

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

Solution: 124962
SITUATION IDENTIFIED IN:
"Copy Projects" (tppdm7840m000)
SITUATION DESCRIPTION:
When a project is copied to a new project and the original project has a text attached to it, then the text is not copied to the
new project.
SOLUTION DESCRIPTION:
The text on a project is now copied along with the other project data to the new project.

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

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

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

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

Solution: 125117
SITUATION IDENTIFIED IN:
"Material to Issue for Production Orders" (ticst0101s000)
SITUATION DESCRIPTION:
When the material is returned from shop floor, if the outbound order line is open/advised/released and even though the order
quantity in outbound orderline can be reduced, a new inbound order line is created.
SOLUTION DESCRIPTION:
When the material is returned from shop floor, if the outbound order line is open/advised/released, and if the order quantity
in outbound orderline can be reduced, new inbound orderline is not created. Instead, outbound orderline quantity is reduced.
SOLUTION 121466 BEFORE THIS SOLUTION.
If your Current VRC is B50L_c_bgl0, download solution 125264 after this solution.
VERSION(S):
B50_b, B50_c

Solution: 125120
SITUATION IDENTIFIED IN:
"Standard equipment" (tppdm0512m000)
SITUATION DESCRIPTION:
When a standard subcontracting or a standard equipment is deleted using sessions "Standard Subcontracting" (tppdm0513m000)
or "Standard Equipment" (tppdm0512m000), the cost objects are removed from the standard cost object tables in Baan Project.
However, if these cost objects are used in orderlines (e.g. in purchase ) then the corresponding records from the General Item
data are not deleted.
SOLUTION
DESCRIPTION:
When trying to delete a subcontracting or equipment cost
object, the program will only delete the cost objects (Cost object data and
general item data) if the cost object is not used elsewhere. If it is being used, no data is deleted.

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

Solution: 125160
SITUATION IDENTIFIED IN:
"(Un)Block Lots" (whinh6120m000)
SITUATION DESCRIPTION:
It is possible to block the entire lot when some stock point is present in the 'Staging' location. Due to this at the time of
unblocking the lot, the stock point in the staging location is corrupted and the shipment could not be confirmed.
SOLUTION DESCRIPTION:
The lot can not be blocked as long as there is some stock present in 'Inspection' or ' Receiving' or 'Staging' locations.

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 125482
SITUATION IDENTIFIED IN:
"Copy Projects" (tppdm7840m000)
SITUATION DESCRIPTION:
In session 'Copy Projects' (tppdm7840m000) the user can select several options to copy different parts of the data. But in
some cases if not all checkboxes are checked, the top element, the leading plan or the actual cost calculation code are not
copied. The description for these fields in the project data then shows 'xxxxxxxxxxxx'.
SOLUTION
DESCRIPTION:
The top element, the leading plan and the actual cost calculation code are now always copied to the new project, irrespective
of the selected checkboxes.

Solution: 125486
SITUATION IDENTIFIED IN:
"Forms" (ttadv3500m000)
SITUATION DESCRIPTION:
Some forms in Dutch and German languages are not linked to English language. Due to this what ever change done in
English language, they are not getting reflected in Dutch and German.
SOLUTION DESCRIPTION:
For these Forms, the link has been re-defined.

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

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

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

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

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

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

Solution: 125604
SITUATION IDENTIFIED IN:
"Process Hours Accounting" (tssoc2235m000)
SITUATION DESCRIPTION:
System is passing wrong integration entries while processing the hours accounting. For the labor rate $100 system is passing
the entry for $100.08 and for $200 it is pasing the entry for $199.87
SOLUTION DESCRIPTION:
BaanERP Service is now passing the correct cost amounts when creating financial transactions. The (small) differences occured
due to the fact that the total cost amount was calcutaled based on the cost rate and the actual time. As hours accounting lines
with the same significant properties are combined into one actual labor cost line the cost rate expresses the average cost rate.
Calculation using average rates can result in differences.
Now the total cost amount is calculated as the sum of all different cost amounts overwhich the amount is distributed.

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

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

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

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

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

Solution: 125774
SITUATION IDENTIFIED IN:
"Cycle Counting / Adjustment Order Lines" (whinh5501m000)
SITUATION DESCRIPTION:
The parameter 'Block During Warehouse Cycle Count' is checked in "Inventory Handling Parameters" (whinh0100s000).
The 'Stock Points' are blocked if the Cycle Counting order is generated from the session "Generate Cycle Counting
Orders" (whinh5200m000). But if a new stock point is added in "Cycle Counting / Adjustment Order Lines"
(whinh5501m000), it is not blocked.
SOLUTION DESCRIPTION:
The 'Stock Point' corresponding to the manually entered Cycle Counting Lines would also be blocked now.

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 126005
SITUATION IDENTIFIED IN:
"Global (Un)Block Lots" (whinh6220m000)
SITUATION DESCRIPTION:
Corrupt inventory after global blocking of lots without inventory.
SOLUTION DESCRIPTION:
Initializing new created records for 'lots by warehouse' table prevents from corrupt data.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 126335
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
It is possible to assign a service order to a service engineer who is no longer employed in the company.
SOLUTION DESCRIPTION:
It is not possible to assign a service employee who is no longer employed.When entering a service engineer to a service
order,the employee's first and last dates of employment are checked with the date of entry.When releasing an order,the
planned start time and planned finish time are used to check whether the employee is still employed.The planned start and
finish times are also used when scheduling the employee using Baan Service Scheduler.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 127033
SITUATION IDENTIFIED IN:
"Process transaction" (tpppc4802m000)
SITUATION DESCRIPTION:
Projects gets closed even when transaction in later period is present.
SOLUTION DESCRIPTION:
Porting of solution 115867 solves the problem.

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

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

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

Solution: 127204
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
1. The receipt procedure of the Inbound Order does not have Generate Inbound and Put away Inbound as activities, meaning
that the inbound would be done automatically when the receipt is confirmed.
2. There is a lot-controlled item.
3. Many unit of this item is entered in the Purchase Order Lines.
4. It is released to Warehousing and the order is linked to a Receipt.
5. While confirming the linked receipt, it takes lot of time.
SOLUTION DESCRIPTION:
The changes have been made in such a way that time taken for the complete process of confirming the receipt is reduced
considerably. Even in cases where the Generate Inbound is a separate activity, the changes will be applicable and the
performance of the advice generation.

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

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

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

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

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

Solution: 127278
SITUATION IDENTIFIED IN:
"Generate Cycle Counting Orders" (whinh5200m000)
SITUATION DESCRIPTION:
1. There are 3 stock points in a particular Warehouse.
2. A cycle Counting Order is created for these stock points and the counted data are processed.
3. For the third stock pint the quantity is made as 0 with an Adjustment Order.
4. Now a new Cycle Counting Order is generated with the Warehouse mentioned above with Maximum number of Lines per
order kept as two.
5. The system gives the following fatal error and it is not possible to proceed further.
++++++++++++++++++++++++
Fatal error 206 (record not locked)
+++++++++++++++++++++++++
SOLUTION DESCRIPTION:
The above-mentioned fatal error doesn't appear now, while creating the Cycle Counting Order Line for a non-existing stock
point.

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

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

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

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

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

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

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

Solution: 127487
SITUATION IDENTIFIED IN:
"Projects" (tipcs2101m000)
SITUATION DESCRIPTION:
When 'Search Key' and other fields of "Projects" (tipcs2101s000) session are modified, then the system saves only the 'Search
Key' whereas the other fields value are defaulted to their previous values.
SOLUTION DESCRIPTION:
The system saves all fields which have been modified when the 'Search Key' is modified.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 127952
SITUATION IDENTIFIED IN:
"Schedule for Automatic Transactions" (tfgld0130s000)
SITUATION DESCRIPTION:
When a Service Integration transaction of type "Operation Cost" is linked to a schedule for automatic transactions, the
amounts of the automatic transaction lines in home currency are zero.This happens only for Single Currency system.
SOLUTION DESCRIPTION:
The amounts are correctly shown in the automatic transaction lines in home currency for Single Currency system when the
service integration transaction is of type "Operation Costs".

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

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

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

Solution: 128041
SITUATION IDENTIFIED IN:
"Financial interim results" (tpppc2560m000)
SITUATION DESCRIPTION:
Even when a finacial results in later period is present for a project system allows to close the project in the current period.
SOLUTION DESCRIPTION:
While processing the transaction there is already a check on all cost types ...now a check on financial results is also been
built which solves the above problem.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 128901
SITUATION IDENTIFIED IN:
"Cycle-Counting/Adjustment Order Lines" (whinh5101s000)
SITUATION DESCRIPTION:
If an adjustment order is created (in session whinh5500 "Cycle-Counting/Adjustment Orders") with two different lines and
the second line:
1) is created in session whinh5501m000 "Cycle-Counting/Adjustment Order Lines" without closing whinh5101s000
"Cycle-Counting/Adjustment Order Lines" session
2) same item as first line is used
then all the fields are enabled for this second line in session whinh5101s000, allowing for instance:
a) to enter an inventory date when outbound priority of the item is by location
b) to enter a location when item is not location control...
SOLUTION DESCRIPTION:
Now fields in session whinh5101s000 are enabled/disabled depending on the characteristics of the item per every line.

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

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

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

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

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

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

Solution: 129158
SITUATION IDENTIFIED IN:
"Cycle-Counting/Adjustment Order Lines" (whinh5101s000)
SITUATION DESCRIPTION:
If an adjustment order is created (in session whinh5500 "Cycle-Counting/Adjustment Orders") with two different lines and
the second line:
1) is created in session whinh5501m000 "Cycle-Counting/Adjustment Order Lines" without closing whinh5101s000
"Cycle-Counting/Adjustment Order Lines" session
(by using CTRL N, for instance)
2) same item as first line is used
for an item lot controlled by unit, then field storage unit is not filled with the default value causing that it stays empty AND
disabled, not being possible to change it manually.
SOLUTION DESCRIPTION:
Now fields in session whinh5101s000 fills the field storage unit with its default value.

Solution: 129213
SITUATION IDENTIFIED IN:
"Lots by warehouse" (whltc1505m000).
SITUATION DESCRIPTION:
Performance problem due to huge number of empty records in the table whltc105 ( Lots by Warehouse )
SOLUTION DESCRIPTION:
A correction program whcor1405m000 is created to delete empty records and also a solution is created in the standard program
itself to delete empty records while updating the table .

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

Solution: 129240
SITUATION IDENTIFIED IN:
"Cycle-Counting/Adjustment Order Lines" (whinh5101s000)
SITUATION DESCRIPTION:
When creating an adjustment order for an item not location controlled and not lot controlled, quantity present at the stock
point is not found, giving the following message "Order Line can not be processed. On hand on stock point has been
changed." at the time of processing the line.
SOLUTION DESCRIPTION:
The quantity present at the stock point is filled properly, so no changes on stock point happen, therefore the order line can
be processed.

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

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

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

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

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

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

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

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

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

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

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

Solution: 129503
SITUATION IDENTIFIED IN:
"Application Function Server" (AFS Integration)
SITUATION DESCRIPTION:
When using Application Function Server for entering projects in Baan, the AFS can call the program logic of session
"Project Status" (tppdm6107m000).
However, that program uses a dll which in it's turn causes an Error 206 (Record is not locked) .
SOLUTION DESCRIPTION:
Record locking has been changed. AFS can now use program logic from session "Project Status" (tppdm6107m000).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 130155
SITUATION IDENTIFIED IN:
"Cycle Counting/Adjustment Order Lines" (whinh5501m000)
SITUATION DESCRIPTION:
Adjustment Order Lines (whinh5101s000) can be made for project items for which the project status is 'closed'.
SOLUTION DESCRIPTION:
When on an Adjustment Order Line a project item is entered for which the project status is 'closed', the following error
message is given: "Project not allowed because the project has the closed status."
The line cannot be saved. The same happens for project items for which the project status is 'free'.

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

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

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

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

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

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

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

Solution: 158174
SITUATION IDENTIFIED IN:
"Baan Open World" (Baan 5 BOIs)
SITUATION DESCRIPTION:
When data is sent to Baan through Open World, item fields are not aligned correctly according to the segmentation of the
fields.
SOLUTION DESCRIPTION:
Data sent to Baan via Open World is now aligned correctly by segment for item fields.

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

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

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

Solution: 158406
SITUATION IDENTIFIED IN:
"Address Jurisdiction Verification Utility" (tccom6210m000)
SITUATION DESCRIPTION:
The session "Address Jurisdiction Verification Utility" needed several improvements. One improvement needed was a change
of the program flow for the session because the non-interactive session was not always getting the correct geo code. Also the
correct information was not always printing to the report.
SOLUTION
DESCRIPTION:
The session "Address Jurisdiction Verification Utility" has been
improved in many ways. One example is the program flow
has been changed to eliminate waste and become more progressive.
Another example of improvement is that all
necessary records are printing to a report.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 159650
SITUATION IDENTIFIED IN:
"Addresses" (tccom4130s000)
SITUATION DESCRIPTION:
For North American Taxware users who modify the city, state, zip code, or country, they are not prompted to select a new
geo code.
SOLUTION DESCRIPTION:
Now when the city, state, zip code, or country, is changed in the session "Addresses", the user is forced to enter a new geo
code.

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

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

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

Solution: 160033
SITUATION IDENTIFIED IN:
"Item Ordering Data" (tcibd2100s000)
SITUATION DESCRIPTION:
In item ordering data, when entering a 'fixed order quantity' amount that is an even multiple of the 'order quantity multiple
of', there is an incorrect error message given, indicating that the 'fixed order quantity' is not an even multiple.
SOLUTION DESCRIPTION:
Now within item ordering data, it is allowed to enter all values into the field 'fixed order quantity' that are even multiples of
the 'order quantity multiple of', without an incorrect error message.