B2B: How iProcurement Uses XML to Offer Multiple Catalog Products to Users, 13 of 16

B2B: How iProcurement Uses XML to Offer Multiple Catalog Products to Users, 13 of 16

Sending Selected Item to iProcurement: External Catalog's HTML File Format

This is the HTML format used to send selected items from the external catalog to iprocurement:

<HTML> 
  <BODY onLoad="document.orderForm.submit()"> 
  <FORM ACTION="URL of the Web Requisitions" METHOD="POST"  
    NAME="orderForm"> 
    <INPUT type="hidden" name="REQ_TOKEN" value="Requisition token"> 
    <INPUT type="hidden" name="NO_OF_DATA_SEGMENTS" value="N"> 
    <INPUT type="hidden" name="ITEM_XML_DATA1" value="First data segment">
    <INPUT type="hidden" name="ITEM_XML_DATA2" value="Second data segment">
........
    <INPUT type="hidden" name="ITEM_XML_DATAN" value="Nth data segment">
  </FORM> 
  </BODY> 
</HTML>

HTML Elements Explained

Table 10-12 lists HTML elements grouped under their corresponding HTML tag names.

Table 10-12 HTML Elements

HTML Element	Format	Description
<BODY>	onLoad="document.orderForm.submit()"	Provides HTTP redirect from client browser to iProcurement.
<FORM>	ACTION="URL of the Web Requisitions" METHOD="POST" NAME="orderForm"	Action attribute of the orderForm should be set to the URL that is provided by Self-Service Purchasiing. Form submit type. Name of the form that is submitted.
<INPUT>	<INPUT type="hidden" name="REQ_TOKEN" value="Requisition token">	Creates a hidden form element for Requisition Token. This token is sent to the 3^rd party catalog provider after a successful authentication process and, without change, is sent back to iProcurement. It contains internal system-related data.
	<INPUT type="hidden" name="NO_OF_DATA_SEGMENTS" value="N">	Creates a hidden form element to send number of data segments that is transferred between two systems. The value N should contain the number of ITEM_XML_DATA form elements.
	<INPUT type="hidden" name="ITEM_XML_DATAN" value="Nth data segment">	Creates a hidden form element to transfer a data segment. The data segments are formed by dividing the XML file into smaller portions. The setting for the size of each segment should be a variable. Current recommended value for this variable is 2000 characters. The last character of the name determines the index of the corresponding data segment. The index starts from 1 and is increased by one up to NO_OF_DATA_SEGMENTS value N.

iProcurement Example 11: HTML/XML File

This example uses the HTML elements defined in Table 10-12.

<HTML> 
  <BODY onLoad="document.orderForm.submit()"> 
  <FORM ACTION="http://ap411sun.us.oracle.com:9999/OA_JAVA_  
SERV/wp4/integrate/apps.Order" METHOD="POST" NAME="orderForm"> 
  <INPUT type="hidden" name="REQ_TOKEN" 
value="template=tpn,action=addLines,function=addToOrder,por_req_session_
id=1,......"> 
  <INPUT type="hidden" name="NO_OF_DATA_SEGMENTS" value="2"> 
  <INPUT type="hidden" name="ITEM_XML_DATA1" value="<?xml   
version='1.0'?><OrderLinesDataElements><catalogTradingPartner><![CDATA[ABCCatalo
gServices]]></catalogTradingPartner><orderLine>....."> 
   <INPUT type="hidden" name="ITEM_XML_DATA2"  value="
.....
</orderLine>
  <orderLine>
    <contract
..... 
</OrderLinesDataElements>"> 
</FORM> 
</BODY> 
</HTML>