Ansicht
Dokumentation

Internet Application Component Product Catalog and Online Store ( RELNLO_MD_AM_40CONST_ISR )

BAL Application Log Documentation   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Short text

Internet Application Component Product Catalog and Online Store

Description

• Integration of Alta Vista® search engine

• Authorization checks for access/maintenance

• Support for COD (cash on delivery) sales order type

• Email verification of online store sales orders

• Workflow error handling for online store transactions

• New customizing profiles

Integration of Alta Vista® search engine

Instead of the standard search algorithms, you can specify an alternative search algorithm (via a user exit). For example, you could incorporate the Alta Vistaâ search engine, which, in addition to speed, has the following advantages:

• Search for a product either in specific shops or throughout the entire online store
  
  

• Search by article number, key words in product name, price range, and/orfull text search of the product description
  
  

• Wildcard search (*) and Boolean logic (AND, OR, NOT)

Authorization checks for access/maintenance

Authorizations checks are done via authorization groups defined in the master records. They fall into two categories:

• Identification of online store customers who will be making purchases (customer, password, and possibly email address). You can specify whether this information must be entered when the customer first enters the store or later when he or she is about to make a purchase.
  
  

• Normal R/3 authorization checks. All authorizations belonging to the object class Sales and Distribution need to be maintained for the R/3 users with which the Internet Application Component logs on to the R/3 System via the Interaction Transaction Server (ITS). This logon is is usually specified in the service file. The authorization checks
  
  

• Authorization to create/update/display customer records (SAP_ALL or V_Verkauf or V_Versand profile for creating/updating/displaying customer records)
  
  

• Authorization to create sales orders
  
  

• Authorization to read the product catalog (either W_PCAT_MTN for for general catalog data or W_PCAT_LAY for the layout areas)
  
  

• Authorization to start the online store (W_ONLSTORE)

Support for COD (cash on delivery) sales order type

In addition to credit cards and invoices, R/3 now supports COD as a valid sales order type. If you choose COD, then you must also enter a payer number which denotes the carrier who will make the delivery and receive payment from the customer (for example, Federal Federal Express or UPS).

Email verification of online store sales orders

With R/3 standard message handling you can specify whether confirmations of Internet sales orders are to be automatically sent to the customers by email. If so, then you can use existing print programs for sales order confirmation.

Workflow error handling for online store transactions

If for some reason a sales transaction cannot be completed in the online store (for example, if something hasn't been entered properly in the master data), the system sends the customer an error message in the web browser. Workflow then automatically creates a work item and routes it to the person person responsible for maintaining the online store so that they can investigate the problem.

New customizing profiles

The following profiles can be set up in the customizing record for the online store:

• Product Presentation Profile. This includes how product information is displayed (by materia number, material description, material header, or all of these), how variants of generic materials (e.g., different sizes and colors) are selected, which search engine is to be used in the online store, and so on.
  
  

• Customer Management Profile. This includes such information as:
  
  

• How a customer is identified (by customer number or by email address)
  
  

• Whether customer identification is done on the home page of the online store or only when the customer is ready to finalize his purchase
  
  

• Geographic regions. You can define your own country groups: for example, group SEAS for southeast Asian countries or CEUR for Central European countries. When an online store customer enters his or her address data, the country field will display a list of countries within the geographic region you have defined.
  
  

• Whether SSL (Secure Socket Layer) is enabled (that is, whether personal data is to be encrypted for security reasons)
  
  

• If the customer registers, the system creates a customer master record. Essentially, only address information is taken from user input. Additional information, such as company code and sales area data, is copied from the reference customer specified in the customer management profile. There is also a user exit where you can specify that additional fields are to be assigned to the customer automatically during customer creation (tax jurisdiction code, terms of payment, and so on). (See the online documentation for more information.)
  
  

• Order Management Profile. This includes the SD order type to be used forsales transactions, which types of payment are to be accepted (credit card, invoice, or COD), whether quotations are to be prepared, and so on). (See the online documentation for more information.)

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

Refer to the IMG under IAC Product Catalog and Online Store

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

ROGBILLS - Synchronize billing plans   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 7282 Date: 20240520 Time: 212725     sap01-206 ( 119 ms )