No price in shopping cart from catalog with non-EA order unit

[Former Member]

When I'm in the shopping cart ordering from catalog, if the item has an order unit that's not EA, the price of the item shows up as 0.00 in the shopping cart, not the price defined in the catalog. Order unit and UOM can be of the same unit, but if it's not EA, the price shows up as 0.00.

Has anyone had this problem before? It should be pretty standard to have other measurements other than EA.

How should one set up the order unit and UOM in the catalog if the two are different?

Thanks.

[Former Member]

Hi

Are you using Requisite Catalogue or CCM ?

In Requisite, the order unit can be defined in Requisite configuration and can be set as EA, which means no other UOM is allowed.

Kay

[Former Member]

Hi

<b>Seems to be catalog configuration is having problems.

[Functional side - SRM ]

In the SRM web page, try selecting an item from catalog, and before ordering the item from catalog, right click on web page and select -> view source (It will display the data in notepad file). See if the price and unit details are appearing there.</b>

<u>Alternatively, you can try out

BBP_CATALOG_TRANSFER BADI in SE18 Transaction to handle the issue from ABAP - technical side.</u>

Do let me know.

Regards

- Atul

[Former Member]

the price is there before they order.

It is AFTER they clicked on add to shopping, and the item arrives into the shopping cart, does the price not show up.

[Former Member]

Hi

Which catalog are you using ? Are you using Requisite or BugsEye ?

Are you responsible for Catalog configuartion in SRM side ?

<u>Here is the SRM - SPRO Path</u>

<b>SAP Implementation Guide -> Supplier Relationship Management -> SRM Server Master Data -> Define External Services (Catalogs, Vendor Lists, etc.)</b>

<b>Please ensure that configuartion settings are maintained correctly in SRM ?</b>

<u>Alternatively, you have couple of BADIs to solve this technically.</u>

<b>BBP_CATALOG_TRANSFER

BBP_CAT_CALL_ENRI</b>

----

---

Here are the details ->

----

---

<b>SPRO - IMG Settings detail</b>

----

---

<u>Define External Web Services (Catalogs, Vendor Lists etc.)</u>

In this step you define Web Services such as product catalogs or vendor lists that are to be available in SRM Server applications.

You have to create the dialog structure, that is, the data that is required for addressing the Web Service. Since this data is service-specific, you must contact the provider of the Web Service obtainthe data from them or get it from the Web Service documentation.

Requirements

You have defined the logical system for the Web Service, that is, for the product catalog, in activity Define Logical System in the IMG.

This is not necessary if you are using the SAP Content Integrator .

Activities

1. To select a Web Service, double-click on an entry in the list.
2. To create a new Web Service, choose New Entries.
Enter the following data:
Web Service ID (required entry field)
User-defined technical name for a Web Service.
Name of the Web Service 
The name is displayed in the Help of the SRM Server application in which the Web Service is embedded. If the application is available in multiple languages, you must translate the name using Edit -> Translate, otherwise the name is not displayed.
Business type (required entry field)
The business type determines the type of the Web Service and, therefore, in which SRM Server applications, this Service is visible. In the Shop application, for example, product catalogs aredisplayed, but no vendor lists. Furthermore, the busines type determines which further options are available in this IMG activity.
3. Select a business type for the Web Service and confirm your selection with Enter. You can make selections as follows:
Product catalog
As product catalogs, you can include catalogs that support the open catalog interface (OCI), for example, catalogs that you have created using SAP Catalog Content Management .
Vendor list
As vendor lists, you can include vendor lists that support the open partner interface (OPI).
E-Form
Means the same as product catalog. However, if you select this type, the sample implementation of the Business Add-In Transfer Additional Parameters is run, and this BAdI is ignored for all other business types.
Vendor evaluation
This business type is currently not used.
Service provider list
The application Supplier Self-Services (SUS) can be included as a service provider list.
Note:
Create only one service provider list because you can only assign one Supplier Self-Services System to each SAP Enterprise Buyer System.
4. If you have selected Product catalog or E-Form as the business type, you have the following entry and selection options:
Source of Supply Assigned to the Product Catalog
a) Enter the number of the business partner and the responsible purchasing organization if the catalog content belongs to one business partner (vendor) only. If you do not assign a business partner to a catalog item, the system automatically assigns this business partner.
Additional Functions in the SRM Server
b) To determine that product numbers transferred from the catalog do not exist as local products in the SRM Server, check the flag Do not check products.
c) To display contract data in the integrated catalog, check the flag Display Contract Data in Integrated Catalog.
Additional Functions in Product Catalogs
Note:
Some catalogs offer additional functions that are specified in the context of the Open Catalog Interface (OCI). Check the following flag only if the product catalog or the E-Form support the additional functions.
d) To display product data in the catalog again after the selection in SAP Enterprise Buyer, check the flag Display Prod. Data Again in Catalog. See also Detail.
e) To enable an update of the product data in SAP Enterprise Buyer after the products have been selected from the catalog, check the flag Validate Product Data from SAP Enterprise Buyer. See also Validation.
f) To call the catalog with only one search term, and to carry out a search for a source of supply, check the flag Sourcing. See also Sources of Supply.
g) To support a simultaneous search in multiple catalogs, check the flag Search Cross-Catalog.
5. The following entry and selection options are available for all business types:
Technical Settings
a) To keep an error log for the catalog, flag Maintain Error Log. This will keep a log of all technical and business errors that occur during transfer of the product or vendor data. To display the log, choose transaction SLG1.
Note: 
This function is not available with the business types Vendor evaluation and Service provider list.
b) To use the HTTP method GET to call the Web Service, check the flag Use HTTP GET to Call Web Services. To use the HTTP method POST, leave the flag empty.
c) Select the technical type of the Web Service. This determines where the Web Service is to be available.
d) Specify the logical system of the Web Service. If you are using the SAP Content Integrator, then this entry is required for mapping the product data.
e) Specify the path for a symbol that represents the Web Service. This symbol is then shown in the application if the system uses symbols for Web Services. This path is relative to the Mime directory IMAGES/WEBSERVICES in Internet Services BBPGLOBAL. If you create subdirectories in this directory, the path must begin with '/'.

6. If you have selected Vendor list as the business type, you have the following entry and selection options:
Additional Functions in Vendor Lists
a) To display the vendor list in the catalog again, flag Redisplay Partner Data in Vendor List.
b) Specify the root node under which vendors are created that are then transferred via the Open Partner Interface (OPI) to SRM Server.
[The Open Partner Interface (OPI) enables the incorporation of Web-based supplier directories in SRM Server applications via the Internet and Intranet. If a product catalog supports the OPI interface, then business partner data can be transferred directly from the supplier directory into the relevant application. Communication between the supplier directory and the SRM Server takes place by way of the user's browser and is based entirely on HTTP.]

7. Create the dialog/call structure.
To open a Web Service in a separate window, choose Standard Call Structure.
To open a Web Service within the application, choose Integrated Call Structure.
Note:
For the Integrated Call Structure of product catalogs, you should use the servlet delivered for this purpose (see post installation steps: Integrating the Requisite Catalog in the Shopping Cart).
Syntax example: 
http://<HTTP-Server>:<port>/<your_entry>/catalog/logonOCI.do
SAP recommends that you only use the Integrated Call Structure for the catalog delivered by SAP because external product catalogs and Web Services usually to not take the SRM-Server-specificHTML frame structures into account. If you wish to include an external Web Service, SAP cannot provide any support in the event that errors should occur.
8. Make entries in the fields Name and Value and select a Type. You must adhere to the sequence as follows:
a) URL of the Web Service
In the first line of the call structure, enter the URL of the Web Service (value) and select the type URL. Do not enter a name.
If you have selected Service provider list as the business type, enter the URL of the SUS Service Provider List.
Syntax example: 
http://<HTTP-Server>:<Port>/sap/bc/bsp/sap/bbp_sus_sagent/sus_serviceagent_f4.htm
http server and port, see transaction SMICM.
Note:
If the URL is longer than the field, distribute it over the following lines and select the type URL for all entries. The URL may not contain any parameters.
b) Parameters
After you have entered the URL, enter all parameters that the Web Service requires on call-up. Take the names and values for the parameters from the documentation on the Web Service.
For the parameters, you choose one of the two possible types:
- Fixed value
The value entered in the Value field is transferred.
SAP Field
You can transfer the system language as a parameter, for example, (Content sy-langu). This way, you can transfer as parameters all the the fields that are globally available at runtime.
Note:
If the fixed values and the generic parameter values are not sufficient, you can transfer additional parameters from the SRM Server to the Web Service by implementing the Business Add-In (BAdI) . Transfer Additional Parameters. Using this BAdI, you can define name-value pairs that can be transferred as additional parameters to the Web Service. If, for example, you wish to transfer the system language in a different format ('EN-en' rather than 'EN'), you can use this BAdI.
c) Return URL
Enter the name with which the Web Service expects the return URL (usually HOOK_URL), and choose the type Return URL. Do not enter a value for the return URL. The SRM Server determines the value at runtime.
The return URL is required in order to transfer data from the Web Service via the browser to the SRM Server System. The Web Service copies the return URL into the 'action' parameters of the transfer form. The return URL is also transferred as a parameter to the Web Service. As this happens, all parameters following the return URL are generated as parameters into the return URL, that is, they are not transferred as individual parameters to the Web Service.
Note:
As of SAP Enterprise Buyer Release 4.0, specification of the return URL is optional. If you do not specify it, 'HOOK_URL' is used as the name. The parameters of the return URL thus become obsolete. The return URL must only be specified if the Web Service expects a different name for it than 'HOOK_URL'.
9. Save your entries.
Note:
To make a Web Service accessible for individual users or for user groups, you must assign the Web Service as the value for the attribute CAT. You do this in the attribute maintenance (Transaction PPOMA_BBP). The Help for this attribute lists all the available Web Services.
Further notes

You can find the documentation on OCI and OPI in the SAP Service Marketplace at the Internet address service.sap.com/instguides.
In order to read additional data from the SRM Server and to transfer it to the Web Service, you implement the Business Add-In (BAdI) Transfer Additional Parameters.
In order to define a different logic for the transfer of data from the product catalogs to the SRM Server System, you implement the BAdI Transfer Shopping Cart from Catalog.

Hope this will help.

Please reward suitable points, incase it suits your requirements.

Regards

- Atul

[Former Member]

We are using CCM SAPK-26406INCCM / BASIS SAPKB64019 / SERVER SAPKIBKS10

We have already defined all that you mentioned in the "Define External Web Service" configuration.

Our catalog is showing up and working fine in the shopping cart.

It's when the catalog items are added to the shopping cart does the pricing data not show up in the shopping cart, and the price is 0.00.

I'm thinking this is more of a shopping cart issue rather than a catalog issue.

[Former Member]

After some testing, I find that if an ISO code has multiple UOM units mapped to it, then the shopping cart will not pull the CCM catalog price, even if a primary code has been identified in SRM.

Are there any OSS notes or fixes for this problem? I couldn't find any notes.

Much thanks.

[Ramki]

Hi Derek

I guess you have one of the following options:

1) Correct the ISO codes in Txn CUNI (Recommended)

2) Use bbp_Catalog_transfer badi

Best regards

Ramki