Editing Punchout information in rqc_config.xml

You should find a file named punchout_config.xml in the same directory as $LAWDIR/system/rqc_config.xml. We recommend that you copy information from punchout_config to rqc_config, then modify the values in rqc_config.

Update settings in rqc_config.xml

  1. Open the $LAWDIR/system/punchout_config.xml file with a text or XML-aware editor.

    This file contains templates for your company ("<buyingOrg>") and templates for certain punchout-enabled vendors ("<vendor>" sections).

  2. Find the section that starts with the <buyingOrg> tag.
  3. Copy the entire <buyingOrg> section.
  4. Open the rqc_config.xml file with a text editor.
  5. Paste the <buyingOrg> section into the rqc_config.xml file.

    There is a placeholder <punchout> tag at the end of the RQC configuration file, after the <server> tag. The order of tags in the file should now be:

    <rqc>
			<server>
			</server>
					<punchout>
							<buyingOrg>
							</buyingOrg>
        <vendor A>
								</vendor A>
								<vendor B>
								</vendor B>
					</punchout>
</rqc>
  6. Edit the buyingOrg tag information.

    This is the element that defines the information about your company. The BuyingOrg section, as delivered, should look similar to this:

    <buyingOrg name="LawsonSoftware">
	<setting name="eMailDomainName" id="" value="yourdomainName.com"/>
	<setting name="From" id="DUNS" value="0123456789" />
	<setting name="Sender" id="DUNS" value="0123456789" />
	<!--setting name="Sender" id="NetworkId" value="LawsonSoftwareInc." 			/-- Another example>
	<setting name="remotePunchOutServer" id="remotePunchOutServer" 
			value="http://your remote Punchout server:port" /><setting name="deploymentMode" id="deploymentMode" value="test"/>
  7. Specify your company's name in the "name" attribute for the BuyingOrg, replacing "LawsonSoftware."
  8. Verify that these required settings are defined within the BuyingOrg. You should not need to modify any other existing settings within the BuyingOrg.

    Note that you and the vendor agree upon the From/To/Sender/Shared Secret values.

    This table lists the required settings within the BuyingOrg:

    Setting name Value Description
    eMailDomainName your organization's email domain Specify your organization's email domain name (the part following the '@' sign) into this element. It becomes part of the "payload" identification of Punchout-related transactions.
    From id

    Specify the type of identifying number you are using. If you are using a DUNS number, then use id="DUNS".

    Id="NetworkId" and id="MutuallyDefined" are commonly used alternatives.
    value Change "0123456789" to an actual DUNS number or other identifying value.
    Sender id

    Specify the type of identifying number the sender is using. If it is a DUNS number, then use id="DUNS".

    Id="NetworkId" and id="MutuallyDefined" are commonly used alternatives.

    Note: This information is usually the same as the "From" information, but can be different.
    value Change "0123456789" to an actual DUNS number or other identifying value.
    remotePunchOutServer id Do not change.
    value Specify the location of the punchout server, such as http://your remote Punchout server:port.
    remotePunchoutServlet Do not change.
    SaveCart Do not change.
    GetCart Do not change.
    deploymentMode

    "test"

    or

    "production"

    		 Flags the document as test or production mode. This setting can be specified at the buyingOrg or vendor level. The default value is test.

    After you make changes, the configuration of the <buyingOrg> is complete.

  9. Define as many vendors as required in the punchout section.

    The vendor section defines the information about other companies with which you do business. At least one vendor must be defined to use the punchout feature. Templates for many, but not all, vendors that Lawson has worked with in the past can be found in "punchout_config.xml", which is found in either the "assembly" directory, or in $LAWDIR/system. These templates are meant to be copied to the RQC configuration file and edited to suit your site-specific requirements. 

    <vendor name="DellPunchout">
	<setting name="DellPunchout" id="URL" 
                 value="https://b2bpreview.dell.com/invoke/B2BDirect.Entry/processDocument"/> 
	<setting name="To" id="DUNS" value="128293714"//>
	<setting name="From" id="NetworkId" value="delllawsontest"/>
 <setting name="Sender" id="NetworkId" value="0123456789"/>
 <setting name="Password" id="SharedSecret" value="LawsonT"/>
</vendor>
  10. Specify a unique value for the "name" attribute for the <vendor> element, such as "DellPunchout" in the example.

    The value that is specified must match the user group name that you defined on Punchout User Group (ED41).

    Use this same value/name for the "name" attribute of the <setting> attribute, where the id attribute value is "URL."

  11. Verify that these required settings are defined for each vendor.
    Note: These values, when delivered, represent what was given to Lawson at one time for development purposes. They can be used to verify general functionality of Procurement Punchout, but keep in mind these were temporary IDs that may not work at the time of your testing.

    This table lists the required settings for vendor:

    Setting name Value Description
    vendor name name name of vendor, same as on Punchout User Group (ED41)
    value

    URL supplied by the vendor to access the vendor server

    If the URL contains any of these characters: > (greater than), < (less than), & (ampersand), " (quote), and ' (apostrophe), you are required to use the corresponding URL-encoded forms of the characters:

    &gt; represents >

    &lt; represents <

    &amp; represents &

    &quot; represents "

    &apos; represents '
    To id

    Specify the type of identifying number for the vendor.

    Typically DUNS (Data Universal Number System) numbers are the preferred way to uniquely distinguish business parties. If either party does not have an assigned DUNS number, then typically a different value for id="DUNS" is used, the value of which can be decided between the two business parties.
    value Change to match the vendor's identifying number.
    From id If a value different from that which is set up in the <buyingOrg> From id is required, then set it here.
    value If a value different from that which is set up in the <buyingOrg> From value is required, then set it here.
    Sender id

    If a value different from that which is set up in the <buyingOrg> Sender id is required, then set it here.

    Note: This information is usually the same as the "From" information, but can be different.
    value If a value different from that which is set up in the <buyingOrg> Sender value is required, then set it here.
    Password id Specify an identifier for the password. For example, "SharedSecret" is commonly used.
    value Specify the actual password that is agreed upon by you and the vendor.
    DOCTYPE value

    Supplying a value will override the default cXML.dtd that is referenced from xml.cxml.org.

    A blank value (value="") will bypass the dtd validation. Otherwise, you can reference a local copy of the cXML.dtd. ex. <setting name="DOCTYPE" value="http://my.server.com:8080/dir/cxml/1.2.017/cXML.dtd"/>.

    The value reference must be a URL protocol, if not left blank.
  12. Save and close the configuration file, then reload the file using Infor Lawson Requisition Center Utilities menu.