Đang chuẩn bị liên kết để tải về tài liệu:
SAS Data Integration Studio 3.3- P32

SAS Data Integration Studio 3.3- P32:This manual is a companion to the online Help for SAS Data Integration Studio. The Help describes all windows in SAS Data Integration Studio, and it summarizes the main tasks that you can perform with the software. The Help includes examples for all source designer wizards, all target designer wizards, and all transformation templates in the Process Library tree. | 150 Example Creating a Job That Joins Two Tables and Generates a Report A Chapter 10 Example Creating a Job That Joins Two Tables and Generates a Report Preparation Suppose that you wanted to create a report that shows which sales person is making the most sales as described in Which Salesperson Is Making the Most Sales on page 45. You decide to extract columns from several existing tables write that information to a new table and run a report on the new table. An example of this report is shown in the following display. Display 10.1 Total Sales by Employee Report Name Total Revenue Emp ID Job Title Company Dept Section Group Alban Kingston 5 030.00 120170 Sales Rep II Orion France Sales Sales Racket Sports Andre Noel 4 535.00 12D411 Sales Rep I Orion France Sales Sales Winter Sports Giulia Buono 6 230.00 120599 Sales Rep II Orion Italy Sales Sales Children Sports One way to create this report is to create a SAS Data Integration Studio job that joins the required tables and writes the output of the join to a new table. The new table would be the input to a report transformation. This example demonstrates one way to create such a process flow. In the example columns from source tables ORGANIZATION_DIM and ORDER_FACT are extracted and mapped to columns in the main target table Total_Sales_By_Employee . The main target table in turn is the input to a report transformation Publish to Archive that creates the desired report. Assume the following about the example job Metadata for both source tables in the job ORGANIZATION_DIM and ORDER_FACT is available in a current metadata repository. Identifying Targets on page 48 describes how these tables were created by combining information from other tables. The ORGANIZATION_DIM and ORDER_FACT tables have the same key column Employee_ID. In the current example these tables will be joined on the Employee_ID column. Metadata for the main target table in the job Total_Sales_By_Employee is available in a current metadata repository.