B2B Parameters {GCS2-18}

Parameters that will be used between the institution and Business to Business (B2B).

During the install, scripts will populate information this table.  These parameters are crucial for the correct functioning of the e-Procurement System as well as any of the other B2B products.  If any changes are needed or if errors occur, please consult ITS on the matter before changing any information here.


Fields in the option:

Block 1:  B2B Parameters

Field Type
&
Length		 Description
Code A8 The code of the supplier, as populated by ITS.  Current codes are:
  • MM - mymarket
  • BULKSMS - Bulk SMSs
  • NSFAS - NSFAS Interface
  • NSFINT -  Provisionally Funded.
  • VHW and VWIRE - vWire credit card interface
  • MOE - MoE Interface
Function A16 The function is populated by ITS and is tied into the code specified above.  For each of the codes specified, the following functions exist:
  • MM
    • CA - Catalogue
    • CL - Catalogue List
    • CO - Cancel Order
    • CP - Catalogue Process List
    • FO - Follow Up Order
    • SO - Send Order
  • BULKSMS
    • SEND - Send the SMS
  • NSFAS
    • GENIRA - Generate request
  • NSFINT 
    • PRVFND - Provisional Funding
    • REGCST - Registration Costs
  • VWH and VWIRE
    • SP - Send Payment
  • MOE
    • ARRIVALS - Student Arrivals
    • CT - Connectivity Test
    • DEX - Access Control at the MoE Data Exchange Control Server
    • LEAVERS - Student Leavers 
    • ROLLRETURN - e-Return
    • SRTBULKNSN - Bulk Search
    • STRDOWN - SRT Download
    • SRTUPL - SRT Upload
Parameter Type A16 The type will indicate the operation of the system: must information be received or sent.
Parameter Name A16 The parameter name is used when generating pairs of data that are to be included in the transmission of the request.
Parameter Value A512 The parameter value is used in conjunction with the parameter name.
Sequence N5 The sequence of this parameter name:value pair within the parameter type.
Reference Type A8 This field is populated by ITS.  The valid values are:
  • V - Where value gets parameter value
  • E - An XPATH expression is to be used to get the value required from the XML in use.

Example:

Example of gcs2-18

 


Processing
Rules		  
  No special processing rules.


See Also:   om_epayments.html



History of Changes

Date System Version By Whom Job Description
23-Jul-2007 v01.0.0.0 Amanda Nell t141898 New manual created
12-Mar-2008 v01.0.0.0 Vaughn Dumas t141898 System owner proof read
10-Sep-2008 v01.0.0.0 Charlene van der Schyff t152060 Edit language obtained from proof read language Juliet Gillies.
29-Oct-2009 v01.0.0.1 Charlene van der Schyff t160044 Update manual with epayment link.
17-Mar-2011 v02.0.0.0 Bea Swart t180429 Add new Code and Functions for MoE (Ministry Interface)
27-jun-2017 v03.0.0.0 Charlene van der Schyff t221814 Added Code and Functions for NSFINT.