Punchout Options - SAP (OCI) Configuration

 

The following configuration steps are required for setting up a SAP punchout.

You must be a SuperAdmin to access the "Punchout Options" admin.

Click "Punchout Options" under the Additional Modules menu to create a new punchout.

OCI punchouts are uncommon at this point. Each OCI punchout record will need to be addressed individually. Contact Aldrich Web Solutions for support.

Add a new Punchout Code

Add a new Punchout Code

Click "Add a New Punchout".

Enter the punchout details

  1. Click the "Enabled" checkbox.  This box will allow you to disable a specific punchout without deleting the punchout configuration.
  2. Enter the "Punchout Name".
    • This will be provided to the business partner for use as their login.
    • The name should be one that will be useful in identifying who the punchout is used for.
  3. Enter the Customer Code that represents the pricing you want the user of the punchout to see.
  4. Enter a "Shared Secret".
    • The Shared Secret can typically be any set of alphanumeric values.
    • Be sure to note the secret code so that it may be shared with your business partner.  Your business partner will use this for their password.
  5. Select "Oci" as the "Punchout Type".  This is the method in use for SAP.

Once you have configured the punchout, click "Save".

Punchout Setup Complete

At this point, the punchout setup is complete.

You should provide the Shared Secret to your business partner.

You should also confirm that the identity they will send from the SAP network corresponds to the Punchout Name you have configured for the punchout.

Activity Logs show you punchout attempts

The "Activity Logs" can be found under the Stats menu in the site Admin panel.

  1. From the log, you can see the identity provided by the SAP network. 
    • If this identity does not match a Punchout Name you have configured and enabled, then the login will fail.
    • This information is useful to find a mismatch between the identity you expect to receive and the identity information you actually receive for a punchout.
    • If there is an identity mismatch, you should either change the Punchout Name in the Punchout Configuration or have your business partner change the Identity information in their SAP configuration.
  2. The Shared Secret entry indicates whether or not the Shared Secret was a match.
    • If the Shared Secret is a match, then the value is hidden.
    • If the Shared Secret sent by your business partner does not match the Shared Secret configured for a punchout, then the Shared Secret will be shown.
    • If there is a Shared Secret mismatch, you should either change the Shared Secret in the Punchout Configuration or have your business partner change the secret in their SAP configuration.

Punchout Customer Access Codes

For every punchout that is created, WebAlliance also creates a corresponding Customer Access Code. These codes have expiry dates. Codes passing their expiry date is one of the most common reasons that a customer cannot access their punchout site. To learn more about, please examine our documentation regarding Customer Access Codes.