Show TOC

Object documentationPOS Browser

 

SAP POS supports the launching of a Web browser session at the POS to access customer information or other information located in third-party databases.

Note Note

To use the Web browser functionality, a mouse or touch screen capability must be available at the POS. The Web browser component is installed during the installation process.

End of the note.

 

You configure Web browser parameters to allow the POS to access sites on your internal network, or to provide cashiers with quick access to store or product information. You can control the browser functions and accessible sites through manager codes and profile prompts, which you set up in the Configurator application.

Note Note

A range of manager codes from 751 to 800 have been reserved for URL addresses. Each defined manager code can access one site. For information on manager codes see Manager POS Functions.

End of the note.
Configuring POS Browser settings

To enable browser access at the POS, you must carry out the following configurations.

  • In POS Browser configuration, define a URL for each web site the POS browser is allowed to access (each one should be a distinct Browser ID.)

  • For access to web sites where information must be entered to launch a query, create a profile prompt to capture this information at the POS. See Profile Prompts for information on setting up a profile prompt.

  • Create a manager code using a value in the 751 to 800 code range for each location the POS browser can access and, if required, link it to the profile prompt set up for the URL address.

Defining the URL for each required POS browser event

  1. Type the URL (Uniform Resource Locator) address for the web site the POS browser can access.

  2. In the Suffix/Data field, type the required string to access the specified web site. This is required to initiate searches or lookups for specific information.

    Note Note

    To specify a GET method, use a ? (question mark character) at the beginning of the string. No question mark is required for POST method requests.

    End of the note.

    The POS automatically incorporates the profile prompt responses entered at the POS to the Suffix/Data field and launches the look-up. To allow the system to recognize the responses, you need to set up name-value pairs showing the names of all the fields that can be queried in the source database. You then set the number of the line in the profile prompt that corresponds to the response. This links the prompt response to a specific field in the source database.

    Example Example

    If the first line in the profile prompt asks for the color of an item, and the field containing information on color in the source database is called i_color, construct the string in the suffix/data field as follows:

    For a GET request:?i_color=%1

    Subsequent name-value pairs are separated by an & as follows:

    ?i_color=%1&i_size=%2

    End of the example.

    The following is a list of control identifiers you may use to define the suffix field for a Total Browser ID. This passes the sub total amount to the browser HTML page as a parameter.

    %N

    Store number

    %R

    Terminal number

    %C

    Customer number

    %S

    Sub-total (excluding Non-Merch and Tax amounts)

    _%P_

    Configured secure data

  3. If a password is required for access to a specific web site or database, type this in the Secure Data field. The POS incorporates the captured information from this field into the Suffix/Data field when you insert the _%P_ string into the Suffix/Data field. The system replaces the value of the _%P_ field when the HTTP request is sent.

  4. You can select any of the following navigation buttons to display on the browser window:

    • Back

    • Forward

    • Print

    • Allow Select Printer

    • Cancel — This option displays a Cancel button when the Web browser is displayed. No data is extracted.

  5. In the Data Element column, you can select up to nine elements from the list to configure a customer look up and then provide the name of the Embedded Tag the POS must seek in the third party database. At the first occurrence of the tag, any alpha-numeric string following the tag is extracted from the page and used as extracted data.

    The following table shows the Data Element options and their maximum field lengths:

    Data Element

    Description

    Maximum field length for Embedded Tag

    webCustNum

    Customer ID

    14 alpha-numeric

    webFirstName

    Customer first

    40 alpha-numeric

    webLastName

    Customer last

    20 alpha-numeric

    webAddress1

    Customer Address

    40 alpha-number

    webAddress2

    Customer Address

    40 alpha-number

    webCity

    City

    20 alpha-number

    webState

    State

    10 alpha-number

    webZip

    Zip

    10 alpha-number

    webPhone

    Phone

    10 numeric

  6. Specify the type of the Web request for the definition by selecting the appropriate option in the URL Type list.

    • A Regular request refers to a simple request for access to a specified web page.

    • A Login is a request to gain access to a secure web site or to a database. The request can be set to occur automatically without any user intervention. To do this, set up a separate URL definition for the login. Specify Login in the URL Request Type field, and reference this definition number in the Login URL ID field of the definition, which contains the main request details. If you want to set up the Login request to occur automatically, do not link it to a profile prompt. Use a profile prompt only if you want the login request to occur through a manager code.

    • A Logout is a request to leave a secure site or database. This request can be set to occur automatically without any user intervention. (See login request for details on how to do this but substitute logout values wherever login is referenced.) If you are setting this up to occur automatically, do not link it to a profile prompt. Use a profile prompt only if you want the logout request to occur through a manager code.

  7. If required, specify the HTTP Request Method by clicking the appropriate option in the drop down list.

    • A GET request method is usually used in requests for web pages.

    • A POST request method is usually required for web pages which contain forms.

  8. For requests to secured web sites that require a log in before access can be granted, type the URL ID number of the log in URL ID definition, which completes the log-in process.

  9. For requests to secured web sites that require a logout to leave the site, type the URL ID number of the logout URL ID definition, which completes the logout process.

Accessing Sales Order Processing

To enable the POS to access the Sales Order Processing functionality, set the Sales Order Processing parameter to Enable. See Using SAP POS for Sales Order Processing for information on how to configure Sales Order Processing.