Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 1

Ts 100 (Operational) Company : 100

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

10226692

Call Description :

It is not possible to re-print service invoices.

When trying to re-print service order invoices I get this error

message "Couldn't write one or more records to finance tssmas6201".

The invoices print normally but can not be re-printed.

Solution Description :

It was not possible to reprint the service orders invoice. This is

modified in the standard program software. So, it's now possible

to reprint the printed service order invoice.

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

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

| tssma3473m000 | Program Source | sma3473 | | 3.1 b6

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

10228426

Call Description :

A selection on the 'Warn-text' when creating a new text within session

tssma1102m000 Maintain Installations is not possible. The installation

could not be found because it is separated in a wrong way.

Solution Description :

When adding a text, it's possible to select a existence text.

Searching on Installation code was not possible, because the fields

were seperated in a wrong way. This is corrected so searching on the

installation code is available to the user.

PMG Service.

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

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

| tssma1102m000 | Program Source | sma1102 | | 3.1 b6

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

10228494

Call Description :

tssma3271m000 is making inventory go negative.

The steps to make this happen are:

1. Enter several lines in tssma3110m000 for an item that does not

have enough inventory to cover all the demand. If the inventory for

the item is 0 then the inventory will not go negative.

2. Issue the inventory using tssma3271m000 and it will issue

ainvnetory for all of the records, even this that do not have enough

inventory.

This only happens when you issue inventory for more than 1 order line

for an item that has enough inventory to partrially cover the demand.

Even with the parameter Negative Inventory Allowed set to 'No' the

inventory is going negative.

Solution Description :

When the parameter Negative Inventory Allowed was set to 'NO' it was

still possible to get a negative inventory with session 'Issue

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 2

Ts 100 (Operational) Company : 100

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

Inventory' (tssma3271m000).

This problem is fixed so when the ILC- and the Negative Inv. Allowed

parameters are set to 'No' the inventory is not go to negative

anymore when issueing the inventory with 'Issue Inventory'.

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

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

| tssma3271m000 | Program Source | sma3271 | | 3.1 b6

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

10228851

Call Description :

The default Finance company for the service order is never taken from

the customer, but is always the default financial company.

Solution Description :

The standard software make no allowance of the Financial company

by customer. This is now modified. When adding a service order/

contract in first case the company of the customer is read (is exists)

So, it's for now possible to invoice/post the orders by customer

company. (set range from Financial Company in tssma3473m000 to related

values.)

PMG Service.

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

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

| tssma2120m000 | Program Source | sma2120 | | 3.1 b6

| tssma3101m000 | Program Source | sma3101 | | 3.1 b6

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

10229283

Call Description :

Whenever the Periodic Maintenance Planning is created again over

two years there are more servicings planned then neccesary.

Solution Description :

When running the session tssma1224m000 ('Generate Periodic

Maintenance Planning') over two years, there are servicings planned.

Whenever the same planning is generated again there are added more

servicings in the planning each time the same planning is generated.

This problem is fixed, so when there's created a planning over two

years and the planning is generated again, none servicings are added

as it should be.

PMG Service.

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

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

| tssma1224m000 | Program Source | sma1224 | | 3.1 b6

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

10229451

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 3

Ts 100 (Operational) Company : 100

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

Call Description :

With the session tssma1402m000 it's only possible to print the global

warn textes. Not the checklist or history text that could be

maintianed via the session tssma1102m000.

Solution Description :

There is now the abbility to choose for the history text to print.

Also is modified the relevant reports to do this.

PMG Service.

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

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

| tssma1402m000 | Program Source | sma1402 | | 3.1 b6

| tssma1402m000 | Report | sma140201000 | | 3.1 b6

| tssma1402m000 | Report | sma140201001 | | 3.1 b6

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

10229801

Call Description :

When a Purchase/Result transaction is created for the price difference

between a purchase invoice and the matched purchase order the

Reporting period and the TAX period assigned to this transaction are

not correct.

Solution Description :

Functionality has been added for determining the correct reporting

year/period when approvals are made.

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

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

| tssma1273m000 | Program Object | sma1273 | | 3.1 b6

| tssma2472m000 | Program Object | sma2472 | | 3.1 b6

| tssma3101m000 | Program Object | sma3101 | | 3.1 b6

| tssma3105m000 | Program Object | sma3105 | | 3.1 b6

| tssma3110m000 | Program Object | sma3110 | | 3.1 b6

| tssma3159m000 | Program Object | sma3159 | | 3.1 b6

| tssma3170m000 | Program Object | sma3170 | | 3.1 b6

| tssma3201m000 | Program Object | sma3201 | | 3.1 b6

| tssma3271m000 | Program Object | sma3271 | | 3.1 b6

| tssma4116m000 | Program Object | sma4116 | | 3.1 b6

| tssma6201m000 | Program Object | sma6201 | | 3.1 b6

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

10229937

Call Description :

Debtors invoice due data is incorrect

The agreed debtors invoice due date was to be 60 days from invoice.

This ageing is not appearing correctly as will be seen from the

attached copy, and in some cases is as little as 6 days only is given

from the actual invoice date. This appears to be related to service

order invoices only because the contract invoice seems to be correct.

The help text for the "Priority for due date calc." (tcmcs013.prio)

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 4

Ts 100 (Operational) Company : 100

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

states for the "Month End" option that the invoice date is shifted to

the end of the month, after which the payment period is added. For

Service orders, however, the program is not calculating the due date

in thsi manner.

After investigation we believe that the program script is not making

any reference at all to this calculation of the due date when the

"Date End" option is selected.

Solution Description :

When the Calculate Due Date Method was : End Of Month, the program

didn't calculate the right due date. The due date was only added with

the Payment Period. The Due Date is calculated right now.

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

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

| tssma3473m000 | Program Source | sma3473 | | 3.1 b6

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

10230202

Call Description :

When the user is Maintaining Deliveries the system sometimes fails to

update the database because of a duplicate key.

Solution Description :

When the user is Maintaining Deliveries the system will not fail to

update the database because of a duplicate key.

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

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

| tssma1273m000 | Program Object | sma1273 | | 3.1 b6

| tssma3101m000 | Program Object | sma3101 | | 3.1 b6

| tssma3105m000 | Program Object | sma3105 | | 3.1 b6

| tssma3110m000 | Program Object | sma3110 | | 3.1 b6

| tssma3159m000 | Program Object | sma3159 | | 3.1 b6

| tssma3170m000 | Program Object | sma3170 | | 3.1 b6

| tssma3201m000 | Program Object | sma3201 | | 3.1 b6

| tssma3271m000 | Program Object | sma3271 | | 3.1 b6

| tssma4116m000 | Program Object | sma4116 | | 3.1 b6

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

10230298

Call Description :

When the receiptline of a RPL order in the destination warehouse needs

to be deleted (e.g in case of a wrong quantity) two records with

negative quantities are generated. This is correct. But the

transactiondate of these records is " " and the transactiontime is

23:59.

The consequence is the generation of a lot of integration transactions

of type 'stock revaluation' each time the standard price is modified.

These transactions are posted on old periods which are closed.

Solution Description :

Inventory transactions are now generated properly when receipt lines

are deleted and/or changed.

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 5

Ts 100 (Operational) Company : 100

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

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

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

| tssma1273m000 | Program Object | sma1273 | | 3.1 b6

| tssma3101m000 | Program Object | sma3101 | | 3.1 b6

| tssma3105m000 | Program Object | sma3105 | | 3.1 b6

| tssma3110m000 | Program Object | sma3110 | | 3.1 b6

| tssma3159m000 | Program Object | sma3159 | | 3.1 b6

| tssma3170m000 | Program Object | sma3170 | | 3.1 b6

| tssma3201m000 | Program Object | sma3201 | | 3.1 b6

| tssma3271m000 | Program Object | sma3271 | | 3.1 b6

| tssma4116m000 | Program Object | sma4116 | | 3.1 b6

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

10230448

Call Description :

Printing with the session sma1471m000 takes a lot off time.

Solution Description :

The session sma1471m000 ('Print Open Servicings by service Area')

is reprogrammed in a more efficientre way, so the report takes less

time.

PMG Service.

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

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

| tssma1471m000 | Program Source | sma1471 | | 3.1 b6

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

10230571

Call Description :

One service order prints on multiple invoices if

work site & postal address countries are different

The defect can be duplicated as follows:

Enter a service order with the postal address to NL and the work site

address to USA country. Enter four line items on the service order

and when you print the service invoice, all lines are printed on a

separate invoice and different invoice numbers are assigned. I also

tested the same scenario in sales invoices and I only get one invoice

number.

Solution Description :

Invoices now print correctly for work site and postal address.

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

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

| tssma3473m000 | Program Source | sma3473 | | 3.1 b6

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

10230815

Call Description :

The session tssma3110s000 displayed the wrong lines and the commands

Next and Previous won't work.

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 6

Ts 100 (Operational) Company : 100

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

With session tssma3142m000 Report Service Order Completed go to the

subsession tssma3110s000 Maintain Actual Costs and Revenues with 'Y'.

The now displayed orderline isn't related to the just set to completed

service order.

Solution Description :

When reporting the service order completed with session tssma3142m000

and continueing with 'Y' to the Actual Costs (tssma3110s000) it is

possible that there are shown rows that doesn't belong to the just

completed order. This is caused by the fact that before a first row is

added the service order is not known in the table from Actual Costs.

The program takes the nearest row to show.

This problem is modified, when adding a row for the Actual Costs for

the first time, no row is shown in the display.

The Next and Previous key's are working properly. Walking through the

rows by the service order is allowed, but walking through the rows of

a another service order is not allowed. It's explicable with the help

of the line of the procedure; when reporting the service order

completed it's logical to maintain the related Cost and Revenues Lines

of that order.

PMG Service.

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

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

| tssma3110s000 | Program Source | sma3110 | | 3.1 b6

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

10230869

Call Description :

Something goes wrong with the invoice data. When a invoice run is done

with several countries, the countries aren't in the right way used.

This problem gives the result that Finance did not accept the invoice

data to post.

Solution Description :

When the customer had a invoice-run with serviceorders wereby the

countries differs from eachother, the invoice table was filled wrong.

This causes trouble when posting the invoice to Finance. Finance

could not handle the invoice data in some cases, so the invoice

data does not appear within Finance.

This problem is fixed so the right Tax-country is written to the

invoice table.

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

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

| tssma3473m000 | Program Source | sma3473 | | 3.1 b6

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

10230921

Call Description :

When there's a run of contract invoices only the invoice amount of the

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 7

Ts 100 (Operational) Company : 100

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

first contract is calculated, all the other have 0,00 on there

invoice.

Solution Description :

When having a run of contract invoices, only on the first contract

invoice the amount is calculated. This problem only occurs when the

parameter Collect Contract Invoices is set to NO. This parameter

can be found on the first form of session tssma3100m000 (Maintain

Service Order Control Parameters).

The problem is fixed so a invoice run can be done now, even when the

parameter is set to 'NO'.

PMG Service.

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

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

| tssma2472m000 | Program Source | sma2472 | | 3.1 b6

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

10230940

Call Description :

There are differences between generic periodic maintenance planning

session and report 1 print planned periodic maintenance planning.

The locations are correct on tables but the report script is incorrect

Solution Description :

This error has been fixed.

The reports will now show the locations correctly on each report.

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

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

| tssma1424m000 | Program Source | sma1424 | | 3.1 b6

| tssma1424m000 | Report | sma142401001 | | 3.1 b6

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

10231166

Call Description :

On the report the 'call-out charge' is not printed. Session info and

fax are send by internal post.

Solution Description :

When by the location the call-out charge is defined, it's now possible

to print it on the report with the session tssma1410m000 ('print

locations').

PMG Service.

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

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

| tssma1410m000 | Program Source | sma1410 | | 3.1 b6

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

10240103

Call Description :

The reported problem is Customization Related. The problem is that in

the standard software some fields are reset that could be used in

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 8

Ts 100 (Operational) Company : 100

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

customization.

PMG

Solution Description :

Customization has given troubles, so the source is maintained to

provide this problems. This troubles only apears in the subsession of

the maintain installation session (tssma1102s000), when adding form

fields.

PMG Service.

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

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

| tssma1102m000 | Program Source | sma1102 | | 3.1 b6

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

10241516

Call Description :

There are a lot of refences to the tables tccom010.cuno and

tccom020.suno in the DD.

Some of them have delete-mode 'restricted (with counter)' this must be

changed by delete-mode 'lookup'. Check also if the update-mode is 'No

check'.

The previous delete-mode causes error 601 by some customers.

Solution Description :

The table defenitions are added to the following versions:

ts3.1_bx

tsB40_bx

tsB40_c

The following tables were modified : sma102

sma110

sma220

sma301

The called session in the modified components is a dummy.

The delete mode is changed to 'look up'.

PMG Service.

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

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

| tssma1102m000 | Table Def. | sma102 | | 3.1 b6

| tssma1102m000 | Table Def. | sma110 | | 3.1 b6

| tssma1102m000 | Table Def. | sma220 | | 3.1 b6

| tssma1102m000 | Table Def. | sma301 | | 3.1 b6

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

10241730

Call Description :

When having a run of contract invoices for one customer the amount on

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 9

Ts 100 (Operational) Company : 100

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

the first invoice is the total of all invoices.

Solution Description :

When the parameter Collect Invoices was set to 'NO' and the user

prints contract invoices with session tssma2472m000, in the case of

several contracts for ONE customer the amount on the first invoice was

calculated wrong.

This problem is fixed, printing the invoices gives the right amount.

PMG Service.

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

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

| tssma2472m000 | Program Source | sma2472 | | 3.1 b6

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

10242389

Call Description :

When a installation of a contract is added or deleted then the price

sharing of the other installations are changed.

Solution Description :

The following action that has taken is only effective if is choosen

for SUGGESTED prices :

Step 1.

A contract 'breman' is created. The following installations are

coupled : 88 with service pack 010 fl 120.- 9.68%

cv with service pack 010 fl 120.- 9.68%

77-nl with service pack 1000 fl 1000.- 80.65%

The contract price is fl 1240.- (ctrl-z suggested prices).

Step 2.

The installation '88' is decoupled from the contract. After that the

new contract price is filled in : fl 1120.- (120 + 1000).

Saving and going back to the 'installations by contract' gives

the following :

cv with service pack 010 fl 120.- 10.71%

77-nl with service pack 1000 fl 1000.- 89.29%

The prices are NOT changed, only the percents.

Step 3.

If the customer is not working with the suggested prices then after

decoupling a installation the prices must be recalculated. If the old

contract price is still active then a new deviation is done to the

installations in relation with the package prices. In this case the

customer get different prices on his installations because the

contract prices must be 100% of the prices of the installations.

Step 4.

If the customer is not working with the suggested prices and not with

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 10

Ts 100 (Operational) Company : 100

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

the previous contract prices, also in this case the deviation is done

in relation with the package price. In this case the package prices

are responsible for generated percentages. Also in this case the

prices by installation are changed because the redeviation of the

percentages.

After a discusion with AD Service it became clear that in fact there's

no program error in the source. But to make it a litle bit easier to

the customer there's added extra 'functionality' to provide the

possibilty to keep the old contract prices.

On this moment the following solution is available :

- A contract with a manual contract price f1000.- with the

installations 1 : f125.- 2 : f275.- and 3 : f600.-

- Deleting installation 2 (f275.-)

- Setting the contract price to 125+600= f725.-

- Back to the installations to see that in this case only the percents

are changed, the prices are the same.

If the contract price is changed then also the instalments (if

available and free) are changed.

The whole story not only counts for deleting installations but also

for adding installations.

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

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

| tssma2120m000 | Program Source | sma2120 | | 3.1 b6

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

10242396

Call Description :

Problems with Service Order integrations!

Orders are not being posted correctly.

Working with Brama in GR PMG on this issue from Klockner.

Karen 4-17-97

Solution Description :

The problem was caused due to a bad fix caused by ID 1001773. This has

been fixed.

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

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

| tssma3473m000 | Program Source | sma3473 | | 3.1 b6

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

10242439

Call Description :

When processing a cycle count order, the message "domain error 99999

value 34xxxx" appears.

Solution Description :

When processing a cycle count order, the message "domain error 99999

value 34xxxx" no longer appears.

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 11

Ts 100 (Operational) Company : 100

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

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

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

| tssma1273m000 | Program Object | sma1273 | | 3.1 b6

| tssma3101m000 | Program Object | sma3101 | | 3.1 b6

| tssma3110m000 | Program Object | sma3110 | | 3.1 b6

| tssma3170m000 | Program Object | sma3170 | | 3.1 b6

| tssma3201m000 | Program Object | sma3201 | | 3.1 b6

| tssma3271m000 | Program Object | sma3271 | | 3.1 b6

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

10242514

Call Description :

When there're several installations with a certain location and from

one installation the location is changed then in session tssma1125m000

all installations appear with the new location.

Solution Description :

When a planning exists for a certain installation and the location of

that installation is changed the planning table is updated in the

wrong way. All the installations that have the same (old) location are

changed. This apears specially via the session tssma1125m000

Maintenance Planning by Location. It seems that the procedure not is

disturbed by this (maintenance procedure), but it gaves a wrong

overview.

This problem is solved. Changing the location of a installation thats

used in a maintenance planning doesn't result anymore in changing all

the same old locations in the maintenance table.

PMG Service.

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

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

| tssma1102m000 | Program Source | sma1102 | | 3.1 b6

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

10242606

Call Description :

When the user in the session tssma3110m000 ('maintain actual costs')

wants to choose for the Tax Type 'Shifted', the warning appears that

the choosen Tax Type is not a sales type.

Solution Description :

When using Tax Type 'Shifted' in the session tssma3110m000 the warning

appears that 'it's not a sales type'.

The reported problem was missing functionality within the Standard

Software.

The problem is solved.

It is now possible to use the Tax Type: Shifted.

PMG Service.

Date : 97-12-12 [12:01] RELEASE NOTES PER P.D CALL NUMBER Page : 12

Ts 100 (Operational) Company : 100

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

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

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

| tssma3110m000 | Program Source | sma3110 | | 3.1 b6

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

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.

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

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

| tssma1102m000 | Program Object | sma1102 | | 3.1 b6

| tssma1105m000 | Program Object | sma1105 | | 3.1 b6

| tssma1202m000 | Program Object | sma1202 | | 3.1 b6

| tssma3110m000 | Program Object | sma3110 | | 3.1 b6

| tssma3170m000 | Program Object | sma3170 | | 3.1 b6

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