The installed Connector will have this interface with the possibility to map / adjust the data.
With the introduction of the template to a new SAP environment a set of default or customizing values needs to be maintained to enable the web services.
Explaining the values
This table is used in all interfaces as it contains general settings for different interfaces. The fields in this table describe the most important fields which are used for this eCommerce platform.
|Values||Technical explanation||Business explanation|
|Website id (KEY)||
unique identifier for the eCommerce Platform which is supplied in each web service request and response
An eCommerce platform may consist of multiple websites. Each website will have its own ID.Website ID is a key field in the Ybite3_VDefault table. For each website ID, the fields in the Ybite3_VDefault can be configured.
|Price vis.||not used; field PRAT9 of table MVKE* determines the price visibility||
This field determines if you show prices of individual products on the eCommerce platform.• Showing prices is boolean, true or false. In SAP terms checked or not.
|Cust Type||value P(artner) or C(ontact) indicating respectively the use of a partner role objects as contact persons or an actual contact person objects as contact persons.||
SAP can handle contacts within a company as either 'contacts' or a 'partner'.
A customer of an eCommerce platform normally has one admin contact who can do everything, but there might be colleagues who should only be able to check invoices / orders, if this is the case you can give them certain roles like assistant buyer, buyer, administrative etc.
Setting up customer roles via partner type is complex, via contacts is easier.
It is also possible manage the contacts and roles in your eCommerce platform.
|Company Code||not used|
|Fld web||field name from table MARA* used for web enabled indicator of product||
Identify a field in MARA which indicates if a product should be displayed at the eCommerce platform. Web enabled=1 not web enabled=0. If a product is not web enabled, it won't be available in the eCommerce platform after importing the data.
|Hide catalog||field name from table MVKE* used for product visibility in the eCommerce platform catalog||
Identify a field in MVKE which indicates if a product should or shouldn't be visible in the default catalog of the eCommerce platform. Visible =1 not visible =0For example: certain products should be enabled on the eCommerce platform, but should not be visible in the default catalog because they only should be available in the my products list (which is generated by SAP) or should only be available for certain customers.
|Fld web||field name from table KNA1* used for web enabled indicator of customer||
Identify a field in KNA1 which indicates if a customer (or contact when contact is used as a type Cust Type) is web-enabled (can be served/order online via the eCommerce platform). Web enabled =1 not web enabled =0.
|Sales Org.||default sales organization||
If you create a new customer in the eCommerce platform, it will be send to SAP. The Connector needs to make sure that this new customer is assigned the correct sales organization from your organization. We need to create a custom logic for this in SAP. A default sales organization is meant for assigning new customers to this “default” sales organization if no other sales organization is set. We can either use the default sales organization or we can add the sales organization to the customer data.
If the sales organization is not defined in the call setCustomer, the field 'default sales organization ' will be used. It's possible to have a different sales organization in the setCustomer call per website.
|Distr. Channel||default distribution channel||
Distribution channel is mainly defined to take care of different types of sales in a sales organization. You can define a distribution channel for direct sales, internet sales, sales through dealers etc. This field indicates which distribution channel is used by default. If a distribution channel is not defined in het call setCustomer, the field 'default distribution channel' will be used.
Quite similar as 'Default sales organization' & 'Default distribution channel'
If the division is not defined in het call setCustomer, the field 'default division' will be used.
|Account Group||default account group||
This field is meant to define to which account group a customer belongs.
In an eCommerce platform, a new account can be created (New customer). To set this customer as new customer, you can add the value "default customer'; this field is used to assign a template for a customer which is used when you create a new customer. This template is used to fill in default fields from SAP which are necessary when you create a customer.
|Sales Group||sales group in order creation||
Identify one sales group which should be used when an order is created.
This field will be used in calls like getPriceandStock / getOrdersimulation. The default plant will be used to check whether products are on stock, if no other plant is defined. Please identify one plant for each sales organization.
Note: When you doing B2C business in multiple countries, with multiple plants: In an eCommerce platform it may be possible to setup multiple websites, so a website for Europe, which will be using Plant ' Europe " and a website for USA, which will use plant 'USA" If this is the case you will need to extend the integration.
|Months||number of months for my product selection||
My products is a list of specific SKU’s connected to customers. The field "months" is meant to define how much months we should look back in the order history of a customer. Based on this we will check which products are ordered more then once in that period so we can define whether this product needs to be in the list of my products.
|Maximum records||maximum number of products in my product selection||
My products is a list of specific SKU’s connected to customers. The field "maximum records" defines how many products should be included in the ‘my product list’.
|Delivery/Credit Block||sales order delivery block when payment is insufficient||
Scenario in an eCommerce platform:
When a payment from PSP/ CC (third party payment provider) is not been approved, the order in SAP will be blocked by the delivery/credit block.
In that case, the order is not processed automatically but has to be finalized manually in SAP by back office employees.
When you are not using the option in SAP, the eCommerce platform can also 'hold' de order in the eCommerce platform until it is approved. A drip campaign / mails or actions should be taken, starting from the eCommerce platform. In this case the process handles from the eCommerce platform point and only ' paid ' orders will be send to SAP. In this case, the status of an order being send to SAP should be set on Completed.
|Checking Rule||checking rule for availability check||
You can define which rules needs to be checked to define the availability of a product.
Let's first give a simple example to explain this function in SAP. When a stock level is 20 and 5 products have been ordered, but not yet paid, business logic can be defined. This business logic can be defined to have the stock level at 15 (stock on shelf minus orders in basket).
Which receipts (for example, purchase orders or production orders) should be taken into account in the availability check.
Which issues (for example, sales orders or dependent requirements) should be taken into account in the availability check.
|Stor. Location||storage location for availability check||
Storage locations are the places where stock is physically kept within a plant for sales organization. Please use this field to define which storage location needs to be used to determine availability. Identify the storage location per sales organization.
|HeaderInfo||text id of sales order header text for delivery block||
Use this field to add a 'default text' in the order from the eCommerce platform, which is being send to SAP.
Example: Some users of the Connector require that every online order goes into a delivery block (so the order is not automatically processed but should processed manually). In this field a standard ’comment’ is added, that could be set as a reason to block the order.
field name from table MARA for alternative product number
!! field ‘Source extnr’ is mandatory and the specified field is used to translate
the SAP material number to the external/alternative product number (which could also be the SAP material number)and vice versa in ALL web service communication
Field ‘Source extnr’ is mandatory and the specified field is used to translate the SAP material number to the external/alternative product number (which could also be the SAP material number) and vice versa in ALL web service communication.
Example: In an eCommerce platform the field SKU is used for unique identifier of the products. Most of the time this field is filled with 'Productnumber'.
SAP is using the field " Source extnr" for the unique identifier of the products as default, but this can be changed in SAP as well to - for example - material number. To connect the SKU from the eCommerce platform to the Unique Identifier in SAP this field can be used to fill in the value of the Unique Identifier in SAP - for example Material Number.
number of months to select delivery days
When you want to place an order in the eCommerce platform and you are at the checkout, you have a calendar with days when you want your order to be delivered. If you need to have these days filled in from SAP the call getDeliverydays is used. Example: for customer X with ZIP code XXXX YY, we only deliver on Wednesday. This way, the calendar only shows Wednesdays. The field 'delivery days months’ is used to define how many months in the future we show relevant delivery days in the calendar.
text id of sales order header text for payment reference
* Table name descriptions
- Table MARA - General Material Data
- Table MVKE - Sales Data for Material
- Table KNA1 - General Data in Customer Master