bluefunda.com Contact Us

Troubleshooting #

Solutions to common problems with SAP connections, linting, the AI agent, GitHub, and the editor.

SAP Connection #

System Shows “Disconnected” After Adding #

  1. Verify the host URL includes protocol and port: https://sap-dev.company.com:44300
  2. Confirm the client number (e.g., 100)
  3. Check that ADT services are active in SICF: /sap/bc/adt
  4. Ensure network access — VPN may be required
  5. Click Test Connection in the Add System dialog for a specific error message

“Authentication failed” (HTTP 401) #

  • User may be locked — check SU01
  • Password may have expired — reset via SAP GUI
  • Verify the username is correct

“Service Not Found” (HTTP 404) #

ADT services are not activated. In transaction SICF, activate the path /sap/bc/adt and its entire subtree.

Connection Drops Periodically #

The editor polls every 15 seconds. If the SAP system has aggressive session timeouts (e.g., rdisp/gui_auto_time), sessions may expire. The editor re-authenticates on the next operation. Contact your Basis administrator about ICF session timeout settings.

“Lock Conflict” When Saving #

Another user or session has the object locked. Close the object in the other tool (Eclipse ADT, SE80), wait for the lock to expire, or ask the other user to release it (transaction SM12).

Linting #

abaplint Shows False Positives #

abaplint runs client-side without SAP data dictionary access. It cannot resolve custom data elements, table types, structures from includes, or standard SAP classes. These appear as “unknown type” warnings. Use server-side syntax check (Ctrl+Shift+B) for definitive validation.

Linting Not Running #

  1. Verify offline linting is enabled: SAP menu > Connection Settings > Enable offline linting
  2. Check the file has ABAP content
  3. Close and reopen the tab to trigger a fresh lint
  4. Check the browser console (F12 > Console) for Web Worker errors

Problems Panel Empty #

  • Panel may be collapsed — toggle with Ctrl+J
  • Make sure the Problems tab is selected (not Output or Transpiler)
  • Verify the correct file is active in the editor

AI Agent #

AI Panel Shows “Offline” #

The MCP agent connection is not established. Possible causes:

  • The abaper-mcp backend service is down
  • Network issues between browser and backend
  • The abaper-bff proxy is not routing correctly

The AI can still answer general ABAP questions without MCP tools, but cannot interact with SAP.

Response Stops Generating #

  1. Click Stop to cancel the current request
  2. Click Clear to reset the conversation
  3. Retry your prompt

SSE streams can be interrupted by network timeouts or proxy limits.

AI Generates Incorrect Code #

Always review generated code before saving:

  1. Run syntax check (Ctrl+Shift+B) after applying suggestions
  2. Run unit tests to verify correctness
  3. Verify naming conventions match your organization’s standards

Tool Execution Fails #

  • get-object fails: Object may not exist or SAP is unreachable
  • activate-object fails: Syntax errors in source — fix first
  • run-unit-tests fails: Object must be activated before running tests

GitHub #

“Connect GitHub” Not Working #

  1. Verify pop-ups are not blocked in your browser
  2. If you previously denied access, re-authorize in GitHub Settings > Applications

File Tree Not Loading #

  1. Verify repository format is owner/repo
  2. Select a branch before clicking Load File Tree
  3. The repo must be accessible with your token (public or authorized private)

Token Expired #

Click Disconnect in GitHub Explorer, then Connect GitHub to re-authenticate.

Editor #

Code Not Saving #

  1. Verify SAP connection is active (green dot in status bar)
  2. Check the Output panel for error messages
  3. If ETag conflict appears, the object was modified externally — close the tab and reopen with Ctrl+P

Keyboard Shortcuts Not Responding #

  1. Click in the editor area to ensure it has focus
  2. Some browser shortcuts (e.g., Ctrl+S for page save) may conflict — the editor captures most when focused

Slow Performance #

  1. Close unused editor tabs — each maintains a Monaco model in memory
  2. Reduce pinned packages — each expansion triggers API calls
  3. Very large files may slow abaplint despite the 300ms debounce

Transpiler #

Transpilation Fails #

The transpiler supports a subset of ABAP. Common failures:

  • Dynamic CALL, complex field-symbol assignments
  • References to SAP standard types or classes
  • ABAP SQL statements (SELECT, INSERT, etc.)

JavaScript Execution Errors #

The sandbox is limited. Transpiled code calling external functions or browser-incompatible features will fail. Check the error message in the console pane.

Browser #

Settings Lost #

ABAPer stores settings in localStorage. Clearing browser data removes system configs, GitHub tokens, and layout preferences. Re-add them after clearing.

Multiple Tabs #

Each tab maintains its own state. Changes in one tab (e.g., adding a system) do not appear in other tabs until refreshed.

Getting Help #

  1. Check the Output panel for error details
  2. Open browser dev tools (F12) — check Console and Network tabs
  3. Contact your ABAPer administrator for backend issues
  4. Report bugs at github.com/bluefunda/abaper/issues
March 2, 2026
Edit this page