User-defined mapping of information

This feature provides a measure of user-configured mapping of shopping session data into your Lawson Requisition. These mappings are vendor-specific, meaning you can specify different mappings for different Punchout vendors. Conversely, if you want the same mapping instructions to apply to more than one vendor, you are required to put the instructions into each relevant vendor section of the RQC configuration file.

  1. Open the rqc_config.xml file with a text editor.
  2. Find the <vendor> section for the vendor for which you are mapping data.
  3. Add the <mapping> tag within the <vendor>. An example of a completed tag is as follows: 
    <mapping source="Classification" fromField="UNSPSC" 
toField="UFQ_RQ_USER_FLD_05"</mapping>

    Use this information to define mappings for your specific implementation.

    Attribute name Value Description
    Source Any message-level XML element name Name of XML element containing data of interest. The 'Classification' and 'Extrinsic' elements are the most frequently used elements to convey information related to an item.
    fromField

    Specify the XML attribute which qualifies the data of interest.

    If the element has no attribute, put the "*" (Asterisk) character to match "Any or no attribute value" at runtime.
    toField For more information on acceptable 'toField' values, see LineDataBean_fields.txt Name of requisition field to hold the data of interest.

    Example

    A vendor is sending you information in the PunchoutOrderMessage document, in an XML element named <Classification> . You want to extract the value that element contains and place into your Lawson requisition into the UFQ_RQ_USER_FLD_05 field. The sample data below contains several elements named <Classification>.

    <Classification domain="SPSC">41122100></Classification>
    <Classification domain="UNSPSC">41122100></Classification>
    <Classification domain="Radioactive">false</Classification>

    Notice that there is an attribute called 'domain' in each <Classification> element. The value of the domain specifies what the <Classification> value is, such as "Toxin", "Radioactive", etc. In this example, we are interested in the one which tells you if the material is radioactive or not. The mapping for such an element would be as follows:

    <mapping source="Classification" fromField="Radioactive" 
toField="UFQ_RQ_USER_FLD_05"></mapping>

    Given this input, the mapping statement would yield the value of "false" and place it into the Lawson requisition field named UFQ_RQ_USER_FLD_05.

    Note: Results can be unpredictable if you place data into a field that doesn't match the expected type. For example, if you chose for your ‘toField’ RLN_USER_DATE_3, the mapped data must be a date, adhering to the Lawson rules for a DATE field.
  4. Save and close the configuration file, then reload the configuration using the Requisition Center utilities page.