Pull failed on ABAP Cloud with Message Pull aborted: Repository pull aborted - Job canceled after system exception ERROR_MESSAGE

[SaschaWaechter]

On our ABAP CLoud System pull fails with Error Message

Pull aborted: Repository pull aborted - Job canceled after system exception ERROR_MESSAGE

In the object log everything is green.

Don't know what was wrong?

Any idea or maybe a problem with newer cloud release. The error message is not very clear.

Thanks

[GeorgReichert1]

Hello Sascha, thank you for reporting this issue. Could you please name the system where it occurs? Thanks and regards Georg

[SaschaWaechter]

Thanks for the reply. Which "system name" do you need because it's or own ABAP instance in BTP. (No trial or free tier)

[ThomasPloski]

Hi Sascha,

Is there a possibility to logon to the system and check the application logs?

Best regards, Thomas

[jabap]

We encountered the same issue on BTP ABAP Environment. After trying to activate the objects anyways, we saw that two function groups were not imported, so we decided to manually create them (and all function modules inside of those). But the system won't let you save the function modules:

So all function modules had to be changed (just remove * comments). Furthermore, one BAdI-call had to be removed, because the BAdI was not imported into the system (and we couldn't find it in the repository?):

With these manual changes, all objects in the /DMO-packages can be activated.

Update 2023-10-09:

• the pull request gets stopped before all objects are loaded into the system. After manually adding the function groups+modules, we had to redo a pull and only pull certain objects (e.g. number range objects)
• modifying the data generator class to not include the BAdI-call will change behavior of demo data generation, so maybe it's better to replace it with the logic that gets executed in the classes that implement the BAdI