SLI sales invoice taxation
Description of the enhancement
In various countries you must calculate tax based on the delivery date on the
delivery date of the shipped goods. So far the BaanERP5.0b SLI module did not
provide this feature; the tax year and the tax period were always based on the
invoice date. Using the enhancement for Sales invoices tax periods the user can
choose the tax date from:
n Invoice date
n Order date
n Delivery date
This new functionality solves Scopus defect number 75011. The solution number
is 17903.
New or changed software components
Table fields were added to the tables cisli100 and cisli205.
The following scripts were changed:
n cisli210
n cisli225
n cisli235
n cisli245
n cisli255
n cisli265
n cisli.dll2080
n cisli.dll2001
n cisli.dll3001
This form was changed:
n cisli1199s0002
Customer implications/benefits
Is the enhancement new?
Yes, but the previous functionality is still available.
What does the enhancement replace?
It extends the existing functionality.
Functional enhancements SP3
Release Notes Service Pack 3
1-9
Can you still use the previous software?
No, after installing SP3 you must run the conversion program for SLI that is
described in Chapter 5, SLI Conversion.
Do you have to start using the enhancement now?
Yes, but after installing the service pack 3 and running the conversion program,
as default, the software will work as it did before. The (key-)user can decide
when to use the new features. The conversion program is described in Chapter 5,
“SLI conversion.”
Can you start using the enhancement later?
No. After installing service pack 3 you must run the conversion program. The
conversion program takes care of setting the parameter(s) in such a way that you
can use the software as you did before.
What must be done to use the enhancement?
1 You must install the service pack 3 as described in Chapter 5.
2 Run the SLI conversion as described in Chapter 5, “SLI Conversion” in these
release notes.
3 You can select the appropriate Date for Sales Order Tax Determination in the
SLI Parameter (cisli1100s000) session.
4 Start the Compose/Print/Post Invoices (cisli2200m000) session to compose,
print, or post the invoice lines.
Functional enhancements SP3
Release Notes Service Pack 3
1-10
Release Notes Service Pack 3
2-1
Service pack 3 is an incremental service pack, which also includes the
enhancements of service pack 2. This chapter describes the functional
enhancements of the Service Pack 2 for BaanERP5.0b.
The following functional enhancements were included in service pack 2. Each of
the enhancements are described in the following sections in this chapter:
n Integration transactions (Warehousing/Finance)
n DTAUS99 format (Finance)
n Central Mapping scheme (multisite/multifinance)
n Integration Options (multisite/multifinance)
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.
Integration transactions
(Warehousing/Finance)
The integration transactions in the Finance package are posted by using the local
currency instead of using the reference currency.
Changed components:
n whinhdll1000
n tfglddll4010
n cislidll2045
n cislidll2055
n cislidll3005
n cislidll3006
2 Functional enhancements SP2
Functional enhancements SP2
Release Notes Service Pack 3
2-2
Service
Changed components to support the new BaanService Remote.
Tables
n tssoc000
n (Newly created. Not present in previous version)
Scripts
n tssoc200
n tssoc2100
n tssoc205
n tssoc210
n tssoc220
n tssoc240
n tssoc250
n tsintdlltino
Forms
n tssoc0100s0003
Session
n Time Stamping for BSR (tsmdm1580m000) It was newly created. Not
present in previous version.
DTAUS99 format
Description of the enhancement
This enhancement allows you to use the new DTAUS99 bank file 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.
Functional enhancements SP2
Release Notes Service Pack 3
2-3
Customer implications/benefits
Is the enhancement new?
Yes.
What does the enhancement 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 the enhancement 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 number 73321. It contains Scopus
solution 16764.
Functional enhancements SP2
Release Notes Service Pack 3
2-4
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 Transactions to Finance Transactions (tfgld4201m000)
n Integration Mapping Scheme (General) (tfgld4500m000)
n Central Mapping Scheme – Detail (tfgld4100s000)
n Integration Mapping Scheme (Manufacturing/Distribution – Overview)
(tfgld4501m000)
n Integration Mapping Scheme (Manufacturing/Distribution ) (tfgld4101s000)
n Integration Mapping Scheme (Project ) (tfgld4502m000)
n Integration Mapping Scheme (Project ) (tfgld4102s000)
n Integration Mapping Scheme (Service ) (tfgld4503m000)
n Integration Mapping Scheme (Service ) (tfgld4103s000)
n Integration Mapping Scheme (Commissions/Rebates ) (tfgld4504m000)
n Integration Mapping Scheme (Commissions/Rebates) (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 who use a large number of logistic
companies, a central mapping scheme was not feasible. With the current
enhancement, 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, because 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 3
2-5
Customers that run with service pack 1 (or higher) of BaanERP5.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 multisite 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 set up a specific scheme 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 multifinance /
multilogistic 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 number73315. 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 3
2-6
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 3
2-7
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 the field 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. If a logistical company does not necessarily use only a
single financial company, and, therefore, you can have many-to many company
relationships, you can use the enhancement immediately to solve your current
reference problems.
Are other components influenced?
No.
Functional enhancements SP2
Release Notes Service Pack 3
2-8
Deferred emergency service orders
Description of the enhancement
By using this enhancement, you can mark a service order as emergency, skip the
planning, and release the order to a field engineer. 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.
Because 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 Orders (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 the 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 3
2-9
Customer implications/benefits
Is the enhancement new?
Yes.
What does the enhancement 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 the enhancement 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.
Take the following 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 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 3
2-10
Emergency call handling
Description of the enhancement
The call center receives a call from the customer who requests an immediate
service from a service engineer. The call center registers the call as an
emergency, assigns the call to a service engineer, 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 Calls (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 Orders (tssoc2500m000)
Functional enhancements SP2
Release Notes Service Pack 3
2-11
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 assigned by default. If the first preferred
engineer is not present, the second preferred engineer should be
assigned by default. 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 the enhancement new?
It is an enhancement to the existing functionality. In BaanERP5.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 the enhancement 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.
Functional enhancements SP2
Release Notes Service Pack 3
2-12
Do you have to start using the enhancement now?
No, 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.
Take the following steps to use the new functionality:
1 Mark the call as an emergency.
2 Get the default service engineer from the configuration (either preferred
engineer 1 or preferred engineer 2) of the business partner.
3 If required, check the availability of the engineer based on the calendar linked
to this engineer.
4 Transfer the call to Service Order Control.
5 View the details of the released service order.
Change Business Processes?
Not applicable.
Are other components influenced?
No.
Functional enhancements SP2
Release Notes Service Pack 3
2-13
Help desk monitoring
Description of the enhancement
Use this enhancement to view calls that have not been responded to within a
given time after they are registered or assigned . Based on these details, the
Dispatcher can take appropriate action. Auto-refresh updates the call details,
which allow the Dispatcher to view the current deferred calls.
New or changed software components
Modules
Call Management (CLM)
Sessions
n Escalated/Deferred Calls (tsclm1520m0000)
n Call Parameters (tsclm0100s000)
Tables
Tsclm000( Call Parameters)
Sno Field Description
1 Dftm A provision is provided to indicate the deferred call time fence
based on which the deferred calls will be identified. The time
duration unit is taken from the Master Data Management
(MDM) parameters.
Tsclm100 (Calls)
Customer implications/benefits
Is the enhancement new?
It is an enhancement to the existing functionality. In BaanERP5.0b, the user can
view all calls that were escalated based on the priority of the call. The user is
now provided with the following options to view:
n Escalated Calls
n Deferred Calls
n All calls (Escalated and Deferred )
n Deferred Emergency Service Orders
What does the enhancement replace?
It does not replace any of the existing functionality.
Functional enhancements SP2
Release Notes Service Pack 3
2-14
Can you still use the previous software?
Yes. There is no problem in skipping this enhancement.
Do you have to start using the enhancement 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.
Take the following steps to use the enhancement;
1 Define the time fence in CLM Parameters. The time duration unit is taken
from the MDM parameters.
2 Check the status of the call.
3 If it is registered, check if the reported time plus the deferred call time fence
is greater than the current time. If yes, display the call as a deferred call.
4 If assigned, check if the assessment time plus the deferred call time fence is
greater than the current time. If yes, display the call as a deferred call.
5 The user can also view the deferred emergency service orders.
Change Business Processes?
Not applicable.
Are other components influenced?
No.
Functional enhancements SP2
Release Notes Service Pack 3
2-15
Paging support
Description of the enhancement
By using this enhancement, the field engineer can be paged whenever an
immediate service is required for an emergency service order.
New or changed software components
Modules
n Master Data Management (MDM)
n Call Management (CLM)
n Service Order Control (SOC)
Sessions
None
Tables
Tsmdm170
Sno Field Description
1 Page Page code
2 Emno Employee to whom the page code belongs
3 Ppno Employee to whom the page code belongs
4 Pager pin code Pager pin code
5 Pager type Type of pager, numeric or alphanumeric
6 Pena Pager enabled (y/n)
7 Page provider Code of the page provider
Tssoc200
Sno Field Description
1 PaMinuge Page frequency
Tsclm100
Sno Field Description
1 Minu Page frequency
Functional enhancements SP2
Release Notes Service Pack 3
2-16
Tscfg220
Sno Field Description
1 Page Page Allowed
Customer implications/benefits
Is the enhancement new?
Yes.
What does the enhancement 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 the enhancement 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.
Take the following steps to use the new functionality:
1 Maintain page information for the required field engineers.
2 Indicate whether pager is allowed for the configuration on site.
3 Indicate the page frequency for the call / service order.
4 Release the service order to the field engineer concerned. Based on the
paging information, the field engineer will be paged.
Change Business Processes
Not applicable.
Are other components influenced?
Tinoway’s BaanService Remote software is influenced by this enhancement. It
can access the paging information provided by Baan and proceed using the
paging functionality. See the section Tinoway integration in Chapter 4.
Functional enhancements SP2
Release Notes Service Pack 3
2-17
Service pack version check
In service pack 2 a feature is added which allows you to see which service pack
is active in your current environment. To check the service pack version you
must use the tccomspinfo (ttdsk2080m000) session. Take the following steps to
check the service pack version:
1 Select File/Run Program in your menu browser. The Run Program
(ttdsk2080m000) session appears.
2 Type tccomspinfo in the Program/Session field.
3 Choose OK. The service pack information will be displayed.
Baan ERP , Help , Consulting , Training , Support 