Infor LN DEM Content Pack Naming and Building Conventions

Transcription

1 Infor LN DEM Content Pack Naming and Building Conventions

2 Contents Contents Publication Information...4 About this guide...6 Contacting Infor...8 Chapter 1: Introduction...10 Chapter 2: General Building conventions...12 Chapter 3: Versions...14 Chapter 4: Scenarios...16 Naming scenarios...16 Business Control Diagram Categories...17 Business Functions (tgbrg2500m000)...17 Business Function Categories (tgbrg2120m000)...18 Buffers / Functions / External Agent Categories (tgbrg9175m000)...19 Business Control Diagram Trigger Categories (tgbrg9185m000)...19 Chapter 5: Business Processes (tgbrg5500m000)...20 Business Process Categories (tgbrg5105m000)...20 Business Process Activity Categories (tgbrg5525m000)...21 Support Applications (tgbrg5170m000)...22 Static Conditions (tgbrg5580m000)...23 Rules (tgbrg7500m000)...24 Transformation Rules...24 Set Static Condition Rules...24 Set Parameters Rules...24 Wizards (tgwzr1500m000)...25 Dynamic Conditions (tgbrg5140m000)...25 Responsibility s (tgbrg8130m000)...25 Chapter 6: Organization Modeling...26 Roles (tgbrg8110m000)...26 Employees (tgbrg8135m000)...26 Employee Groups (tgbrg8155m000)...26 Employee Group Types (tgbrg8150m000)...27 Enterprise Structure Models (tgbrg0512m000) Infor LN DEM Content Pack Naming and Building Conventions

3 Contents Chapter 7: Business Models...28 Reference Models (tgbrg3500m000)...28 Project Models (tgbrg4500m000)...28 Infor LN DEM Content Pack Naming and Building Conventions 3

4 Publication Information Publication Information Release: Infor LN DEM Content Pack Publication date: July 19, 2013 Document code: U9778C US 4 Infor LN DEM Content Pack Naming and Building Conventions

5 Publication Information Infor LN DEM Content Pack Naming and Building Conventions 5

6 About this guide About this guide This document describes the naming and building conventions regarding the content of the DEM Content Pack. Changes to the content of the standard model must follow these conventions, same goes for changes made by local ICS. For customizations customers can decide upon using these conventions. Intended Audiense The intended audience is DEM consultants and DEM system administrators. Related documents You can find the documents in the product documentation section of the Infor Xtreme Support portal, as described in ""Contacting Infor" on page 8" Infor LN - DEM Content Pack User Guide (U9774) 6 Infor LN DEM Content Pack Naming and Building Conventions

7 About this guide Infor LN DEM Content Pack Naming and Building Conventions 7

8 Contacting Infor Contacting Infor If you have questions about Infor products, go to the Infor Xtreme Support portal at com/inforxtreme. If we update this product or document after the product release, we will post the new version on this Web site. We recommend that you check this Web site periodically for updates. If you have comments about Infor documentation, contact 8 Infor LN DEM Content Pack Naming and Building Conventions

9 Contacting Infor Infor LN DEM Content Pack Naming and Building Conventions 9

10 Introduction Introduction 1 DEM Content Pack is used to provide a fast Implementation process. By setting up a Project Model (copy from the standard Project Model STD) with the needed scenarios and correct choice of options according to the boundaries set in the sales process, DEM generates the correct business processes that need to be trained and implemented with the correct settings of the most important parameters. Some building conventions are based on common practice. For example, the graphical view of the business processes is used during training sessions, where this representation helps the user understand the processes. After a couple of weeks the users switch from the graphical view to directly starting sessions from the menu. Terms used in this guide: Business control Diagrams are called Scenarios. Static Conditions are called Options. 10 Infor LN DEM Content Pack Naming and Building Conventions

11 Introduction Infor LN DEM Content Pack Naming and Building Conventions 11

12 General Building conventions General Building conventions 2 To ensure that the Process Menu generated from the Project Model is easy to use; these general building conventions are used: In a Business Process model the happy flow vertically. This means that if the Control Activity output is No it goes downwards. If the output is Yes or an Option (Static Condition) it is modeled horizontally. If the next activity in the process can be opened from the previous activity using the appropriate menu, this activity is not modeled. During a training session, it is explained to the user how to perform those process steps. Exception to this: If it is common practice that this activity is performed by another Role then it is modeled as a separate step. Print and inquiry sessions are all grouped together in a Support Application and linked to the main Business Process. Exception to this: If a print or inquiry session is a process step (for example change status or decision supporting steps) then they are modeled. Business Process levels are kept to a minimum Only in case the description of the session is completely different from the process step that must be performed, you can manually add an activity description. But avoid this as much as possible. The Users, Roles and the link between the two are set up in the Repository. The link between Roles and Business Processes are set up in the Project Model. 12 Infor LN DEM Content Pack Naming and Building Conventions

13 General Building conventions Every new Business Process must be added to the Project Model and linked to the appropriate Role(s). In the standard Project Model STD the Roles are linked to the Main Business Processes. For training purposes it is good to have people viewing the big picture. During the implementation the customer might decide upon changing this to a more detailed level. Infor LN DEM Content Pack Naming and Building Conventions 13

14 Versions Versions 3 In the Version (tgbrg1500m000) session use these naming convention to add a new DEM version needed for new releases of the Infor LN Suite, local ICS changes or customizations to the standard DEM Content Pack. 1 4 I10_ Fixed The new version is implemented as derived from the original version. 5 6 Version number of the product 7 Sub-version 8 S Standard DEM Content Pack created by Infor Development 8 R Regional changes created by local ICS teams 8 O Own environment created at the customer site 9 1, 2, 3, Example: I10_030O1 and I10_030R1 are both derived from I10_030S1. 14 Infor LN DEM Content Pack Naming and Building Conventions

15 Versions Infor LN DEM Content Pack Naming and Building Conventions 15

16 Scenarios Scenarios 4 Scenarios depict a general flow of information across the involved business functions and are modeled as Business Control Diagrams (tgbrg9550m000). Because of the tight link with the calculation sheet ICS uses to determine the implementation budget: It is necessary that scenarios overlap each other as little as possible so things are not budgeted twice. The landscape of scenarios should resemble a puzzle. During implementation only those pieces of the puzzle are selected to build the picture resembling the customer's business model. It is not allowed to add/change/delete any Scenario (Business Control Diagram) in the standard DEM Content Pack without approval of the Review Board which is responsible for keeping the calculation sheet up to date. Naming scenarios Scenarios are named according to these rules: 10 Logistic Case Scenario 20 Planning & Progress Control Case Scenario 50 Financial Case Scenario 70 Quality oriented Case Scenario 90 ERP Application Supporting Case Scenario Order Fulfillment oriented Case Scenario Supply oriented Case Scenario Service oriented Case Scenario Internal oriented Case Scenario , 25, 50, Infor LN DEM Content Pack Naming and Building Conventions

17 Scenarios Business Control Diagram Categories Business Control Diagram Categories (tgbrg9155m000) is a fixed list, do not add new codes. The codes are linked to the scenarios to provide a reference to a SCOR Process. You can use these categories: CRM Customer Relationship Management EIT Executive Information Technology HRM Human Resource Management PLM Product Life Cycle MAKE Make PLAN Plan DELIVE Deliver DELRET Deliver Return FINANC Financials QUALIT Quality SERVIC Service SOURCE Source SOURET Source Return Business Functions (tgbrg2500m000) Business Functions are the building blocks in a scenario. The Business Functions link the following to the scenario: Business Processes Wizards (there can be only one wizard for one business function. If more than one wizard must be linked to a main business function, setup a parent-child relation for the sub-business functions that link the wizards to the main business function. Rules 1 6 Only used for business functions that link master data business processes to scenarios. These business functions have the same code as the scenario they are linked to. 1 M Main Function AP Account Payable AR Account Receivable AS Assets CM Cash Management CO Common Infor LN DEM Content Pack Naming and Building Conventions 17

18 Scenarios FI General Ledger & Financial Integration FM Freight Management ME Employee Management MN Production PA Product Assortment Management (previous EN) PB Financial Budgeting PL Planning PR Project Management (previous PJ) PU Purchase QM Quality Management RA Financial Reporting (previous PO) SE Service SL Sales, Account Management; Marketing (previous AM) SU Supplier Management IT ERP Application Management (previous TT) WH Warehousing , Business Function Categories (tgbrg2120m000) This is a fixed list, do not add new codes. M00000 Mxxnn0 Mxxnnn Mega Business Functions Main Business Functions Remark Use only for Business Functions that link the master data business processes to the scenario. Business Functions that are used in the scenarios. Sub Business Functions Business Functions that are needed if more than one wizard is linked to a main business function. There is a one to one relationship between the two. In case of more than one wizard for a main business function, you must create sub business functions and link those to the main business function concerned.. 18 Infor LN DEM Content Pack Naming and Building Conventions

19 Scenarios Buffers / Functions / External Agent Categories (tgbrg9175m000) This is a fixed list, do not add new codes. Remark Color BufAct Buffer Activity Warehouse or activity in the goods flow below the picture in the BCMs. Middle Grey ( ) Demand Sales / Demand Forecasting Light Blue ( ) Extern External Actors External Actors Light Grey ( ) Financ Financials Overall Financials Dark Blue ( ) Manage Managing Project Management Red ( ) MasDat Master Data Master Data Dark Grey ( ) Qualit Product Quality Quality Control Green ( ) Supply Supply Supply through purchase, distribution and production Orange ( ) Suppor Support ERP Application Support Purple ( ) Wareho Warehousing Internal stock movements within the warehouse Yellow ( ) Business Control Diagram Trigger Categories (tgbrg9185m000) This is a fixed list, do not add new codes. Inform Information Flow Arrow Remark Infor LN DEM Content Pack Naming and Building Conventions 19

20 Business Processes (tgbrg5500m000) Business Processes (tgbrg5500m000) 5 Ensure that a new standard Main Business Process is linked to the STD Project Model and link the correct Roles. 1 M Main Flow Only Main Business Processes are permitted to be linked to a DEM Project Model 1 D Detail Flow Same set up as Business Functions , Sequence number with steps of 10 1 O Overview Processes AD Aerospace & Defense Only used for overview business processes AU Automotive Only used for overview business processes GM General Manufacturing Only used for overview business processes HT High Tech Only used for overview business processes 4 6 0xx Main overview business processes 4 6 1xx Detail overview business processes Business Process Categories (tgbrg5105m000) This is a fixed list, do not add new codes. DD_APP DD_FIN Dynamic Data (Application Mgt.) Dynamic Data (Financials) Remark 20 Infor LN DEM Content Pack Naming and Building Conventions

21 Business Processes (tgbrg5500m000) DD_LOG MD_APP MD_FIN MD_LOG MR_FIN MR_LOG OP_DEM Dynamic Data (Logistics) Parameters / Master Data (Application Mgt.) Parameters / Master Data (Financials) Parameters / Master Data (Logistics) Management Reporting (Financials) Management Reporting (Logistics) Overview Process Business Process Activity Categories (tgbrg5525m000) This is a fixed list, do not add new codes Initiation (Sub) Business Process System Parameters Master Data (Fixed Data) Master Data (where new codes starts) Remark For example Initialize Parameters (tcmcs0295m000) During the implementation process these activities are listed to determine what system parameters must be set. For example Text Windows (tttxt1520m000) / Price Calculation s (ticpr1100m000) During the implementation process these activities are listed to determine what master data to set up. And determine a naming convention Master Data (where no new code starts) For example Items Purchase (tdipu0101m000) / Default Relations by Customer (tdcms0119m000) Document (in/ex)ternal (unassigned) Document (external) Document (internal/decision supporting step) Document (internal/business process step) For activities that create reports that do not need a customized report. During the implementation process these activities are listed to determine which report layouts must be changed to reflect company requirements. For example Evaluate Sales Contracts (tdsls3420m000) For example Print Cycle Counting Orders (whinh5402m000) / Print Sales Contract Acknowledgements (tdsls3405m000) Infor LN DEM Content Pack Naming and Building Conventions 21

22 Business Processes (tgbrg5500m000) Inquiry Remark For example Sales Order Lines Monitor (tdsls4510m000) Data Entry (not automatic migratable) For example Tax Numbers by Business Partner (tctax4100m000) Data Entry (automatic migratable) Batch (transactions) Batch (archiving) User Defaults 360 (Dashboard) Manual Process Step Migration For example Sales Contracts For example Global Update of Terms and Conditions (tctrm2205m000) Support Applications (tgbrg5170m000) Support Applications are used to link all report and inquiry sessions to a main Business Process. To keep it readable, add a parent-child structure. XX Highest level display and/ or print support application within the tree See Coding Conventions for Business Processes position. 3 _ Underscore Level 1 directly below XX_ Level 2 directly below Level 3 directly below _ Underscore First menu option within a certain level Second menu option within a certain level Example: XX_000_010 Data Retrieval (Company Wide) highest level 22 Infor LN DEM Content Pack Naming and Building Conventions

23 Business Processes (tgbrg5500m000) XX_010_010 Data Retrieval (All Logistics)level 1 PU_020_010 Purchase level 2 PU_030_010 Purchase (Actual)level 3 PU_030_020 Purchase (History)level 3 Static Conditions (tgbrg5580m000) If a new Static Condition is created, ensure it is also added to the STD project model with value Yes in the Static Condition Values by Project Model (tgbrg5595m000 ) session. AA General CI Invoicing CO Common Previous TC DM Document Management EM Employee Management Previous BP FM Freight Management IT ERP Application Management Previous TT MN Manufacturing Previous TI PL Planning Previous CP PM Process Management PR Project Delivery Previous TP PU Purchase Previous TD2 QM Quality SE Service Previous TS SL Sales Previous TD1 FI Financials Previous TF WH Warehousing 3 6 Numeric Try to sort as much as possible in a logical sequence Infor LN DEM Content Pack Naming and Building Conventions 23

24 Business Processes (tgbrg5500m000) Rules (tgbrg7500m000) Transformation Rules To link main Business Processes to Business Functions. Scenario Master Data: 1 6 Alphanumeric Rule gets the same code as the Scenario BF Dynamic Data: 1 6 Alphanumeric Rule gets the same code as the Business Function Set Static Condition Rules Selecting Scenarios or Business Functions sets the value of certain Options. Scenario Options: 1 6 Alphanumeric Rule gets the same code as the Scenario BF Options: 1 6 Alphanumeric Rule gets the same code as the Business Function Set Parameters Rules Selecting Scenarios for Business Functions or Options sets the value of certain parameters. Scenario Parameters: 1 6 Alphanumeric Rule gets the same code as the Scenario BF Parameters: 24 Infor LN DEM Content Pack Naming and Building Conventions

25 Business Processes (tgbrg5500m000) 1 6 Alphanumeric Rule gets the same code as the Business Function Option Parameters: 1 6 Alphanumeric Rule gets the same code as the Static Condition Wizards (tgwzr1500m000) Wizards are used to implement Options. However, not for every option there is a wizard. Only where implementation time of complex and/or cross functional business functions can be reduced dramatically, wizards are created. Every wizard is linked to a Business Function in the Business Functions (tgbrg2500m000) session. 1 6 Alphanumeric The code of the Business Function where the wizard is linked to. 7 Dot = The code of the Static Condition to implement. 14 Dot = Serial No.: 10, 20, 30, Dynamic Conditions (tgbrg5140m000) Not in use. Responsibility s (tgbrg8130m000) Not in use. Infor LN DEM Content Pack Naming and Building Conventions 25

26 Organization Modeling Organization Modeling 6 Roles (tgbrg8110m000) SU Super User Highest level Role KU Key User Role below the Super User Role EU End User Role below the Key User Role 3 4 See Coding Conventions for Business Function , 20, 30, Employees (tgbrg8135m000) 1 6 Same code as the code in the User data (ttaad2500m000) Employee Groups (tgbrg8155m000) Not in use. 26 Infor LN DEM Content Pack Naming and Building Conventions

27 Employee Group Types (tgbrg8150m000) Not in use. Organization Modeling Enterprise Structure Models (tgbrg0512m000) Not in Use. Infor LN DEM Content Pack Naming and Building Conventions 27

28 Business Models Business Models 7 Reference Models (tgbrg3500m000) Not in Use. Project Models (tgbrg4500m000) New Project Models are created by copying the STD Project Model to a new one using the naming convention described below. 1 3 STD Standard Project Model Maintained by Development. 1 6 All others are used to create a customer specific model for kernel building or standalone implementation. 28 Infor LN DEM Content Pack Naming and Building Conventions

29 Business Models Infor LN DEM Content Pack Naming and Building Conventions 29