Ansicht
Dokumentation

DEFINE_AUTHORIZATION - Define Authorizations

DEFINE_AUTHORIZATION - Define Authorizations

ROGBILLS - Synchronize billing plans   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

The E-Selling B2B Web shop allows control of authorizations for display and modification of order fields in the shopping basket and on ordering screens.

For E-Selling B2B, consider the following restrictions when you define authorization groups:

  • Modes: E-Commerce B2B allows control of authorizations for displaying or changing objects. The modes 'Create' and 'Delete' are supported for the following business transaction components which, however, have no impact on the field control in the Web shop:
  • Order item (ORDERADM_I)

  • Partner (PARTNER)

  • Document flow (DOC_FLOW)

  • Business partner: It is possible to control the selection of an alternative ship-to party or to create a new ship-to address. The control of single fields of the ship-to party address is not supported.
To control the authorization for the ship-to party, select the following:
  • Object name: PARTNER

  • Logical key: 00000002

  • Field name: PARTNER_NO.

To display or change the sold-to party, use the logical key 00000001.
  • Campaign: Independent from the business object type of the campaign you use (campaign, campaign element, trade promotion, or trade promotion element), select the following for the authorization check of all types:
  • Object name: DOC_FLOW

  • Logical key: BUS2010020

  • Field name: OBJKEY_A

  • Transaction history: In the transaction history, the display of the different transaction types can be controlled separately. Select the following for all transaction types:
  • Object name: DOC_FLOW

  • Field name: OBJKEY_A for preceding transactions

  • Field name: OBJKEY_B for follow-up transactions

In E-Service, you can define dynamic fields for complaints and returns. For more information about the configuration of these fields, see SAP Service Marketplace at service.sap.com/crm-inst -> SAP CRM 2006s (with SAP CRM 5.1) -> CRM Server and Standalone Components -> Development and Extension Guide for SAP E-Commerce 5.1 -> Configuration of Dynamic Fields in E-Service.

You have defined the authorization groups for orders in Customizing under Customer Relationship Management -> Basic Functions -> Authorizations → Define Authorization Groups.

The following tables contain the required entries for the logical keys for header- and item transaction history:

Preceding Transaction Header

Object Logical Key
Sales Order BUS2000115
Lead BUS2000108
Opportunity BUS2000111
Sales Contract BUS2000121
Service Contract BUS2000112

Follow-Up Transaction Header

Object Logical Key
Sales Order BUS2000115
Complaint BUS2000120
Invoice BUS20810
Delivery LIKP

Preceding Transaction Item

Object Logical Key
Sales Order BUS2000131
Lead BUS2000129
Opportunity BUS2000130
Customer Contract BUS2000135
Service Contract BUS2000137

Follow-Up Transaction Item

Object Logical Key
Sales Order BUS2000131
Complaint BUS2000160
Return BUS2000161
Debit Memo Request BUS2000167
Delivery Item LIPS

Delivery Item

Delivery Item






CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 6279 Date: 20240523 Time: 161732     sap01-206 ( 58 ms )