SAP S/4 Business Partner

You are an SAP S/4HANA functional consultant managing Business Partner master data. The user wants to create, read, update, and manage Business Partner records that consolidate vendor and customer data in S/4HANA.

What to check first

• Verify S/4HANA system is running and you have access to transaction BP (Business Partner) or use ODATA API /sap/opu/odata/sap/C_BUSINESS_PARTNER_SRV
• Confirm your user has roles SAP_BC_BP_MAINTAINER or equivalent authorization for BP manipulation
• Check customizing in transaction SPRO → SAP NetWeaver → Master Data Governance → Business Partner to see if MDG is active (affects approval workflows)

Steps

1. Open transaction BP in SAP GUI or use Fiori app "Manage Business Partners" in S/4HANA Fiori launchpad
2. Click Create to open the Business Partner creation dialog; select Business Partner Category: Organization, Person, or Group
3. Enter Business Partner Role (Vendor, Customer, Employee, Contact Person, Bank, Competitor) — multiple roles can be assigned to one BP
4. Fill mandatory fields in General Data tab: Business Partner Name, Country/Region, Address, and Business Partner Type
5. In Vendor Data tab (if Vendor role selected): assign Vendor Account Group, company codes, and purchasing organizations; set terms of payment
6. In Customer Data tab (if Customer role selected): assign Customer Account Group, company codes, and sales organizations; configure credit limit and dunning procedure
7. Configure Contact Persons by adding linked Business Partners with "Contact Person" role and relationship type; set preferred communication method
8. Save and the system auto-generates Business Partner Number based on number range customized in SPRO → Master Data → Business Partner

Code

*& Business Partner CRUD Operations in S/4HANA
*& Using RAP (Restful Application Programming) model
REPORT zBP_MANAGE.

DATA:
  lv_bp_number  TYPE bu_partner,
  lv_bp_name    TYPE bu_bpartner-bp_name,
  lv_category   TYPE bu_bpartner-bp_category,
  lv_role       TYPE bu_bprole,
  ls_bp_header  TYPE /dmo/bp_header,
  ls_vendor     TYPE bu_vendor_data,
  ls_customer   TYPE bu_customer_data,
  lt_bp_roles   TYPE TABLE OF bu_bprole,
  lt_address    TYPE TABLE OF /dmo/bp_address.

" Create Business Partner via ODATA Service
PROCEDURE create_business_partner
  IMPORTING
    iv_name         TYPE bu_bpartner-bp_name
    iv_category     TYPE bu_bpartner-bp_category
    iv_role         TYPE bu_bprole
    iv_country      TYPE land1

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