cancel
Showing results for 
Search instead for 
Did you mean: 

Error "Create an application copy. There is no copy maintained currently" in ODN determination app

JoergAldinger
Active Contributor
0 Kudos
156

Hello everyone,

We have gone through all the prerequisites of configuring Official Document Numbering. But when accessing the ODN determination app and selecting the business process, we get the following warning and cannot continue: "Create an application copy. There is no copy maintained currently":

JoergAldinger_0-1726499452015.png

Do you have any idea what we are missing here?

Thanks!

Joerg.

View Entire Topic
Stefan_Scholten
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Jörg,

Please check the newly available documentation below and compare your prerequisites for setting rules for Official Document Numbers.

There are now mandatory prerequisite steps for using the ODN Determination BRF application as a reference for all supported business processes. With this a SAP reference application must be copied into the customer specific application.

Basically without having system access further answering  this question would be heavily possible – so in case of an unresolvable error I would suggest to open an corresponding incident.

Best regards

Stefan

=============

Latest version:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/60a09f68f2444ceca31dcac2e7017945/6edf3adf10be469eaf14a53a...

Version of 2408 release:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/60a09f68f2444ceca31dcac2e7017945/6edf3adf10be469eaf14a53a...

JoergAldinger
Active Contributor
0 Kudos

Hello Stefan! Thanks for the link. I had been trying to follow these steps, but I've hit some roadblocks.

For example:

  • I haven't been able to create the package in step 1 (I'm requesting help from the dev team to do that, but it would be nice to have a link to step-by-step instructions in the documentation.) 
  • The search for the app id (step 4) in the customizing tenant turns up empty:
    JoergAldinger_0-1726579831895.gif

    Might that be because the package from step 1 is not existing yet?

Thanks,

Joerg.