Not able to add the Live Process “General Ledger Master Record Creation Process”

[BillGiotDel]

Hi everyone,

On our SAP BTP we are not able to add the Live Process “General Ledger Master Record Creation Process”.

When configuring the WM_CF_SPACE_PROVIDER we get the 404 error when testing.

Does someone know how to successfully connect to this destination?

[Sesh_Sreenivas]

Hello,

WM_CF_SPACE_PROVIDER is required to import a live process package from SAP Build Process Automation Store. I believe that you have created it following our help documentation, especially the format of the URL.

You can ignore the 404 error when you test this particular destination. The 'Test Connection' pings the URL for existence and in this case, it does not necessarily confirm the accuracy of the data maintained. The URL that needs to be maintained in the destination is not complete (hence the 404 error) and that is expected. The URL along with credentials maintained in the destination are used within the Store to import the package.

[BillGiotDel]

Hi,

How can we validate if the destination is correct? Or is there no way?

[Sesh_Sreenivas]

There is no way to check this destination from the BTP cockpit. If you have followed the documentation to create the destination, then the import of Live Process content package should be successful. If not, then please share the error message that you get.

[BillGiotDel]

We followed the documentation and still can't add the Live Process.

We tried adding the Live Process via the Process Flexibility Cockpit and we get this error referring to the destination not being correct.

[Sesh_Sreenivas]

The probable cause for this error message is either or both of the following:

1. Wrong URL maintained in the destination - here is the solution:

• make sure that the URL is exactly as described in the help document. Recheck the landscape and the space id for correctness. Maybe, post the URL here (mask any sensitive information).

2. Authentication error - here is the solution:

• Check once more if the credentials are correct (I am assuming you have already provided the space developer role as in the screenshot. No harm in checking again).
• Use a user who does not have two-factor authentication enabled.