Delivery type unchanged in both Transaction & B2B Web shop

Hi Gurus,
My requirement is to change the Delivery type to 'expedited' in the b2b web shop if the gross weight is less than 4 kg. I wrote sample code, without condition, in BADI to see the delivery type change in both transaction and in webshop. It seems there is some issue with the below code I could not find any changes in .both transaction and in webshop. I tried with 'CRM_SHIPPING_CHANGE_OW' also. But no luck. Could anly one please tell the bug in the code?
BADI: CRM_ISA_BASKET_HEAD
Method.CHANGEHEAD_SET_DATA
DATA: LS_SHIPPING TYPE CRMT_SHIPPING_COM,
 ls_shipping_com TYPE CRMT_SHIPPING_COM,
 lt_input_field_names TYPE crmt_input_field_names_tab,
 ls_input_field_names TYPE crmt_input_field_names.
Get the shipping data from ISA layer
loop at IT_SHIPPING INTO LS_SHIPPING.
 MOVE-CORRESPONDING ls_shipping TO ls_shipping_com.
 ls_shipping_com-SHIP_COND = '02'.
fill ct_input_fields
 ls_input_field_names-fieldname = 'SHIP_COND'.
 INSERT ls_input_field_names INTO TABLE lt_input_field_names.
change shipping segment
 CALL FUNCTION 'CRM_SHIPPING_MAINTAIN_OW'
 EXPORTING
 is_shipping_com = ls_shipping_com
 CHANGING
 ct_input_field_names = lt_input_field_names
 EXCEPTIONS
 error_occurred = 1
 OTHERS = 2.
ENDIF.
endloop.
Method.:GETHEAD_GET_DATA
DATA: LS_BASKET_HEAD TYPE CRMT_ISALES_BASKETHEAD_UI,
 LS_FIELD_CHANGEABLE TYPE CRMT_INPUT_FIELD_NAMES,
 LS_CRMT_SHIPPING_WRK TYPE CRMT_SHIPPING_WRK.
*Get the changed data
CALL FUNCTION 'CRM_SHIPPING_READ_OW'
 EXPORTING
 IV_REF_GUID = LS_BASKET_HEAD-GUID
 IV_REF_KIND = 'A'
 IMPORTING
 ES_SHIPPING_WRK = LS_CRMT_SHIPPING_WRK
 EXCEPTIONS
 ENTRY_DOES_NOT_EXIST = 1
 OTHERS = 2.
IF SY-SUBRC = 0 AND LS_CRMT_SHIPPING_WRK-SHIP_COND IS NOT INITIAL.
 LS_BASKET_HEAD-SHIP_COND = LS_CRMT_SHIPPING_WRK-SHIP_COND.
ENDIF.
Pass back to ISA layer.
READ TABLE CT_FIELD_CHANGEABLE INTO LS_FIELD_CHANGEABLE WITH KEY FIELDNAME = 'SHIP_COND'.
IF SY-SUBRC <> 0.
 LS_FIELD_CHANGEABLE-FIELDNAME = 'SHIP_COND'.
 LS_FIELD_CHANGEABLE-CHANGEABLE = 'X'.
 APPEND LS_FIELD_CHANGEABLE TO CT_FIELD_CHANGEABLE.
ENDIF.

In theory, ZOR orders created from both CRM GUI and B2B should use the same number range only. (internal)
Since the B2B is not creating ZOR type, it is very likely, the shop settings are not effective.
Check if the webshop profile you have set the ZOR is the default webshop that gets used by the B2B. This is done through webshop XCM admin.
Or - are you using Transaction Type Group?
Easwar Ram
http://www.parxlns.com
Edited by: Easwar Ram on Nov 4, 2008 4:13 PM

Similar Messages

What are most valuable and required features in the B2B Web shop checkout?

Hi,
I am product manager for SAP Web Channel. I would like to use this forum as a channel to learn more about our customer's requirements for Web shop checkout. Also, I would like to gather new ideas from our customers and partners for a highly usable and functional Web shop checkout.
What do you think are very valuable or even u201Cmust haveu201D features in a B2B scenario Web shop checkout? You can let me know checkout features that are especially relevant for your own business process. In this respect, it would be interesting to know what B2B checkout features you developed in your E-Commerce project. However, I would also like to know what features, apart from your own specific process requirements, that you would judge as very important standard B2B checkout features. Think of features such as an Ajax search for shipping addresses or payment via direct debit or 3D Secure.
Let me tell you upfront what I roughly understand as "checkout". Checkout for me is a process typically triggered by a 'Checkout' button in the shopping basket. As a result, a checkout page gets called. On this page or accross different sequent pages the customer is requested to enter or select certain information such as billing and shipping address(es) and payment data. This information is required by the Web shop owner in order to fulfill the customer order.
All your ideas, feedback, and thoughts on this topic are very welcome. Please understand that providing your ideas and requirements on the checkout will not necessarily mean that SAP will develop them in the future. But every idea will broaden my mind on what are the market requirements regarding this topic.
I hope that I can start an interesting discussion for all of you here in the forum. I will provide points for interesting ideas, thoughts and requirements.
Greetings
Torsten Kliesch

Hi Sateesh,
thanks for your feedback. I have granted you some points for it first of all. Let me ask 1-2 two questions regarding your feedback though:
Regarding the pricing I understand your point in a way that it should be possible to display more price details in the basket or at least in the order overview of the checkout (before submitting the basket as a sales order). Meaning it should be possible to more easily switch on the display of price details like subtotal, customer discount in the basket and order overview. Is my understanding correct?
Greetings
Torsten

Item external document Link in B2B Web Shop

Hi Gurus,
we have a business request, allow B2B users to viewing external document of
order, delivery and invoice.
This document will be created automatically by DocIsland.
Now I want to know if there are any possibility to view this document
by standard B2B, only modifying ERP system.
In some B2B JSP page, I have found some portion of code that manage with document and
write it if it's enabled.
I mean "/ecombase/itemconnecteddocuments.inc.jsp".
Any help would be more appreciated.
Nicola Bisinella

Hi Nils,
how can attach the SAP Document as you mean?
Which are right transactions ?
Thanks
Nicola

Images were not displaying in the B2B web shop for the products

Hi,
We have an issue with Product catalog images.we maintained images for the products and replicated(Initial) to TREX server,replication was successfull,but the images were not displaying in the b2b webshop for the products.
Anyone suggest what could be the problem?
Regards,
PV.

Hi,
The problem could because of following issues.
1) The replication is not done properly
2) The XCM doesn't have Image server's settings(URL)
3) The Image server is not reachable from ISA application.
4) The image server is not connected through HTTP.
Please check.
Regards,
Sateesh Chandra

Steps to define new delivery type

Hi ,
I want to know that,what is the complete step to define the new delivery type ,that can be use in exsiting order type to complete the sales cycle process.
Regards
Prabudh

Consignment Stock Processing:
Consignment Stock Processing
Purpose
Consignment goods are goods which are stored at the customer location but which are owned by the company. The customer is not obliged to pay for these goods until they remove them from consignment stock. Otherwise, the customer can usually return consignment goods that are not required.
Consignment Fill-Up: Consignment fill-up replenishes the stock at the customer site. Since the goods remain the property of the company, this process is not relevant for pricing and consequently not for invoicing either.
Create a sales order using order type KB.
Enter the required data on the customer, the consignment goods and the delivering plant.
Enter all other relevant data and save the order.
Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
The underlying goods movement type is a stock transfer. This ensures that when goods issue is posted, consignment special stock is created for the customer concerned. If special stock of this kind already exists in the delivering plant for this customer, the goods are posted to this special stock.
Order type: KB (document category C: sales order)
Std. Delivery type: LF
Item category: KBN (not relevant for pricing and billing)
Schedule line category: E1 (relevant for deliveries, uses availability check, 631 (GI consignment: lending) to post the stock into a special consignment category in the delivering plants stock for that particular customer and material)
Copy control rules for the sales doc, item category, and schedule line category.
Use trans MB58 or MMBE to check the stock.
Consignment Issue: The Consignment issue enables the customer to withdraw consignment goods from the special stock that are to be used or sold.
Create a sales order using order type KE.
Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
Enter all other relevant data and save the order.
Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
The goods are then reduced by the relevant quantity in the special stock assigned to the customer. This goods issue also reduces your total stock.
Invoice the delivery which issues the consignment goods.
Order type: KE (document category C: sales order)
Std. Delivery type: LF
Invoice: F2
Item category: KEN (relevant for pricing and deliver related billing, special stock indicator W, should determine cost too)
Schedule line category: C1 (relevant for deliveries, uses availability check, 633 (GI issue: customer consignment)
Consignment returns: proceed as follows: Consignment returns enable your customer to return goods to the consignment stock that has already been issued from it.
Create a sales order using sales order type CR.
Enter the required data on the customer and the consignment goods.
Enter all other relevant data and save the order.
Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The goods issue posting cancels the goods issue posting which was carried out when the consignment goods were issued. This posting records the return of the goods to the plant where goods receipt was carried out.
Create a credit memo for the consignment return you created in Step 1.
Order type: KR (document category H: returns)
Delivery type: LR
Credit for Returns Order type: RE (delivery or order related billing)
Item category: KRN (relevant for pricing and deliver related billing, special stock indicator W
Schedule line category: D0 (relevant for deliveries, no availability check, 634
Consignment Pick-Up: The company uses consignment pick-up to take back consignment goods that are faulty or excess materials that the customer does not need. This process is not relevant for billing since the goods remain the property of the company.
It may be beneficial to have a mandatory reference such as the consignment fill-up. In addition to it copy control rules can be used to further control it. In the copy control rules indicate the document flow. As the stock is coming back into the warehouse or plant, you can specify a returns shipping point to be automatically determined. No invoice is necessary, as the goods are not changing ownership.
Create a sales order using order type KA.
Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
Enter all other relevant data and save the order.
Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The transaction is completed by the goods issue posting which initiates a transfer posting from the customer's special stock to your plant stock.
Order type: KA (document category C: sales order)
Delivery type: LR
No invoice
Item category: KAN
Schedule line category: F1 (relevant for deliveries, availability check against the stock on the customers consignment, 632 (Consignment pickup)
Reward points if useful
Re: Delivery Document Type
Re: Consignment Process

How to set up WEB SHOP in R/3 & CRM?

Hi
I want to set up Webshop in both R/3 & CRM & linking of url for CRM B2B transaction.
please let me know.
-Rohit

Hi Rohit:
1.Access the activity using the following navigation options:
http://<host>:<port>/shopadmin/shopadmin/init.do?scenario.xcm=<yourscenario>
2.Select a logon language, for example EN.
3.Logon to the Web Shop Management with the Web Shop Manager user/password. 4.Choose Create New Shop for scenario and select the Internet Sales scenario, for example Internet Sales B2B or Internet Sales B2C via dropdown list.5.Create a Web Shop for each language you want to offer.
6.Make the following entries for a sample B2B Web Shop:
New Shop Value (Example)
Shop ID B2B_SHOP
Description Business to Business Shop
General Information Value (Example)
Usage Internet Sales B2B
Authorization Group
User Administration- Partner Function Contact Person- Country group e.g. 00000015Z001 (US) or Z002 (EU)
Catalog Value (Example)
Catalog PRODUCT CATALOG
Variant Variant 1 (EN) (defines the language of the shop)
Controlling price determination in the catalog Via IPC
Order Value (Example)
Order type ISBB
Sales office <empty>
Order Templates Allowed Select
Availability check control CRM integrated availability check (SAP APO) or availability information (SAP R/3)
Display product determination information Select
Quotations Value (Example)
Request for Quotation Select
Order type AGIS
Contract (B2B only) Value (Example)
Contract Determination <empty>
Contract Negotiations Value (Example)
Allow Contract Negotiations <empty>
Marketing Value (Example)
Global Product Recommendation Optional, you can assign later
Personalized Product Recommendation Optional, you can assign later
Cross-, Up-Selling and Accessories Optional, you can assign later
7.Choose Save.
8.Make the following entries for a sample B2C Web Shop:
New Shop Value (Example)
Shop ID B2C_SHOP
Description Business to Consumer Shop
General Information Value (Example)
Usage Internet Sales B2C
Authorization Group
User Administration- Country group Z001 (US) or Z002 (EU)
Catalog Value (Example)
Catalog PRODUCT CATALOG
Variant Variant1 (EN) (defines the language of the shop)
Controlling price determination in the catalog Via IPC
Order Value (Example)
Order type ISBC
Sales office No entry
Availability check control CRM integrated availability check (SAP APO) or availability information (SAP R/3)
Marketing Value (Example)
Global Product Recommendation Optional, you can assign later
Personalized Product Recommendation Optional, you can assign later
Cross-, Up-Selling and Accessories Optional, you can assign later
9.Choose Save.
Best Regards,
Pratik Patel
Reward with Points!

Upgrade Plan - Web Shop - NWDI

Hi Experts,
My customer has planned to upgrade their portal from version 7.01 to 7.02 SPS4. They have four environments namely Dev, Quality, Acceptance & Production. They plan to upgrade Dev first, followed by Acceptance & then Production. (Quality is kept as it is for incident mitigation till Production is patched)
The portal is effectively an e-commerce portal which has both portal components & Web shop deployed on it. The Web Shop code is hosted on NWDI which is configured to build the Dev server once the code is checked in.
Now these are my questions:
1. Lets say that while Dev is being upgraded, we need to fix a critical incident involving web shop code. Can we configure NWDI to build Quality rather than Dev. The current setup is that transports need to be done sequentially i.e. D->Q->A->P.
And even if build fails in Quality, can i directly configure NWDI to point to production and do the build there?
2. Is it possible to register the same instance multiple times (say quality instance)under 'target instance'. Will this help me at all?
Regards,
Ramanathan Palaniappan

Hi Ramanathan,
First of all let me make one thing clear.
No matter how many Runtime systems you have in your landscape (In your case D->Q->A->P), your NWDI usage type or instance, whether it is hosted on your Development Server or some different host separately is common across these systems.
To give you more clarity you need to understand the following concepts.
1) Your Landscape consists D->Q->A->P.
2) Here, lets assume that NWDI is running on your Development Server D.
3) That means all the 3 pillars (DTR, CBS & CMS) of NWDI are present in Dev host.
4) Now, Suppose are maintaining a Track named "Track-A"
5) Whatever developments that are carried out (Source Code Modification) specific to "Track-A" are available in the DTR-Server present Dev Host only.
6) So, the Build process is also specific to Development Host ONLY
7) You cannot use terms like "Can we configure NWDI to build Quality rather than Dev", it simply doesn't make sense.
OK, so far so good.
Lets move further ahead.
There's a big difference between Build process and Deploy Process.
1) When you create a Track, you need to define the Runtime Systems of your Track.
2) When you define runtime systems, your purpose is to provide information to the CMS about--> to which all systems you will be DEPLOYING your Compiled Source Code (Which is in the form .SCA that is created as an output in Assembly step)
3) Build Process as explained above happens only on Development Host in Development Buildspace and Consolidation Buildspace of your Track.
You can also refer to the thread where i have explains step-by-step process about what happens under the hood in NWDI
Re: Comparing records in Update Rules
Now, if you meant to configure NWDI to point Quality rather than Dev in terms of Deployment only then Yes, It is very much possible.
Follow the below mentioned procedure...
1) Open the CMS Web UI >> Landscape Configurator >> Track Data >> Runtime Systems
2) Here, you can configure your runtime system as you wish.
3) For Example if you want to skip the deployment into Quality and directly deploy in production then you can uncheck the "Test" from Selected Runtime Systems.
After you modify the setting in Runtime systems in Landscape configurator, then relevant changes will be reflected in the Transport Studio of your track. Considering the above example The "Test" tab will not be available.
I hope my inputs will help you resolve your query.
Regards,
Shreyas Pandya

Web shop LWC Chat and Interaction Center integration

Hello All,
As I know, Live Web Collaboration in SAP E-Commerce for mySAP CRM (B2B, B2C Shops, and Internet Customer Self-Service) supports chat in CRM Interaction Centre WebClient, so that customer requests for assistance via chat are forwarded directly to the IC WebClient.
I had maintain LWC component in B2B Web Shop and LWC application for Agents, so chat between Consumer and Agent work fine. Also I maintain IC WebClient and Contact Center Simulator for testing, as described in this blog (/people/stephen.johannes/blog/2008/05/21/crm-contact-center-simulator-setup) . I tested chat and telephony functions u2013 all work fine.
Than I tried to integrate LWC chat function and IC WebClient. I did all necessary settings as described in LWC XCM application help, CRM7.0 help (http://help.sap.com/saphelp_crm70/helpdata/en/fe/4cad3efa11b300e10000000a114084/frameset.htm) and SAP Solution Manager (http://help.sap.com/SCENARIOS_BUS2004/helpdata/EN/E8/9B0342D0369C39E10000000A155106/frameset.htm) .
But integration donu2019t work. When I try requests for assistance via chat in B2B shop, I receive message u2013u201C No agent is available to assist you. Try again lateru201D
Can any one tell me what are the possible ways to integrate LWC Chat in B2B Web Shop with Interaction Center WebClient?
Regards,
Yuriy

Hello Oliver,
I had maintain LWC component in B2B XCM (http://<host>/b2b/admin/xcm/init.do path: General Application Settings -> Customer -> lwc -> lwcconfig). Here I configure JMS host and port.
Also I maintain LWC XCM (http://<host>/lwc/admin/xcm/init.do). I had create custom scenario where I configure JCO connector to back end system.
Then, in customer side I go to the B2B Web shop (http://<host>/b2b/init.do), click Help link, and then in pop-up window - Customer Support - > by Chat.
In Agent side I open LWC (http://<host>/lwc /init.do), enter my user name and password, click Available button, and after Customer send request for Chat, press Pick Request.
In this case B2B Web Shop Customer can chat with Agent. Multichat also supported u2013 one Agent can chat more than one customer. But LWC application interface looks primitive and limited.
I am interesting how I can integrate LWC and IC WebClient as it described in SAP help. Anybody can help me?

Upgrade of e-commerce web shop

Hi everybody,
I am working on a b2b web shop (release 5.0) in nw developer studio. There I developed some classes in a new Software Component so that there should be no problems to integrate them into newer releases of the sap standard shop. But how can I upgrade all my changed jsp files of SC "sap.com_SAP-SHREB"? Is the only way to solve conflicts after upgrading the web shop? Or is there perhaps a better way to seperate my own developments from the sap standard? My goal is to achieve a minimum of conflicts between my own developments and new sap releases.
Thanks in regard, Mirko
Message was edited by:
Mirko

Hi,
If you got to know how this can be done, please let us know.
Thanks,
Uma.

How to assign 2 Delivery Types to a single Internal Confirmation category ?

Hi all,
According to this transaction OMGZ that assign the Delivery type to the Internal Confirmation categories, I'll like to assign another Delivery Type to the Internal Confirmation category "2 Shipping Notification".
I previously created a new Confirmation Control Key (0005) copy from the 0004 for the P.O & a new Confirmation category ZA (copy of the LA - Inbound Delivery).
My issue is how to use the single Internal Confirmation category "2 Shipping Notification" to the both Inbound Delivery Types ZEL (copy of EL) and ZAL (copy of ZEL) ?
Thanks for your reply !!!
Ed

Hi Steve,
Thanks for your reply. I know that SAP standard system can't have two. My Client want to distinguish between 2 Delivery Types used for different businesses in the same SAP system. As every Inbound delivery Type will be used in other Z developpements programs. And we don't want to create confusion in our figures. But I thing we can use another PO type to make it.
Ed

Customised look and feel for B2B/B2C web shop.

Dear experts,
I would like to find out if there is an admin page for SAP E-commerce to customise the look and feel of the webshop?
Thanks.
Wein

Hi Wein,
To change Look and Feel for Web shop is depends on scenario of eCommerce application i.e. B2B or B2C. B2B has different structure than B2C.
Web Channel application comes in SAP standard with SAP look and Feel. You have to change look and feel as per client requirement.
To change look and feel of Both B2B/B2C scenario you have to deal with files like CSS, JSP, Properties, XLF and some time you have to add your custom JAVA, JSP, CSS, Properties files etc...
To change standard SAP logo youhave to make change in CSS files. Also you have to consider Browser type while changing look and feel because to display your B2B/B2C application correctly in different browser you have to make changes in different CSS.
You will get better idea with example how to change look and feel in "Dev & Ext. Guide" for Web Shop. You will get this from Service Market place.
eCommerce Developer.

Using Different inbound delivery type?

Dear experts,
In the goods receipts process we currently are using the standard inbound delivery type "EL" with the standard item category ELN, which is not "Relevant for putaway".
We are assessing the possibility of start using WM in one of our plants. So, I found out that the we should be using a item category (in the inbound delivery) with the field "Relevant for putaway" flagged. Like, for example, the standard WIDN (maybe together with the standard inbound delivery type WID). But only at those plants with WM!
The issue is that as far as I know the inbound delivery type determination depends on the "Internal Confirmation Categories":
So for the type "2 Shipping Notification" only one delivery type can be chosen, how are we suppose to do it plant dependent?
It looks like a unique delivery type should be used in the client?
Thanks in advanced,
Fortian
P.S.: I already read SAP notes 214604 & 201655 but they are not being helpful so far... Maybe I'm missing something.

From your post I understand that the current plants are IM managed.
So for these plants the put away relevancy will not have any effect so if you enable the put away relevancy for the EL delivery type there will be no impact on the IM plants and for the WM plant the put away will be relevant.
Now the usage of the put away relevancy will also depend on which transaction you are using for posting a goods receipt. If you post via VL32N then you will first have to perform the put away step and then the GR posting. If you use the MIGO/MIGO_GR transaction then the goods receipt in WM will also be posted before the put away happens.

Automatic determination of Delivery type and Billing type in a sales order

Hi,
I want to know that in a sales order cycle, how does automatic assignment of delivery type and billing type takes place after we create a sales order?
For example,when I create an outbound delivery for a sales order of type normal (OR) then in that case how does the system knows that it has to create an outbound delivery of type LF.How does the system propses it automatically and same is the case of billing document.

Hi
In customising the sales document type (Tcode VOV8) -
specify the default Delivery type in the field DELIVERY TYPE in the 'Shipping' area of the sales document type customisation.
Similarly you can specify the billing type in the BILLING area for both Delivery related billing and Order related billing.
Thanks,
Ravi

Delivery type LR cannot be invoiced with billing type RE?

Hi,
I am refering below flow to create an return order, but face an error when creating credit billing document:
ret sale order(RE)-ret delivery(LR)-post goods receipt(stock will be restored in corresponding storage loc)---credit for return(RE)
Error msg: " Delivery type LR cannot be invoiced with billing type RE;
Check the table entries for the copying control of billing
documents and add the missing entries as necessary.
Make the appropriate settings in Customizing if you have
the authorization to do so."
So i guess i might need maintain corresponding copying control for 'delivery document to billing document'...As the source order type is LR, and target order type is RE...I checked SPRO and found there are below inputs needed. May i know what kind of data should be inputed normally??
"Copying requirements
Determ.export data
Assignment Number
Reference number"
Thank you very much!!

Hi
In standard SAP credit memo for sale returns with refrence to return order only. (RE). Thats why you are getting this error. If your requirement is to refer the delivery quantity for the credit memo then you can do any one of the following
1. Change the copy control setting for Return order to Credit memo.
    Go to VTFA transaction and select your return order type (RE) and Credit memo type (RE) and go to item category level and select your returns item category (REN) and change the billing quantity to 'D' -Delivery quantity.
    Now create your credit note with reference to your returns sale order. (not delivery). Onlly delivered quantity will be copied to the credit memo.
2. If you want to create return credit memo with reference to your return delivery then follow the first two guy's reply. Also you have to do one more setting at your return order document type (RE).
   Go to VOV8 and enter ur return order type and go to details then enter the return credit memo type in the delivery related billing field. (FKARV) in the billing section.
Regards
Shiva

Not able to send Email in SOA Suite 12c,getting No matching driver found for delivery type = EMAIL

Hi All,
I am getting following Errror whlie Sending Testing Mail from Human Workflow .
No matching driver found for delivery type = EMAIL
I followed all the steps mentioned in blogs.
Steps that I followed--
1,Downloaded Gmail and Imap Certificate.
2.Imported in Keystore
3.Create a Email driver properties.
Than

Did you resolve this? I am running into the same problem. Not sure if it a configuration issue or an issue with 12c (go figure). I have tried both a blank sender address list and explicitly putting the target address in. Notification mode is set to email. I am using the Notification Test under Human Workflow/Notification Managent. Where else could it be trying to match the driver to EMAIL?
exception.type: ERROR
exception.severity: 2
exception.name: Error status received from UMS.
exception.description: Status detail :
Status type : DELIVERY_TO_DRIVER:FAILURE,
Status Content : No matching driver found for delivery type = EMAIL,
Addressed to : EMAIL:[email protected],
UMS Driver : null,
UMS Message Id : dcb01e3ec0a8456856fe8a439e6ecf3f,
Gateway message Id : null,
Status Received at : Mon Jan 12 00:49:27 EST 2015.
exception.fix: Check status details and fix the underlying reason, which caused error.
>

Delivery type unchanged in both Transaction & B2B Web shop

Similar Messages

Maybe you are looking for