Presentation is loading. Please wait.

Presentation is loading. Please wait.

Database Fundamentals – Part 2

Similar presentations


Presentation on theme: "Database Fundamentals – Part 2"— Presentation transcript:

1 Database Fundamentals – Part 2
Applying Table Relationships in Sage 300 Construction and Real Estate to Create Meaningful Reports

2 CPE Credit In order to receive CPE credit for this session, you must be present for the entire session. Session Code: C-0635 Recommended 1.5 Delivery Method = Group Live Field of Study = Specialized Knowledge and Applications Visit the Sage Summit Connect kiosks to enter CPE credit during the conference. Required Slide This slide is required as part of our NASBA CPE certification. For the most part, you do not need to change the text on this slide. However, you do need to enter the Session Code and Recommended CPE Credit. A one-hour session is equal to 1 CPE credit. A 90-minute session is equal to 1.5 CPE credits. The session code is the same code as the session was listed on the Sage Summit website ( and on the attendees schedule. An example of a code is C-CRE12 or P-ERP45. Sessions are either 60 (1 credit) or 90 minutes (1.5 credits). Information about how to claim CPE credit is provided at conference check-in and in the conference guide.

3 Introduction Presenters
James Coyle, Co-Founder & President, Event 1 Software Michael Newland, Co-Founder & Vice Present Product Management, Event 1 Software This presentation will be available on Sage Summit Virtual Totebag Follow Sage on Use the official hashtag: #SageSummit Recommended Slide A good introduction piques interest, sets expectations, and answers the question, “What’s in it for me?” Use this slide if you have particular issue(s) you need to cover about your session such as introducing guest speakers or roundtable participants, reminding participants of prerequisites or advanced content, explaining how you want to handle questions, and so on. Alternately, you can use your Title slide or Learning Objectives slide for this purpose (and delete this Introduction slide). You can change the title from “Introduction” to something that better suits your slide content or delete this slide altogether. Remember sessions are short in length so introductions should be brief and cover only information pertinent to the presentation. Example: For a session about Crystal Report® design, it might be relevant to describe presenters’ consulting experience, but their Microsoft® Certification is probably not relevant. Please add your Twitter hashtag

4 Session Agenda Relating Tables Driving Table Relationship Types
Exercise #1 – Identify a Table Relationship Driving Table Relationship Types Exercise #2 – Report Groundwork

5 Relating Tables Example – Report drives from AP Distribution table
Can the JC Commitment item table be accessed?

6 Relating Tables – Examine Candidate Table
Unique database-wide codes that mean the same thing in any table JC Commitment Item

7 Relating Tables – Finding the Foreign Keys
AP Distribution

8 Relating Tables – Expressing the Relationship
An AP Distribution can “lookup” values from a JC Commitment Item record using its Commitment (#20) and Commitment Line Item (#22) fields. This is because the Primary Key of JC Commitment Item is Commitment (#20) and Item Number (#22). Note The names and internal names of the fields don’t need to match Every Primary Key field in the table being added (JC Commitment Item in this case) must have a value which would ordinarily be represented as a Foreign Key in the existing table (AP Distribution in this case).

9 Exercise #1 – Identify a Table Relationship
Print available fields for GL Transaction Print available fields for AP Distribution Find the relationship. If reporting a list of GL Transactions, how would the rows from the AP Distribution table be included (related)? Example – For the purpose of including the JC Cost Code.

10 The Driving Table Every row in this table meeting the criteria (if any) will be represented in the report.

11 Choosing the driving table: Utilize Experience
My report needs to include every “________” What table best represents this? Consider desired level of detail Master file table vs. Transaction file table

12 Related Table (Need to pull in additional content)
Relationship Types Driving Table Contains much of the required content Related Table (Need to pull in additional content) To lookup information Break out details

13 Relationship Types Driving Table Related Table Many to One (Lookup)
Many rows in driving table related to the same row in a related table Each Driving Table row is included only once Driving Table Related Table

14 Relationship Types Driving Table Related Table One to Many (Detail)
Provides detail for each row in the driving table Each Driving Table row may repeat any number of times Driving Table Related Table

15 Relationship Types One to Many (Detail)
Example Query with Driving Table rows combined with Related Table rows Repeating information from Driving Table

16 Relationship Types One to Many (Detail)
What to do with repeating values? Approach 1 : Suppress Repeating Values Typical Reporting Features – Print Controls (RD), Groups (CR), Suppress Duplicates (CR), Formulas (OC), Conditional Formatting (OC) Approach 2 : Aggregate the Detail Typical Reporting Features – Aggregate Functions (ASUM (RD), TSSUM (OC)), SQL SUM & Group By (OC,CR)

17 Relationship Types One to Many (Detail)
Approach 1 : Suppress Repeating Values Typical Reporting Features – Print Controls (RD), Groups (CR), Suppress Duplicates (CR), Formulas (OC), Conditional Formatting (OC)

18 We can only aggregate amounts
Relationship Types One to Many (Detail) Approach 2 : Aggregate the Detail Typical Reporting Features– Aggregate Functions (ASUM, TSSUM), SQL SUM & Group By We can only aggregate amounts Desired Result

19 We can only aggregate amounts
Relationship Types One to Many (Detail) Approach 2 : Aggregate the Detail Typical Reporting Features – Aggregate Functions (ASUM, TSSUM), SQL SUM & Group By We can only aggregate amounts

20 Relationship Types One to Many (Detail)
Approach 2 : Aggregate the Detail Typical Reporting Features – Aggregate Functions (ASUM, TSSUM), SQL SUM & Group By

21 Relationship Types One to Many (Detail)
Approach 2 : Aggregate the Detail Typical Reporting Features – Aggregate Functions (ASUM, TSSUM), SQL SUM & Group By

22 Exercise #2 – Report Groundwork
Job Cash Flow Summary Groundwork is what we need to do before starting to build the report design. MOCK-UP

23 Exercise #2 – Report Groundwork
Find Job-Related Fields Find the GL Company Name Field Find the source for each cash flow amount Identify the Driving Table and Table Relationships

24 Exercise #2 – Report Groundwork
Conclusion Column Answer A – Company Table JC Job Column Cost Account Prefix B – Company Name Table GL Company (Prefix A) Column Company Description C – Job Table JC Job –OR– JC Transaction Column Job D - Description Column Description

25 Exercise #2 – Report Groundwork
Conclusion Column Answer E – Cash Receipts Table JC Transaction Column Amount Condition Transaction Type equals “Cash receipt” F – Dollars Paid Table JC Transaction Column Amount Condition Transaction Type equals “Dollars paid” G – Other Costs Column Amount Condition Transaction Type is one of “AP cost”, “EQ cost”, “IV cost”, “JC cost”, “PR cost”, “SM cost”. Also where Application of Origin <> “AP”

26 Exercise #2 – Report Groundwork
Conclusion Fast-Forward To Completed Report Design (Report Design Review)

27 Your Feedback is Important to Us!
Completing a session survey is fast and easy:  Stop by a Sage Summit Survey kiosk or complete the survey on your mobile phone, laptop, or tablet through the Sage Summit mobile app. IOS, Blackberry, or Android users may download the app from the App Store by searching “Sage Summit” Laptop users may use this link Remember each completed survey is another entry for one of several daily prize drawings, including an Apple iPad! Your feedback helps us improve future sessions and presentation techniques. Session code for this session: C-0635 Required Slide All sessions will include this slide; please do not change the verbiage on this slide. Please add the session code to this slide where indicated. 27

28 Contact Information Presenter Contact Information: James Coyle: Michael Newland: Follow us on Use the official Sage Summit hashtag: #SageSummit Don’t forget to use the Sage Summit mobile or web app for all your conference needs. Access presentations on Sage Summit Virtual Tote Bag. Thank you for your participation.


Download ppt "Database Fundamentals – Part 2"

Similar presentations


Ads by Google