Date : 97-11-20 [14:49] 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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3473m000 | Program Source | sma3473 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10228359
Call Description :
This problem occurs on the BW version.
The Selection form (tssma3297s000) activated by Select Service Job
Sheets (tssma3260m000) is missing the 'OK' Button. The choosen
selection criteria can not be executed in this way.
Solution Description :
There was a button on the Selection form (tssma3297s000) missing, this
button is added and set to default.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3297s000 | Form | sma3297s0001 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma1102m000 | Program Source | sma1102 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10228494
Call Description :
tssma3271m000 is making inventory go negative.
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 2
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
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
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'.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3271m000 | Program Source | sma3271 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10228662
Call Description :
As you can see on enclosure 2 we do have first free mumbers for
service order due to the parameter (enclosure 3).
The problem once more, is that the session tcmcs0547s000. Display
first free numbers starts the display with the wrong records:
Bestellungen (enclosure) when we zoom from the field service order
number in the insert mode.
Solution Description :
When zooming from series when adding a new service order record, in
some cases the series of purchase orders were displayed.
This is problem is solved, the series of Service are now correctly
displayed.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3101m000 | Program Source | sma3101 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10228837
Call Description :
Field warningtext does not update
When we has written a warningtext the field warningtext does not
change from No to Yes in the session.
Solution Description :
When zooming in the session tssma3105m000 ('Maintain Technician's
Daily Planning') to the sub-session tssma3142s000 ('Report Service
Order Completed') the warning-text that was added was not shown.
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 3
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
This problem is solved, so the customer can see his warning text when
it appears.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3142s000 | Form | sma3142s0001 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma2120m000 | Program Source | sma2120 | | B40 b3
| tssma3101m000 | Program Source | sma3101 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma1224m000 | Program Source | sma1224 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10229295
Call Description :
If a text is copieed in the session Maintain Servicings, changes are
made in the original and derived text simultaneously.
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 4
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
Solution Description :
Within the session Maintain Servicings ('tssma1120m000') it's possible
to add a checklist. Copying that checklist with Ctrl-c gave the
problem that no new checklist was created, so modifying that checklist
results in modifying the original text and the duplicated text.
That problem is fixed, now both text are maintained as independent
checklists.
PMG Service.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma1120m000 | Program Source | sma1120 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10229882
Call Description :
Hours transactions can not be entered due to conversion
factors.(tphrs1100m000)
Solution Description :
This call contains the solution from ID 10226549 for the related
components.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3101m000 | Function Source | sma0012 | | B40 b3
| tssma3101m000 | Program Object | sma3101 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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)
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.
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 5
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3473m000 | Program Source | sma3473 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10230033
Call Description :
The domain for postal codes is given as tcccty, should be tcpstc. Also
in program tssma3170, tax code calculation should be calling
itcmcs0036.
Solution Description :
Tax will now be calculated correctly.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3110m000 | Program Source | sma3110 | | B40 b3
| tssma3170s000 | Program Source | sma3170 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma1471m000 | Program Source | sma1471 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10230815
Call Description :
The session tssma3110s000 displayed the wrong lines and the commands
Next and Previous won't work.
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
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 6
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3110s000 | Program Source | sma3110 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10230921
Call Description :
When there's a run of contract invoices only the invoice amount of the
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma2472m000 | Program Source | sma2472 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma1424m000 | Program Source | sma1424 | | B40 b3
| tssma1424m000 | Report | sma142401001 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10240051
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 7
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
Call Description :
When adding a record to the Installations Types with session
tssma1101m000, it's possible to clear the key field with Ctrl-X and
save the record.
Solution Description :
The field Installation Type could be left empty in the session
sma1101m000 ('maintain installation types'). This gaves troubles in
other sessions where this data was used. This problem is solved.
PMG Service
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma1101m000 | Program Source | sma1101 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma1102m000 | Program Source | sma1102 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10240418
Call Description :
Testing BAAN on NT operating systems, using SQL server as
database, locking problems occur. Yhis is causing a bad performance.
Solution Description :
solution for distribution as follows:
Application locks were set when data were modified (change; add;
text; deletes) and were removed when the action was finished.
This lead to many transactions on application locks.
Now the application locks are set when the data are modified (change;
add; text; deletes) but the lock is removed when the user passes to
any other order line (first view, last view, previous view, next view,
find, query) or when ending the program.
The solution is implemented for sales and purchase order lines and for
sales qutotation lines and purchase inquiry lines.
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 8
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
For purchase contracts a bug on application locks (they were only
removed when ending the session) is solved.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma1202m000 | Program Source | sma1202 | 002 | B40 b3
| tssma1206m000 | Program Source | sma1206 | 002 | B40 b3
| tssma1224m000 | Program Source | sma1224 | 002 | B40 b3
| tssma1230m000 | Program Source | sma1230 | 002 | B40 b3
| tssma1271m000 | Program Source | sma1271 | 002 | B40 b3
| tssma1272m000 | Program Source | sma1272 | 002 | B40 b3
| tssma2204m000 | Program Source | sma2204 | 002 | B40 b3
| tssma2220m000 | Program Source | sma2220 | 002 | B40 b3
| tssma2221m000 | Program Source | sma2221 | 002 | B40 b3
| tssma2222m000 | Program Source | sma2222 | 002 | B40 b3
| tssma2223m000 | Program Source | sma2223 | 002 | B40 b3
| tssma2271m000 | Program Source | sma2271 | 002 | B40 b3
| tssma3212m000 | Program Source | sma3212 | 002 | B40 b3
| tssma3292m000 | Program Source | sma3292 | 002 | B40 b3
| tssma3293m000 | Program Source | sma3293 | 002 | B40 b3
| tssma5201m000 | Program Source | sma5201 | 002 | B40 b3
| tssma5202m000 | Program Source | sma5202 | 002 | B40 b3
| tssma6211m000 | Program Source | sma6211 | 002 | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma1102m000 | Table Def. | sma102 | | B40 b3
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 9
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
| tssma1102m000 | Table Def. | sma110 | | B40 b3
| tssma1102m000 | Table Def. | sma220 | | B40 b3
| tssma1102m000 | Table Def. | sma301 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10241730
Call Description :
When having a run of contract invoices for one customer the amount on
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma2472m000 | Program Source | sma2472 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10242061
Call Description :
The service orders are not printed correctly if there is a maximum
selection in the session tssma3473m000. Only the orders of the first
order type are printed.
Solution Description :
If was choosen for the complete selection within the session
tssma3473m000 (print service order invoices) then only the service
orders of the first service order type were printed.
This problem is solved now all order types with there service orders
are printed correct now.
PMG Service.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3473m000 | Program Source | sma3473 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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 :
SC,
This is the further information on the previous answer and a
extension on the existing functionality.
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 10
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
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
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.
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 11
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
The whole story not only counts for deleting installations but also
for adding installations.
Kind Regards,
PMG Service.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma2120m000 | Program Source | sma2120 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3473m000 | Program Source | sma3473 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
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.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma1102m000 | Program Source | sma1102 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10242861
Date : 97-11-20 [14:49] RELEASE NOTES PER P.D CALL NUMBER Page : 12
Ts 100 (Operational) Company : 100
------------------------------------------------------------------------------------------------------------------------------------
Call Description :
This ID is made for the problems with ID 10240418.
In a action from PMG, the by AD entered ID 10240418 must be deleted
from the sources of the B40_bx environment.
However, under this ID there are modifications made that doesn't
belong to this ID. So, a new ID is created to keep the ment solution
and delete the ID 10240418 from the source.
PMG Service.
Solution Description :
This ID is created to keep a solution when the ID 10240418 is deleted.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3473m000 | Program Source | sma3473 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------
10242868
Call Description :
Embedded financial transactions not working correctly.
Solution Description :
Several problems regarding embedded financial integrations have been
solved.
+--------------------------------------------------------------------------------------------------------------------------
| Session | Software Component | Modified Component | Language | VRC
|-------------------+----------------------+------------------------+-------------------------------------+----------------
| tssma3473m000 | Program Source | sma3473 | | B40 b3
| tssma6201m000 | Program Source | sma6201 | | B40 b3
------------------------------------------------------------------------------------------------------------------------------------