ts

VERSIONS:

B40_a1, B40_a2,

B40L_a1_gls0, B40L_a1_glo0, B40L_a1_sch0,

B40Lbglo0, B40Lbgls0, B40Lb1glo0, B40Lb1gls0, B40Lb2glo0,

B40Lb2gls0, B40Lb3glo0, B40Lb3gls0, B40Lb3sch0

B40_c

SESSION ERROR IDENTIFIED IN:

tssma3473m000 - Print Service Order Invoices

PROBLEM TEXT:

1. It is possible for the invoice process to invoice only part of the order.

2. Enter a service order with more than one position. When printing the service invoice, only the first position from the

order prints on the invoice. No financial transaction is created for the invoice. When creating financial transactions, the

error message is printed "Service order not yet (completely) invoiced." Tax provider has been implemented on the system.

3. When the Tax Error Report gets printed, the lines showing the tax error, are invoiced without the tax amount. Tax

provider has been implemented on the system.

SOLUTION DESCRIPTION:

The error #1 described above has been corrected by backporting ID 10243216 under the defect DF 698-1. The error #2 and error

#3 described above have been corrected using DF 698-2. Now all lines, for which the tax can be calculated without any errors,

will be invoiced correctly and the financial transactions written correctly. If an error occurs during tax calculation the line

amount is not considered for tax calculation.

The correction under DF 698-2 , may cause the same itemline to be printed multiple times. This happens when a tax

calculation error occurs for an item and the system tries to invoice the whole order again, because of failure in invoicing the

order in the previous try. This feature cannot be avoided unfortunately.

tiB40_b, tiB40_c,

tsB40_b,tsB40_c

tpB40_b, tpB40_c

tcB40_b,tcB40_c

psB40_b, psB40_c

SITUATION IDENTIFIED IN: Maintain Engineering Item Revisions (tiedm1101m000)

SITUATION DESCRIPTION:

(Reported for NT Backoffice build 15.8)

When using the session "maintain engineering item revisions" ( tiedm1101m000), and trying to launch a drawing, it gives

the following message:

" ttstpvtemul.

Shell functionality not supported by Windows NT"

SOLUTION DESCRIPTION:

It will now be possible to display the drawing attached to an engineering item revision by clicking the button "Drawing" or

using <Shift><Ctrl><D>.

The drawing file name will be read from the above session (tiedm1101m000) in form 3.

This file should exist in the directory as mentioned in the session "Maintain EDM Parameters" (tiedm0100m000) in the

field 'Directory Name for Drawing". Furthermore, the field "Display Drawing" indicates which application program should

be used to display the drawing.

In BW mode, this application must exist on the client. The name of the application should be the executable name and

should be in the PATH.

Note:

1.) It is required to have a /temp directory on the client since the application puts the file in this temporary directory for

reading and keeps it there.

2.) For this solution, it is required to have the DLL "ottdllbw" in the $BSE/tools/{...} directory. Please check if this

exists on your system and if not, contact the the support center.

This solution solves defect 365

SESSION ERROR INDENTIFIED IN: tssma3142m000 (Report Service Orders Completed)

PROBLEM TEXT:

In case ILC is implemented and service orders are reported completed via the session tssma3142m000, the field 'VAT' in

the session tssma3110m000 is changed. This problem only occurs when after maintaining Estimated Rows (tssma3170m000)

a Outbound advice is generated with session tdilc4201m000.

SOLUTION DESCRIPTION:

The problem is solved by PMG Service. If on Service Order niveau is choosen for 'No' tax then no tax appear on the Order

lines.

SESSION ERROR INDENTIFIED IN: Create Financial Transactions for Service Order. ( tssma6202m000 )

PROBLEM TEXT:

When defining Intergration Elements with Dimensions to use on the service order and creating a collect invoice, the posting

data in Finance was not correct. Only the last dimension code was logged in the Finance data. The result is wrong financial

information.

SOLUTION DESCRIPTION:

The problem is corrected in that way that the used dimensions with a collect invoice are filled in right now in the Financial

data.

SESSION ERROR INDENTIFIED IN: Report Service Order Completed ( tssma3142m000 )

PROBLEM TEXT:

The maximum number of sequences (9990 per employee) is reached. Customer has to look for free numbers manual.

When the Planned service order is report completed, the question appears 'Delete from planning?'. When giving Yes, the

order is removed from the plannings table (sma305). But the sequence by employee is now 'disturbed' with gaps. Only the

highest sequence number is used by adding employees to an order in session tssma3158m000 (Plan Service Order). So the

problem occurs that once the maximum sequence should be reached.

SOLUTION DESCRIPTION:

When a service order is reported completed now, for the related employees of the order the sequence is renumbered in the

plannings table so that there are no longer gaps. Adding a employee in the session tssma3158m000 is now based on the last

sequence number in a range without gaps.

SESSION ERROR INDENTIFIED IN: Plan Service Orders (tssma3158m000)

PROBLEM TEXT:

When planningsrows are linked to a serviceorder in the session above, Triton asks the user if the status of the order should

be changed

from FREE to PLANNED. When the session is aborted without a planningrow is added, then the status of the order remains

'Planned'.

SOLUTION DESCRIPTION:

After changing the related service order status from 'Free' to 'Planned', and aborting the sessions with 'A' then, when no rows

are added the status

form the service order is set back to free.

SESSION ERROR INDENTIFIED IN: Generate Periodic Maintenance Planning (tssma1224m000)

PROBLEM TEXT:

With the session above a planning could be generated depending on the frequence type of the servicing.

If for a certain installation and servicing a new planning is generated no problem occurs. When the choossen

frequency is fixed and the user didn't generate a planning for a whole year then generating a planning for a new

year is also not for a whole year.

SOLUTION DESCRIPTION:

Added some new functionallity :

When a new planning is generated and the used frequency was fixed then a check is done if there's a previous

year and if so or it has a complete planning. The user get a question if he wants to keep his old one or generate

a new planning.

SESSION ERROR INDENTIFIED IN: maintain Service Order Costs and Revenues. ( tssma3110m000 )

PROBLEM TEXT:

When by 'Service Order Costs Estimate' a purchase order is generated, it must be confirmed and tranfered within

Distibution.

After that the Purchase order number is known in the service tables. When adding a new record in Maintain Service Order

Costs

and Revenues the purchase number is copied for each new record.

SOLUTION DESCRIPTION:

The problem is solved, now the purchase order number only exists with the right Order and Sequence number.

SESSION ERROR INDENTIFIED IN: Print contract Invoices. ( tssma2472m000 )

PROBLEM TEXT:

On the report from the Contract Invoicing was no taxnumber available.

SOLUTION DESCRIPTION:

A taxnumber is now printed on the report with the same conditions as the printing of the service orders (tssma3473m000)

SESSION ERROR INDENTIFIED IN: Create Financial transaction For Service Orders. (tssma6201m000 )

PROBLEM TEXT:

WIP transactions from Service to Finance are going wrong when having several WIP-lines on a order with different cost

type groups.

The amount of the first WIP line is deducted on the second, the second on the third and so on.

SOLUTION DESCRIPTION:

The WIP transactions from Service to Finance are posted and reverse posted on the proper way.

SESSION ERROR INDENTIFIED IN: Display Locations (selection). ( tssma1592s000 )

PROBLEM TEXT:

When using the Telephone Screen (tssma3140m000) and zooming to the location session after filled in the Customer

the data of the customer doesn't appear in the display fields from the Display locations. This is only actual for the first

row.

SOLUTION DESCRIPTION:

The data of the customer b location is now also shown on the display location session.