Skip to Content
avatar image
Former Member

Do not want to record BRFplus Decision table entries in Customizing TR.

Hi Experts,

I am working on "EHP6 FOR SAP ERP 6.0". I created an Application with Storage type as 'Customizing'. I want to transport BRFplus application to other systems, so I have to make it customizing only.

Now, I am able to make entries in decision table, but if someone else trying to create entries in decision table than they are getting error "User <> has no task assigned to transport request <>".

Issue: I don't want to record the entries in transport request.Moreover I want that all user should be able to maintain the entries independently in all systems.

Solution that I tried: I added an application exit class and in the method GET_CHANGEABILITY, I changed the parameter CV_CHANGEABLE to X based upon certain conditions.

But still I am getting same error "User <> has no task assigned to transport request <>".

Please suggest how to resolve this issue.

Regards,

Khushbu

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jan 15, 2017 at 02:28 PM

    Hi,

    can you also set the parameter CV_CHANGE_RECORDING to ABAP_FALSE. Never tried it, but this parameter should prevent the recording of changes in transport requests.

    However, overriding the changeability in productive environments is quite dangerous as you might risk inconsistencies due to changes coming via transport request from DEV and QA system vs the changes you made directly in the system.

    Best regards,

    Christian

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 16, 2017 at 03:11 AM

    hi Khushbu

    Did you try below solution by adding AUTHORITY_CHECK as well

    Also this may be dependent on the netweaver version being used

    "You need to implement two application exits “AUTHORITY_CHECK” and “GET_CHANGEABILITY” to make the decision tables maintainable in non-development environment. Application exit AUTHORITY_CHECK: If the AUTHORITY_CHECK application exit is implemented, it is called before the standard authorization check is performed. The result of the custom check is returned as a Boolean parameter ev_passed. Additionally, the standard authorization check can be either skipped completely or only for referenced objects.

    Check these 2 links which talk about the similar issue

    https://archive.sap.com/discussions/thread/1604811

    And the solution provided here.

    https://blogs.sap.com/2015/03/23/brfplus-application-exits-ability-to-maintain-entries-in-decision-tables/

    Let me know if that helps?

    Regards

    Vinita

    Add comment
    10|10000 characters needed characters exceeded