1 Functional enhancements SP2
This chapter describes the functional enhancements of the Service Pack 2 for
BaanERP 5.0b. The first section lists an overview of the functional
enhancements. The sections that follow describe the topics for which restriction
or defects apply.
Overview of functional enhancements
The following functional enhancements are included in this service pack. Each of
the enhancements are described in the following sections in this chapter:
n DTAUS99 format (Finance)
n Central Mapping scheme (multi site/multi finance)
n Integration Options (multi site/multi finance)
n Deferred emergency service orders (Service)
n Emergency call handling (Service)
n Help desk monitoring (Service)
n Service pack version check
Service pack 2 enables BaanERP for AS/400 (porting). This enhancement is not
described.
DTAUS99 format
Description of the enhancement
This enhancement allows you to use the new DTAUS99 bankfile in the Create
German Bank Order for Diskette (tfcmg1261m000) session and the Create
German Bank Order (Debit) for Diskette (tfcmg4261s000) session.
The format was changed to support payments or receipts in either German Marks
or euros.
New or changed software components
n Create German Bank Order for Diskette (tfcmg1261m000) session
n Create German Bank Order (Debit) for Diskette (tfcmg4261s000) session
1 Functional enhancements SP2
Functional enhancements SP2
Release Notes Service Pack 2
1-2
Customer implications/benefits
Is it new ?
Yes, this is a new feature.
What does it replace ?
It replaces the former bank file created in the previously mentioned sessions.
Can you still use the previous software ?
No, the previous bank file is no longer available.
Do you have to start using it now ?
Yes, you have to start using it now.
Can you start using the enhancement later ?
No, because the previous option is no longer available it cannot be used.
What must be done to use the enhancement ?
Nothing extra has to be done. When a payment method is created that uses one of
the previously mentioned sessions, the new format will be used instead of the old
format.
Central mapping scheme
Description of the enhancement
Having a logistic company is not mandatory anymore in the central mapping
scheme. When you leave it empty, it is used as the base setup in the ledger A/C
mapping for all logistic companies. The integration mapping company
functionality is removed from the Logistic Companies by Financial Companies
(tfgld0100m000) session.
This enhancement solved Scopus defect 73321. It contains Scopus solution
16764.
Functional enhancements SP2
Release Notes Service Pack 2
1-3
New or changed software components
There are no new software components.
The following sessions were changed:
n Logistic Companies by Financial Company (tfgld0100m000)
n Post Integration Transaction into Finance (tfgld4201m000)
n Central Mapping Scheme – Overview (tfgld4500m000)
n Central Mapping Scheme – Detail (tfgld4100s000)
n Integration Mapping Scheme (Manufacturing/Distribution – Overview)
(tfgld4501m000)
n Integration Mapping Scheme (Manufacturing/Distribution – Detail)
(tfgld4101s000)
n Integration Mapping Scheme (Project – Overview) (tfgld4502m000)
n Integration Mapping Scheme (Project – Detail) (tfgld4102s000)
n Integration Mapping Scheme (Service – Overview) (tfgld4503m000)
n Integration Mapping Scheme (Service – Detail) (tfgld4103s000)
n Integration Mapping Scheme (Commissions/Rebates – Overview)
(tfgld4504m000)
n Integration Mapping Scheme (Commissions/Rebates – Detail)
(tfgld4104s000)
Customer implications/benefits
In the old situation for all logistic companies in an enterprise, a central mapping
scheme had to be defined. For customers using a large number of logistic
companies, this could not be maintained. Now, you only need to setup a central
mapping scheme once and leave the Logistic Company field empty. It will be
used as a base setup for all logistic companies. Logistic companies that require a
specific mapping onto Finance can be maintained only for this specific logistic
company.
For customers, that already run BaanERP this has no consequences. It is easier to
share one central mapping scheme across logistic companies. Because this is an
optional enhancement, customers are not forced to change their current setup.
Functional enhancements SP2
Release Notes Service Pack 2
1-4
Customers that run with Service pack 1 of BaanERP 5.0b are now able to work
with the Integration Mapping Company field in the Logistic Companies by
Financial Company (tfgld0100m000) session. This field was removed, because it
cannot work for all multi site scenearios.
What must be done to use the enhancement ?
Customers may need to reconsider the central mapping scheme setup and find
out whether a standard mapping scheme setup can be used, and when they need
to setup a specific one for one logistic company.
Are other components influenced ?
No
Integration options
Description of the enhancement
When you define options by integration element, you can now define a logistic
company to which the logistic data in the session will refer. You can also leave
this field blank and define a blank setup. Especially in multi finance/multi
logistic company setups, the logistic data had to be shared because database
references and zoom session could not be established otherwise. Now, only when
the Logistic Company field is left blank, we expect your data not be shared.
This enhancement solves Scopus defect 73315. It includes Scopus solution
16763.
New or changed software components
There are no new software components.
The following components were changed:
Table defintions
n tfgld421
n tfgld422
n tfgld423
n tfgld424
n tfgld425
Functional enhancements SP2
Release Notes Service Pack 2
1-5
Forms
n tfgld4121m0001
n tfgld4122s0000
n tfgld4122s0001
n tfgld4122s0002
n tfgld4123s0000
n tfgld4123s0001
n tfgld4123s0002
n tfgld4123s0005
n tfgld4124s0000
n tfgld4124s0001
n tfgld4124s0002
n tfgld4124s0003
n tfgld4124s0004
n tfgld4124s0005
n tfgld4124s0006
n tfgld4124s0007
n tfgld4124s0008
n tfgld4125s0000
n tfgld4125s0001
n tfgld4125s0002
n tfgld4125s0003
n tfgld4125s0004
n tfgld4125s0005
n tfgld4125s0006
n tfgld4125s0007
n tfgld4125s0008
n tfgld4421m0000
n tfgld4422m0000
Reports
n tfgld442111000
n tfgld442112000
n tfgld442211000
Libraries
n tfgld.dll4000
n tfgld.dll4016
n tfacp.dll0015
Functional enhancements SP2
Release Notes Service Pack 2
1-6
Scripts
n tfgld4121
n tfgld4122
n tfgld4123
n tfgld4124
n tfgld4125
n tfgld4201
n tfgld4421
n tfgld4422
Customer implications/benefits
You can specify integration option relations by logistic company. The logistic
entities of a specific logistic company can now be used for reading
references/establishing zoom sessions and you do not need to share your data.
Only in situations where you always use the same logistic company/financial
company relationship do you need to share tables.
The Logistic Company field is optional. When this is left blank, the setup is
used as a sort of base setup. When a dimension cannot be found based on logistic
company search, the blank setup will be used.
What must be done to use the enhancement ?
When there is a current setup, the customer does not have to create a specific
new setup. Programs that use the Integration Option setup will always determine
the correct setup. If you have problems with the current solution you should
reconsider your setup. In situations where it is not obvious that a certain logistic
company will always use a certain financial company, and as a consequence you
can have many-to-many relationships, you can use this solution immediately to
solve your current reference problems.
Are other components influenced ?
No.
Functional enhancements SP2
Release Notes Service Pack 2
1-7
Deferred emergency service orders
Short description of the enhancement
By using this enhancement, a service order can be marked as emergency and
released to a field engineer, skipping the planning part. Also all the released
service orders that are either emergency/created by emergency calls, and that are
not responded to within the given time, are displayed as deferred emergency
service orders. As these service orders are auto-refreshed, the dispatcher can
easily view orders that have not been responded to.
New or changed software components
Modules
n Service Order Control (SOC)
Sessions
n Service Order Processing (tssoc2100s000)
n Deferred Emergency Service Orders (tssoc2502m000)
Tables
Tssoc000 (SOC Parameters)
Sno Field Description
1 Oect A provision is provided to indicate the order escalation time on
which the deferred orders will be identified. The time duration
unit is calculated from MDM (Master Data Management)
Parameters
Tssoc200 (Service Orders )
Sno Field Description
1 Emer Determines whether the service order is emergency or not.
2 Orrt Order release time keeps track of the date on which the service
order is handled to the field engineer
3 Ract The reaction time is used to keep track of the last changes that
are made to the service order after it is released
4 Ltdt Last transaction date keeps track of changes with Tinoway
Functional enhancements SP2
Release Notes Service Pack 2
1-8
Customer implications/benefits
Is it new ?
Yes.
What does it replace ?
It does not replace any of the existing functionality.
Can you still use the previous software ?
Yes. There is no problem in skipping this enhancement.
Do you have to start using it now ?
It is not mandatory.
Can you start using the enhancement later ?
Yes.
What must be done to use the enhancement ?
Conversion of data is not required.
Follow these steps to use the enhancement.
1 Maintain order escalation time in SOC parameters.
2 Get the details of the service orders that are set to emergency and released.
3 Check if the release time plus the order escalation time is greater than the
current time.
4 If the check in step 3 is answered with yes, the order is considered as a
deferred escalation service order.
Is there a change of business processes?
Not applicable.
Are other components influenced ?
No.
Functional enhancements SP2
Release Notes Service Pack 2
1-9
Emergency call handling
Description of the enhancement
The call center receives a call from the customer requesting an immediate service
from a service engineer. The call center registers the call as an emergency, enters
to which service engineer the call should be assigned, and transfers the call to
Service Order Control, which creates a service order with status released. This
Service order is readily available to the service engineer, who can respond to the
customer quickly.
You can now automatically transfer the calls to a service order. If a deferred call
is for a configuration that is covered under a contract or a warranty, the system
automatically transfers the call to a released service order, to make it available to
the field engineer as soon as possible. A new session is provided for this
enhancement, which can be maintained as a repetitive job for performing the
automatic transfer.
New or changed software components
Modules
n Call Management (CLM)
n Service Order Control (SOC)
Sessions
n Call Handling (tsclm1100s000)
n Escalated / Deferred Calls (tsclm1520m0000)
n Print Calls (tsclm1400m000)
n Call History (tsclm8510s000)
n Calls (tsclm8520m000)
n Call Processing (tsclm1118s000)
n Automatic transfer of Deferred Calls (tsclm1250m000)
n Service Order Processing (tssoc2500m000)
Functional enhancements SP2
Release Notes Service Pack 2
1-10
Tables
Tsclm100 (Calls)
Sno Field Description
1 Emer A provision is provided in the call to indicate whether the call is
an emergency or not.
2 Oemn Whenever the call taker records the call as an emergency, the
first preferred engineer maintained for the configuration
(tscfg220) should be defaulted. If the first preferred engineer is
not present, then the second preferred engineer should be
defaulted. If the second preferred engineer is not present, then
the call handler should fill, the service engineer manually
3 Minu The call handler can mention the page frequency in the call
header. In other words how many times to page the service
engineer.
Tsclm810 (Call history)
As the data maintained in tsclm100 is also maintained in history, all the fields
(emergency (y/n) , service engineer, and page frequency) will also be replicated
in call history.
Tssoc200 (Service Orders)
Sno Field Description
1 Minu Page frequency for the service engineer
Customer implications/benefits
Is it new ?
It is an enhancement to the existing functionality. In BaanERP 5.0b, the call
center can create a call and transfer it to Service Order Control (SOC) where the
order is planned and released to an appropriate service engineer. The new
functionality enables the user to directly create a service order by skipping the
planning part (Detailed Service Requirements Planning and Global Service
Requirements Planning) and automatically transferring calls to service orders.
What does it replace ?
It does not replace any of the existing functionalities.
Can you still use the previous software ?
Yes. There is no problem in skipping this enhancement
Baan ERP , Help , Consulting , Training , Support 