What’s new in Version 6.2 ?

Technology Evolutions
SAGE ENTERPRISE WEBTOP
The Netvibes evolution
 Sage Enterprise Webtop : Netvibes evolution
• An access to X3 widgets via Netvibes portal
• Different configurations :
Browser on PC
Web service
– Hosted
by Netvibes
Netvibes server
Sage ERP X3 Browser on PDA
Hosted by Netvibes
(on customer’s site)

Browser on PC
Web service

– Installed on
customer site
Sage ERP X3 Browser on PDA
Netvibes server
(on customer’s site) installed on premise
 Sage Enterprise Webtop
• Functions available :
– “standard list widget”
– “standard detail widget”
– Customer details
– Purchase requisition widget
• The widgets are all based on SOAP web
services (sub-programs) :
– Purchase requisition : 3 dedicated web services
– List and detail : through a new setup generating
the web services
 Sage Enterprise Webtop
• Setup screen for “standard” widgets :

Based on a data
model or an object
Selection criterion,
colored flag,
and specific program

List of fields presents

in the list widget

List of fields usable as

criteria for additional tabs

List of fields presents

in the detail widget
 Sage Enterprise Webtop
• At validation time for XXXXX record setup:
– 5 web services are described
• N_XXXXXLEC : reads the detailed fields for a record
• N_XXXXXLIS : reads the list of N lines with filtering criteria
• D_XXXXXLEC : describes the fields sent when detail is
requested
• D_XXXXXLIS : describes the columns present in the list
• R_XXXXXLIS : refreshes the favorite list
– The corresponding program is WNETXXXXX
• A specific program can be added with the same
labels.
 Netvibes evolution
• What about security ?
– Based on a single sign on hosted by Sage
– At connection time, authentication is needed (by
giving email address and password)
– A SSO token is then stored and sent during web
service connection
 How does Netvibes connection work ?
• First step : a contract between Sage, Netvibes and the customer
establishing a link :
– my_small_but_smart_company.com domain
– my_server_ip_address:my_port, MYFOLDER
• Second step : a list of users with email addresses defined in the users
table of Sage ERP X3 :
john.doe@ my_small_but_smart_company.com
• Third step : John Doe opens his Netvibes portal and adds a Sage Netvibes
widget
– The first time, a redirection will bring him on a single sign on screen hosted by
Sage, and he will create an account and validate it by clicking in a link sent by
email.
– If already registered, he will enter his password once.
– Netvibes will establish the link with the server, the folder, the user and perform
the requests in order to feed the widgets
How does Netvibes connection work ?
• When a list widget or detail widget is used :
– Netvibes calls the description web service and gets a
list of fields and criteria (the layout can be built)
– Netvibes calls the list web service with the right
criteria and gets the data to feed the widget
• Favorite list management :
– Netvibes stores locally the key of favorites
– Netvibes calls the refresh web service in order to get
the updated data

DEMO
 Sage Enterprise Webtop
• Purchase requisition management
– 3 web services are described
• H_PSH : called at header level, gives default values
• L_PSH : called at line level, when an item is selected
• C_PSH : at creation time
 Sage Enterprise Webtop
• Which pre-setting is delivered?
– The purchase requisition
– And a list of standard list / detail widgets :
SAGE SEARCH
Powered by Exalead
 Sage Search
• Adding a search engine in Sage ERP X3
– Based on a meta data description :
• A list of data models describing the table in which searches
can be done
• Indexing is done the character typed field
• A setup allows filtering per company and module on the
search
– With a search page
• That allows entering any text for search
• Presenting a list of results with counts and additional filtering
(per date, user, company and site, type of document)
• With hyper-links to the context
 Sage Search
• The pre-setting delivered
– An additional tab in Data models
– Defining if a model can be indexed, and on which
criteria
 Sage Search example screen

The result of the search

Direct link

Categories for
refining the
search
A first search screen
 Sage Search
• How is this done ?
– Indexation is triggered from ERP
• Usually as a batch task
• The Exalead server executes SQL sentences to extract the data
from X3 repository and performs the indexation
• The indexation can be complete or incremental (in that case,
time stamps must be added in some tables)
– The search
• Can only be triggered from X3 (a single sign on is done in
order to allow the right filtering on search)
• Is done through a http server in a portal view
• Allows a direct link to the objects
LEGAL COMPLIANCE (FRENCH MARKET)
CERTIFICATION REQUIREMENTS
 Legal certification
• We have a certification process running in
France for Sage ERP X3
– Constraints have been given (that will probably
become standard in other countries)
• Extended traceability (on maintenance and system
transactions, for example)
• Parameter modification sometimes forbidden
• Possibility of simple integration of an archiving system
• Cancelling log files must be impossible except via purging
• Evolution on the TABCOUNTRY table in order to make the
SIC number mandatory for business partners that are
companies in some countries.
 Legal certification
• Parameter modification forbidden
– Done through a modification at parameter definition
• A formula can be associated to a parameter
• If it exists, the formula is evaluated. If the result is false in the context, the value of
the parameter cannot be changed.
– Some global variables have been added :
• GUSR is the user for which the parameter are modified
• GSOC is the company, GSIT is the site, GLEG is the legislation if the value is
attached to a level where these fields can be defined (otherwise, it is false)
• GKFR is equal to 2 if KFR (French legislation) is activated
– Examples :
• GKFR<>2 : parameter cannot be changed if French legislation used on the
folder
• GLEG<>“FRA” : parameter cannot be changed for a company or site related
to the French legislation
• GUSR=GSUPER : only the super-user can have a different value than the
value defined at folder level
 Legal certification
• Chronological counters setup
– Already existing for Italian legislation for some type
of journals only
• Has been extended for other journal types
• Needs to check the right checkbox in counters
• Enhanced traceability
– Table maintenance control
• When entering to maintenance functions, the system
requests again the user to enter his password
• This is controlled via SIGMAINT parameter
• This parameter is modifiable only if GKFR<>2
 Legal certification
• Enhanced traceability
– Table maintenance control
• When entering to maintenance functions, the system
requests again the user to enter his password
• This is controlled via SIGMAINT parameter
• This parameter is modifiable only if GKFR<>2
– No log file cancellation allowed, except via purge
• This is controlled via CLRLOG parameter
• This parameter is modifiable only if GKFR<>2
 Legal certification
• Audit trail mandatory
– AUD activity code becomes active if AUDIT=2 or
KFR=2
– Audit condition are added on the Audit tab of the
table dictionary in the reference folder :
• They will be copied to the dictionary of every folder where
KFR activity code becomes true
• If this is needed for other legislations, the condition may be
changed (a request must be done to the development team)
 Legal certification
• New constraints on companies related data
– Controlled by an additional checkbox in the country
table
– A field allowing to distinguish companies from people
has also been added in the BP table (default value is
companies)
– When the BP is a company, SIC code becomes
mandatory, as well as zip code
 Legal certification
• This pre-setting is delivered for French market
– Traceability constraints
– Audit on some files
– Chronological counters
– Table maintenance control
– SIC control
MULTI-LEGISLATION ENHANCEMENT
 Filter on legislation per user
• Allows a user to see only the elements related to
a legislation code (or used by all legislations)
– Almost a “demo” flag
– Should be added to some users in demo folder
– Don’t forget to keep at least a multi-legislation user
• Implemented through a parameter named
LEGFIL (Legislation filter)
– Used for any data linked to legislation
– Used also by portal processes (replaces the LEGPORT
parameter used in V 6.1)
 Mass recodification for default codes
• The standard default codes are done in order to
allow a multi-legislation folder to be effective
– Payment terms codes are prefixed by legislation
– Journal type are also prefixed
– Standard Edition and mono-legislation folder will
require simple codes
 Mass key changes
• A setup allows the definition of mass recodification
• No more based on memos on codification tool, but on a
dedicated function :

• At folder initialization, a pattern

can be given in order to trigger
mass re-codification just after
data transfer (ex : US*)
SUPPORT OF ZPL PRINTERS
 Support of ZPL printers
• Allows the direct and fast print on bar code
printer by generation and transfer of ZPL files
– Avoids Crystal Reports
– Based on a new type
of printing destination
– The device address is
defined
 Support of ZPL printers
• Changes in the report dictionary

• In order to be used on a
ZPL printer, a report code
must be associated to a
ZPL report description
• In that case, the Crystal
Report is no more
mandatory, but may
remain if this report can
be sent on a ZPL printer or
on a normal printer
 Support of ZPL printers
• A new function describes a ZPL report :
– The format is
defined as a file with pattern
– The database request
is defined through
a data model
with filtering criteria
– Computed fields or
formulas will replace
patterns in the ZPL file
 Support of ZPL printers
• What is a SPL label looking like ?
– Today, no standard label is delivered in standard
(usually they are done by the customer)

– But it might look as this one :

ARCHIVE MANAGEMENT CONNECTOR
 Archive management connector
• A standard setup allowing to define :
– Triggering events for the archiving process :
• Reports execution
• Log file generation
• Standard export
• Attachment of document during object management
• Excel export from any grid in a screen
• Manual (ie. through an action)
– If a linked document attachment should be generated
on another object
– Meta data associated to the document to be
archived, according to their type
 Archive management connector
• A standard program defining methods :
– Definition of the meta data
– Archiving
– By default, delivered as a template
– We expect the EDM vendors to provide the specific
program for their product, as well as their installation
and configuration procedures
• A function allowing to inquire the document
through an URL (defined as a parameter) :
– As a linked document
– Through a search based on meta data value
 Archive management connector
• Several suppliers are expected to provide a
connector
– Version One
– Audros
– Docubase
• For version 6.2 :
– The standard connector was done
– A common work with Version One and Audros was
done (they are able to supply such a connector)
– A technical documentation as well as two
implementation definition document exist
 Some Version One screens

Direct access
to a document

Access to a list of documents

based on meta data value
 Some Audros screens

Direct access
to a document

Access to a list of documents

based on meta data value
OFFICE SUPPORT ENHANCEMENT
 Office support enhancement
• The Word and Excel templates have been
improved for quotation
– Based on comments (Excel) or tags
– Allows an update of a Word/Excel document without
loosing the modifications done by the user
– Macros have been changed
• Office 2010 is officially supported
– except for Outlook integration
OPTIMISTIC / PESSIMISTIC LOCK
 Optimistic / pessimistic lock
• Allows a record inquiry in object management
not to lock the record
– Lock is done at first modification attempt
– Based on a flag in object setup
– Not used in standard, but available for bespoke
development
– Needs sometimes to slightly adapt the code
NEW VERSION OF PORTAL
 New version of portal
• With the ability of changing the frames organizations
in a tab, to display or not the frame border…

Title

Number of pages

Frames organization

Display widgets frame

Display separators
ENHANCEMENTS FOR BUSINESS INTELLIGENCE
Enhancements for Business Intelligence
• The version 3.1 of Business Object is now used :
• Latest version (more stable, maintained)
• Available on Windows Server 2008 64 bits
• Needs to change the format of each report
• Performance enhancements have been done
• Incremental updates on fact tables
• Most efficient datawarehouse updates
MEMO BUTTON ON EXCEL EXPORT
 Memo on Excel Export
• Allows the predefinition of export templates
directly used at export time :
• Memo button
• Recall button
• STD template is used by default
• What has to be done for pre-setting :
• Prepare a specific Excel export setup (for
example in financial data reports)
DEVELOPMENT ENVIRONMENT IN
ECLIPSE
 The Eclipse plugin
• A lot of improvements done :
• ~ 90 entries related to Eclipse plugin enhancements in release note.
• Some examples:
• The program dictionary is now linked and updated from Eclipse
plugin
• Online help on data types
• Hierarchical structure of the X3 code presented in a dedicated view
• Direct execution of X3 code from editor
• Auto completion on Subprograms
• Better syntactic control (max length on variables…)
• Calculation tool available from editor
• Google translate access for comments translations
• Performance enhancements…
THANK YOU
What’s new in Version 6.2 ?

Inquiries and reports on company

groups having different fiscal years
 Goal
Allowing inquiries and reports on
company groups having different fiscal
years
 Scope
• Inquiries
– Account Balances (CONSBAL)
– Currency Account Balances (CONSBAF)
– Accounts (CONSCPT)
– Analytical Accounts (CONSNAT)
– Dimensions (CONSSEC)
– Dimension Balances (EDITBLA)
• Reports
– General Balance
– Auxiliary Ledger Balances (BP Balances)
 Prerequisites
• Same ledger type
• Same currency
• Same charts of accounts
• Same division of periods
Account Balances : New columns
Before Now
Ledger debit previous balance
Ledger credit previous balance
Ledger debit Ledger period debit
Ledger credit Ledger period credit
Ledger debit balance Ledger debit period balance
Ledger credit balance Ledger credit period balance
Ledger debit end balance
Ledger credit end balance
Debit previous balance
Credit previous balance
Debit Period debit
Credit Period credit
Debit balance Debit balance period
Credit balance Credit balance period
Debit end balance
Credit end balance
Account Balances : columns in detail

Columns The fiscal years of the inquired companies have the same start dates The fiscal year start dates are
and end dates different

(1) Debit ∑ debit entries – ∑ credit entries from fiscal year begin (fiscal year Columns not populated
previous corresponding to the inquiry start date) to the end of previous period
balance (period prior to the first inquiry period)
The carry forward of the fiscal year is included or not according to the
(2) Credit criterion « Fiscal Year-1 » (checked by default)
previous If the inquired period covers several fiscal years, intermediate periods
balance of carry forwards and closures are not taken into account.
One of the two columns is populated according to the calculation
result.
Account Balances : columns in detail
(rest)
Columns The fiscal years of the inquired companies have the The fiscal year start dates are
same start dates and end dates different
(3) Debit entries ∑ Debit entries on the requested period ∑ Debit entries on the requested
Carry forward periods are never taken into account in period.
this column Carry forward periods are never
Regarding the closing period: taken into account.
-          periods of intermediate closure are not taken Closing periods are not taken into
into account (in the case of an inquiry on several account.
fiscal years)
-          closure entries are taken into account only if
the inquiry end date corresponds to the fiscal year
end date and the criterion « Closing period » is
checked.
(4) Credit entries ∑ Credit entries on the requested period ∑ Credit transactions on the
Carry forward periods are never taken into account in requested period.
this column Carry forward periods are never
Regarding the closing period: taken into account.
-          periods of intermediate closing are not taken Closing periods are not taken into
into account (in the case of an inquiry on several account.
fiscal years)
-          periods of intermediate closing are taken into
account only if the inquiry end date corresponds to
the fiscal year end date and the criterion « Closing
period » is checked.
Account Balances : columns in detail
(rest)
Columns The fiscal years of the inquired The fiscal year start dates
companies have the same start dates and are different
end dates
(5) Debit Column 3 – Column 4
balance period One of the two columns is populated depending on the result of
calculation
(6) Credit
balance period
(7) Debit end Column 1 + Column 5 – (Column 2 + Column 6)
balance One of the two columns is populated depending on the result of
calculation
(8) Credit end
balance
 Currency Account Balances
• Same rules than Account Balances
• New columns to display amounts in the
currency selected
• Conversion is based on the rate type of the
parameter value CNSTYPCUR (Module
‘Common Data’, Group ‘CUR’)
 Accounts, Anlytical Accounts and
Dimensions
• For a request on company groups with
different fiscal years
– the balance in the header is not calculated /
displayed
– the tab ‘Balance’ is not populated
 Dimension Balances

• No modification in the screen structure

• The amount columns display the cumulative
amounts of entries for the requested period
• Carry forwards and closures are taken into
account only if inquiry dates (start or end) =
fiscal year dates (start or end)
 Reports
• General principles regarding both reports
Before Now
Debit previous balance
Credit previous balance
Debit entries of the period Debit entries of the period
Credit entries of the period Credit entries of the period
Cumulative debit entries at the end of period
Cumulative credit entries at the end of the
period
Balance at the end of the period (debit or Balance at the end of the period (debit or
credit) credit)
 Reports
For a company group whith different fiscal years
• Same rules as for inquiries
• Previous balances not displayed
• Cumulative Debit and Credit movements for
the period are displayed
• Balance end of period is displayed = difference
between the two previous columns
 What you have to do
• translate titles of new columns
• translate the title of the function Currency
Account Balances
• translate the text description of the inquiry
screen (BAF)
• Think about the parameter value CNSTYPCUR :
for your legislation, do you want that this
parameter value has a default value ?