使用oDataV2Model.callFunction时提示Function XXX元数据未找到

Alright, let's break down the possible causes and troubleshooting steps for this issue, since you've already confirmed the Function Import works in other tools and basic OData operations are functional.

1. Fix the typo in your callFunction configuration (most likely root cause!) #

Looking at your code, you've written methode: "POST" — but the correct parameter name in SAPUI5's ODataModel.callFunction API is method (English spelling, not German).

This typo means UI5 is ignoring your HTTP method setting and defaulting to GET. Since your Function Import is defined with m:HttpMethod="POST" in the metadata, UI5 can't find a matching GET-based Function Import, hence the error.

Corrected code snippet:

oDataModel.callFunction("/XXX", {
    method: "POST", // Fixed spelling here
    urlParameters: { Parameter1: "", Parameter2: "", Parameter3: new Date()  },
    success: function (oResultMod) {
        console.log(oResultMod);
    },
    error: function (oError) {
        console.log(oError);
    }
});

2. Verify UI5 has loaded the correct metadata #

Sometimes UI5 might be using cached metadata that doesn't include your Function Import:

• Open your browser's DevTools → Network tab, find the /$metadata request sent by UI5. Check the response XML to confirm the <FunctionImport Name="XXX"> entry exists.
• If the metadata is outdated, clear your browser cache, or add the cache: false setting to your dataSource in manifest.json to force a fresh metadata load:

  "odataSource": {
      "uri": "/sap/opu/odata/sap/ZUPD_C_UPDATES_CDS/",
      "type": "OData",
      "settings": {
          "odataVersion": "2.0",
          "cache": false
      }
  }
  

• Alternatively, run oDataModel.getServiceMetadata() in the browser console and inspect the output to confirm the Function Import is present.

3. Validate Function Import path and namespace #

Double-check that the path you're using (/XXX) matches the exact name in the metadata. Even though Gateway Client works, ensure there's no missing namespace or entity container prefix (though typically, direct /{FunctionImportName} works for V2 services).

Compare the full request URL from Gateway Client (e.g., /sap/opu/odata/sap/ZUPD_C_UPDATES_CDS/XXX) with what UI5 is sending (check Network tab for the callFunction request).

4. Check parameter type compatibility #

Your Parameter3 is defined as Edm.DateTime in metadata. While this shouldn't cause a "not found" error, ensure UI5 is formatting the date correctly for OData V2:

• Try replacing new Date() with an OData-compliant string, e.g., "2024-05-20T00:00:00" or the /Date(timestamp)/ format, to rule out any type-related parsing issues that might interfere with request routing.

5. Rule out UI5 version bugs #

You're using UI5 version 1.71.40, which is a relatively old maintenance release. Check the SAP UI5 Release Notes for your version to see if there are known issues with Function Import handling in OData V2 models. If possible, upgrade to the latest patch version of 1.71.x to see if the issue is resolved.

6. Confirm BOPF/CDS metadata alignment #

Even though Gateway Client works, UI5 might be stricter about certain metadata attributes:

• Verify that the sap:action-for="ZZZ.AAA" attribute in your Function Import points to a valid entity type that exists in the metadata. If this reference is broken, UI5 might fail to recognize the Function Import.
• Ensure your CDS definition for the Function Import is correctly exposed via BOPF, with all parameters and return types properly mapped (since you confirmed SEGW works, this is less likely, but worth a quick check).

内容的提问来源于stack exchange，提问作者Erch