GB Cen 509 Uti Adm 091 1

G.O.L.D.
CENTRAL-SHOP
ADMINISTRATION
Manual type: User manual

Manual reference: GB-CEN-509-UTI-ADM-091-1
This manual corresponds to the patch: CEN509-RM00JAN11

CONFIDENTIALITY
This document contains information that is proprietary and confidential to Aldata Solution.
This information is provided for the sole purpose of permitting the recipient to evaluate the
information. In consideration of the receipt of this document, the recipient agrees to treat the
information as confidential and to not reproduce or otherwise disclose this information to any
persons outside the group directly responsible for the evaluation of its contents, without the
prior written consent of Aldata Solution.
Copyright
2007, Aldata Solution. All rights of reproduction reserved.
G.O.L.D. is a registered trademark of Aldata Solution.
All other brand names of products mentioned may be registered trademarks or trademarks of
their respective companies.
FOREWORD
ABOUT G.O.L.D. PRODUCT DOCUMENTATION
Types of manuals
There are three types of manuals related to G.O.L.D. products:

user manuals provide functional explanations and explain how to use G.O.L.D. screens
administration manuals are for the use of administrators and project managers in charge
of the installation and the maintenance
installation manuals provide all information necessary for the installation of the products
Typographic convention
In order to make Aldata manuals easier to follow, the following typographic convention has been
adopted:
Convention Use
Bold screen, programme, field
[Bold in square brackets] button
"In quotation marks" panel, tab
CAPITAL AND BOLD table
Courrier font code
Functions
This manual does not describe the use of:

lists of values to help field input
calendars to help date input
search panels
contextual menus etc
This manual explains how to create records. To consult, modify or delete records, the proce-
dure is generally identical in all screens which is why it is not described here either.
For information on these functions common to all the screens, please consult the manual Intro-
duction to G.O.L.D., Ref. GB-ALL-UTI-INTRO-001. It also contains important information on
how to navigate in G.O.L.D., carry out a search in the drop-down lists and table columns, per-
sonalise the colours of G.O.L.D. etc.
MANUAL UPDATES
This page presents the modifications that have been made to this manual since its creation.
Patch CEN509-RM00JAN11 (January 11):

Evolution(s) described in the version GB-CEN-509-UTI-ADM-091-1 of this manual
Update of "Defining functional profile rights without using reference profiles", page 26:
-> update of entry 76 of table 1029
-> addition of entry 82 of table 1029 to manage access rights to the new REACH function-
ality
-> addition of entries 94 and 95 of table 1029 to manage respectively the modification of
customer orders and the modification of supplier orders
Patch CEN508-RM00OCT08 (October 08):

Update of the section "Entries of the "Administration" menu not documented in this man-
ual", page 10: the User third-party link management entry and the [Import ord. actions]
button (in the Profile management screen) are described in the "Import order follow-up"
manual, ref. GB-CEN-UTI-CDEIMP-322
Update of the description of the Profile type field in the procedure "Creating a reference
profile", page 22
-> general update of the entries of table 1029
-> addition of entries 76 to 81
Addition of "Defining authorised competitors during price statement management", page 51
Addition of "Defining the sales prices authorised by profile", page 52
Addition of "Preventing the modification of orders depending on their origin", page 53
Patch CEN507-RM00JUL07 (July 07):

Update of "Introduction", page 10
-> general update of the entries of table 1029 (access paths, screen names, etc.)
-> deletion of entry 19
-> addition of entries 67 to 75
Patch CEN506-RM00NOV06 (November 06):

Update of "Preventing the creation/modification of certain discount types", page 47:
-> impact on the Interactive calculator screen
-> new "Free authorised" column
-> new parameter 2353/2 concerning the discount type display
Addition of "Preventing cost price display by context", page 48
-> addition of entries 55 to 66 to table 1029
-> update of entry 30
-> update of entry 37
Patch CEN505-RM00MAY06 (May 06):

Evolution(s) described in the version GB-CS-505-UTI-ADM-091-2 of this manual
Addition of "Allowing the Invoice Control users to update the stock following the variance
identification", page 30
Patch CEN505-RM00MAY06 (May 06):

Evolution(s) described in the version GB-CS-505-UTI-ADM-091-1 of this manual
addition of entries 37 to 54 to table 1029
Addition of "Managing the display of certain data when displaying stock movements",
page 48
Addition of "Defining the article lists authorised by profile", page 49
Addition of "User passwords", page 11 and "Managing user passwords", page 17 following the
menu reorganisation of G.O.L.D. Central (this data was previously defined in "Common
functions")
Functions of the "Administration" menu of G.O.L.D. Central Version 5 not documented in this
manual / Other manuals to be consulted:
Networks and sites which can be selected in the screens are now defined in G.O.L.D.
Administration in the business profile, not in the functional profile anymore => See the
"G.O.L.D. Administration" manual, ref. GB-CS-UTI-GOADM-016
All procedures linked to the article pre-referencing are described in a separate manual:
see the "G.O.L.D. PIM" manual, ref. GB-CS-UTI-PREREF-200
Events warnings management is documented in the "G.O.L.D. Events" manual, ref. GB-CS-
UTI-EVENTS-049
Patch CEN504-RM00NOV05 (November 05) - Version GB-CS-UTI-ADM-091-1 of this manual

Manual revision. No change in this manual as:
the "Local profiles by site/network" and "Local user management" entries are documented
in the "Franchise Management" manual, ref. GB-CS-UTI-FRAN-136
the "Instance address management" entry is described in the "Management of G.O.L.D.
Central in distributed environment" manual, ref. GB-CS-EXP-MBASES-147
=> Alignment of manual with the November patch.
Note: the reference of the document remains unchanged.
Patch CEN503-EV01AUG05 (August 05):

Evolution(s) described in the version GB-CS-UTI-ADM-091-1 of this manual
This manual was created following the menu reorganisation of G.O.L.D. Central in functional
modules. It comes from the "User Management" manual, ref. GB-CS-UTI-GTUTIL-021-4 and the
"Master management" manual, ref. GB-CS-UTI-MASTER-070-1.
Here are the main modifications made to document the functionalities of the patch CEN503-
EV01AUG05:
General update of "General presentation", page 9 with the introduction of reference pro-
files
Addition of the chapter "Transferring files to GAIA and consulting the database", page 55
Update of the chapter "Managing users and functional profiles", page 21 with:
-> addition of new entries 8, 29, 30, 31, 32, 33, 34, 35 and 36 to table 1029
-> deletion of entries 7, 23, 24 and 25 of table 1029 (as the workflow is now used to manage
the input of general data concerning articles, suppliers, customers and sites)
-> introduction of reference profiles
-> addition of "Preventing the creation/modification of certain discount types", page 47
TABLE OF CONTENTS
CHAPTER 1
GENERAL Introduction ........................................................................................... 10
PRESENTATION Aim of this manual ............................................................................... 10
Who is this manual destined for? .............................................................. 10
Entries of the "Administration" menu not documented in this manual .................. 10
User passwords ........................................................................................ 11
Profiles and user rights .............................................................................. 12
The different profiles in G.O.L.D. ............................................................. 12
Defining functional user rights ................................................................. 13
Transferring files and consulting the database ................................................. 14
Master ................................................................................................... 15
Service ............................................................................................. 15
Schedule ........................................................................................... 15
Job ................................................................................................. 16
Synonyms .......................................................................................... 16
Dynamic data ..................................................................................... 16
CHAPTER 2
MANAGING USER Parameterising user password management .................................................... 18
PASSWORDS Via table 2288 .................................................................................... 18
Via G.O.L.D. Administration .................................................................... 19
Changing your user password ...................................................................... 20
CHAPTER 3
MANAGING USERS Creating a reference profile ....................................................................... 22
AND FUNCTIONAL Defining the rights of a reference profile ....................................................... 23
PROFILES
Creating a functional profile and linking users to this profile ............................... 24
Defining functional profile rights without using reference profiles ....................... 26
Defining the authorised stock adjustment and supplier return reasons (table 506) ... 27
Allowing the Invoice Control users to update the stock following the variance identification
30
Defining the other functional authorisations/prohibitions of a profile (table 1029) .. 31
Defining merchandise structure access rights ............................................... 41
Defining the "supply" and/or "price" sectors of a profile .................................. 44
Defining access rights to reports for a profile ............................................... 45
Masking certain data during order creation .................................................. 46
Preventing the creation/modification of certain discount types ......................... 47
Preventing cost price display by context ..................................................... 48
Managing the display of certain data when displaying stock movements ............... 48
Defining the article lists authorised by profile .............................................. 49
Defining which steps of the article pre-referencing workflow a profile is authorised to enter
50
Defining authorised competitors during price statement management ................. 51
Defining the sales prices authorised by profile .............................................. 52
Preventing the modification of orders depending on their origin ........................ 53
Defining functional profile rights by reference profile composition ....................... 54
CHAPTER 4
TRANSFERRING FILES Sending a file to GAIA ................................................................................ 56
TO GAIA AND Receiving files transferred by GAIA ............................................................... 57
CONSULTING THE
Consulting the database ............................................................................. 58
DATABASE
CHAPTER 5
MANAGING THE Creating a service .................................................................................... 64
MASTER Creating a job ......................................................................................... 65
Scheduling the launch of a service ............................................................... 67
Defining a synonym .................................................................................. 68
Consulting the last execution date of a service ("Dynamic data") .......................... 69
CHAPTER 1
GENERAL PRESENTATION
To be found in this section:

"Introduction", page 10,
"User passwords", page 11,
"Profiles and user rights", page 12,
"Transferring files and consulting the database", page 14,
"Master", page 15.
ADMINISTRATION MANUAL CHAPTER 1 - GENERAL PRESENTATION
INTRODUCTION
INTRODUCTION
Aim of this manual
This manual mainly describes the creation and parameterisation of functional profiles of
G.O.L.D. Central, the management of user passwords, the management of the Master and the
consultation of the database.
Who is this manual destined for?
This manual is destined for:

the administrator
super-users
Entries of the "Administration" menu not documented in

this manual
Some entries in the "Administration" menu are not documented in this manual. The following
table indicates the entries concerned and the manuals in which they are documented:
Entries Manual to consult
User - third party link management "Import order follow-up", ref. GB-CEN-UTI-CDEIMP-322
Profile management --> [Import ord. actions]
button
Local profiles by site/network "Franchise Management", ref. GB-CEN-UTI-FRAN-136
Local user management "Franchise Management", ref. GB-CEN-UTI-FRAN-136
Instance address management "Management of G.O.L.D. Central in distributed environment",

ref. GB-CEN-EXP-MBASES-147
Events alert management "G.O.L.D. Events", ref. GB-EVT-UTI-EVENTS-049
Aldata Solution Confidential document 10

USER PASSWORDS
USER PASSWORDS
Any user referenced in G.O.L.D. Administration can connect to G.O.L.D. Central using a default
password (supplied by the administrator). The procedure "Changing your user password",
page 20 must be carried out by the user himself if he has the access rights or by the adminis-
trator; it can be used to customise or modify the password. Depending on the parameterisation,
it is possible to define a minimum number of characters for the password input and/or make
the user respect a certain type of format. When accessing G.O.L.D., parameterisations allow
you to:
force the change of the initial password at the first connection and prevent the user from
keeping his password by default
force the regular modification of the password
block a users connection after a period of inactivity
block a users connection after 3 unsuccessful attempts
manage a validity end date for the password
display the last connection date of a user
etc.

PROFILES AND USER RIGHTS
Reminder: user identification

All users of G.O.L.D. Central must be referenced in the G.O.L.D. Administration application.
Once this referencing has been done, any user can be personally identified by his user name
and password on his connection to G.O.L.D. Central.
The different profiles in G.O.L.D.
There are two types of profiles: "menu" profiles (also called "business" profiles) and "functional"
profiles (also called "user" profiles). Each profile type has a specific function in G.O.L.D. Central
user management.
"Menu" profiles A user is always linked to a menu profile. This operation is carried out in the G.O.L.D. Admin-
istration application. Menu profiles are used, in particular, to restrict the access of "member
users" to certain menus and screens.
"Functional"
profiles
Functional A user is always linked to a functional profile. This operation is carried out in the Administra-
profiles tion menu of G.O.L.D. Central. The use of functional profiles allows the overall management
of user rights. The following elements are defined in G.O.L.D. in the functional profiles, and
not at the user level:
merchandise structures and merchandise structure levels which can be selected in the
screens
authorisations linked to receptions (modification of quantities and/or article prices dur-
ing a VRN modification, display or modification of prices when entering a reception without
order)
authorisations linked to orders (display or modification of purchase prices of articles on
order, possibility to hide certain data in the order creation screen)
authorisations linked to price lists (modification of VAT on sales price of articles at a shop)
etc.
Reference The functional profiles can be defined on a large scale using reference profiles. A reference
profile profile is always defined in relation to only one component (authorisation for structures OR for
discounts OR etc.). Once the reference profiles have been defined, you can define new user
profiles by combining the reference profiles.

Defining functional user rights
There are two ways of defining user rights through their functional profiles. You can choose to
use the reference profiles or not.
If you choose proceed as follows:
to use reference 1. Create reference profiles (one profile per area => its type)
profiles, See "Creating a reference profile", page 22.
2. Define the rights of every reference profile based on its type.
See "Defining the rights of a reference profile", page 23.
3. Create a functional profile and link users to this profile.
See "Creating a functional profile and linking users to this profile", page 24.
4. Link one or more reference profiles to this functional profile. The rights of the mem-
ber users of the functional profile correspond to the rights defined in these reference
profiles.
See "Defining functional profile rights by reference profile composition", page 54.
5. Define the other functional profiles (steps 3 and 4) in the same way. You can reuse
the reference profiles as many times as you wish.
to avoid using reference 1. Create a functional profile and link users to this profile.
profiles, See "Creating a functional profile and linking users to this profile", page 24
2. Define the rights of this functional profile.
See "Defining functional profile rights without using reference profiles", page 26.
3. Repeat these steps to define the other functional profiles. Even if some rights (for
example, access rights to merchandise structures) are identical for some profiles, you
must redefine these rights for every functional profile.

TRANSFERRING FILES AND CONSULTING THE DATABASE
TRANSFERRING FILES AND CONSULTING THE DATABASE
Some G.O.L.D. screens allow you to send files to the GAIA server and receive a file from the
GAIA server. A screen also allows you to consult the database using SQL queries. Predefined SQL
queries can be used (and modified) or new queries can be created (e.g.: you can use the Sales
total query to consult the number of articles sold and the turnover of every article on the
desired site).

MASTER
MASTER
The main function of the Master is to automatically trigger the processes of G.O.L.D. Pro-
grammes managed by the Master require the definition of:
a service
one or more jobs
IMPORTANT
Programmes managed by the Master can only be launched if the programme PSTPX31P s running
as a background job on the server.
Service
A service is characterised by its name, its description and its trigger mode (table 403):
If the mode is... then the programme is triggered...
Real-time every minute, as a background job.
Interval at regular parameterisable intervals expressed in minutes.
Planned according to a parameterised schedule (see "Schedule", page 15).
Manual on request (only one execution is triggered manually).
Batch in the context of a batch.
Schedule
When the trigger mode of a service is "planned" (and only in this case), a schedule must be
carried out:
in days of the week
e.g.: on Mondays at 10 p.m., on Tuesdays at 11 p.m etc.
and / or
by date: date + hh:mm:ss
e.g.: on 22/08/2005 at 10:15:00 p.m.
Several launches per day are possible without restriction.
Note: for services launched at short intervals (a few minutes), relaunching the process at every
execution can be expensive in terms of machine resources. The launch of the process requires
the allocation of memory, an ORACLE connection, disconnection etc. This operation can take
several seconds. To relieve the machine, the programme can be launched once for all, as a
background job. During periods of inactivity, the process is dormant and does not consume sys-
tem resources.

MASTER
Job
A service should be divided into one or more jobs which will be launched one after the other.
A job describes the launching parameters of a programme or a PL-SQL procedure (table 404).
Synonyms
Synonyms allow a correspondence to be established between a general name in G.O.L.D. Cen-

tral and an object in another database, for example G.O.L.D. Stock.
Dynamic data
The master screen which allows the date of the last execution of a service to be consulted is
called "Dynamic Data".

CHAPTER 2
MANAGING USER PASSWORDS

"Parameterising user password management", page 18,
"Changing your user password", page 20.
ADMINISTRATION MANUAL CHAPTER 2 - MANAGING USER PASSWORDS
PARAMETERISING USER PASSWORD MANAGEMENT
Via table 2288
Table 2288 allows you to activate or deactivate the functionalities linked to password manage-
ment. All these parameters should be defined before creating the users or when installing the
patch, and should not be modified later.
Entry Explanation
Entry 1 This entry allows you to parameterise the minimum number of characters required when entering
the password:
if the numeric value 1 is set at 1, the user will not have to enter a minimum number of charac-
ters when defining his password
if the numeric value 1 is set at 2, the user will have to enter a minimum number of characters
when defining his password. In this case, the minimum number of characters must be defined in
the numeric value 2.
By default, the numeric value 1 is set at 1.
Entry 2 This entry allows you to parameterise the password type:

if the numeric value 1 is set at 1, the user will not have to enter a specific type of password
if the numeric value 1 is set at 2, the user will have to enter a type of password. In this case,
the numeric value 2 must be used to enter the type of password used (numeric=1, alphabeti-
cal=2, complex=3).
Entry 3 This entry allows you to determine if the user will have to modify his password when connecting for
the first time:
if the numeric value 1 is set at 1, the user will not have to modify his password when connecting
for the first time
If the numeric value is set at 2, the user will have to modify his password when connecting for
the 1st time => After the connection, a warning message is displayed and the user is directed to
the Password modification screen.
Entry 4 This entry allows you to define the frequency of password modification:
if the numeric value 1 is set at 1, the user will not have to modify his password regularly
if the numeric value 1 is set at 2, the user will have to modify his password regularly. In this
case, the input of the frequency of modification (every X days) must be defined in the numeric
value 2. => When the due date of the users password is reached, after connecting, a warning
message is displayed and the user is directed to the Password modification screen.

Entry Explanation
Entry 5 This entry allows you to determine if the user must be blocked after a period of inactivity:
if the numeric value 1 is set at 1, the user will not be blocked after a period of inactivity
if the numeric value 1 is set at 2, the user will be blocked after a period of inactivity. In this
case, the numeric value 2 must be used to enter the inactivity time for the blocking (number of
days of inactivity). => When trying to connect, a warning message is displayed for the user who
is not authorised to connect anymore. He will have to ask the administrator for a new connection
to G.O.L.D.
Entry 6 This entry allows you to define if the user must be blocked after entering 3 incorrect passwords.
if the numeric value 1 is set at 1, the user will not be blocked after 3 unsuccessful attempts. He
can therefore try to reconnect.
if the numeric value 1 is set at 2, the user will be blocked after 3 unsuccessful attempts and a
message will be displayed. He will have to ask the administrator for a new connection to
G.O.L.D.
Via G.O.L.D. Administration
The User Management screen of G.O.L.D. Administration allows you to carry out the following
operations:
define a validity end date for the user password. When the validity end date is earlier
than or equal to the connection date, the user will not be allowed to connect to G.O.L.D.
A message will then warn the user
display the last connection date of a user
reactivate a user profile after a period of inactivity or after entering 3 incorrect passwords
For more information, see the "G.O.L.D. Administration" manual, ref. GB-ALL-UTI-GOADM-016.

CHANGING YOUR USER PASSWORD
CHANGING YOUR USER PASSWORD
1. Go to the Password modification screen

(access path in the standard version of G.O.L.D. Central Version 5:
Administration > Password modification).
2. Enter your current password in the Password field.
3. Enter your new password in the corresponding field then confirm your input in the following
field.
4. Click on the [Validate] button on the toolbar to save the modification.

CHAPTER 3
MANAGING USERS AND FUNCTIONAL
PROFILES

"Creating a reference profile", page 22,
"Defining the rights of a reference profile", page 23,
"Creating a functional profile and linking users to this profile", page 24,
"Defining functional profile rights without using reference profiles", page 26,
"Defining functional profile rights by reference profile composition", page 54.
ADMINISTRATION MANUAL CHAPTER 3 - MANAGING USERS AND FUNCTIONAL PROFILES
CREATING A REFERENCE PROFILE
CREATING A REFERENCE PROFILE
1. Go to the Profile management screen

Administration > Profile management).
2. Click on the [Add] button on the toolbar to create a new profile.
-> The Profile update screen is displayed.
3. Define the fields in the header panel:
Field Explanation Type Help
Code Mandatory Enter a code to identify the profile. Alphanumeric -
Explanation Mandatory Enter the profile description. Alphanumeric -
Reference Opt. Check the box to indicate a reference profile. Checkbox -

profile
Profile type Opt. Indicate the profile reference type. Numeric List of values
Note: the various types of reference profiles
are stored in the entries of general parameter
table 1416.
4. Click on the [Validate] button on the toolbar.

DEFINING THE RIGHTS OF A REFERENCE PROFILE
DEFINING THE RIGHTS OF A REFERENCE PROFILE
The rights can be defined for a reference profile depending on its type. For example, when the
type of the reference profile is "Merchandise structure", you can only define access rights to
merchandise structures.
Note: the various types of reference profiles are stored in the entries of general parameter
table 1416.
The procedure used to define the rights of a reference profile is identical to that used to define
the rights of a functional profile. It involves going to the Profile management screen, searching
for then selecting the reference profile, and clicking on the appropriate button at the bottom
of the screen to define rights in the new input screen which is displayed. For further informa-
tion, refer to "Defining functional profile rights without using reference profiles", page 26.
Note: it is possible to modify the reference profiles and to apply these modifications to the
related profiles. It is also possible to modify one or more reference profiles for a given profile
to update it.

CREATING A FUNCTIONAL PROFILE AND LINKING USERS TO THIS PROFILE

2. Click on the [Add] button on the toolbar to create a new profile.
-> The Profile update screen is displayed.
3. Define the fields in the header panel:
Code Mandatory Enter a code to identify the profile. Alphanumeric -
Explanation Mandatory Enter the profile description. Alphanumeric -
Reference Opt. Do not check this box because it allows you to define a Checkbox -
profile reference profile, and not a functional profile.
Profile type - Do not take this field into account since it concerns ref- - -
erence profiles, and not functional profiles.
Super user Opt. If you wish, define the user members of this profile as Checkbox -
super users.
By default, a super user has all rights: he has access to
stock adjustment and supplier return reasons in table
506, he can carry out all input types, he can enter the
purchase prices of the articles during a reception with-
out order (optional input) etc.
Any operation which aims at managing the functional
rights of a super user will thus have no impact.
Translation Opt. Indicate if you wish to authorise the user members of Checkbox -
this profile to translate the descriptions entered (sup-
plier, article descriptions etc.)
Example: in this example, the user is authorised to
translate the description of table 901:

4. On the right part of the screen, select an available user to be linked to this profile, then
click on the [Add] button at the bottom right of the screen. A user can only be linked to
one profile.
-> The user is added to the list of members of the profile.
A. Select the user you wish to save as profile member.

B. Then click on the [Add] button.
C. The user is added to the list of members of the profile.
5. Repeat step 4 to add as many user members as necessary.

In case of error, you can delete a user from the list of members of the profile. To do so, select
the user in the list, then click on the [Delete] button at the bottom left of the screen.
6. Click on the [Validate] button on the toolbar to save the profile and its members.
7. By default, a new profile which is not super user has no "functional" right. You can now
define the rights of this profile:
either in a unitary way, i.e. without using reference profiles (see "Defining functional
profile rights without using reference profiles", page 26)
or using the reference profiles created beforehand (see "Defining functional profile
rights by reference profile composition", page 54)

DEFINING FUNCTIONAL PROFILE RIGHTS WITHOUT USING REFERENCE PROFILES
Here we explain how to define the rights of a non-super user functional profile, without using
reference profiles. It can be done by:
"Defining the authorised stock adjustment and supplier return reasons (table 506)", page 27
"Allowing the Invoice Control users to update the stock following the variance identifica-
tion", page 30
"Defining the other functional authorisations/prohibitions of a profile (table 1029)",
page 31
"Defining merchandise structure access rights", page 41
"Defining the "supply" and/or "price" sectors of a profile", page 44
"Defining access rights to reports for a profile", page 45
"Masking certain data during order creation", page 46
"Preventing the creation/modification of certain discount types", page 47
"Preventing cost price display by context", page 48
"Managing the display of certain data when displaying stock movements", page 48
"Defining the article lists authorised by profile", page 49
"Defining which steps of the article pre-referencing workflow a profile is authorised to
enter", page 50
"Defining authorised competitors during price statement management", page 51
"Defining the sales prices authorised by profile", page 52
"Preventing the modification of orders depending on their origin", page 53
To define these rights, use the buttons (A below) at the bottom of the Profile management
screen, except the [Composition] button (because it is used to define reference profiles):

Defining the authorised stock adjustment and supplier

return reasons (table 506)
General During a stock adjustment or a supplier return, the user must indicate the reason for the oper-
presentation ation. From then on, when displaying stock movements, the reason for each movement can also
be identified. Functional profile management includes the parameterisation of the list of avail-
able reasons for each user member.
This parameterisation manages the input of the following screens:
Stock quantity adjustment
Stock price adjustment
Supplier return
To define the authorised stock adjustment and supplier return reasons, execute the following
steps:
Step Explanation
1 Parameterise table 506.

This parameterisation must be carried out during the installation of G.O.L.D.
It can later be modified at any time.
2 Define authorised reasons:

for stock adjustment and/or
for supplier returns
Parameterising All reasons which may be used by G.O.L.D. users during a stock adjustment in quantity or price,
table 506 or during a supplier return, are saved in table 506. To parameterise them, proceed as follows:

1. Open general parameter table 506.

Note: for further information on general parameter management, see the "Parameters" man-
ual, ref. GB-CEN-UTI-PARAM-092.
2. Depending on your requirements:

modify the default reasons (double-click on the corresponding entry to access the Entry
management screen in modification mode)
add new reasons (click on the [Add] button in the toolbar to access the Entry manage-
ment screen in creation mode)

delete the reasons (select the reason to delete and click on the [-] button in the toolbar)
VALUES TO BE ENTERED IN THE COLUMNS "VALUE 1" AND "VALUE 2" DURING THE MODIFICATION OR CREATION OF A REASON:
A. Table 506 is a table of user parameters (this is why it can be customised). Through the numeric value displayed in
column "Value 1", every entry in this table refers to the 524 system parameter table. This reference allows you to indi-
cate, depending on the reason, which process must be launched when a stock adjustment screen or a supplier
return screen is validated (modification of cost price, sales price etc.)
B.
- When the numeric value displayed in column "Value 2" is 7, the reason is available in the "Reason" list of values of the
Supplier return screen.
Stock quantity modification screen.
Stock price modification screen.
3. Click on the [Validate] button on the toolbar to save the modifications in the table.
Defining 1. Go to the Profile management screen

authorised (access path in the standard version of G.O.L.D. Central Version 5:
reasons Administration > Profile management).
2. Search for and select the profile (non super user) for which you wish to manage stock
adjustment and supplier return reasons.
Caution! By default, a super user has access to all available reasons (of table 506). Any oper-
ation which aims at defining the authorised reasons of a super user will thus have no impact.
3. Click on the [Modif. stock] button at the bottom of the screen.
-> The Stock adjustment screen is displayed.
4. Click on the [+] button at the bottom right of the screen to display a new line.

5. On this line, define the stock adjustment or supplier return reason you wish to authorise in
the list of values (table 506).
Note: table 506 must first have been customised based on your requirements. If this is not the
case, see "Parameterising table 506", page 27 to carry out this parameterisation.
6. Repeat steps 4 and 5 to define as many reasons which you wish to authorise as necessary.
Reminder: the descriptions of the reasons have no impact on the processes launched when val-
idating a stock adjustment or a supplier return. Similarly, the reasons entered are not checked
when these screens are validated. For example, a "Quantity +" reason can be entered and the
stock decreased instead of being increased.
In other words, even though the input of a reason is mandatory during the validation of adjust-
ment and return screens, the reason is given as an indication to the user who wishes to consult
stock movements, for example.
7. Click on the [Validate] button on the toolbar to save the data.
-> User members of this profile can now only enter the authorised reasons for adjustments
and returns. Thus, the list of values which can be displayed is limited to the authorised
reasons.
Allowing the Invoice Control users to update the stock

following the variance identification
This procedure allows you to authorise the users of a profile to:

access the Stock update field in the Variance detail screen (access path: Finance and
invoice control > Variance management) to update the stock when the screen is validated
access the Stock update by SIC screen (access path: Finance and invoice control > Stock
adjustment by SIC)

2. Search for and select the appropriate profile (non super user).
Caution! By default, a super user has all authorisations. Any operation which aims at defining
the authorised reasons of a super user will thus have no impact.
3. Click on the [Modif. stock] button at the bottom of the screen.
-> The Stock adjustment screen is displayed.
5. On this line, define the entry 973 ("Supp inv chk modif") of table 506 to authorise the mem-
bers of the profile to update the stock.

Defining the other functional authorisations/prohibitions

of a profile (table 1029)

2. Search for and select the profile (non super user) for which you wish to define the func-
tional authorisations.
Caution! By default, a super user has all authorisations. Any operation which aims to define
the functional authorisations of a super user will thus have no impact.
3. Click on the [Input] button at the bottom of the screen.
-> The Input authorisations screen is displayed.
4. Use the [+] button at the bottom right of the screen and define the desired authorisation(s)
using the table below:
Authorisations (table 1029) Explanation
Entry Description
1 VRN qty. mod. This authorisation gives user members of the profile the right to modify the quan-
tities of articles checked in during a VRN modification.
The use of the VRN modification (detail) screen is affected.
2 VRN prc. mod. This authorisation gives user members of the profile the right to modify the prices
of articles checked in during a VRN modification.
The use of the VRN modification (detail) screen is affected.
Note: when authorisation 2 "VRN prd. mod." is not entered, the columns linked
to the prices (purchase price, VAT rate etc.) are hidden.
3 Purchase ord. prc. Do not take this authorisation into account. It is no longer implemented in
G.O.L.D.
4 Local prc. VAT This authorisation gives user members of the profile the right to modify the VAT
on the Simplified sales price input screen.
5 Purchase prc. displ. This authorisation gives user members of the profile the right to display the pur-
chase prices of the articles.
The following are managed:
the order note generated from the Order follow-up screen
the Quantity input screen, and the order note generated from this screen
Note: the [Display quantity] button is activated.
the order note generated after the validation of the Order confirmation
screen
the stock variance report and the valued inventory report, launched from the
Reports screen
the Article adjustment screen
the Reception without order screen

Entry Description
6 Stock price display This authorisation gives user members of the profile the right to display the stock
purchase prices and cost prices of the articles during an inventory adjustment.
The use of the Article adjustment screen is affected.
8 Transfer prc. mod. This authorisation gives the profile member users the right to modify the transfer
price of an article during an inter-department transfer (=> the Trans. price field
is accessible).
The Inter-department transfer screen is affected.
10 Inv. type creation This authorisation gives user members of the profile the right to create and delete
inventory types on the Inventory type screen.
11 Spec. period auth. This authorisation gives user members of the profile the right to create and delete
specific periods on the Specific periods screen.
12 Article link auth. This authorisation gives user members of the profile the right to create and delete
links between articles. The Article link selection screen is managed in this way.
13 Sales prc. displ. This authorisation gives user members of the profile the right to display the sales
prices of articles during a reception without order.
The Reception without order screen is affected.
14 Purchase prc. mod. This authorisation completes authorisation 5 "Purchase prc. displ.". It gives user
members of the profile the right to modify the purchase prices of articles during
a reception without order, an inventory adjustment or during an order.
The following screens are managed:
Reception without order
Article adjustment
Quantity input
15 Sales prc. mod. This authorisation completes authorisation 13 "Sales prc displ.". It gives user
members of the profile the right to modify the sales prices of articles during a
reception without order.
The Reception without order screen is affected.
16 Sales op. creation This authorisation gives user members of the profile the right to create new clear-
ance sales operations for the connection site.
The Clearance sales operation article management screen is affected.
18 Inv. prc. mod. auth. If this authorisation is entered, then, during inventory adjustments, user mem-
bers of the profile are authorised to modify the stock purchase prices and cost
prices of inventoried articles.
This authorisation thus affects the Article adjustment screen.
20 Urgent ord. auth. This authorisation allows the input of urgent orders. The "Urgent order" checkbox
can thus be entered on the following screens:
Order creation
Enter the quantities

Entry Description
21 Normal simu. auth. This authorisation gives user members of the profile the right to carry out a nor-
mal simulation (Assisted sales module).
The Simulation management screen is affected.
22 Delayed sim. auth. This authorisation gives user members of the profile the right to carry out a
delayed simulation (Assisted sales module).
The Simulation management screen is affected.
26 SP 0 FAV art. This authorisation gives user members of the profile the right to enter a sales
price of zero for "Fruit & Vegetables" articles.
The Simplified sales price input screen is affected.
27 Suppl. rtn. report This authorisation gives user members of the profile the right to print return notes
(=> the [Print return note] button is thus activated).
The Supplier return screen is affected.
28 Ship suppl rtn. This authorisation gives user members of the profile the right to launch the
processing of supplier returns (=> the [Ship] button is thus activated).
The Supplier return screen is affected.
29 Suppl. rtn cur. rate This authorisation gives profile member users the right to modify the exchange
rate (Exchange rate field) when they carry out a supplier return (Supplier return
screen).
30 Suppl Transfer prices This authorisation gives user members of the profile the right to display and mod-
ify the transfer price (Price field) during a stock transfer. It also allows users to
modify the actual return price (Return price field) when a supplier return is car-
ried out.
The following screens are affected: Stock transfer request modification, Simple
transfer, Transfer without request, and Supplier return.
31 Valid. w/acc. note This authorisation gives the user members of the profile the right to validate a
multimedia return (=> the [Validate] button at the bottom of the screen is acces-
sible).
The Simple transfer screen is affected.
32 Ship w/acc. note This authorisation gives user members of the profile the right to ship merchandise
during a multimedia return (=> the [Ship] button at the bottom of the screen is
accessible).
The Simple transfer screen is affected.
33 Validate suppl. rtn. This authorisation allows the user members of the profile to activate the [Vali-
date] button at the bottom of the Supplier return screen.
34 Ord. max. mod. This authorisation gives user members of the profile the right to modify the order
maximum defined for an orderable assortment, even if this assortment is valid.
The Orderable assortment management screen is affected.
35 SDC mngt restriction If this parameter is defined for a profile, the user members of the profile cannot
create SDCs. They can only modify the target margin of an existing SDC.
The SDC management screen is affected.

Entry Description
36 Local purchase prc. This authorisation gives the user members of the profile the right to modify the
purchase price of an article for a local supplier.
The Purchase price list screen is affected.
Reminder: a supplier is described as "local" when his commercial contract is local
(Local contract box checked).
37 Ord ship auth exceed Caution: this functional profile parameterisation is only taken into account by
G.O.L.D. if the numeric value 2 of entry 16 of general parameter table 1095 is set
at 3.
In this case, when parameter 1029/37 is defined for a profile, the user members
are allowed to send non-urgent orders after the collection date and time. A
warning message is displayed, but the order can be sent.
This parameterisation affects the following screens: Order creation, Order
duplication and Order follow-up (these screens can be accessed from the menu:
Supply > Supplier orders).
Note: parameter 1095/14 allows you to define the checks to be carried out on
non-urgent orders when the collection date (date and time) has passed.
38 Urgent ord ship auth This authorisation gives the right to user members of the profile to send urgent
orders.
This authorisation affects the Order creation screen and the Order follow-up
screen.
39 Print break. stat. This authorisation gives the right to user members of the profile to print the
breakage statements.
The Breakage statement screen is affected (access: Stock management > Move-
ments and adjustments).
40 Validate spoil. stat This authorisation gives the right to user members of the profile to validate the
41 Close spoil. stat. This authorisation gives the right to user members of the profile to close the
42 Local article input This authorisation gives user members of the profile the right to manage local
articles on the Local article detail screen (access: Articles > Local articles
(shops)).
Moreover, the numeric value 1 allows you to define which sites are allowed to
modify local articles (either the site which created the article or all the sites
which have referenced the article locally).
For further information, see the "Franchise Management" manual, ref. GB-CEN-
UTI-FRAN-136.

Entry Description
43 Local suppl. input This authorisation gives the right to user members of the profile to manage local
suppliers and local supplier contracts.
Moreover, the parameterisation of the numeric value 1 allows you to define which
sites are authorised to modify the local supplier data as well as the related con-
tracts (either only the creation site or all the sites which have referenced the data
locally).
For further information, see the "Franchise Management" manual, ref. GB-CEN-
UTI-FRAN-136.
44 Save truck This authorisation gives the right to user members of the profile to save a new
truck in the truck queue of the Truck queue management screen (access: Recep-
tions > Truck queue management).
45 Exclude truck This authorisation gives the right to user members of the profile to exclude a
truck from the truck queue in the Truck queue management screen (access:
Receptions > Truck queue management).
46 Free truck This authorisation gives the right to user members of the profile to free a truck
from the queue during cross-docking in the Truck queue management screen
(access: Receptions > Truck queue management).
47 Ext. suppl. forbid. When this parameter is defined for a profile, the user members of the profile are
not authorised to modify external supplier schedules.
The Supplier delivery schedule screen is affected (access: Third party > Suppli-
ers > Supplier schedule management).
48 Transit suppl forbid When this parameter is defined for a profile, the user members of the profile are
not authorised to modify transit supplier schedules.
49 PO suppl. forbid. When this parameter is defined for a profile, the user members of the profile are
not authorised to modify Purchasing Office supplier schedules.
50 Purch. VAT code mod. When this parameter is defined for a profile, the user members of the profile are
authorised to modify the article purchase VAT codes.
The following screens are managed: Purchase price list, Variant article pur-
chase price input, Supplier order creation, Reception without order, Transfer
creation, Article general data ("Other" tab), Article default data management
("Other" tab), the article interfaces (article and root article general data) and
their rejection screens, the article default data interfaces (article and root arti-
cle general data) and their rejection screens.
51 Sales VAT code modif When this parameter is defined for a profile, the user members of the profile are
authorised to modify the article sales VAT code.
The following screens are managed: Sales price management, Sales price sim-
plified input, Variant article sales price input, Article general data ("Other"
tab), Article default data management ("Other" tab), the article interfaces (arti-
cle and root article general data) and their rejection screens, the article default
data interfaces (article and root article general data) and their rejection screens.

Entry Description
52 Return prc. mod. When this parameter is defined for a profile, the user members of the profile are
authorised to modify the article return price on the Supplier return screen
(access: Supplier returns > Return management).
53 Th cash disc forbid When this parameter is defined for a profile, the user members of the profile are
not authorised to modify the supplier theoretical cash discount displayed in the
header panel of the Invoice reconciliation, "Invoice" tab (access : Finance and
invoice control > Invoice reconciliation).
54 SN cancellation When this parameter is defined for a profile, the user members of the profile (for
the sites they can access) are authorised to consult and cancel sales notes of a
site different from the one where the sale occurred.
The Sales note selection for customer return screen is affected (access: Assisted
sales > Customer return > Sales note selection).
55 Fault list display This authorisation gives user members of the profile the right to display a stock
fault list on:
the Validations and adjustments according to schedule screen (access:
Mobility > Stock check according to schedule)
the Schedule selection screen of G.O.L.D. Mobile (access: Stock manage-
ment > Article schedule)
56 Ord backdat forbid when this parameter is defined for a NON super user profile, it prevents
member users from antedating orders. This parameterisation affects the fol-
lowing screens: Order creation, Order duplication and Order follow-up
(these screens can be accessed from the menu: Supply > Supplier orders).
when this parameter is NOT defined for a NON super user profile, G.O.L.D.
allows antedating depending on general parameter 911/1 (numeric value 1)
Reminder: the members of a super user profile can always antedate orders,
whether parameter 1029/65 is set or not.
57 Order creation auth. Caution: this parameterisation of the functional profile is only taken into account
by G.O.L.D. if the numeric value 2 of entry 1 of general parameter table 1095 is
set at 2. The numeric value 1 indicates the order maximum status which is taken
into account by the control.
of the profile are allowed to create an order (concerning the order status, see
the numeric value 1 of entry 1095/1) even if an order already exists for the
same supplier/address chain/commercial contract, the same site, and the same
sending date/time (the sending date/time is checked only if the numeric value 3
of parameter 1095/1 is set at 1).

Entry Description
58 S/C date val auth. Caution: this functional profile parameterisation is only taken into account by
at 3.
of a profile are allowed to value an order after its sending and collection date.
59 Ord mod for ext supp Caution: this functional profile parameterisation is only taken into account by
at 2.
In this case, when this parameter is defined for a profile, the user members of the
profile are allowed to modify an order whose status is 5 for an external sup-
plier.
60 Ord mod for tr supp Caution: this functional profile parameterisation is only taken into account by
at 2.
profile are allowed to modify an order whose status is 5 for a transit supplier.
61 Ord mod for PO supp Caution: this functional profile parameterisation is only taken into account by
at 2.
profile are allowed to modify an order whose status is 5 for a Purchasing Office
supplier.

Entry Description
62 Financial rtn. auth. When this parameter is defined for a profile, the user members of the profile are
allowed to enter a return or a transfer whose type is "financial".
The following screens are managed:
Supplier return (access: Supplier returns > Return management)
Return campaign management (access: Supplier returns > Return campaign
management)
Shop return mass input (access: Supplier returns > Return mass input)
Simple transfer (access: Transfers > Simple transfer creation)
Transfer without request (access: Transfers > Transfer without request)
Stock transfer request modification (access: Transfers > Transfer request
creation)
Return campaign interfaces, supplier return interfaces and simple transfer inter-
faces are also affected.
63 RLT display When this parameter is defined for a profile, the user members of the profile are
allowed to display the resale at loss thresholds on:
the RLT display screen (access: Price > Sales prices > RLT display)
the RLT display screen (access: Price > Sales prices > RLT and AP display)
the delivery note report
64 AP1 display When this parameter is defined for a profile, the user members of the profile are
authorised to display the first availability price.
This parameterisation affects:
the Stock detailed display screen, "Miscellaneous" tab, AP1 back margin
total field (access: Stock management > Stock follow-up > Stock display)
the RLT display screen, AP1 field (access: Price > Sales prices > RLT display)
the RLT and AP display screen, AP1 field (access: Price > Sales prices > RLT
and AP display)
authorised to display the second availability price on:
and AP display)

Entry Description
authorised to display the third availability price on:
and AP display)
67 Suppl rtn prc mod When this parameter is defined for a profile, the user members of the profile are
authorised to modify the article return price in the context of a return to an
external supplier, on the Supplier return screen (access: Supplier returns >
Return management)
68 Ord charge set modif When this parameter is defined for a profile, the user members of the profile are
authorised to modify the set of charges on the Quantity input screen, "Import"
tab, Set of charges field (access: Supply > Supplier orders > Order creation).
69 Clear shp-po forbid When this parameter is defined for a profile, the user members of the profile are
not authorised to clear a shop order to a Purchasing Office supplier on the
Order follow-up screen (access: Supply > Supplier orders > Order follow-up).
The [Clear] button at the bottom of this screen can be accessed. When the user
clicks on this button, G.O.L.D. displays a warning message indicating that the
order clearance is not allowed by the functional profile.
70 Clear shp-exts forb When this parameter is defined for a profile, the user members of the profile are
not authorised to clear a shop order to an external supplier on the Order follow-
up screen (access: Supply > Supplier orders > Order follow-up).
71 Clear warh-ts forbid When this parameter is defined for a profile, the user members of the profile are
not authorised to clear a warehouse order to a transit supplier on the Order fol-
low-up screen (access: Supply > Supplier orders > Order follow-up).
72 Clear warh-exts forb When this parameter is defined for a profile, the user members of the profile are
not authorised to clear a warehouse order to an external supplier on the Order
follow-up screen (access: Supply > Supplier orders > Order follow-up).
73 Rec. clerk auth. When this parameter is defined for a profile, the user members of the profile are
authorised to modify the receiving clerk on the Quantity input screen, "Recep-
tion" tab, Receiving clerk field (access: Receptions > Checked-in qty input).

Entry Description
74 Rtn. camp. mand. When this parameter is defined for a profile, the user members of the profile must
select a return campaign code to continue the data creation on:
the Supplier return screen (access: Supplier returns > Return management)
the Shop return mass input screen (access: Supplier returns > Return mass
input)
the Simple transfer screen (access: Transfers > Simple transfer creation)
75 Rec. 2 steps check Do not take this authorisation into account. It is no longer implemented in
G.O.L.D.
76 Clear cust ord forb. When this parameter is defined for a profile, the user members of the profile are
not authorised to clear a customer order on:
the Customer order display screen (access: Flow management > Customer
orders > Customer order display)
The [Clear] button at the bottom of this screen is not displayed.
the Customer order detail display screen (access: Flow management > Cus-
tomer orders > Customer order display, then customer order selection)
The Clear and Reason fields at the bottom of this screen are not displayed.
the Customer order management screen (access: Flow management > Cus-
tomer orders > Customer order management)
The [Clear] button at the bottom of this screen is not activated and, conse-
quently, does not authorise the total clearance of the customer order.
77 PIM access restr When this parameter is defined for a profile, the user members of the profile can
only display and access the files that they created themselves in G.O.L.D. PIM.
78 P.I.M. file deletion When this parameter is defined for a profile, the user members of the profile are
authorised to modify files in G.O.L.D. PIM.
79 Order release This authorisation gives the right to user members of the profile to release an
order for a customer site, on which an order blockage period is defined and is
active in the Customer Data Sheet.
User members of the profile can for example value and send the order.
Note: even if this parameter is defined on a user profile, an order blocked for
another reason (for example a free freight threshold or an order minimum which
is not reached) cannot be released.
80 Smo during smoothing When this parameter is defined for a profile, the user members of the profile are
autorised to smooth the warehouse load only during the special operation smooth-
ing period. This period is defined in the Promotions (SO) screens.
Note: when parameter 81 is also defined on the profile, user members of the pro-
file can carry out smoothing at any time.
81 Smo out smo period When this parameter is defined for a profile, the user members of the profile are
autorised to smooth the warehouse load only outside the special operation
smoothing period. This period is defined in the Promotions (SO) screens.
Note: when parameter 80 is also defined on the profile, user members of the pro-
file can carry out smoothing at any time.

Entry Description
82 Reach modification When this parameter is defined for a profile, the users members of the profile are
authorised to manage (i.e. create, modify and delete) chemical substances and
components and to manage the chemical composition of articles on the "Reach"
sub-tab of the Article general data screen.
94 Cust ord modif forb When this parameter is defined for a profile, the user members of the profile are
not authorised to modify a customer order on the Customer order management
screen (access: Flow management > Customer orders > Customer order manage-
ment).
The customer order detail screen then opens in display mode.
95 Suppl ord modif forb When this parameter is defined for a profile, the user members of the profile are
not authorised to modify a supplier order after sending on the Order follow-up
screen (access: Supply > Supplier orders > Order follow-up).
The quantity input screen then opens in display mode.
Defining merchandise structure access rights
Scope G.O.L.D. can filter records which appear on the screens according to the functional profile of
the user. If you wish to filter the records, you must define the "merchandise structure access
rights", i.e. indicate the merchandise structure nodes which must be "accessible" by all users
of a profile. The records linked to structure nodes which were not defined as "accessible" will
systematically be masked.
Note: this parameterisation only concerns NON super users, since the users linked to a super
user profile have, by default, all authorisations and can display all data on the screens.

If a node (N) of a merchandise structure (S) is "accessible":

in the screens (selection and input), users can only display and select records linked to N
and its child nodes
EXAMPLE
Here, an access right was defined on the Hygiene structure node. On the Article display
screen, the user can only display the articles which are part of this structure node and its
child nodes:
users can display in the Merchandise structure window ALL S levels but they cannot display
the other merchandise structures. They can only select N, AS WELL AS ITS CHILD NODES.
If users try to select structure nodes or articles to which they do not have access rights, a
warning appears when they click on the [Select] button.
Reminder: the Merchandise structure window is accessible via a right-click in the Level or
Structure ID fields
Users can only launch processes on N, as well as its child nodes.

Exceptions A user can carry out movement and flow transactions on all articles of the database, what-
ever the access rights defined in his functional profile. In other words, no access rights
check is made on receptions, receptions without order, reception follow-ups, returns, VRN
modifications.
A user can launch an inventory on all articles of the database, whatever the access rights
defined in his functional profile.
Procedure 1. Go to the Profile management screen

the authorisations of a super user will thus have no impact.
3. Click on the [Merchandise str.] button at the bottom of the screen.
-> The Merchandise structure screen is displayed.
5. In the contextual menu of the Merchandise structure field, choose Selection:
-> The small Merchandise structure window is displayed.

6. In the Merchandise structure window, proceed as follows:
a. Double-click on the Merchandise structure field to select the desired merchandise

structure.
b. Expand the tree-structure of this merchandise structure, then select the structure level
you wish to make accessible to member users of the profile.
c. Click on [Select].
7. Repeat steps 4 to 6 to define as many access rights as you wish.
8. Click on the [Validate] button on the toolbar:

Defining the "supply" and/or "price" sectors of a profile
General A sector is a group of suppliers.

presentation "price" sectors are used while defining a user profile. They make it possible to restrict
access (display/creation/modification) to discounts and costs to a specific group of suppli-
ers
"supply" sectors are used while defining a user profile. They make it possible to restrict
access (display/creation/modification) to orders and receptions to a specific group of sup-
pliers
Important: access rights to sectors are only checked if entry 5 of table 1095 is set at 1.


3. Click on the [Supply sector] button at the bottom of the screen.
-> The Supply sector link management screen is displayed.
5. On this line, double-click on the Supply sector field to display a list of values, then select
the "supply" or "price" sector of the profile.
6. Repeat steps 4 and 5 to authorise access to other sectors.
Defining access rights to reports for a profile
General G.O.L.D. Central allows you to define, by profile, the reports which can be launched from the
presentation Report launch screen (access path in the standard version of G.O.L.D. Central Version 5:
Reports > Report launch).
Note: other screens of G.O.L.D. (the supplier order Quantity input screen, for example) allow
you to launch reports. But no check is made regarding the report rights for these screens. Access
rights to reports by profile are only checked on one screen: Report launch.

3. Click on the [Reports] button at the bottom of the screen.
-> The Reports screen is displayed.
5. Double-click on the Module field to display a list of values, then select the report you wish
to make accessible to the profile members.
6. Repeat steps 4 and 5 to authorise access to other reports.

Masking certain data during order creation
General By default, much information is displayed on the Quantity input order screen: purchase price,
presentation merchandise structure, allocation, purchase variant, purchase unit, logistic variant, sales price,
etc. This information is displayed whatever the profile of the connected user (super user or
not).
The aim of the following procedure is to mask certain information on this screen. The parame-
terisation is carried out based on the supplier type and the opening context of the screen.
Types of There are three types of suppliers:

suppliers
External
Transit
Purchasing Office
For further information, see the "Suppliers" manual, ref. GB-CEN-UTI- FOURN-010.
Opening There are 3 opening contexts:

contexts
the DEFAULT context: it includes "normal" supplier orders and supply orders
the DAILY PRICED (DP) context: it concerns daily-priced orders
the DISTRIB context: it concerns orders with a distribution list
Order Data which can be masked according to the parameterisation is, for example, Purchase price,
data Merchandise structure, Allocation, Purchase variant, Purchase unit, Logistic variant, Sales
price, Cost price, Net invoiced price, Comment, Commercial reason, Current purchase promo-
tion and Future purchase promotion, etc.

2. Search for and select the appropriate profile.
Note: information can be masked whatever the profile selected (super user or not).
3. Click on the [Order param] button at the bottom of the screen.
-> The Order screen parameterisation screen is displayed.
5. Define the data:
Context Mandatory Define the opening context (table 1336). Numeric List of values
Supplier Mandatory Define the supplier type (table 530). Numeric List of values
type

Order data Mandatory Define the data you wish to mask (table 1337). Numeric List of values
Note: The parameterisation of the purchase prices
also takes parameters 5 and 14 of table 1024 into
account (see "Defining the other functional authori-
sations/prohibitions of a profile (table 1029)",
page 31)
Visible Opt. Do not check this box in order to MASK the selected Checkbox -
data.
6. Repeat to define as many lines as necessary.

Preventing the creation/modification of certain discount

types
General By default, a user can create and modify any discount type on the following screens:
presentation Discount and cost input
Interactive calculator (accessible via the supplier order screen or the cost price display
screen)
However, the user members of the profile can be prevented from creating and modifying certain
discount types.
Note: this operation will have no impact if the selected profile is a super user.

3. Click on the [Discount type] button at the bottom of the screen.
-> The Discount right management screen is displayed.
5. Define the discount type whose creation/modification you wish to prevent (list of values).
Thus, the user linked to the profile can only display this discount type, unless the numeric
value 1 of parameter 2353/2 is 0 or null since, in this case, the discount is masked.
Caution!
if you define a discount type and you check the "Free art. auth." column, the user linked
to the profile can only create discounts of this type with a value of 100%
if you define a discount type and you do not check the "Free art. auth." column, this type
of discount is not allowed for the profile
6. Repeat to define as many lines as necessary.

Preventing cost price display by context
General By default, any user can display the article cost prices in all contexts: purchase price, cost
presentation price, sales price and margin. Those contexts refer to the different ways to calculate article
cost price.
Functional profile management allows you to mask the desired context(s) in the following
screens:
Cost price detail, accessible via the cost price display screen. If a context is masked, the
corresponding tab is not displayed anymore at the bottom of the screen.
Interactive calculator (accessible via the supplier order screen or the cost price display
screen). If a context is masked, it is not displayed anymore in the "Context" list of values.

3. Click on the [Display] button at the bottom of the screen.
-> The Display restriction management screen is displayed.
5. Define the context whose display you wish to prevent (list of values).
6. Repeat to mask as many contexts as necessary.
Managing the display of certain data when displaying

stock movements
General Much data may be displayed on the Stock movement display screen: Replenish. quantity., Val-
presentation uation quantity, Movement number, Purchase price value, etc. This data is stored in table 1338.
Its display on the Stock movement display screen depends on 2 parameterisations:
a general parameterisation allows you to define the data you wish to display on the screen.
It is valid for all users of G.O.L.D.
a parameterisation on functional profiles then allows you to define exceptions by mask-
ing or displaying certain fields only for user members of a profile
General 1. Go to the General parameter management screen

parameterisation (access path in the standard version of G.O.L.D. Central Version 5:
Parameters > General parameters > General parameter management).

2. Search for table 1338, then select it in the result panel and click on the [Entry] button at
the bottom of the screen.
-> The Table entry screen is displayed. Each entry corresponds to a piece of data that may
be displayed on the Stock movement display screen.
3. Double-click on a piece of data in order to manage it in the Entry management screen as
follows:
To Proceed as follows:
mask this piece of data, a. Enter 0 in the numeric value 1.

b. Click on the [Validate] button on the toolbar:
display this piece of a. Enter 1 in the numeric value 1.

data,
b. Click on the [Validate] button on the toolbar:
4. Repeat as many times as necessary to parameterise all the data of the table as you wish.
Functional profile 1. Go to the Profile management screen

parameterisation (access path in the standard version of G.O.L.D. Central Version 5:
Note: information can be masked whatever the profile selected (super user or not).
3. Click on the [Stock mvt param] button at the bottom of the screen.
-> The Stock movement management screen parameterisation screen is displayed.
5. Define the data:
Stock Mandatory Define the piece of data for which you wish to manage Numeric List of values
the display (table 1338).
Visible Mandatory check this box to make this piece of data visible Checkbox -
for members of the profile
do not check this box to mask this piece of data for
the members of the profile
6. Repeat to manage as much data as necessary.

Defining the article lists authorised by profile
General If an access authorisation by profile was defined for an article list (i.e. if, for a given article list,
presentation the Access by profile field is checked on the Article list management screen), then:

by default, all super users can access this list in the screens of G.O.L.D.
and
by default, no user who is not a super user cannot access this list. The procedure below
allows you to give him access rights.

3. Click on the [Article list] button at the bottom of the screen.
-> The Article list screen is displayed.
5. Define the article list profile which can be accessed by the profile members (available list
of values).
Note: only the lists for which access by profile is required can be selected.
6. Repeat to define as many lists as necessary.
Defining which steps of the article pre-referencing

workflow a profile is authorised to enter
This procedure, and all those linked to article pre-referencing, is described in a separate man-
ual: see the "G.O.L.D. PIM" manual, ref. GB-PIM-UTI-PREREF-200.

Defining authorised competitors during price statement

management
In G.O.L.D. Central, competitors entered to manage price statements are defined for the con-
nection site.
Competitors can also be defined at the profile level on the Profile management screen.
When a competitor is linked to a profile, the user members of this profile can:
add only this competitor to the Competition price statement creation screen (access
path: Price > Price statements > Price statement creation)
duplicate a price statement concerning only this competitor on the Competition price
statement creation (access path: Price > Price statements > Price statement creation)
display and select only this competitor on the Competition price statement creation
screen (access path: Price > Price statements > Price statement input)
select only this competitor to launch the price statement report printout linked on the
Price statement input screen (access path: Price > Price statements > Price statement
input)
Besides, a general parameter must be set to activate competitor management by profile.
General To activate competitor management by profile, the numeric value 1 of entry 13 of general
parameterisation parameter table 1064 must be equal to 1.
When this parameter is set, the [Competitor] button, at the bottom of the Profile management
screen is active if:
the selected profile is a reference profile whose type is "Competitor" OR
the selected profile is not a reference profile and is not defined by combining reference
profiles (for further information, see "Defining functional profile rights by reference profile
composition", page 54)
Note: by default, all SUPER-USERS have access to these competitors on G.O.L.D. screens de-
pending on the connection site.

3. Click on the [Competitor] button at the bottom of the screen.
-> The Competitor input authorisation screen is displayed.
5. In the Competitor code, define the code of the competitor the profile members must have
access to (list of values available).
Note: the values which are available is this field refer to the competitor codes which are
defined on all connection sites in the Competitor update screen (Prices > Price statements
> Competitor input).
6. Repeat to define as many competitors by profile as necessary.

Defining the sales prices authorised by profile
General By default, a user can create and modify any sales price.
presentation However, profile member users can be allowed to create and modifiy only some specific sales
prices, i.e. sales prices in the Sales prices menu (in the Price module), in the Purchase condi-
tions menu (in the Purchasing and negotiation module), in the Menus and recipes menu of
G.O.L.D. Central, and in the franchise area.
A general parameter must be set to activate this authorisation to modify and create sales prices
by profile, and to take into account the sales price lists linked to the profile.
Note: however this autorisation does not concern sales price display: users can display all the
existing sales prices.
General To activate the authorisation to create/modify sales prices by profile, the numeric value 1 of
parameterisation entry 9 of general parameter table 1267 must be equal to 1.
If this parameterisation is activated:
all the user members of the profile for which the authorisation is defined for a specific sales
price have access to this sales price in G.O.L.D. screens
and
by default, the user members of a profile for which no sales price is defined in the Profile
management screen have no access to sales prices in G.O.L.D. creation and modification
screens. The procedure below allows you to give him access rights.
Note: by default, all super users can access this sales price in G.O.L.D. screens.

3. Click on the [Sales price list] button at the bottom of the screen.
-> The Sales price list screen is displayed.
5. In the Price list code field, define the code of the sales price to which the members of the
profile must have access (list of values available).
Note: the values available in this field refer to the sales price codes defined in the Sales
price list selection screen (Prices > Sales prices > Sales price list input).
6. Repeat to define as many sales prices by profile as necessary.

Preventing the modification of orders depending on their

origin
General By default, users can modify all orders on the following screens:
presentation Order follow-up (access path: Supply > Supplier orders > Order follow-up)
Order confirmation (access path: Supply > Supplier orders > Order confirmation)
Order duplication (access path: Supply > Supplier orders > Order duplication)
Planning detail data input (access path: Supply > Supplier orders > Order line planning,
then click on the [Management by order] button)
Planning detail data input (access path: Supply > Supplier orders > Order line planning,
then click on the [Management by line] button)
Daily-priced order follow-up (access path: Supply > Daily-priced products > Daily-priced
order follow-up)
However, the user members of the profile can be prevented from modifying certain orders
depending on the order origin.
Profile To forbid order modifications depending on the order origin, the [Order origin] button at the
parameterisation bottom of the Profile management screen must be activated.
This button is active if:
the selected profile is a reference profile whose type is "Order origin" OR
the selected profile is not a reference profile and is not defined by combining reference
profiles (for further information, see "Defining functional profile rights by reference profile
composition", page 54)
Note: by default, all super users can modify all orders in G.O.L.D. screens.

3. Click on the [Order origin] button at the bottom of the screen.
-> The Order origins not authorised screen is displayed.
5. In the Origin code field, define the code of the order origin whose modification must be
forbidden (list of values available).
Note: the values which are available in this field refer to the entries of general parameter
table 2017.
6. Repeat to forbid as many order origins as necessary by profile.

DEFINING FUNCTIONAL PROFILE RIGHTS BY REFERENCE PROFILE COMPOSITION
DEFINING FUNCTIONAL PROFILE RIGHTS BY REFERENCE PROFILE COMPOSITION
Only the functional profiles which are not super users can be defined by composition. Further-
more, no right can be defined for the functional profile.

3. Click on the [Composition] button at the bottom of the screen.
-> The Composition screen is displayed.
4. Click on the [+] button at the bottom right of the screen to display a new line, then define
the desired reference profile (list of values).
5. Repeat step 4 to define as many reference profiles as necessary.
it is not possible to define reference profiles whose type is identical (e.g.: "Merchandise
structures")
it is not necessary to define a reference profile of each type. For example, if you wish,
you can define only a network-type reference profile.

CHAPTER 4
TRANSFERRING FILES TO GAIA AND
CONSULTING THE DATABASE

"Sending a file to GAIA", page 56,
"Receiving files transferred by GAIA", page 57,
"Consulting the database", page 58.
ADMINISTRATION MANUAL CHAPTER 4 - TRANSFERRING FILES TO GAIA AND CONSULTING THE DATABASE
SENDING A FILE TO GAIA
SENDING A FILE TO GAIA
This procedure allows files to be sent to the GAIA server. The files sent will be stored in the
"Received" directory on the GAIA server.
1. Go to the File transfer screen

Administration > File transfer).
-> G.O.L.D. displays all the files in the default source directory C:SendToServer.
Notes:
to search for a source directory, enter the name of the directory where the file is located
and click on the [Search] button: G.O.L.D. displays the list of files in this directory.
Example: c:emp
to change source directory:
a. Click on the [Change] button: G.O.L.D. displays the Open window.

b. Select the directory, then click on [Open]: G.O.L.D. displays the list of files in this direc-
tory.
2. Select the file to send from the list of files displayed.
3. To validate the file transfer, click on the [Validate] button on the toolbar.
-> The selected file is sent to the "Received" directory of the GAIA server.
In case of a problem: check the existence of the "Received" directory on the GAIA server.

RECEIVING FILES TRANSFERRED BY GAIA
RECEIVING FILES TRANSFERRED BY GAIA
This procedure allows you to receive a file from the GAIA server. The files which you can receive
must be in the "STORExxxx" directory of the GAIA server where xxxx represents the shop
number.
1. Go to the File reception screen

Administration > File reception).
-> G.O.L.D. displays all the files in the "STORExxxx" directory of the GAIA server where xxxx
represents the shop number.
Note: to change the directory, click on [Change]. Select the directory, then click on [Open].
2. Select the file to receive from the list of files displayed.
3. To validate the reception of the file, click on the [Validate] button on the toolbar.
-> The selected file is transferred by the GAIA server. It is saved in the directory of the
specified destination.
In case of a problem: check the existence of the "STORExxxx" directory on the GAIA server.

This procedure allows the consultation of the database using SQL data. By default, G.O.L.D.
proposes a certain number of queries. You can use (and modify) the predefined SQL queries or
create your own queries.
Using a 1. Go to the Database consultation screen

predefined query (access path in the standard version of G.O.L.D. Central Version 5:
Administration > Query management).
2. Select the query to execute.
3. If the right part of the screen is not empty, enter the parameter values in the Value field.
-> G.O.L.D. displays the result of the query in a new screen.
Creating a new Important

query
The SQL queries are defined in .xml files which are in the eGoldweberetail directory:
the list_default.xml file contains the titles of the queries and the names of the related files
(in which the queries are defined)

the other .xml files contain queries:

1. Open the list_default.xml file in a text editor.

Reminder: the file is located in the eGoldweberetail directory:
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>

<ROOT>
<REQ>
<FILE>TPX001</FILE>
<LIB>Sales price</LIB>
</REQ>
<REQ>
<FILE>TPX002</FILE>
<LIB>Sales total</LIB>
</REQ>
<REQ>
<FILE>TPX006</FILE>
<LIB>Date </LIB>
</REQ>
</ROOT>
2. Add a <REQ> tag containing the following tags:
Tag Explanation
<FILE> Name of the .xml file in which you are going to define the related query
<LIB> Description of the query

This description is displayed as a query in the Database consultation
screen. This screen allows you select and launch the query.
Example: the "Articles by supplier" query

When you wish to create the "Articles by supplier" query, you can add the following <REQ> tag
to the list_default.xml file:
<REQ>
<FILE>Query01</FILE>
<LIB>Articles by supplier</LIB>
</REQ>
3. Save the modifications.

4. Create a new .xml file which has the name you have just defined in the <FILE> tag (in the
list_default.xml file).
Syntax of .xml file

<ROOT>
<TXT>
Define the query here
</TXT>
<COL>Define the description of the first column here </COL>
<COL>Define the description of the second column here </COL>
<COL>etc.</COL>
<VAR>
<NAME>:Define the name of the variable here:</NAME>
<DEFAULT>Define the text to display by default here</DEFAULT>
<PROMPT>Define the description of the variable here</PROMPT>
</VAR>
</ROOT>
5. Define the following tags within the <ROOT> tag:
Tag Explanation
<TXT> SQL query

The SQL query can concern several columns of the database.
<COL> Result table column description

You can define several columns here.
The names of the columns will be displayed in the screen which displays the query
results.
<VAR> <NAME> Variable name. The variable name must be preceded and
followed by ":".
The name of the variable will be displayed in the Descrip-
tion field of the Database consultation screen.
<DEFAULT> Text displayed by default.

This text will be displayed by dafault in the Value field.
<PROMPT> Name of the variable as it will be displayed on the screen

in the Description field.

Example: the "Articles by supplier" query
The "Query01" file of our example could contain the following text:
<ROOT>
<TXT>
select cnucint, artlibl,artean13
from artdgene, artfourn
where artdgene.ARTCINT= artfourn.CNUCINT
and cnucnuf=:Fournisseur:
</TXT>
<COL>Internal article code</COL>
<COL>Article description</COL>
<COL>EAN article code</COL>
<VAR>
<NAME>:Supplier:</NAME>
<DEFAULT></DEFAULT>
<PROMPT>Supplier </PROMPT>
</VAR>
</ROOT>
Note: to facilitate the creation of the .xml file which contains the query, you can copy an ex-
isting .xml file, rename it and replace the text in the tags.
6. Save the file as the name defined in the <FILE> tag (of the list_default.xml file).

CHAPTER 5
MANAGING THE MASTER

"Creating a service", page 64,
"Creating a job", page 65,
"Scheduling the launch of a service", page 67,
"Defining a synonym", page 68,
"Consulting the last execution date of a service ("Dynamic data")", page 69.
ADMINISTRATION MANUAL CHAPTER 5 - MANAGING THE MASTER
CREATING A SERVICE
CREATING A SERVICE
1. Go to the Master management screen

Administration > Master management).
2. Click on the [Add] button on the toolbar.
-> A creation screen is displayed.
3. Enter the following fields:
Service Mandatory Enter the reference of the service. Alphanumeric -
Group Opt. Enter the service group. Alphanumeric -
Explanation Mandatory Enter the description of the service. Alphanumeric -
Mode Mandatory Enter or select the trigger mode of the service Alphanumeric List of values
(table 403). See "Service", page 15 for details on
each mode.
Interval Opt. If you have chosen the "Interval" mode (and only in Numeric -
this case), enter the value of the interval between
every execution in minutes.
Permanent Opt. Check the box to activate the permanent mode and Checkbox -
mode thus allow the process to restart after the process-
ing.
Active Opt. To authorise the launch of the programme, check Checkbox -

the box.
Order - Do not take this field into account. - -
Launch - Do not take this field into account. - -

CREATING A JOB
CREATING A JOB

2. Enter the necessary fields in the search panel, then click on the [Search] button on the
toolbar to search for the service.
-> G.O.L.D. lists the services corresponding to your search criteria.
3. Select the appropriate service, then click on the [Jobs] button at the end of the screen.
-> The Jobs screen is displayed. If the jobs are already defined for this service, one of
them is displayed on the screen. Use the [Go to next line] and [Go to previous line]
buttons to display all the jobs which have already been defined.
4. Click on the [Add] button on the toolbar to create a new job.
5. Define this new job:
Order Enter the name of the programme or PL-SQL procedure. Alphanumeric -
Arguments Enter the arguments of the programme or PL-SQL proce- Alphanumeric -

dure.
Note: the arguments can be customised. They are specific
to the programme. This allows the launch of programmes
not adapted to the Master.
User / Enter the user code and the Oracle password. Alphanumeric -
password
Source site Enter or select the source site (specific to every pro- Numeric List of values
gramme).
Note: to select all the sites, enter -1 (if the programme
launched allows it).
Destination Enter or select the destination site (specific to every pro- Numeric List of values
site gramme).
Note: to select all the sites, enter -1 (if the programme
launched allows it).
Source class Enter the data of the source site (specific to every pro- Numeric -
gramme).
Possible values:
10 => Shop-type sites
=> Warehouse, administrative site
Destination Enter the data of the destination site (specific to every pro- Numeric -
class gramme).
Possible values:
10 => Shop-type sites
=> Warehouse, administrative site
Mask code Enter the mask of the article code (specific to every pro- Alphanumeric -
gramme).

CREATING A JOB
Digit 1 Enter parameter number 1 (specific to every programme). Numeric -
Language Enter the launch language. Alphanumeric -
Cont. with. Indicate if the following job of the service is stopped or con- Checkbox -
foll. job tinued.
Command Enter the order to launch in case of a problem with the Alphanumeric -
failure launched programme.
Job type to launch a programme, check the box Checkbox -

to launch a PL/SQL function, uncheck the box

SCHEDULING THE LAUNCH OF A SERVICE
SCHEDULING THE LAUNCH OF A SERVICE
This procedure is only useful if you have first chosen the "planned" mode in the service defini-
tion.

3. Select the appropriate service, then click on the [Schedule] button at the bottom of the
screen.
-> The Schedule screen is displayed.
4. You can schedule by week day and/or by date.
Schedule
Schedule by week day a. Click on the [+] button at the bottom of the table to add a line.
b. Enter or select a day of the week (list of values available).
c. Enter the time corresponding to the selected day (hh:mm:ss
format).
Schedule by date a. Click on the [+] button at the bottom of the table to add a line.
b. Enter or select a start date (calendar available).
c. Enter the time corresponding to the selected date (hh:mm:ss
format).

DEFINING A SYNONYM
DEFINING A SYNONYM

3. Select the appropriate service, then click on the [Synonyms] button at the bottom of the
screen.
-> The Synonym definition screen is displayed.
4. Click on the [+] button at the bottom of the table to add a line.
5. Define the fields on this line:
Name Mandatory Enter the general name in G.O.L.D. Central for which Alphanumeric -
you wish to establish a correspondence.
E.g.: N3_EAVIEX
Address Mandatory Enter the name of the object in the other database. Alphanumeric -
E.g.: N3_EAVIEX@STOCK5

CONSULTING ("DYNAMIC DATA")
THE LAST EXECUTION DATE OF A SERVICE
CONSULTING THE LAST EXECUTION DATE OF A SERVICE ("DYNAMIC DATA")

3. Select the appropriate service, then click on the [Dynamic data] button at the bottom of
the screen.
-> The Dynamic data screen is displayed.
4. The two panels list the following fields:
Field Explanation
Last processing Date This field indicates the last execution date of the service.
Manual process This field indicates if the processing is manual (box checked) or not
(box unchecked).

INDEX
A Functional prohibitions of a profile

definition 31
Allocation
masking 46
Article lists I
authorising 49 Invoice control
Article pre-referencing authorisation to update the stock 30
defining the authorised workflow steps 50
J
C Job
Comment creating 65
masking 46 definition 16
Commercial reason
masking 46 L
Competitors
Last connection of a user 19
authorising 51
Logistic variant
Cost price
masking 46
masking 46
preventing cost price display by context 48
M
D Master
definition 15
Database
managing 63
displaying 58
Menu profiles (or business profiles)
Discount types
definition 12
preventing creation/modification 47
Merchandise structure
Discounts
masking 46
preventing creation/modification 47
parameterising rights 41
Dynamic data
definition 16
N
F Net invoiced price
masking 46
File
receiving from GAIA 57
sending to GAIA 56 O
Functional autorisations of a profile Order origin
definition 31 preventing 53
Orders Stock movements
masking certain data 46 masking/displaying certain data 48
preventing modification depending on the origin 53 Super user 24
Supplier return reasons
P authorising 27
Password Supply sector
blocking access after a period of inactivity 19 parameterising rights 44
blocking access after entering 3 incorrect passwords Synonym
19 definition 16, 68
changing 20
frequency of modification 18
minimum number of characters 18
T
modifying when connecting for the first time 18 Table 1029 31
password type 18 Table 1095 44
validity end 19
Table 1336 46
Price statements
Table 1337 47
defining the authorised competitors 51
Table 1338 48
Purchase price
masking 46 Table 2288
entry description 18
Purchase unit
masking 46 Table 506 24, 27
Purchase variant Table 530 46
masking 46 Translation
functional authorisation 24
R
Reactivating a user profile 19
U
Reference profile User (or functional) profiles
creating 22 creating 24
defining rights 23 defining rights 26
definition 12 definition 12
deleting 24
Reports
parameterising rights 45
S
Sales price
authorising 52
masking 46
Sales price lists
authorising 52
Schedule 15, 67
Sectors
definition 44
Service
creating 64
definition 15
scheduling 67
Stock adjustment reasons
authorising 27
Stock movement display
authorising 48
Aldata Solution S.A. G.O.L.D. is a trademark of Aldata Solution S.A.
Aldata Solution S.A. acknowledges the rights of all trademarks cited herein.
Aldata Solution www.aldata-solution.com

37, rue du Colonel Pierre Avia info@aldata-solution.com
75508 Paris Cedex 15
FRANCE
Tel.: +33 (0)1 46 48 28 00
Fax: +33 (0)1 46 48 28 01

GB Cen 509 Uti Adm 091 1

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

GB Cen 509 Uti Adm 091 1

Transféré par

Droits d'auteur :

Formats disponibles

G.O.L.D.

Manual type: User manual

This manual corresponds to the patch: CEN509-RM00JAN11

There are three types of manuals related to G.O.L.D. products:

Bold screen, programme, field

[Bold in square brackets] button

"In quotation marks" panel, tab

CAPITAL AND BOLD table

Courrier font code

This manual does not describe the use of:

Patch CEN509-RM00JAN11 (January 11):

Patch CEN508-RM00OCT08 (October 08):

Patch CEN507-RM00JUL07 (July 07):

Patch CEN506-RM00NOV06 (November 06):

Patch CEN505-RM00MAY06 (May 06):

Patch CEN505-RM00MAY06 (May 06):

Patch CEN504-RM00NOV05 (November 05) - Version GB-CS-UTI-ADM-091-1 of this manual

Patch CEN503-EV01AUG05 (August 05):

To be found in this section:

Aim of this manual

Who is this manual destined for?

This manual is destined for:

Entries of the "Administration" menu not documented in

Entries Manual to consult

Local profiles by site/network "Franchise Management", ref. GB-CEN-UTI-FRAN-136

Local user management "Franchise Management", ref. GB-CEN-UTI-FRAN-136

Instance address management "Management of G.O.L.D. Central in distributed environment",

Events alert management "G.O.L.D. Events", ref. GB-EVT-UTI-EVENTS-049

Aldata Solution Confidential document 10

Aldata Solution Confidential document 11

PROFILES AND USER RIGHTS

Reminder: user identification

The different profiles in G.O.L.D.

Aldata Solution Confidential document 12

Defining functional user rights

If you choose proceed as follows:

Aldata Solution Confidential document 13

TRANSFERRING FILES AND CONSULTING THE DATABASE

Aldata Solution Confidential document 14

If the mode is... then the programme is triggered...

Real-time every minute, as a background job.

Interval at regular parameterisable intervals expressed in minutes.

Planned according to a parameterised schedule (see "Schedule", page 15).

Manual on request (only one execution is triggered manually).

Batch in the context of a batch.

Aldata Solution Confidential document 15

Synonyms allow a correspondence to be established between a general name in G.O.L.D. Cen-

Aldata Solution Confidential document 16

To be found in this section:

PARAMETERISING USER PASSWORD MANAGEMENT

Via table 2288

Entry 2 This entry allows you to parameterise the password type:

Aldata Solution Confidential document 18

Via G.O.L.D. Administration

Aldata Solution Confidential document 19

CHANGING YOUR USER PASSWORD

1. Go to the Password modification screen

Aldata Solution Confidential document 20

To be found in this section:

CREATING A REFERENCE PROFILE

1. Go to the Profile management screen

Field Explanation Type Help

Code Mandatory Enter a code to identify the profile. Alphanumeric -