Overview/Introductions:
This article describes the Banner/ESM eProcure integration and ESM Configuration settings. The article should give an overview of the related components to convey an understanding of this application.
Details:
Ethos/Banner Integration
ESM Subscriber
- This element contains the API Subscriber Key, which is shared (securely) with the Ethos integration partner.
- A custom user ESM_API_CLIENT has been established with appropriate security for the Banner/Ethos objects
- Integration API
- Student Api
- Lastly, Resource Subscriptions are established based on the partner Ethos API specifications.
Banner Ethos Configuration (GORICCR)
Default value and field mapping is configured either via the Banner Admin Page (GORICCR) or via the Ethos API Management Center Application.
EXPAND AS DESIRED NECESSARY
Custom Banner Integration (FWPIESM)
While the Ethos Integration is established to pass transactional information from ESM to Banner, there is certain Master Data management that is not passing data from Banner to ESM and requires files to be sent to ESM via SFTP.
Run Type (Parameter 01)
| AC - Accounting Codes |
FOAPAL information sent to ESM. |
| SU - Suppliers |
Supplier information sent to ESM (once ESM Supplier is live this will not be required and ESM will send data to Banner via Ethos). |
| US - Users |
User information sent to ESM. Certain User Profile data, such as Delegate and Cart Routing Email, can be updated by each ESM user. This also uses certain Banner FOMPROF data for security settings. |
| WF - Approval Workflows |
Banner Requisition Workflows sent to ESM, based on Banner configuration which has the benefit of FOAPAL hierarchy logic. |
- Cart User Email (Parameter 06)
This parameter contains a default email address for ESM Cart Users that have not defined their own Cart User routing.
ESM Configuration
Auxilary Fields (Eight Implementation defined Custom Fields)
| Aux 1 |
Co-Op Contract - Not Currently Used |
| Aux 2 |
Co-Op Description - Not Currently Used |
| Aux 3 |
Receipt Type |
| Aux 4 |
PRF Number |
| Aux 5 |
Property Tag Req'd? |
| Aux 6 |
Procurement Analyst |
| Aux 7 |
N/A |
| Aux 8 |
N/A |
Entity Settings
Workflows (ESM Layers on top of Banner)
NOTE: These layered workflows will contain User pointers that are NOT maintained by the nightly feed from Banner and WILL need to be manually changed as these assignments become invalid or should change.
- GT100K - Specific to transactions greater than $100,000
- GT250K - Specific to transactions greater than $250,000
- PURC - Last workflow entry for Procurement approval
- CCINCREASE - Credit Card transactions above a threshold for a temporary increase in card limits
Transaction Validation
| CATALOG_PO |
|
| CC_RECEIPT_TYPE |
 |
| Item Tag No But Accounts |
 |
| Non-Catalog PO @ Release |
 |
| P-Card Over 10K example |
 |
| PCard Controllable Item |
 |
| PCARD_SUPPLIERS |
 |
| PO Procurement Analyst |
 |
| PO_RECEIPT_TYPE |
 |
| SourceTransmission |
 |
| Tax Code Required |
 |
| Uncertain Controllable |
 |
FAQ:
See also:
If this article still does not answer your question, please submit a Service Request. <<Link>>