Skip to main content

Intro

SAP has many systems. This article addresses connecting to data from the SAP ECC (ERP Central Component) tool. This connector consists of several modules, including utilities for marketing and sales, field service, product design and development, production and inventory control, human resources, finance and accounting. SAP ERP collects and combines data from the separate modules to provide the company or organization with enterprise resource planning.

Primary Use Cases

  • Just in time inventory tracking

  • Finance

  • Production quality and efficiency

  • Profit and loss tracking

  • Availability of critical equipment

Primary Metrics

  • Purchase orders

  • Purchase requests

  • Income statement

  • Balance sheet

  • General ledger

  • Sales orders

  • Accounts receivable

  • Accounts payable

  • Materials

  • Manufacturing

Primary Company Roles

  • CEO

  • CFO

  • HR

  • Sales Manager

Average Implementation Time

80 hours

Ease of Implementation (on a 1-to-10 scale with 1 being easiest)

10

Architecture

The architecture of this connection can be summed up as follows:
sap_architecture.png
  1. A Service-Oriented Architecture (SOA) is created in ECC and published for subscription (Publish & Subscribe).
  2. The service generates a Web Service Definition Language (WSDL) XML file which defines the flow of data.
  3. Domo then calls the service through the WSDL and requests data as defined by the WSDL.
  4. ECC then interrogates the call and sends data through the SOA packet.
  5. This is all controlled and defined in SAP ECC and Netweaver.

Connection Summary

To connect to SAP data in Domo, you must establish a DOMO-SAP data link. To do this, you will go through all of the following steps. If a step contains a hyperlink, you can click on that link to read about this step in more detail.
  1. Do all of the following in your development system:
    1. Establish an RFC user for DOMO
    2. Create the ZZDOMO Function Group
    3. Find your ICF server path
    4. Load your first DOMO function module
    5. Create an Enterprise Service
    6. Publish your new service using SAP SOA
    7. Send an email to DOMO with:
      • Server Path
      • DOMO RFC username and password
    8. Test your first web service with a DOMO representative
    9. Load all additional web services
    10. Test all services in the Development Environment
  2. Transport all of the above to a Quality Assurance System and test thoroughly.
  3. Transport all of the above to a Production, or BI System.

Connection Steps

Step 1: Establish an RFC user for Domo

To enable communication between the SAP ERP back-end system and DOMO, you must create an RFC user in the SAP ERP system. To establish an RFC user for Domo,
  1. Log onto the SAP ECC system.
  2. Access the activity using one of the following navigation options:
    1. Call transaction code SU01.
    2. In the SAP ERP GUI, choose Tools > Administration > User Maintenance > Users.
  3. In the User field, enter ERP2DOMO.
  4. Select Create (F8).
  5. On the Maintain User screen, enter information as shown here:
    1. On the Address tab page, enter the following:
      • Last Name: ERP2DOMO
      • Function: <Enter your function>
    2. On the Logon Data tab page, enter the following:
      • User Type: System
      • Password: <Enter your password>
    3. On the Defaults tab page, enter the following:
      • Logon Language: EN
    4. On the Profiles tab page, enter the following:
      • Profile: SAP_ALL and SAP_NEW
    5. Save your entries (Ctrl - S).
    Note: The ERP2DOMO user has the profiles SAP_ALL and SAP_NEW assigned, which gives him full authorization rights. If this authorization is not applicable to your project, you can restrict the rights of this user according to SAP Note 0338537.

Step 2: Create the ZZDomo Function Group

After establishing your RFC user in the SAP ERP system, you must next create the ZZDomo function group. To create the ZZDomo function group in the SAP ERP system,
  1. Run transaction SE80 (/nSE80).
    sapimages_2_1.png
  2. Select Repository Browser.
  3. Select Function Group in the menu.
  4. Enter ZZDOMO in the empty field then hit Enter.
    sapimages_2_2.png
  5. Click Yes.
  6. In the Short text field, enter Domo Function Group, then hit Enter.
  7. Select your Business Intelligence package then click Save. (If you don’t have a B.I. package, use a package starting with “z”).
  8. Enter or select your CTS request number for your Domo development, then click Save.
    sapimages_2_3.png

Step 3: Find Your ICF Server Path

To find your ICF server path,
  1. Run transaction SICF (/nSICF ).
    sapimages_3_1.png
  2. Click the Execute icon.
    sapimages_3_2.png
  3. Navigate to path default_host > sap > bc > gui > sap > its > webgui > SE61-DISPTXT.
  4. Right-click and select Test Service.
    sapimages_3_3.png
    If the webgui service does not contain the SE61-DISPTXT sub-element, right-click on the webgui service and select Test Service.
  5. Copy the IE path and email it to Domo.
    sapimages_3_4.png

Step 4: Load Your First Domo Function Module

Use the following set of steps to load all Domo function modules. You can find specifications for all available function modules in Function Module Specifications.
  1. In your development client, run transaction SE37 (/ nSE37 ).
  2. Input the provided function module name, then click Create. In this example, the name is Z_DOMO_PP.
    sapimages_4_1.png
  3. Enter ZZDOMO in the Function Group field.
    sapimages_4_2.png
  4. In the Short text field, describe your function module.
  5. Click Save.
  6. In the Import tab, enter the input fields from your load sheet. Make sure to check the boxes for Optional and Pass Value.
    sapimages_4_3.png
  7. In the Attributes tab, select Remote Enabled Module.
    sapimages_4_4.png
  8. In the Tables tab, enter your return tables from your load sheet.
    sapimages_4_5.png
  9. Copy the code section from your load sheet.
  10. Paste the copied code into the Source code tab.
    sapimages_4_6.png
  11. Click the Check icon.
    sapimages_4_7.png
  12. Click the Save icon.
    sapimages_4_8.png
  13. Click the Activate icon.
    sapimages_4_9.png
  14. Click the green checkmark at the bottom of the screen.
Congratulations, you have created a function module!

Step 5: Create an Enterprise Service

To create an enterprise service,
  1. Run transaction SE80 (/nSE80 ).
  2. Under Function Group, enter ZDOMO then click on the dropdown to open the list of function modules.
  3. Right-click on your new function module and select Create > Enterprise Service.
  4. Name the new service and give it a description, then click Continue.
  5. Click Continue again.
  6. Select a security profile, then click Continue.
  7. Select your Package and Transport Request, then click Continue.
  8. Click Complete.
  9. Click Activate.
  10. Click Continue.

Step 6: Publish Your New Service Using SAP SOA

To publish your new enterprise service,
  1. Run transaction SOAMANAGER (/ nSOAMANAGER ). This launches the web-based SOA Manager.
  2. Click Log On.
  3. Log in using your ECC credentials.
  4. Select Service Administration.
  5. Select Single Service Configuration.
  6. In the Search Pattern field, enter the name of the new enterprise service, then click Go.
  7. Select your service, then click Apply Selection.
  8. Open the Configuration tab.
  9. Click Create Endpoint.
  10. In the Service Information dialog, enter the following:
    • The service name (match the name of the service)
    • A description
    • A binding name
  11. Click Apply Settings.
  12. Check the box for User ID/Password.
  13. Scroll up and click Save.
  14. Open the Overview tab.
  15. Click Display selected Binding’s or Service’s WSDL URL.
  16. Copy the URL and email it to Domo.

Next Steps

Once you have completed all of the above steps, you have only a few tasks remaining. These tasks are as follows:
    1. Send an email to DOMO with:
      • Server Path
      • DOMO RFC username and password
    2. Test your first web service with a DOMO representative
    3. Load all additional web services
    4. Test all services in the Development Environment
  1. Transport all of the above to a Quality Assurance System and test thoroughly.
  2. Transport all of the above to a Production, or BI System.

Function Module Specifications

Use the following table to locate specification sheets in.docx format for each function module (as required in Step 4 above).

Data Type

Function Module

Tables

Link to Spec Sheet

Costs

Z_DOMO_COST

COBK, COEP

Cost Details Specification.docx

Cost Element Group

Z_DOMO_COST_KAH3

KAH3

NOT YET AVAILABLE

General Ledger:Actual Line Items

Z_DOMO_FAGLFLEXA_SO

FAGLFLEXA, BKPF, SKA1

FAGLFLEXA Specification.docx

Cost Center Master

Z_DOMO_CSKS

CSKS

NOT YET AVAILABLE

General Ledger Totals

Z_DOMO_FAGLFLEXT

FAGLFLEXT

FAGLFLEXT Specification.docx

General Ledger Details

Z_DOMO_FAGLFLEXT_COST

CEPC, CEPCT, SKB1, SKAT, TFKBT

NOT YET AVAILABLE

Financial Documents

Z_DOMO_FI_DOC

BKPF, BSAD, BSAK, BSID, BSIK, BSEG

FI Documents Specification.docx

Financial Documents GL Detail

Z_DOMO_FI_DOC_GL

BKPF, BSIS, BSAS

FI GL Documents Specification.docx

Account Master

Z_DOMO_GLT0

GLT0

GLT0 Specification.docx

Inventory

Z_DOMO_INVENTORY

MARD, MARC

Inventory Specification.docx

Profitability Analysis

Z_DOMO_KE30

CE31010

NOT YET AVAILABLE

Purchase Orders

Z_DOMO_PO

EKKO, EKPO

Purchase Order Specification.docx

Sales Billing

Z_DOMO_SALES_BILLING

VBRK, VBRP, VBPA, MVKE

Sales Billing Specification.docx

Sales Documents

Z_DOMO_SDOC

VBFA

Sales Document Specification.docx

Sales Orders

Z_DOMO_SO

VBAK, VBAP, VBEP, VBKD

Sales Orders Specification.docx

Address Master

Z_DOMO_ADR

ADR6, ADRC

Address Specification.docx

Cross Application Time Card

Z_DOMO_CATS

CATSDB

Cross Application Time Card Specification.docx

Customer Master

Z_DOMO_CM

KNA1, KNVP, KNB1, KNKK

Customer Master Specification.docx

Cost Center Master

Z_DOMO_COA

SKA1

NOT YET AVAILABLE

Cost Totals

Z_DOMO_COST_TOTAL

COSS, COSP

Cost Totals Specification.docx

Delivery

Z_DOMO_DELIVERY

LIKP, LIPS

Delivery Specification.docx

Expense Details

Z_DOMO_EXPENSE_COE

COVP

Expense COE Specification.docx

Expense by Vendor or Customer

Z_DOMO_EXPENSE_PCA

GLPCA

Expense PCA Specification.docx

Expense PCT Details

Z_DOMO_EXPENSE_PCT

GLPCT

Expense PCT Specification.docx

Materials Documents

Z_DOMO_MAT_DOC

MKPF, MSEG

Material Documents Specification.docx

Material Master

Z_DOMO_MM

MARA, MVKE, TVM5T, MARM, MBEW, T001W, MAKT

Material Master Specification.docx

Product Hierarchy

Z_DOMO_PH

T179T

Product Hierarchy Specification.docx

Purchase Order History

Z_DOMO_PO_HIST

EKBE

Purchase Order History Specification.docx

Pricing

Z_DOMO_PRICING

KONH, KONP, KONV

Pricing Specification.docx

Reservations

Z_DOMO_RESB

RKPF, RESB

Reservations Specification.docx

Messages

Z_DOMO_T001

T001, T001S

Messages Specification.docx

Vendor Master

Z_DOMO_VM

LFA1, LFB1

Vendor Master Specification.docx

Account Master joined with Chart of Accounts

Z_DOMO_COA_GL

COA_GL

NOT YET AVAILABLE

Relationships in GOS

Z_DOMO_SRGBTBREL

SRGBTBREL

NOT YET AVAILABLE

Sales Status

Z_DOMO_SALES_STATUS

VBUK, VBUP

NOT YET AVAILABLE

Note: The hyperlinks in the Link to Spec Sheet column does not point to any documentation.

Troubleshooting

  • Test the connection to the web service using SoapUI.
  • Run the function module locally in the SAP environment.