Skip to Content
avatar image
Former Member

ZUJF_COPY_FILES_TO_TARGET_SYS returns error

We are attempting to copy files from our QA system to PRD. How do we resolve the RFC error?

selection.png

rfc-error.png

selection.png (104.3 kB)
rfc-error.png (12.9 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Oct 02, 2017 at 06:54 PM

    Sorry, but please explain, what are you doing!

    ZUJF_COPY_FILES_TO_TARGET_SYS - looks like some custom development!

    Add comment
    10|10000 characters needed characters exceeded

    • "ZUJF is an SAP file copy tool" - it's not an official SAP tool, it's some code that you can use on your own risk. From this document:

      "Any software coding and/or code lines / strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment."

      Perform debugging yourself.

  • avatar image
    Former Member
    Oct 02, 2017 at 07:56 PM

    We have DEV. TRAINING, QA, UAT, PRD environments. To copy reports and input schedules through this chain is very time consuming. We do not use transports for BPC reports and input schedules. Considering SAP high tech I am amazed there isn't a tool already in place for such efficiencies. To make a change on a report starting in DEV and 'promote' it - with is actually copy it - is very time consuming. We have to log into each environment and overwrite the file one by one. I am open for suggestions. ??

    Add comment
    10|10000 characters needed characters exceeded

    • "We do not use transports for BPC reports and input schedules." - why?

      If you want to use unofficial tool you need to have a person able to debug it. It's the same story with all unofficial tools.

      Nothing is perfect :)

  • avatar image
    Former Member
    Oct 02, 2017 at 08:29 PM

    The reason is there are different teams managing different content. To create a transport for one or few reports is counterproductive to efficiencies. The number of transports to support ongoing changes will become untenable. In BPC we do one transport for go-live for the entire environment. From this point on reports and input schedules are copied not transported. We are not a small SAP shop. With over 500 users nationwide, with which we have more than 50 developers for reporting objects, being subject to transports for reporting will kill productivity and generate distaste for the tool/project. We sell productivity and efficiency. If a change is made to a report or a new report is created - non-admin people (usually a small group) with admin access should be able to simply grab the files and copy them top update DEV to UAT to TRAINING to QA to PRD servers than log into one by one for each file. we shouldn't need to tie down Admins who are far removed from BPC business development (reports) to copy a file.

    Add comment
    10|10000 characters needed characters exceeded

    • Different companies use different workflows! I remember some huge company that don't use UJFS templates storage at all :)

      In general if you need a productivity tool - do it yourself and maintain it yourself! Not everything can be available from the box. Do you have locally developed badi's in your system? Same approach.

      P.S. I am not working for SAP