Key User Extensibility: Extensions Without Developer Access

Business Context: Business Partner - Customer
Field Label: Customer Priority
Technical Name: YY1_CUSTOMER_PRIORITY
Field Type: Code List

Values:
- A = High Priority
- B = Medium Priority
- C = Low Priority
- D = No Classification

-- Automatically generated CDS View Extension
extend view I_BusinessPartner with ZE_BusinessPartner_CF {
  YY1_CUSTOMER_PRIORITY as CustomerPriority
}

App: Custom Fields and Logic
Business Context: Business Partner - Customer
Logic Type: Determination
Trigger: On Create

Condition: Customer number is initial

Action:
  Set field "YY1_CUSTOMER_PRIORITY" = "C"

" Generated code (not directly visible)
IF customer-customer_id IS INITIAL.
  customer-yy1_customer_priority = 'C'.
ENDIF.

App: Custom Fields and Logic
Business Context: Business Partner - Customer
Logic Type: Validation
Trigger: On Save

Condition:
  YY1_CUSTOMER_PRIORITY = "A"
  AND Contact person is empty

Action:
  Error: "High-priority customers require a contact person"

// Comparison operators
Field1 = "Value"
Field2 <> "Value"
Field3 > 100
Field4 >= 50

// Logical operators
Condition1 AND Condition2
Condition1 OR Condition2
NOT Condition1

// Field operations
Field1 + Field2
Field1 * Factor
LENGTH(TextField) > 10
TODAY()

Custom View: YY1_CustomerOverview

Fields:
- BusinessPartner (from I_BusinessPartner)
- BusinessPartnerName (from I_BusinessPartner)
- CustomerPriority (Custom Field)
- OrderCount (Calculated: Number of orders)
- TotalRevenue (Calculated: Sum of revenue)

Filter:
- BusinessPartnerCategory = '1' (customers only)

Aggregation:
- Grouping by CustomerPriority

@AbapCatalog.viewEnhancementCategory: [#NONE]
@Analytics.query: true
@VDM.viewType: #CONSUMPTION
define view entity YY1_CustomerOverview
  as select from I_BusinessPartner as BP
  association [1..*] to I_SalesOrder as _Orders
    on $projection.BusinessPartner = _Orders.SoldToParty
{
  key BusinessPartner,
      BusinessPartnerName,
      YY1_CUSTOMER_PRIORITY as CustomerPriority,

      @Aggregation.default: #SUM
      count( distinct _Orders.SalesOrder ) as OrderCount,

      @Aggregation.default: #SUM
      @Semantics.amount.currencyCode: 'Currency'
      sum( _Orders.TotalNetAmount ) as TotalRevenue,

      _Orders.TransactionCurrency as Currency
}
where BP.BusinessPartnerCategory = '1'
group by
  BusinessPartner,
  BusinessPartnerName,
  YY1_CUSTOMER_PRIORITY,
  _Orders.TransactionCurrency

- Complex calculations across multiple objects
- Integration with third-party systems
- Mass processing
- Custom UIs (only field integration)
- Background jobs
- Custom transactions

Prefix for Custom Objects: YY1_ or ZZ1_
(automatically assigned by the system)

Recommendation for field names:
- Descriptive: YY1_CUSTOMER_PRIORITY instead of YY1_FIELD01
- Consistent: Same terms for same concepts
- Documented: Maintain label and description

1. Document requirement
   - What should be extended?
   - Why is the standard not sufficient?

2. Feasibility check
   - Is Key User Extensibility sufficient?
   - Or does it need Developer Extensibility?

3. Implementation
   - Create in development system
   - Test

4. Transport
   - Transport to quality system
   - Acceptance test

5. Go-Live
   - Activate in production
   - Monitoring

Step 1: Key User Extensibility
├── Create Custom Field "Customer Priority"
├── Simple default value logic
└── Make available in UI

Step 2: Developer Extensibility (if needed)
├── Complex calculation logic in ABAP
├── Integration with external CRM
└── Custom report with ALV

Business Context: Business Partner - Customer

Custom Fields:
1. YY1_REVENUE_12M (Amount) - Revenue 12 months
2. YY1_PAYMENT_SCORE (Number) - Payment score 1-5
3. YY1_COMPLAINT_RATE (Number) - Complaint rate %
4. YY1_CUSTOMER_RATING (Code List) - Rating A/B/C/D

Trigger: On Save

Rule 1:
IF YY1_REVENUE_12M > 100,000
  AND YY1_PAYMENT_SCORE >= 4
  AND YY1_COMPLAINT_RATE < 2
THEN YY1_CUSTOMER_RATING = "A"

Rule 2:
IF YY1_REVENUE_12M > 50,000
  AND YY1_PAYMENT_SCORE >= 3
  AND YY1_COMPLAINT_RATE < 5
THEN YY1_CUSTOMER_RATING = "B"

Rule 3:
IF YY1_REVENUE_12M > 10,000
  AND YY1_PAYMENT_SCORE >= 2
THEN YY1_CUSTOMER_RATING = "C"

Rule 4: (Default)
THEN YY1_CUSTOMER_RATING = "D"

View: YY1_CustomerRatingAnalysis

Fields:
- Number of customers per rating
- Average revenue per rating
- Trend vs. previous year

Grouping: YY1_CUSTOMER_RATING