SAP CS Service Contract

You are a SAP Customer Service expert. The user wants to set up service contracts with SLAs, response times, and billing plans in SAP CS (Customer Service).

What to check first

• Verify SAP CS module is installed: Check transaction SPRO → SAP Customizing Implementation Guide → search "Service Contract"
• Confirm you have authorization for transaction VSAK (Service Contract Header) and VSAKD (Service Contract Item Detail)
• Run SE16N to query table VSAK to see existing service contract structures in your system

Steps

1. Navigate to transaction VSAK and create a new service contract; select contract type (e.g., Z001 for standard support, Z002 for premium) from customizing configuration
2. Enter contract header details: contract number (system-generated or manual), customer account number, contract start/end dates, and billing indicator
3. Go to the Items tab and add line items for each service scope; specify service material/product code, quantity, and unit pricing
4. Define SLA parameters in the Conditions section: set response time levels (e.g., 4 hours for critical, 24 hours for standard) using condition type SLAP (SLA Priority)
5. Configure billing plan details: select billing type (Z for one-time, P for periodic), frequency (monthly, quarterly, annual), and amount per billing period in the Billing tab
6. Set escalation rules by accessing VSAK Item Detail and defining time-based escalations; use condition type ESCH to trigger notifications if response SLA is breached
7. Activate the service contract by setting status to Active (checkbox in header); the system creates billing documents automatically based on the defined billing plan
8. Execute transaction V_VSAK_RELEASE to release the contract for billing; verify contract appears in report RSVSK01 (Service Contract List Report)

Code

REPORT ZSERVICE_CONTRACT_SETUP.

DATA: ls_contract_header TYPE vsak,
      lt_contract_items  TYPE TABLE OF vsakd,
      ls_contract_item   TYPE vsakd,
      lv_contract_number TYPE vsak-vsnmr.

START-OF-SELECTION.

  " Create Service Contract Header
  ls_contract_header-vsnmr = '1000001'.          " Contract Number
  ls_contract_header-kunnr = '0000001234'.       " Customer Account
  ls_contract_header-vtype = 'Z001'.             " Contract Type (Support)
  ls_contract_header-vsart = 'Z'.                " Service Agreement Type
  ls_contract_header-bgdat = sy-datum.           " Begin Date
  ls_contract_header-endat = sy-datum + 365.     " End Date (1 year)
  ls_contract_header-bedat = sy-datum.           " Billing Start Date
  ls_

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change