SCT Banner Finance / Release Guide / 7.0

More documents

Recommendations

Info

Section 4 E-procurement Enhancement - FunctionalIntegration between HigherMarkets and Banner• Ship to code (FTMSHIP)• Vendor/supplier identification (FTMVEND, FOATELE, FOAIDEN)• Vendor address (FTMVEND, FOAIDEN)• Vendor phone numbers, including FAX (FTMVEND, FOATELE)Note: Synchronization only occurs for vendors specified as e-procurementvendors on the Additional Information window of the VendorMaintenance Form (FTMVEND).Defining Data Elements on GURMESGTo implement this synchronization, you must define the preceding data elementson the Banner Message Aware Entities Rules Form (GURMESG). This BannerGeneral form contains the names of the entities that may be message-enabled. Youwill need to select entities for message enabling to correspond with the integrationpoint chosen by your institution.Synchronizing Data or using Mass LoadAs you begin your implementation, you can synchronize Banner data withHigherMarkets by modifying any of the Banner data elements from the precedinglist. The messaging components then publish a message, requesting thatHigherMarkets create, update, or delete the relevant data.You may prefer to perform a "mass load" of data into the HigherMarkets database.After initial values are loaded into HigherMarkets, the updates to the Banner formsin the preceding list will update the values in HigherMarkets and keep the twosystems synchronized.Using the HigherMarkets Shopping CartHigherMarkets is a browser-based, hosted software solution that faculty and staff atyour institution may use to initiate purchases.Users of HigherMarkets software select product items from Higher Markets’extensive on-line catalog and add them to a shopping cart.Note: The HigherMarkets user always initiates procurement activities using theshopping cart interface, no matter which integration point isimplemented at your institution.The shopping cart contains supplier information, product information, catalognumber, quantity, unit price, and free form text. It may also support accountingdistributions, commodity codes, or ship-to information. Due to the synchronizationFinance Release 7.0 January 200546 Release Guide Confidential
Section 4 E-procurement Enhancement - FunctionalIntegration between HigherMarkets and Bannerof data between Banner and HigherMarkets, much of this information is consistentwith Banner values.Note: Currently, the integration with the external system does not includediscount, additional amount, or taxes.When a HigherMarkets user completes the shopping cart, messaging componentsmove the data from the HigherMarkets shopping cart to Banner Finance. Thecreated requisition or purchase order is validated by the API to include all requiredfields enforced in the Banner document. The API will take values supplied by theHigherMarkets user when creating the shopping cart, such as commodity codes,document text, and item text, or it will use information that defaults from theBanner user’s profile, such as organization code or ship code.Note: Free-form text may appear in Banner as either document level text oritem text.Communicating Data between Banner and HigherMarketsThe messaging layer in conjunction with the Banner APIs handles thecommunication of key data back and forth between HigherMarkets and BannerFinance. The Banner APIs confirm that the HigherMarkets user is an authorizeduser in Banner, check the user’s fund/organization security privileges, and alsocheck budget availability for items to be purchased.Requisitions and Purchase Orders• As part of the integration, a document containing product items from theshopping cart is created in Banner via the Requisition or Purchase Order API.The document is created with commodity level accounting and is marked as acompleted document after it passes validation. HigherMarkets provides foraccounting splits (multiple accounting distributions for a product item). Formore information, please refer to your HigherMarkets documentation.• If your integration is at the requisition level, you can process a Banner e-procurement requisition as you would any requisition created manually by oneof your users. This includes the option to route these e-requisitions throughthe Finance approvals process. You must then perform buyer assignment,assign items to a purchase order, and perform other procurement processing.• The APIs will enforce similar business logic used by the FPAREQN orFPAPURR forms in Banner. Accounts used include General Ledger,Expenditure, or Transfer.• If the document is disapproved or fails the posting process, Banner will cancelthe document and specify a reason code of EPCN. Documents are retained inthe requisition or purchase order tables but are marked with a status of“cancelled” and do not exist in the transaction history or detail tables.January 2005 Finance Release 7.0Confidential Release Guide 47
Page 1 and 2: SCT BannerFinanceRelease GuideJanua
Page 3: Tropical Texas Behavioral Health Ju
Page 7 and 8: Table of ContentsSection 9 Problem
Page 10 and 11: IntroductionRelease Contents Releas
Page 12 and 13: Section I New User Interface - Func
Page 16: Section I New User Interface - Func
Page 23 and 24: Section 2 New Banner Online Help -
Page 29 and 30: Section 3 Common Matching - Functio
Page 43 and 44: Section 4 E-procurement Enhancement
Page 45: Section 4 E-procurement Enhancement
Page 55 and 56: Section 5 1099 Enhancement - Functi
Page 57 and 58: Section 5 1099 Enhancement - Functi
Page 59 and 60: Section 6 Common Matching - Technic
Page 65 and 66: Section 8 Miscellaneous Enhancement
Page 85 and 86: Section 9 Problem ResolutionsAccoun
Page 87 and 88: Section 9 Problem ResolutionsBudget
Page 89 and 90: Section 9 Problem ResolutionsGenera
Page 91 and 92: Section 9 Problem ResolutionsOperat
Page 93 and 94: Section 9 Problem ResolutionsPurcha
Page 95 and 96: Section 9 Problem ResolutionsStores
Page 97 and 98:
Section 9 Problem ResolutionsAPIs(#
show all

SCT Banner Finance / Release Guide / 7.0

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?