1. Service Description

External Webshop (or OCI Punchout or Roundtrip) is an SAP standard providing means to transfer data from supplier external catalog system to procurement systems.

Please note that Basware P2P supports only the html-variant of the SAP OCI, XML-variant is NOT supported.

Supplier needs to be contacted in 100% of the cases in order to secure the correct configuration; as the name says "External Webshop", it's administrated and maintained by the supplier.

1.1 Glossary of terms

Term	Meaning
OCI	Open Catalog Interface
DUNS	Dun & Bradstreet D‑U‑N‑S Number is a unique nine-digit identifier for businesses

1.2 Pre-requisites

Your order will be eligible for processing via the Service Catalog provided the request meets all the conditions specified in the checklist below. If the request does not meet all conditions, the order may be returned to you or it will be handled according to the standard Change Request process with a specified work estimate.

Service Catalog Checklist for Punch-out
1	Confirmation that the spend has been authorized (e.g. a Purchase Order)
2	The request does not include changes to the current organization hierarchy or enabling setup for Marketplace
3	XML Order Integration not included
4	Make sure the Supplier supports OCI HTML variant
5	Supplier sends details of OCI Catalog
6	Valid Marketplace setup must be completed for the customer
7	Supplier exists in the customer system (DUNS code optional additional data)

1.3 Deliverables (What you’ll get)

Your order will be completed and closed when the following deliverables are finalized:

• A punch out catalog created in Production as specified by the customer

In case you cancel an accepted order, or it is indefinitely delayed or by more than 3 months, Basware will close the order and invoice the work on a pro rata basis.

2. Customer Requirements

We’re committed to completing your order as soon as possible and to do this, we need you to observe all the stated requirements, including data and resources, at the stated or agreed timelines. If any requirement is incomplete, ambiguous or delayed, throughout any stage of the order, it will likely impact the delivery schedule and in some cases, result in additional costs.

If you’re not ready with all needed information and resources, we recommend you hold off placing your order until you’re ready.

2.1 When placing the order

When placing the order, we need you (the Customer) to observe the following requirements and provide all necessary information, documents and/or test data.

Requirements
1	Confirmation that the spend has been authorized (e.g. a Purchase Order)
2	Make sure the Supplier supports OCI HTML variant
3	Request the supplier sends details of the OCI catalog. Complete the Punchout catalog Form
4	Customer should provide details of which companies will be using the catalog
5	Possible custom fields need to be assessed (list out the custom fields, if required). Also list out standard fields Purchase Order Data files1 that includes the new company (if applicable)

2.2 When your order is accepted

Once your order has been accepted, you’ll be informed of when the new validation rules will be configured to your test environment, the target testing period and deployment date. To facilitate this, you’ll need to ensure the following resources are assigned and available to:

	Key Task/Responsibility	Resource type	When
1	Join planning and order confirmation meeting	Customer, Basware	Order acceptance
2	Co-ordinate responses to Basware queries as they arise (SPOC)	Customer or Basware	Build and testing
3	Deploy necessary changes to customer-controlled interfaces	Basware	Build and testing
4	Review and correct any integration issues	Basware	Build and testing

2.3 When your order is accepted

Once we’ve made the change to your test environments, we’ll confirm to you that it is ready for testing. You’ll need to mobilize your team to validate that the solution and services are acting as expected. As part of this, you’ll need to ensure the following resources are assigned and available to:

	Key Task/Responsibility	Resource type	When
1	Review and correct any validation issues	Basware	User acceptance testing
2	Perform end-to-end user acceptance testing for specified business scenario	Customer	User acceptance testing
3	Report issues with collected evidence	Customer	User acceptance testing

2.4 When your order is ready for production

Once you’ve completed your acceptance testing, we’ll be ready to move your change into production. As part of this, you’ll need to ensure the following resources are assigned and available to:

	Key Task/Responsibility	Resource type	When
1	Formally sign-off user acceptance testing and confirm deployment to production	Customer	Move to production
2	Confirm production deployment date	Customer	Move to production
3	Deploy necessary changes to customer-controlled interfaces	Basware	Move to production
4	Validate successful deployment to production	Customer	Move to production

3. Delivery Process

3.1 Implementation

Basware deliverables:

Activity Check-list
Basic Data Configuration
1	Name - Descriptive name for the external webshop configuration
2	Organization - Organization where external webshop is created​
3	Inherit - Is the configuration inherited or not
4	Set as Marketplace - Yes only if Basware Marketplace configuration
5	Price Type - Net or Gross
6	URL - supplier's webshop address
7	Username - supplier will create a unique username for each customer
8	Password - supplier will create a unique password for each customer
9	HTTP method - defines how the inbound/calling user is authenticated to external webshop GET: adds the username and password in the URL POST: generates a html form which is sent in the background hidden from the user
Outbound Fields
10	​~OkCode - ADDI
11	~caller – CTLG
12	~target - _​top (this means that the external webshop connection opens in the same browser window, currently hardcoded and _parent value NOT supported)
13	HOOK_URL - return URL to P2P, this is the address where external webshop returns the data
Inbound Fields
14	Inbound Field Mapping

Basware deliverables:

• A punch-out OCI catalog

Customer activities:

• Provide requested details
• Respond to queries related to Supplier/Catalog from Basware

3.2 System Testing

Basware deliverables:

• Testing Catalog

Customer activities to be completed:

• Respond to queries related to configuration from Basware

3.3 User Acceptance Testing

Basware deliverables:

• Confirm test environment is ready for UAT
• Issues identified during UAT have been resolved, providing they meet the original scope of the order
• Support provided to Customer during the agreed 1-week period

Customer deliverables:

• Test that purchases can be made for the new catalog, considering specific customer scenarios
• Add supplier in specific company
• Report issues in the agreed tool
• Signed User Acceptance form, stating that the solution works as expected and is ready for production use
• Confirmed date to move changes to the production environment

3.4 Move to Production

Basware deliverables:

• Migrate changes to production environments
• Provide hypercare support for 1 week

Customer deliverables:

• Confirmation the new catalog has been added to production environments successfully

4. Assumptions 

• The Supplier supports OCI HTML variant

5. Out of Scope 

• Any activity that has not been specified throughout this service description