Date : 97-11-20 [14:37] RELEASE NOTES PER P

Date : 97-11-20 [14:37] RELEASE NOTES PER P.D CALL NUMBER Page : 1

Ts 100 (Operational) Company : 100

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

10222958

Call Description :

In case an operation is completed before the planned quantity has been

completed, the allocations for the materials are not deleted.

Solution Description :

In case the parameter : "Update Allocated and Issued Quantities when

Quantity Planned Changes" was on "Alloc. and Reverse Entry ", the

allocated quantity for the materials was increased at the moment the

planned quantity decreased.

The planned quantity would decrease in case less was completed than

planned in an operation and the operation was closed.

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

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

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

10229309

Call Description :

When running MRP we get message "index 201 out of dims (1) 200 can't

continue in timrp1210m000 in DLL: opspmgdll2001". The validation of

the routing was not correct, because all operations were not valid and

pspmgdll2001 was called.

Solution Description :

The problem was caused by a requirement being generated for a process

item, for a date where the routing was not valid. This caused an

infinite loop which generated the out of dims error.

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

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

| pspmg0101m000 | Program Source | pmg0101 | | B40 b3

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

10229419

Call Description :

Sessie pspmg0111m000, enter material issue, defaults when building up

screen set to zero. When you want to enter issue [C], the issue field

defaults with the estimated quantity and a subsequent delivery of

zero.

When you enter through the issue field, (to keep it the same as the

estimate) the field subsequent delivery is set to be the same as the

issue, this is wrong.

Subsequent delivery quantity did not get recalculated when user

acepted the suggested issue quantity.

Solution Description :

Problem with material issuue in session pspmg0111m000 has been fixed.

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

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

| pspmg0111m000 | Program Object | pmg0111 | | B40 b3

Date : 97-11-20 [14:37] RELEASE NOTES PER P.D CALL NUMBER Page : 2

Ts 100 (Operational) Company : 100

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

| pspmg0111m000 | Program Source | pmg0111 | | B40 b3

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

10229510

Call Description :

For process item A a co-product B is defined in

"Maintain Co- and By-Products" (psfrm0112m000).

For process item B ,, ,, ,, A ,, ,,

If there is a sales order for 10 pcs A and 10 pcs B MRP should

generate only an advice for item A or B.

MRP however generates advise for A and B which would

result in too much stock.

Solution Description :

MRP production batches are now included in stock balance in print

sessions and co/by product receipts are considered in

"Generate Planned (MPS)/MRP Orders/Batches" (timrp1210m000).

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

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

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

10229601

Call Description :

Incorrect low level code calculations and planning of related items

if item range is selected by the user. The result is that all selected

items are not processed by the program.

Solution Description :

Low level codes and planning of item ranges will be performed

correctly.

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

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

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

10229793

Call Description :

Sommige inkoopdelen worden in de MRP niet meegenomen.

Als we van deze artikelen de geplande voorrraadmutaties opvragen

zien we wel mutaties staan.

Als we na de MRP-run (regenatief) het gepland voorraadverloop

van deze artikelen opvragen zijn er geen of onvoldoende mutaties

te zien.

Het betreft hier de artikelnr.'s 14.2235-14 en 17.2155-04

in bedrijf 300.

Toegangskode : applic 123applic

---

some purchase parts are not included in MRP.

if you look at planned inventory movements they do show.

when running regenerative MRP the planned inventory of these items

show none or not enough records.

Date : 97-11-20 [14:37] RELEASE NOTES PER P.D CALL NUMBER Page : 3

Ts 100 (Operational) Company : 100

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

Customer is in moulding business, and has set up an article (the left

part of the mould) and as co-product, he has defined the right part of

the mould. BUT ALSO VICE VERSA.

In this case I reproduced it at the customer test environment, and got

a message from the system that there is a loop in the structure. The

structure is :

left part : 720.6898.L0b

l-> 17.2155-04

l-> 41.2792-35 + co product right part

720.6898.R0b

right part : 720.6898.R0b

l-> 17.2155-04

l-> 41.2792-35 + co product left part

720.6898.L0b

We also tried to set it up as a by-product with positive costs.

Our question is: Is there any information at your end , why this is

not possible, because there are no restrictions mentioned in the

help-texts.

Please investigate.

Solution Description :

looping problem in case of co-products has been fixed.

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

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

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

10230232

Call Description :

The Problem of duplicate orderlines after regenarative mrp for all

items in timrp1510m000 ( TABLE timrp010, "Planned inventory movements

by item") still exist after installing ID 10229601.

Solution Description :

When using session (timrp1210m000)"Generate Planned MRP orders"

running a regenarative mrp for all items, in some cases there will be

duplicate mrp orders generated.

Program changed so this error does not appear any more.

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

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

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

10230903

Call Description :

Double Order Lines occur in the Planned Inventory Movements for MRP

Date : 97-11-20 [14:37] RELEASE NOTES PER P.D CALL NUMBER Page : 4

Ts 100 (Operational) Company : 100

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

Firm Planned Orders if the Planning Method is changed from backward to

forward, and if the fixed start date is changed (and not the same as

the planned start date), and if the status is changed from planned

into firm planned. This occurs also after Nett Change MRP.

This problem only occurs with a Level I driver and an Oracle Database,

if no index optimizer was used for the MRP tables.

Solution Description :

Session "Generate Planned MRP Orders" (timrp1210m000) modified in

order to prevent double orderlines in table timrp010 (Planned

inventory movements by Item) for firm-planned MRP orders.

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

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

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

10231177

Call Description :

Actual scheduling area and schedule period are not updated when

changing the corresponding Item Data.(tppdm0110m000: "Maintain

Standard Items")

Solution Description :

Actual scheduling area and schedule period are now updated when the

corresponding Item Data are changed.

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

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

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

10231238

Call Description :

For process items, the safety time as defined in the Item table is not

taken into account when Planned MPS/MRP Production Batches are

generated (in session timrp1210m000).

Solution Description :

Session "Generate Planned (MPS)/MRP Production Orders/Batches

(timrp1210m000) has been modified to take into account the safety time

defined for process items.

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

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

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

10239998

Call Description :

If the formula size is changed, a question "Change all co-/by-products

and....." is asked followed by a BSHELL message about the domain

"psfrm.reca" being wrong in ask_enum.

Solution Description :

The domain descriptions were added.

Now, the answer to the question 'Change all co-/by-products and

Date : 97-11-20 [14:37] RELEASE NOTES PER P.D CALL NUMBER Page : 5

Ts 100 (Operational) Company : 100

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

quantity-dependent materials proportionally ?' will show the four

possible values:

Both

Co-/By-Products

Materials

None.

These are actions to be selected by the user.

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

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

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

10241587

Call Description :

In session pspmg0202m000 it is possible with "Y" option to book items

into stock that do not have a costprice/costprice structure.

Solution Description :

It is no longer allowed to maintain a production batch for an item

that has no cost price structure.

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

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

| pspmg0101m000 | Program Source | pmg0101 | | B40 b3

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

10242454

Call Description :

In case the Issue Status of a Sales Order was "Issue Components", the

following two problems occur :

- A process Item can have a Cost item with an empty warehouse as a

material. This causes an error 606 (reference not found).

- In case ILC is implemented, all the components have to have the

same warehouse. This check is wrong because it should check if

the SAME component (in a different position) has a different

warehouse.

Solution Description :

The check if all components have the same warehouse has been removed.

It is not allowed to issue components in case one of the components

has an empty warehouse.

In case ILC is implemented, an item exists more than once as a

component and has different warehouses. In that case , issue

components is not allowed.

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

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

| psfrm0111m000 | Program Source | frm0111 | | B40 b3

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