Student 9.5 API Handbook

Banner Student API HandbookRelease 9.5March 2016/nWithout limitation: Ellucian®, Banner®, Coll eague®, and Luminis® are trademarks of the Ellucian group of companies that are reg istered in the U.S. and certain other countries; and Ellucian AdvanceŽ, Ellucian Course SignalsŽ, Ellucian Degree WorksŽ, Ellucian PowerCampus Ž, Ellucian RecruiterŽ, Ellucian SmartCallŽ, are also trademarks of the Ellucian group of companies. Other names may be trademarks of their respective owners. © 2016 Ellucian. Contains confidential and proprietary information of Ellucian and its subsidiaries. Use of these materials is limited to Elluci an licensees, and is subject to the terms and conditions of one or more written li cense agreements between Ellucian and the licensee in question. In preparing and providing this publicati on, Ellucian is not rendering legal, accounti ng, or other similar professional service s. Ellucian makes no claims that an institution's use of this publication or the soft ware for which it is provided will guarantee compliance with ap plicable federal or state laws, rules, or regulations. Each organiza tion should seek legal, accounting, and other similar professional services from comp etent providers of the organization's own choosing. Ellucian 4375 Fair Lakes Court Fairfax, VA 22033 United States of America Revision History Publication DateSummary March 2016New version that supports Banner Student API 9.5 software. /n 1Handbook |Contents Contents Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 REST is about ‚resources™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Oracle Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Application server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Middle Tier (application server) platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Ellucian software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Java dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Banner Setup Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Sample client applicat ion in API source code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Globally Unique Identifier (GUID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 Rationale for Using GUIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Create a GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Generating a GUID using Java. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Generating a GUID using JavaScript. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Generating a GUID using Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Generating a GUID using C#/.NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Generating a GUID using Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Crosswalk GUIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Crosswalk GUID for Validation tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Integration Configuration Settings Form (GORICCR). . . . . . . . . . . . . . .18 /n 2Handbook |IntroductionIntroductionAn Application Programming Interface (API) is a specification intended to be used as an interface by software components to communicate with each other. REpresentational State Transfer (REST) is a set of principles that define how Web standards such as HTTP and URIs. The objective of the Banner RESTful APIs (is to expose the services available in the new Banner applications powered by XE as RESTfu l APIs. The target end users for these APIs will be developers at campuses and partner developers. These RESTful APIs will enable integration across a number of Ellucian product offerings. RESTful APIs provide simple yet powerful in terface for interacting with Banner. APIs are useful for developers and administrators who aim to integrate Banner with external applications. APIs are excellent choice for integration as they are accessible using simple HTTP methods (GET, POST, PUT, and DELETE). APIs also provide flexibility to specify the response data format (JSON or XML). REST is about ‚resources™RESTful architectures expose resources. A resource is an abstraction of a piece of information, such as a single data record or a collection of records. RESTful resources provide the following benefits: ŁEach resource is identified by a unique URI. ŁAll resources are accessed with a uniform interface over HTTP. Any resource can be manipulated using standard HTTP methods (GET, POST, PUT, DELETE). ŁEach resource support multiple representations (JSON and XML). Security OverviewIt is recommended that APIs be submitted over HTTPS to ensure encryption of the request and response. Note: All examples in the following documentation show HTTP against a local host. The client will want to deplo y the war file to a server that has HTTPS and the URL for the API will be for that server and HTTPS. The web service definition for the API includes the pattern for HTTPS and for the server and port information. /n 3Handbook |IntroductionAPIs requires submission with an authorization header. The authorization header ID must use a valid Oracle ID with proxy access to the banproxy user. Security for Banner APIs powered by XE is similar to security fo r accessing Banner Administrative forms. A Banner administrative account (Oracle user ) must be created to access RESTful APIs. The following privileges should be defined in the Banner administrative account for RESTful API access: ŁDefine Oracle Create Sess ion privilege or the USR_DEFA ULT_CONNECT Oracle role as the default role for the user. ŁDefine the BAN_DEFAULT_M Oracle role as granted to the user. It does not need to be a default role, as it is password protected. ŁDefine the BANPROXY access set in the Or acle/Banner Security Maintenance Form (GSASECR) or the ALTER USER us ername GRANT CONNECT THROUGHBANPROXY. ŁDefine access to the General Menu (GUAGMNU) Banner security object using the Oracle/Banner Security Maintenance Form (GSASECR). We can grant access to‚GUAGMNU™ directly to the user or assign user to a security class that is granted access to ‚GUAGMNU™. ŁIf Banner has been configured for MEP, the user must be authorized for any VPDI contexts that will be accessed from APIs. Note: In MEP-enabled Banner, instituti ons must include their MEP code (also known as VPDI_CODE) in the URL to access the API. Following is a sample URL with MEP code: http://host:port/StudentApi//api/ Hardware requirements The application has the following CPU and memory requirements: Recommended:Quad core CPU with 4 to 8 GB of memory for the application server Minimum:Quad core CPU with 4 GB of memory for the application server /n 4Handbook |IntroductionSoftware requirements The application has the follo wing software requirements. ŁfiOracle Database fl on page4 ŁfiApplication server fl on page4 ŁfiMiddle Tier (application server) platforms fl on page4 ŁfiEllucian software fl on page5 Oracle Database This upgrade is recommended to be applied with Oracle Database Release 11.2.0.4. Application serverThe application is supported on t he following application servers: ŁOracle Fusion Middleware 11gR1, 11gR2, and 12c using WebLogic 10.3.3, 10.3.4, 10.3.5, 10.3.6, and 12.1.3 ŁApache Tomcat 7 and 8 Middle Tier (application server) platforms The application is supported on the following application server and operating system combinations:Tomcat (64 bit) WebLogic (64 bit) Red Hat Linux 5.3 Red Hat Linux 5.3 Windows Server 2008 Windows Server 2008 Solaris 10Solaris 10AIX 6.1 (JDK 1.6.0 SR10 or later) AIX 6.1 (JDK 1.6.0 SR10 or later) HP-UXHP-UX 11iV3 (11.31) /n 5Handbook |IntroductionNote: Banner 9.x applications were tested on WebLogic using both the Classic Domain template and the Basic Domain template. For WebLogic server environments, JPA 2.0 support must be enabled. WebLogic server does not enable JPA by default. To enable JPA, use the steps in the appropriate Oracle documentation: WebLogic 10.3.3: http://docs.oracle.com/cd/E14571_01/web.1111/e13720/ using_toplink.htm#i1221315 WebLogic 10.3.4: http://docs.oracle.com/cd/E17904_01/web.1111/e13720/ using_toplink.htm#i1221315 WebLogic 10.3.5: http://docs.oracle.com/cd/E21764_01/web.1111/e13720/ using_toplink.htm#EJBAD1309 WebLogic 10.3.6: http://docs.oracle.com/cd/E23943_01/web.1111/e13720/ using_toplink.htm#autold2 Weblogic 12.1.3 https://docs.oracle.com/middleware/1213/wls/EJBAD/ using_toplink.htm#EJBAD1288 Ellucian software Depending on the products that are licensed at your institution, the following product upgrades must be applied: ŁBanner DB Upgrade 9.4 Ł(Optional) EMS v1.0.1 Ł(Optional) Banner Event Pub lisher (BEP) 1.2.3 or 2.0 Ł(Optional) INTCOMP 8.0.2.6 Note: EMS v1.0.1 and BEP 1.2. 3 or 2.0 are needed for clients using APIs asynchronously and INTCOMP 8.0.2. 6 is needed for ILP clients using grade-entries API. To access the grade-entries API that is used to submit mid-term and final grade for a student, you must install the INTCOMP 8.0.2.6 patch (pcr- 000124801_int8000206). /n 6Handbook |IntroductionJava dependenciesJava 7 (64-bit version) must be installed on the application server before you install the application. The application supports Java 7 JDK and JRE in run time. The JDK bin directory must be defined in the PATH system property. Banner XE Student API 9.5 is now certified on the following: Banner Setup Requirements Various integration configuration elements that are required for APIs must be set up as part of the Banner setup requirements. A script is being delivered to insert the integration configuration elements into the GORICCR table with UPDATEME value. During implementation, these values must be set based on the requirements. The script is delivered as part of Banner DB Upgrade 9.4. Compile Runtime Application Server Java 7Java 7 Tomcat 7 Java 7Java 7 Weblogic 10.3.6 Java 7Java 7 Tomcat 8 Java 7Java 7 Weblogic 12.1.3 Java 7Java 8 Tomcat 8 Java 7Java 8 Weblogic 12.1.3 /n 7Handbook |IntroductionSample client application in API source codeA sample client application (G rails application) is included with the API source code and will be delivered to customers via GIT. Use the following procedure to run the sample client application. 1.Download the following .zip file. [ssh://git@banner-src.ellucian.com/banner/apps/ banner_student_api_app.git] / docs / samples / banner- rest-ga-demo.zip 2.Extract the files from the .zip file to C:\banner-rest-ga-demo. 3.Open the command prompt in the C:\banne r-rest-ga-demo directory and execute the following command: grails run-app Note: You must set all the environment variables such as JAVA_HOME and GRAILS_HOME before executing the grails run-app command. The default server port used to run your demo application is 8090. You can change the port by editing the value of grails.server.port.http property in banner-rest-ga- demo/grails-app/conf/BuildConfig.groovy 4.Open the http://localhost:8090/banner-rest-ga-demo/restdemo/mainMenu URL in Google Chrome or Mozilla Firefox Web browsers. 5.From the main menu, click the API Configuration tab to configure the required det ailsto call the APIs (Banner API App URL, user name, and password). 6.From the main menu, click the Registration APIs to call the APIs. 7.From the drop-down list, select your desired API. 8.Click Go Fetch it .The list of API results will be displayed automatically. /n 8Handbook |Globally Unique Identifier (GUID) Globally Unique Identifier (GUID)GUID is a unique 128 bit number. You use GUIDS when there are multiple independent systems or when generating unique IDs. Rationale for Using GUIDSGUIDS are just one form of an enterprise identifier. The following are some of the characteristics: ŁThe format is well known ŁSupported by an international standard (RFC 4122) ŁMultiple tools available to support ŁIt is a single data type ŁIt has a very large symbol space Create a GUIDAccording to RFC 4122 standard, the GUIDS must be of version 4. Version 4 GUID are formed from randomly generated 122 bit numbers in which 6 bits are reserved by the specification. GUID sub-components must be considered as hexadecimal values. Hexadecimal must use lower-case letters when the GUID is creat ed but should be treated as case-insensitive when being compared. Note: Ellucian RESTful API™s GUID confor ms to RFC 4122 of version 4. The GUID format is constrained in the JSON schema definitions and cannot be changed. If you change the format of this value it will break Ellucian product integrations which are dependent on JSON schema™s for exchanging data. /n 9Handbook |Globally Unique Identifier (GUID) Generating a GUID using JavaThis is Supported since Java 1.5. Java prov ides a simple utility f unction for generating Version 4 GUIDS. The following code block illust rates how to create a Version 4 GUID and return that GUID as a STRING. public class RandomUUID { public static String create() { return java.util.UUID.randomUUID().toString(); } }Generating a GUID using JavaScriptGeneration of GUIDS using JavaScript should be restricted to server side JavaScript. It is relatively easy to use browser tools like GreaseMonkey on Firefox or TamperMonkey on Chrome to subvert the GUID generation. JavaScript does not have a built in method for generating Version 4 GUIDS. Generating a GUID using Node.jsThe following code block illustrates ho w to create a Version 4 GUID: var uuid = require('node-uuid'); ...// Generate a v4 (random) id uuid.v4(); // -> '110ec58a-a0f2-4ac4-8393-c866d813b8d1' Generating a GUID using C#/.NET.NET provides the Guid.NewGuid() function which returns a versio n 4 GUID. The following code block illustrates how to create a Version 4 GUID: using System; namespace ConsoleApplication1 { class Program { static void Main(string[] args) { for (int i = 0; i < 5; i++) /n 10Handbook |Globally Unique Identifier (GUID) { Console.WriteLine(Guid.Ne wGuid()); } Console.ReadLine(); } }}Generating a GUID using Microsoft SQL Server Microsoft SQL Server provides the NEWID() call to return a version 4 GUID. To generate a GUID using Microsoft SQL Server, you must call the NEWID() using the following code: Validating NEWID() is Version 4 SELECT NEWID(); Crosswalk GUIDSThe GORGUID table holds the GUID for the a ll records required fo r the integration API. Column Name CommentGORGUID_GUID Column holds the GUID information GORGUID_LDM_NAME The name of the domain object GORGUID_DOMAIN_SURROGATE_ID The hibernate unique id for the domain object GORGUID_ACTIVITY_DATE Date on which the GUID was added or last changed GORGUID_DOMAIN_KEY The Banner domain business key which used to identify the record in the domain object. GORGUID_SURROGATE_ID The hibernate unique index for the GORGUID table GORGUID_VERSION The hibernate optimistic lock version GORGUID_USER_ID User who inserted or last update the data GORGUID_DATA_ORIGIN Source system that created or updated the row GORGUID_VPDI_CODE Multi-entity processing code /n 11Handbook |Globally Unique Identifier (GUID) Crosswalk GUID for Validation tables The GORGUID_DOMAIN_KEY holds the code information of the validation table. The following table contains the list of validation tables that supports domain and the corresponding domain object name. Domain Name Table NameDomain Key ColumnSQL Query ACADEMIC- LEVELS STVLEVL STVLEVL_CODE select gorguid_guid, stvlevl_code, stvlevl_desc from gorguid, stvlevl where stvlevl_code = gorguid_domain_key and gorguid_ldm_name = 'academic-levels' and stvlevl_code = '' CAMPUSESSTVCAMP STVCAMP_CODE select gorguid_guid, stvcamp_code, stvcamp_desc from gorguid, stvcamp where stvcamp_code = gorguid_domain_key and gorguid_ldm_name = 'campuses' and stvcamp_code = '' COLLEGESSTVCOLL STVCOLL_CODE select gorguid_guid, stvcoll_code, stvcoll_desc from gorguid, stvcoll where stvcoll_code = gorguid_domain_key and gorguid_ldm_name = 'colleges' and stvcoll_code = '' ETHNICITIESSTVETHN STVETHN_CODE select gorguid_guid, stvethn_code, stvethn_desc from gorguid, stvethn where stvethn_code = gorguid_domain_key and gorguid_ldm_name = 'ethnicities' and stvethn_code = ' GORGUIDSelect gorguid_domain_key from gorguid Where gorguid_ldm_name='ethnicities-us'; Note: The new query is added to implement V3 and V4 versions of ethnicities API. This returns the new Hispanic or Latino, Not Hispanic or Latino and None records/n 12Handbook |Globally Unique Identifier (GUID) GRADE-SCHEMES STVGMODSTVGMOD_CODE select gorguid_guid, stvgmod_code, stvgmod_desc from gorguid, stvgmod where stvgmod_code = gorguid_domain_key and gorguid_ldm_name = 'grade-schemes' and stvgmod_code = '' INSTRUCTIONAL -METHODSSTVSCHDSTVSCHD_CODE select gorguid_guid, stvschd_code, stvschd_desc from gorguid, stvschd where stvschd_code = gorguid_domain_key and gorguid_ldm_name = 'instructional- methods' and stvschd_code = '' MARITAL- STATUS STVMRTL STVMRTL_CODE select gorguid_guid, stvmrtl_code, stvmrtl_desc from gorguid, stvmrtl where stvmrtl_code = gorguid_domain_key and gorguid_ldm_name = 'marital-status' and stvmrtl_code = '' RACES GORRACE GORRACE_RACE_CDEselect gorguid_guid, gorrace_race_cde, gorrace_desc from gorguid, gorrace where gorrace_race_cde = gorguid_domain_key and gorguid_ldm_name = 'races' and gorrace_race_cde = '' Note: Copy GORICCR script is delivered as part of the Banner DB Upgrade 9.4 for RACES and MARITAL- STATUSES APIs that copies the existing GORICCR settings to th e new RACE.RACIALCATEGORY and MARITALSTATUS.MARITALCATEG ORY V4 GORICCR settings. RESTRICTION-TYPESSTVHLDDSTVHLDD_CODE select gorguid_guid, stvhldd_code, stvhldd_desc from gorguid, stvhldd where stvhldd_code = gorguid_domain_key and gorguid_ldm_name = 'restriction- types' and stvhldd_code = '' Domain Name Table NameDomain Key ColumnSQL Query /n 13Handbook |Globally Unique Identifier (GUID) SUBJECTSSTVSUBJ STVSUBJ_CODE select gorguid_guid, stvsubj_code, stvsubj_desc from gorguid, stvsubj where stvsubj_code = gorguid_domain_key and gorguid_ldm_name = 'subjects' and stvsubj_code = '' ROOMSSLBRDEFSLBRDEF_BLDG_CODE || '-^' || SLBRDEF_ROOM_NUMBER || '-^' || SLBRDEF_TERM_CODE_EF Fselect gorguid_guid,slbrdef_bldg_code, slbrdef_room_number,slbrdef_term_cod e_eff from gorguid,SLBRDEF where gorguid_domain_surrogate_id = slbrdef_surrogate_id and gorguid_ldm_name = 'rooms' and slbrdef_bldg_code = '' and slbrdef_room_number = '' and slbrdef_term_code_eff = '' ROOM-TYPESGORGUIDGORGUID_DOMAIN_KEY = 'C'Select gorguid_guid from gorguid Where gorguid_ldm_name='room-types' and gorguid_domain_key=; ACADEMIC-DISCIPLINES STVMAJRSTVMAJR_CODE || ^ || STVMAJR_TYPESelect gorguid_guid as GUID , to_char(STVMAJR_CODE || '^' || ) as DOMAIN_KEY from gorguid,STVMAJR Where gorguid_ldm_name='academic- disciplines' and gorguid_domain_key= to_char(STVMAJR_CODE || '^' || ) and STVMAJR_CODE = ; EMAIL-TYPESGTVEMALGTVEMAL_CODE Select gorguid_guid as GUID , gtvemal_code as DOMAIN_KEY from gorguid,gtvemal Where gorguid_ldm_name='email-types' and gorguid_domain_key=gtvemal_code and gtvemal_code = ; Domain Name Table NameDomain Key ColumnSQL Query /n 14Handbook |Globally Unique Identifier (GUID) LOCATION- TYPESSTVATYPSTVATYP_CODE Select gorguid_guid as GUID , stvatyp_code as DOMAIN_KEY from gorguid,stvatyp Where gorguid_ldm_name='location-types' and gorguid_domain_key=stvatyp_code and stvatyp_code = ; PHONE-TYPESSTVTELESTVTELE_CODE Select gorguid_guid as GUID , stvtele_code as DOMAIN_KEY from gorguid, stvtele Where gorguid_ldm_name='phone-types' and gorguid_domain_key=stvtele_code and stvtele_code = ; GRADE-MODESSTVGMODSTVGMOD_CODE Select gorguid_guid as GUID , stvgmod_code as DOMAIN_KEY from gorguid,stvgmod where gorguid_ldm_name='grade-schemes' and gorguid_domain_key=stvgmod_code and stvgmod_code =; SECTION-GRADE-TYPES GORGUIDselect gorguid_domain_key, gorguid_guid from GORGUID where gorguid_ldm_name=™section-grade- types™; GRADE-CHANGE- REASONSSTVGCHGSTVGCHG_CODE select gorguid_guid from GORGUID where gorguid_ldm_name=™grade- change-reasons™ and gorguid_domain_key=; CREDIT- CATEGORIES N/AN/Aselect gorguid_guid,GORGUID_DOMAIN_KEY from gorguid where gorguid_ldm_name = 'credit-categories' and GORGUID_DOMAIN_SURROGATE_ID = '' Domain Name Table NameDomain Key ColumnSQL Query /n 15Handbook |Globally Unique Identifier (GUID) DEPARTMENTSSTVDEPT STVDEPT_CODE select gorguid_guid,stvdept_code, stvdept_desc from gorguid, stvdept where stvdept_code = gorguid_domain_key and gorguid_ldm_name = 'departments' and stvdept_code = '' INSTRUCTIONAL -PLATFORMS GORINTGGORINTG_ INTEGRATION_ CDEselect gorguid_guid, gorintg_integration_cde, gorintg_desc from gorguid, gorintg where gorintg_integration_cde = gorguid_domain_key and gorguid_ldm_name = 'instructional- platforms' and gorintg_integration_cde = '' SUBTERMSOBPTRM SOBPTRM_TERM_CODE||' -^'||SOBPTRM_PTRM_COD Eselect gorguid_guid, sobptrm_term_code, sobptrm_ptrm_code from gorguid_guid, sobptrm where gorguid_ldm_name = 'subterm' and sobptrm_term_code = '' and sobptrm_ptrm_code = '' TERMSOBTERM SOBTERM_TERM_CODEselect gorguid_guid,sobterm_term_code from gorguid, sobterm where sobterm_term_code = gorguid_domain_key and gorguid_ldm_name = 'term' and sobterm_term_code = '' YEARSTVACYR STVACYR_CODE select gorguid_guid,stvacyr_code, stvacyr_desc from gorguid, stvacyr where stvacyr_code = gorguid_domain_key and gorguid_ldm_name = 'year' and stvacyr_code = '' Domain Name Table NameDomain Key ColumnSQL Query /n 16Handbook |Globally Unique Identifier (GUID) BUILDINGSSLBBLDG SLBBLDG_BLDG_CODEselect gorguid_guid, slbbldg_bldg_code from gorguid, slbbldg where slbbldg_bldg_code = gorguid_domain_key and gorguid_ldm_name = 'buildings' and slbbldg_bldg_code = = '' INSTRUCTIONAL -EVENTS SSRMEETSSRMEET_TERM_CODE || '-^' || SSRMEET_CRN || '-^' || SSRMEET_CATAGOR select gorguid_guid,ssbsect_term_code, ssbsect_crn from gorguid, ssrmeet, ssbsect where ssrmeet_surrogate_id = gorguid_domain_surrogate_id and ssbsect_crn = ssrmeet_crn and ssbsect_term_code = ssrmeet_term_code and gorguid_ldm_name = 'instructional- events' and ssbsect_crn = '' and ssbsect_term_code = '' PERSONSSPRIDEN SPRIDEN_PIDM select gorguid_guid, spriden_id, spriden_pidm, spriden_last_name from gorguid, spriden where spriden_pidm = gorguid_domain_key and gorguid_ldm_name = 'persons' and spriden_id = '' PERSON-FILTERS GLBEXTRGLBEXTR_APPLICATION || '-^' || GLBEXTR_SELECTION || '-^' || GLBEXTR_CREATOR_ID || '-^' || GLBEXTR_USER_ID Select gorguid_guid as GUID , GLBEXTR_APPLICATION || '-^' || GLBEXTR_SELECTION || '-^' || GLBEXTR_CREATOR_ID || '-^' || GLBEXTR_USER_ID as DOMAIN_KEY from gorguid,GLBEXTR Where gorguid_ldm_name='person-filters' and gorguid_domain_key= GLBEXTR_APPLICATION || '-^' || GLBEXTR_SELECTION || '-^' || GLBEXTR_CREATOR_ID || '-^' || GLBEXTR_USER_ID And GLBEXTR_APPLICATION = And GLBEXTR_SELECTION = And GLBEXTR_CREATOR_ID = And GLBEXTR_USER_ID = ; Domain Name Table NameDomain Key ColumnSQL Query /n 17Handbook |Globally Unique Identifier (GUID) SECTIONSSSBSECT SSBSECT_TERM_CODE,SS BSECT_CRN Select ssbsgid_guid, ssbsgid_term_code,ssbsgid_crn from ssbsgid where ssbsgid_term_code='' and ssbsgid_crn='' DIVISIONSSTVDIVS STVDIVS_CODE Select gorguid_guid as GUID , stvdivs_code as DOMAIN_KEY from gorguid,stvdivs Where gorguid_ldm_name='divisions' and gorguid_domain_key=stvdivs_code and stvdivs_code = ; COURSESSCBCRSE SCBCRSE_SUBJ_CODE,SC BCRSE_CRSE_NUMB,SCBC RSE_TERM_CODE_EFF Select scbcgid_guid ,scbcgid_subj_code,scbcgid_crse_numb ,scbcgid_term_code_eff from scbcgid a where scbcgid_subj_code=''and scbcgid_crse_numb='' and scbcgid_term_code_eff=(selectmax(scb cgid_term_code_eff) from scbcgid b where a.scbcgid_subj_code=b.scbcgid_subj_c ode and a.scbcgid_crse_numb=b.scbcgid_crse_n umb and scbcgid_term_code_eff<='') SECTION-REGISTRATIONS SFRSTCRSFRSTCR_PIDM,SFRSTCR TERM_CODE,SFRSTCR CRNSelect sfrrgid_guid,sfrrgid_pidm,sfrrgid_te rm_code, sfrrgid_crn from sfrrgid where sfrrgid_pidm='

Banner_Student_API_Handbook_9.5.pdf (174.2 KB)
Helpful?

Related Articles: