Date : 98-02-27 [09:07] RELEASE NOTES PER P

Date : 98-02-27 [09:07] RELEASE NOTES PER P.D CALL NUMBER Page : 1

Ts 100 (Operational) Company : 100

------------------------------------------------------------------------------------------------------------------------------------

10222740

Call Description :

When using session "Maintain Engineering BOMs" (tiedm1110m000) the

message "E-item revision has already been released; changing not

possible" (tiedm31221) is given while E-Item is not released.

Solution Description :

When using session "Maintain Engineering BOMs" (tiedm1110m000) the

message "E-Item revision has already been released; changing not

possible" (tiedm31221) was given while E-Item was not released.

The program is changed so the check have been done with the

right E-Item data.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| tiedm1110m000 | Program Source | edm1110 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10230573

Call Description :

When the session "Print Product Variants (tipcf5401m000)" is run

error 2417, i.e. Oracle error 1417, "A table may be outer joined to

atmost one other table" is displayed.

Solution Description :

In oracle, a table may be outer joined to atmost one other table. This

outer join to two other tables has been removed.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| tipcf5401m000 | Program Source | pcf5401 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10240541

Call Description :

If I print a detailed report with containers for multiple items,

the calculation of the cost price is erroneous.

Solution Description :

The report will now show the correct sum total of the surcharges.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| ticpr2410m000 | Report | cpr241001000 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10241205

Call Description :

By testing with TEST_RETRY > 0, a lot of problems are occurring in

different sessions in different packages.

The errors can be:

1. Record not locked

2. Transaction is on

3. Wrong output of data (table and print)

Date : 98-02-27 [09:07] RELEASE NOTES PER P.D CALL NUMBER Page : 2

Ts 100 (Operational) Company : 100

------------------------------------------------------------------------------------------------------------------------------------

Solution Description :

Db.retry.point modified in combination with commit.transaction().

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| ticpr2250m000 | Program Source | cpr2250 | | B40 b4

| ticpr2210 | Program Source | cpr2210 | 002 | B40 b4

| ticpr2220 | Program Source | cpr2220 | 002 | B40 b4

| ticpr2250 | Program Source | cpr2250 | 002 | B40 b4

| tipcs2121 | Program Source | pcs2121 | 002 | B40 b4

| tisfc0101 | Program Source | sfc0101 | 002 | B40 b4

| tisfc0202 | Program Source | sfc0202 | 002 | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10241394

Call Description :

In session "Report Complete Order and Adjust Stock" (tisfc0202m000) a

problem occurs with order-qty and reject qty error complete namely:

Prod-Order-Qty = 0 - it has been rejected.

Sys gave question "post to Inventory?"

If ansered YES, Zoom to ILC, where an attempt to load zero to Stores

is made.

Error is returned and record must be Skipped - but Status is Updated

to COMPLETE.

IF ABOVE QUESTION IS ANSWERED NO, NOTHING happens.

Why are we treating qty-0 this way?

If qty-0, then the system should be updating the Status to COMPLETE.

Solution Description :

To report a production order completed was impossible with quantity

to deliver equal to zero. When ILC was implemented, the session

zoomed to "Maintain Receipts" were input of zero quantity is rejected.

The program script of session "Report Production Orders Completed"

(tisfc0202m000) has been modified in order to allow completion of

production orders with no quantity to deliver.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| tisfc0202m000 | Program Source | sfc0202 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10241600

Call Description :

Once a phantom generic item is configure and the sales order lines are

populated with the components, if a RE-configuration is done, the

components which have become invalid due to some constraints do not

get removed from the sales order lines.

Solution Description :

The following changes have been done:

All situations are related in case of a new sales order postion is

linked to the same already created project (and structure). In other

words, a situation where position 10 exists and position 20 is being

inserted.

Date : 98-02-27 [09:07] RELEASE NOTES PER P.D CALL NUMBER Page : 3

Ts 100 (Operational) Company : 100

------------------------------------------------------------------------------------------------------------------------------------

1. Generic NON-phantom, PCF parameter identifying item code = Yes

If the item code does not change after generation of the

structure, and if this item code already exists for the project,

then a new structure will not be generated but the existing

structure and variant information would be imported. By doing

this, the new variant information is lost in the sales order

position.

The project parts do not get updated if that particular item code

already existed as a part.

2. Generic NON-phantom, PCF parameter identifying item code = No

The project part gets updated in case the item is repeated on

another sales order position since a new item code gets generated.

New item codes get generated if those already exist for the

project becasue of the PCF parameter.

The BOM structure gets created and updated as per the constraints.

3. Generic Phantom, PCF parameter identifying item code = No

Project part is same as the main phantom item. If the phantom

item gets updated (in its name), then the project part also gets

updated with the new code.

For std. item in project, the variant on the sales order is

blanked. If the re-generate session is run for this position,

then the variant comes blank in the sub-session 'Generate Product

Variant Structure for Project' - it is required to note the

variant number from the other positions.

If the variant is re-configured to eliminate one item, the sales

order is updated with the new items (the invalid component is

removed). Project parts get updated and the existing items get

incremented.

Since history is maintained for all items on the sales order

lines, the variant is blanked in the 'customized item data' for

invalid items. If these items get re-validated for another

configuration, the variant number is linked again.

4. Generic Phantom, PCF parameter identifying item code = Yes

This will be similar to point 1 and 3 and its combination.

If the items which populate the sales order are already existing

in the project then no new items are generated and the variant

switches to the variant linked to the old item structure.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| tipcf5260m000 | Program Source | pcf5260 | | B40 b4

| tipcf5260m000 | Function Source | pcf6000 | | B40 b4

| tipcf5280m000 | Program Source | pcf5280 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10242123

Call Description :

When copying the E-bom to P-bom, the field Ebom copied will not be set

to 'yes' and the copydate misses.

This happens only when a new revision is created for a E-bom from

which a bom-line has been deleted.

Date : 98-02-27 [09:07] RELEASE NOTES PER P.D CALL NUMBER Page : 4

Ts 100 (Operational) Company : 100

------------------------------------------------------------------------------------------------------------------------------------

Solution Description :

When pressing the CTRL+X within the session 'Maintain EBOM copy data'

(tiedm1220m000) the field EBOM copied will be set to 'yes' and the

date when the item was copied will be filled in.

DO NOT USE THIS SOLUTION; USE THE SOLUTION OF DEFECT 12135 IN SCOPUS.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

------------------------------------------------------------------------------------------------------------------------------------

10242128

Call Description :

Erroneous EBOM is generated in session "Generate EBOM copy Data"

tiedm3235m000 when in the session "Maintain ECOs" tiedm3110m000 the

field "All Lines Must Apply to item" is set to NO.

For example :

Old EBOM: A, B and C.

Lines of the ECO:delete A

delete B

delete C

add D

New EBOM (processed by session "Process EBOM changes" (tiedm3205m000))

will be : A, B, C and D. However the result should have been only D.

Solution Description :

When you now delete ALL E-Items from the old EBOM the new EBOM will

have only the added E-Item.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| tiedm3205m000 | Program Source | edm3205 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10242417

Call Description :

Problems with material issueing.

Following the next procedure:

During the mutation of the sales order a project is generated using a

dmmy article MACHINE (manufactured item on order).

Next a standard material listis interactively copied to this dummy

article using session "Copy standard Product Structure

to Project" (tipcs2230m000). After a PRP run the purchase and

production orders are confirmed and finalized. The production order is

released. Then the goods are received using session

"Maintain Receipts" (tdpur4120m000).

From the marked receipt line subsession "Maintain Estimating

Parameters" (ticst0105m000) is started.

For the latter session a new object was obtained recently. However, it

is not possible to enter the material issue for the production.

A second order that does not use ticst0105m000 gives no problems. The

anonymous production orders work fine as well.

We did not use the possibility to issue the materials immediately at

Date : 98-02-27 [09:07] RELEASE NOTES PER P.D CALL NUMBER Page : 5

Ts 100 (Operational) Company : 100

------------------------------------------------------------------------------------------------------------------------------------

leaving the session ticst0105m000

Solution Description :

This session now only selects and displays the first six production

orders against which the purchase receipt may be allocated and issued.

The form has been modified to display the quantity allocated vs. the

quantity received. Note that the quantity allocated may be negative

on form initialisation. This will occur when the the total quantity

planned for issue is greater than the quantity received.

If ILC is implemented the user will be warned that materials must be

issued via the ILC module, although it is still possible to adjust

planned issue quantities.

DO NOT USE THIS SOLUTION; USE THE SOLUTION OF DEFECT 11941 IN SCOPUS.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| ticst0105s000 | Program Source | cst0105 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10242604

Call Description :

When the purchase parameter "Automatic Recalculation of Prices and

Discounts" has the value "automatic", no recalculation takes place of

the generated purchase order.

Solution Description :

When the purchase parameter "Automatic Recalculation of Prices and

Discounts" has the value "automatic", recalculation of prices and

discounts is now done for the generated purchase order.

This only happens in the case that the order has been generated from

an inventory order.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| timps5250m000 | Program Object | mps5250 | | B40 b4

| timps5270m000 | Program Object | mps5270 | | B40 b4

| timrp1260m000 | Program Object | mrp1260 | | B40 b4

| tipcs5260m000 | Program Object | pcs5260 | | B40 b4

| tisfc2250m000 | Program Object | sfc2250 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10242779

Call Description :

Wrong revision is displayed for revision-controlled items in session

'Maintain Item Data' and also some other sessions.

Solution Description :

Revision selection is changed so now the correct revision is displayed

for revision-controlled items in session 'Maintain Item Data' and

other sessions.

DO NOT USE THIS SOLUTION; USE THE SOLUTION OF DEFECT 12135 IN SCOPUS.

Date : 98-02-27 [09:07] RELEASE NOTES PER P.D CALL NUMBER Page : 6

Ts 100 (Operational) Company : 100

------------------------------------------------------------------------------------------------------------------------------------

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

------------------------------------------------------------------------------------------------------------------------------------

10242855

Call Description :

Under the Sub Header Transfer Result for Item / Description the wrong

description prints for items listed under Transfer Result.

Solution Description :

Prior to the fix, the description of the previously printed item was

printed for the item under the "Transfer Result" header.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| tipcs3462m000 | Program Source | pcs3462 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10242857

Call Description :

When using IRP:

Whe having an MPS structure, like: MPS1 - MPS2 (MPS2 is a component of

MPS1), then MRP generates orders to cover the demand for the items.

For MPS items, the demand should be based on the production plan. In

the error situation it is based on the production plan and on existing

orders. So in our example: 100 pcs MPS1 results in a demand of 200 pcs

of MPS2; MRP will generate an order for 400 pcs for MPS2 (200 because

of exploded demand; 200 because of the MPS order for MPS1).

For MPS items the production plan is leading. Therefore MRP should

base the generation of orders exclusively on the production plan.

Solution Description :

Error solved.

When using IRP:

When generating MPS Orders in session "Generate Planned MRP Orders"

(timrp1210m000), the MRP run is based on the MPS Plan.

In the planned inventory movements however, the actual situation is

displayed.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| timrp1210m000 | Function Source | mrp5000 | | B40 b4

| timrp1210m000 | Program Object | mrp1210 | | B40 b4

| timrp1210m000 | Program Object | mrp1211 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10242889

Call Description :

MPS planning does not consider safety time while planning backward.

Date : 98-02-27 [09:07] RELEASE NOTES PER P.D CALL NUMBER Page : 7

Ts 100 (Operational) Company : 100

------------------------------------------------------------------------------------------------------------------------------------

This works fine for forward planning.

Solution Description :

Safety time will be appropriately considered while generating MPS

orders. In the maintain session, the use of the <CTRL> R option will

not consider safety time. Only the order lead time will be considered

as per the message displayed on depressing the option keys.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| timps5120m000 | Program Source | mps5120 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10242935

Call Description :

MRP does not effectively plan BOM changes in the event of a phantom

item structure change. This occurs while running Net-Change MRP.

Regenerative MRP solves this inconsistency.

Solution Description :

The modifications in the BOM of a phantom will be effectively planned

by Net Chg.MRP. However, it is essential that Re-generative MRP be run

regularly to correct the low level codes (which could change in the

event of a deletion of an item from the BOM).

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| tibom1110m000 | Program Source | bom1110 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10242939

Call Description :

en tibom1501m0001, it is possible to zoom to tibom0520s000. But, this

session does not exist so you get the error message:

can't read session or object ( tibom0520s000)".

Solution Description :

Because of a mistake in the softwaredelivery, customers on B40b got

the forms of call 10225454 which was just meant for B40c. The

components of this call contains the B40b forms.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

Date : 98-02-27 [09:07] RELEASE NOTES PER P.D CALL NUMBER Page : 8

Ts 100 (Operational) Company : 100

------------------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------------------

10242984

Call Description :

Performance improvements needed in session "Calculate Cost Prices"

(ticpr2210m000).

Solution Description :

Performance improvements have been implemented.

DO NOT USE THIS SOLUTION; USE THE SOLUTION OF DEFECT 12080 IN SCOPUS.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| ticpr2210m000 | Program Source | cpr2210 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10243234

Call Description :

Copy an existing item (with BOM and routing) to a new item without

copying the BOM. Generate a cost price. After this insert a new BOM

line. Generate the cost price again with session "Calculate Cost

Prices" (ticpr2210m000). Result: the cost price is not updated

correctly due to the fact that the BOM is not taken into acount.

Solution Description :

The internal table with costprice components was not correct read. Due

to this the costprice was not correctly generated.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| ticpr2210m000 | Program Source | cpr2210 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------

10243240

Call Description :

When more then one surcharge base by item (or itemgroup) is entered

per surcharge by item (or itemgroup) a fatal error comes up. Also

surcharges by itemgroup are not considered in the costprice

calculation bu session "Calculate Cost Prices" (ticpr2210m000).

Solution Description :

If more then one surcharge base by item or item group is entered the

insert will be done correctly. Now also the surcharges by item group

are considered in the costprice calculation.

+--------------------------------------------------------------------------------------------------------------------------

|-------------------+----------------------+------------------------+-------------------------------------+----------------

| ticpr2210m000 | Program Source | cpr2210 | | B40 b4

------------------------------------------------------------------------------------------------------------------------------------