Training Course TEC201: Common Tools Advanced February 2011 V6.2

Training Course

TEC201: Common Tools Advanced

February 2011

V6.2

/ © Sage 2011

Sage ERP X3 ExpertSage ERP X3 Advanced

Course Map

Sage ERP X3 Fundamentals

OPE201 - Distribution

(3 days)

FIN201 - Finance(4 days)

TEC101 - Common Tools

(3 days)

OPE203 - Manufacturing

(3 days)

OPE202 - Inventory(2 days)

Manufacturing (5 days)

Configurator

Weighing

Optimisation ILOG

Distribution and Inventory

Purchasing Subcontracts

Pre-Allocations (Pegging Function)

Radio Terminals

Finance

Multi-Legislation Set Up

Operating Budgets

Analytical Allocations

Factoring

Distribution Contracts (Purchasing and Sales)Loan OrdersPackaging & Shipment PreparationPurchasing Signature ManagementSales and Purchasing PrepaymentsSales Reps and CommissionsSourcing: RFQs, ResponsesCarrier ManagementInter-Site and Intercompany TransactionsInvoice Elements (Purchasing & Sales)Kits, Options & VariantsPrice List Management (Advanced)

FinanceBank Communication & ReconciliationBudget Control/ Analytical BudgetFinancial Data ExtractionStatements & RemindersAutomatic Journals & Dimension DefaultsAdvanced Payment TransactionsMonth and Year End ProcessesFixed Assets

You Are Here

Manufacturing (4 days) Advanced Global Manufacturing Production Costing

Inventory (3 days)Allocation Rules (Advanced)Stock CountsSerial Number Management Reodering Replenishment Storage PlanValuation Methods and Price Adjustments and cost calculationsQuality Control & Sampling

CB 101 – 102Introduction &

Functional Overview(3 days)

TEC102Development

(4 days)

TEC103Installation

(4 days)

Tools & DevelopmentAdvanced Common Tools Advanced Development

Tools & DevelopmentUsing BI in Sage ERP X3Java Bridge Serveur ComponentsEDM – Version OneWeb ServicesCrystal Reports

TEC201: Common Tools Advanced2

/ © Sage 20113

Objectives

Presentation of Sage ERP X3 ‘Common Tools’ Advanced

To be able to create & set-up users and their access to the X3 system

To be able to define batch jobs and control the batch server.

To be able to define more complex workflows

To be able to link Crystal Reports to the X3 system

To be able to install & create patches

To be able to archive and purge data from the X3 system

To able to update the on-line documentation

Three-day session


/ © Sage 20114

Sage ERP X3 Introduction (CB101)

Sage ERP X3 Overview (CB102)

Sage ERP X3 Common Tools Fundamentals (TEC101)


Prerequisites

/ © Sage 20115

INTRODUCTION

Part 1USERS, SECURITY & AUTHORISATIONSBATCH SERVERWORKFLOW

Part 2REPORT MANAGEMENTPATCH MANAGEMENTPURGING & ARCHIVING

Part 3TOOLSDOCUMENT MANAGEMENT

Contents


/ © Sage 2011

Part 1

Users, Security & Authorisations

• Overview• The User record• Access Right management

(Concepts)• Security Parameter values• Menu Profiles• Functional Profiles• Access Codes• Roles• Usage / Users menu• Password deletion (by

Administrator)

Batch Server• The batch server• Operating principles• Defining a task• Defining a group of tasks• Submitting a request• Monitoring the tasks• Hourly constraints & Batch server diary• Batch server parameters• Submitting a job by file• The accounting batch task

Workflow• Workflow engine : basic principles• Parameters• Rule Definition• Workbench (Workflow Monitor)• Workbench parameterisation


Schedule

Introduction

/ © Sage 2011

Part 2

Report Management• Printer Destinations• Destinations by User• Reports (Dictionary)• Reports (Printing)• Allocation of Internal Codes• Default Parameters

Patch Management• Patches• Standard Patches• Patch integration• The Patch Tester • Patch Enquiry• Patch Creation

Archiving & Purging• Overview• The Archive folder• Purge / Archive Rules• Purge / Archive Parameters• Running Purge / Archive• Viewing archived information


Schedule

/ © Sage 2011 TEC201: Common Tools Advanced

Part 3

Tools• Toolkit (Searches, dictionary etc.)• Database mass updates• Maintenance

Document Management• Parameters• Document Organisation• Field Help• HTML Editor• Documentation Links• Generation• Publication

8

Schedule

Introduction

/ © Sage 2011 TEC201: Common Tools Advanced9

Part 1

/ © Sage 2011

Users, Security & Authorisations


Menu ProfileMenu Profile Function ProfileFunction Profile

Default Access CodesDefault Access Codes

Default Sites per ModuleDefault Sites per Module

Authorised Report GroupsAuthorised Report Groups

Functional Profile(Options Function/Site/Access

rights)


rights)

BP InformationBP Information

AccountAccount

BankBank

AddressesAddresses

User CodeUser Code

User Login (unique)

User Login (unique)

E-mail, Phone etc.

E-mail, Phone etc.

Roles (Data filters)Roles (Data filters)

Parameter ValuesParameter Values

Authorised DestinationsAuthorised

Destinations

HierarchyHierarchy

Access Codes (Dictionary and Data)


/ © Sage 2011

User & Security Parameters







rights)


rights)


AccountAccount

BankBank

AddressesAddresses

User CodeUser Code

User Login (unique)

User Login (unique)

E-mail, Phone etc.

E-mail, Phone etc.




Destinations

HierarchyHierarchy



/ © Sage 2011

Menu Profile







rights)


rights)


AccountAccount

BankBank

AddressesAddresses

User CodeUser Code

User Login (unique)

User Login (unique)

E-mail, Phone etc.

E-mail, Phone etc.




Destinations

HierarchyHierarchy



/ © Sage 2011

Functional Profile







rights)


rights)


AccountAccount

BankBank

AddressesAddresses

User CodeUser Code

User Login (unique)

User Login (unique)

E-mail, Phone etc.

E-mail, Phone etc.




Destinations

HierarchyHierarchy



/ © Sage 2011

Functional Profile


Function Access Rights

Function Profile SALPAR

Function GESSOH Create Allocate

Allocate

Delete

Sales OrderSite: ASN

CreateAllocat

eDelete

Sales OrderSite: PAR

CreateCreate Allocate

Allocate DeleteDelete

Sales OrderSite: GEN

/ © Sage 2011

Access Codes







rights)


rights)


AccountAccount

BankBank

AddressesAddresses

User CodeUser Code

User Login (unique)

User Login (unique)

E-mail, Phone etc.

E-mail, Phone etc.




Destinations

HierarchyHierarchy



/ © Sage 2011

Access Codes


Screen Code BPC2

Code SAD

Authorized Credit 890.00

Total Credit 53.48

Parameters > Users > Access Codes (GESACS)

Parameters > General Parameters > Personalisation > Screens > Access Code Assignment (CODACC)

Parameters / Users / Users

11

22

33

/ © Sage 2011

Roles







rights)


rights)


AccountAccount

BankBank

AddressesAddresses

User CodeUser Code

User Login (unique)

User Login (unique)

E-mail, Phone etc.

E-mail, Phone etc.




Destinations

HierarchyHierarchy



/ © Sage 2011

Batch Server Principles


Log File

(Process)

Log File

(Batch Server)

Request Table

(ABATRQT)

Working Folder SERVX3Folder

Batch Process

User Session

Batch Server

(process SERVX3)

Submission

Submission by Text FileDropped in Folder

Launch

Interruption(time-out, kill)

PeriodicPolling

RecurringTasks

/ © Sage 2011

Batch ServerA request may be submitted to the batch server:Through the Request Submission function

Directly in the Request Management function

A request may be submitted by entering:• the folder where it is to be executed• the user code• the task or the group• the requested execution time• the parameters of the validation window

Via a text file that acts as a task submission when it is dropped to the adequate directory in the SERVX3 Folder.

Through a Recurring Task definition, i.e. a task to be launched periodically:

Monthly (1 to 5 possible days + End of Month flag)

Weekly (Any combination of weekdays)

Launching time (Up to 3 choices)

Periodically (Time intervals between two times).

Time constraints may be defined in order to specify unavailability periods during which no batch job may be launched.

The management of the requests is used to monitor or modify the pending requests, the tasks being executed or the completed tasks.

It is possible to view the different trace files, to submit a new request, to delete a pending request or to modify the parameters.


/ © Sage 2011

Batch Server -Text File Submission


Request.mod

Request.job

Request.req

Request.old

Request.run

Request.sta

Request.kil

Request Management

Request Submission

Batch Server Processes Request

Request Terminated

Request Interruption Demand

Request Running

/ © Sage 2011

Workflow Engine


Sage X3 Process

Email

Log Table

Triggering ConditionsTriggering Conditions

Event CodeEvent Code

Triggering Action(Button,

Operation…)

Triggering Action(Button,

Operation…)

Additional ConditionsAdditional Conditions

Action ParametersAction Parameters

Return ValuesReturn Values

Message TextMessage Text

AttachmentsAttachments

Send OptionsSend Options

RecipientsRecipients

Return ShortcutReturn Shortcut

Log Structure and Data Definition

Log Structure and Data Definition

Event Type(Object, Batch

Job…)

Event Type(Object, Batch

Job…)

Return Shortcut

Users

Sage X3 Context

11

22

33

GBIDC1/2/3GBIDI1/2/3GBIDA1/2/3GBIDD1/2/3

/ © Sage 2011

E-mail Principles


Sage X3 Server(s)

Web Server(s)

MAPI Client

MAPI SMTP

Email Server

/ © Sage 2011

Signature Principles

Sage X3 Server(s)

Web Server(s)

MAPI Client

MAPI SMTP

Email Server


SIG

/ © Sage 2011

Workflow Parameters


SERMES

TYPMES

WRKDAY

WRKRMTDIR

WRKRMTHTTP

WRKRMTMAC

WRKSINTER

WRKSINTRA

SMTP E-mail Server Identity Type of E-Mail Server Number of Days prior to today for Workbench

dates Web Server Directory to place workflow Files Web Server location to process Workflow Files X3 solution connection information Internet Workflow Feedback Intranet Workflow Feedback

/ © Sage 2011 TEC201: Common Tools Advanced25

Workflow Rules

Parameters > Workflow > Workflow Rules

This allows more complex Workflow Scenarios to be definedAdditional types of triggering events

More than two recipients (and these can be variable)

Signature processes can be defined (and records updated)

Delegation can be used

Parameterization screen of the Workflow rules is comprised of 5 tabs, with the first three concerning the basic parameterization and the other two enabling an advanced parameterization .

Notifications can be sent by E-mail or logged as an entry in the Workflow Monitor or both

/ © Sage 2011

Workflow monitor

The workflow monitors are used to display the flows to be monitoredUsage > Workflow monitor

Event trackingEvent update

Creation of a planning workbenchParameters > Workflow > Planning workbench setup

An enquiry is used to filter and present the flows to be tracked

26 TEC201: Common Tools Advanced

/ © Sage 2011

Part 2


/ © Sage 2011

Report Principles


Sage X3 Server(s)

Web Server(s)

Print Server(s)

Request

Request

CrystalReport.rpt

/ © Sage 2011

Sage ERP X3 Solution

X3 (Reference Folder)

TESTTest Folder

PILOTPilot Folder

LIVELive Folder

Patch Management (Sage X3)


Creation

Inheritance

IP Port

Runtime

Integration

/ © Sage 2011



TESTTest Folder

PILOTPilot Folder

LIVELive Folder

Patch Management (Development)


Creation

Inheritance

IP Port

Runtime

Integration

/ © Sage 2011



TESTTest Folder

PILOTPilot Folder

LIVELive Folder

Patch Creation (Development)


Creation

Inheritance

IP Port

Runtime

Creation

/ © Sage 2011

Archive & Purging Principles


Working Folder Archive Folder

Group of Tables to beArchived

Group of Tables not to beArchived

Archiving

PurgingPurging

/ © Sage 2011

Part 3


/ © Sage 2011

Tools

Toolkit (Searches, dictionary etc.)

Database mass updates

Maintenance


/ © Sage 2011

Documentation

This function is used to personalize the standard delivered documentation or to develop the documentation on specific developments.

This function is integrated into the software package and is based on the organization of the X3 entities.

The start entity of a documentation is the X3 (AFC) function to which the documentation is linked. The main components of a function may concern specific documentation (Action, Screen, Table etc.)

Documentation organization is based on that of the X3 dictionary. Documentation may be based on a link table used to associate additional documentation.

The structuring elements of a document are as follows:The language code

The type of X3 entity documented

The associated components.


/ © Sage 2011

Documentation

X3 documentation is organized in paragraphs. One paragraph is made up of a workframe which describes the hierarchal organization of the basic text it is made up of.

The description of the paragraph’s structure is saved in the ADOCUMENT table.

Paragraphs may be accessed directly via online help.

Compiling this hierarchal structure with the associated texts enables the documentation generator to produce XHTML text.

These paragraphs may be generated automatically according to the type associated (function / activity code etc.)


/ © Sage 2011

Thank you for your attention


Documents

Training Course TEC201: Common Tools Advanced February 2011 V6.2