Troubleshooting
Common SAP errors and what they actually mean. See Overview for the concepts behind these.
| Symptom | Likely cause & fix |
|---|---|
501 … *_GET_ENTITY / CREATE_ENTITY not implemented | You called a stateless CRUD op on a transactional service. Use open_* / update_* / post (soft-state) or the curated action. |
400 Property '<X>' is invalid | You sent fields the create doesn’t accept (e.g. inline line items, or fields on the wrong entity). Open first, then MERGE fields onto the right entity. |
RAISE_SHORTDUMP when creating a line item | You POSTed a draft child to its flat entity set. Fill the auto-created row with update_*; add extra lines through the parent navigation (the add_* action / curated helper). |
404 The request URI contains an invalid key predicate | The session keys are off (wrong root). Re-open and use the sessionId the connector returned; don’t hand-build keys. |
Action returns ActionOk: true but no items derived | A determination didn’t run. Set the mandatory header fields (e.g. company code, document date) before the derivation step. |
401 | Wrong/missing sap-client, or bad credentials. |
403 | Missing service authorization (S_SERVICE) for the user — ask SAP Basis to grant it. |
__count = 0 on a billability/value-help lookup | No data matches (e.g. PO not yet billable). This is data, not an error. |
Still stuck?
Re-read the action’s schema with getAction (it carries the exact field names and
which value helps apply), and confirm you’re using the right
namespace for the task.