Message nr 00347 by transaction FBV0 for field BKPF-REINDAT.

Hello experts,
I did a modification in the screens 0100 and 0700 of the program SAPLF040.
I added an inputfield for BKPF-REINDAT on the screen 0100 and an outputfield on the screen 0700.
When I execute transaction F-63 (register a document), I can fill in this inputfield and in the table BKPF the field REINDAT is filled in with the data.
Then I call transaction FBV0 (booking the document), and on the screen the data for BKPF-REINDAT is showed. That is good. But if I then execute the booking, I receive the message 00347 – field BKPF-REINDAT (input is not allowed).
What can I do for a succesfull booking?
Kind regards,
Luc

hi all,
the solution for this problem is "Enhancement":
Program:"SAPMF05A"
Enhancement Implementation Type:"Static Enhancement Point/Section"
Enhancement Implementation Point/Section: "\PR:SAPMF05A\FO:REF_FUSSZEILE\SE:BEGIN\EI"
    LOOP AT SCREEN.
      IF screen-name = 'BKPF-REINDAT'.
        screen-input      = 1.
        screen-output     = 1.
        screen-active     = 1.
        screen-invisible  = 0.
        screen-display_3d = 1.
        screen-value_help = 1.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
Best regards.

Similar Messages

  • Message no. KI506: Transaction RKP2 for version 0 is not permitted

    Hi CO Gurus,
    I'm getting error Message no. KI506: Transaction RKP2 for version 0 is not permitted in Transaction code KP26 when I'm trying to extend the Activity types cost for year 2009. Before that I already extended Version 0 for year 2009.
    Now system is not allowing me to enter and maintain values for a particular combination of cost center and activiy types.
    Please help out.
    Thanks & Regards,
    Abu Arbab

    Hi Suraj,
    Thanks for immediate help.
    Best Regards,
    Abu Arbab

  • Units field XYZ for field ABC of DataSource ZRST Message no. R8147

    HI,
    When I'm trying to SAVE my datasource ZRST, I've got following error.
    Units field XYZ for field ABC of DataSource ZRST Message no. R8147
    In extraction structure of this datasource thare are at least two fields that use the same unit field.
    Accordign SAP note no 867795:
    One of the fields is displayed and another is hidden.
    Then the unit field is hidden and the above error occurs.
    This note is valid for component SAP_ABA release 700. I'm running my R/3 source system on SAP_ABA     620.
    Could it be the same case as described in this SAP  note?
    Anybody got same problem? Please advise.
    Thanks
    m./

    Hi,
        Please check the dependencies on the fields, as some fields should have the units defined ,check the fields and activate the datasource.
    hope this helps,
    thanks,
    vrrp.

  • Transaction variant for VA02 is not working for few fields

    Hi All,
    I have created a transaction variant for VA02. Made the necessary code changes for populating the variant name in MV45AFZZ. It is working fine for all the screens and all the fields except for second screen of VA02.
    First screen - Enter sales order number.
    Second screen - Overview screen.
    In second screen, I have disabled all the screen fields. When I run the variant, all fields are disabled except sold-to party, ship-to party and create sold to party ICON. All these fields belongs to screen 4701.
    In the transaction variant I can see that these fields screen attributes set to output only. I don't see anything different for these fields compared to other fields.
    First I thought it is because of mandatory fields. But some other mandatory fields are disabled after my changes. Why is this happening only for these 3 fields (Only for screen 4701 I can say).
    Surprisingly, if I do any action like enter/select other tab, these fields are getting disabled.
    Your inputs on this are highly appriciated.
    Thanks,
    Vinod.
    Edited by: Vinod Kumar Vemuru on Dec 31, 2009 10:01 AM

    Thanks, happy to see the reply.
    But I have given the correct names as suggested by you.
    I have also created a Transaction ZVA02 as i dont want this variant to be applied on standard VA02.
    It is working on first screen but not on subsequent screens. Am i missing something, some link or activation?
    Transaction Code VA02                  Change Sales Order
    Transaction Variant  ZTRN_VA02                       testing
    ZTRN_VA02_0102                                        SAPMV45A     102
    ZTRN_VA02_4001                                        SAPMV45A     4001
    ZTRN_VA02_4021                                        SAPMV45A     4021
    ZTRN_VA02_4050                                        SAPMV45A     4050
    ZTRN_VA02_4401                                        SAPMV45A     4401
    ZTRN_VA02_4701                                        SAPMV45A     4701
    ZTRN_VA02_4900                                        SAPMV45A     4900
    when I run this the first screen is applied correctly but what happens next.

  • Change field label for field IZWEK in transaction AS03

    Hi experts,
    I would like change field label for field IZWEK because I want use it for another purposes. Itu2019s name is Investment Reason at transaction as03.I can change name this label in reports by using se63(translation->abap object->short text->repository text->data element) and giving object name as IZWEK. I get changes in reports only, in help(F1). But I havenu2019t idea what cause change label in as03 transaction.
    Help me please.
    Regds Stenwa

    in tr. AOLK and AOLA you can change this.

  • Transaction F.5D send message a breakdown is already running for company co

    Whe I try to run the transaction F.5D send message A breakdown is already running for company code 1600 and I can't run again for this compnay code the calculate Balance Sheet Adjustment on other  hand  I see in standar table RF180 that the process in not finished since 1 day what i have to do to finish this run created?
    Thanks!
    Edited by: Otoniel Trevino on Oct 30, 2008 12:53 AM

    Hi,
           Check the Transaction Code : SM04 if still the t.code F.5d is running terminate that, or ask BASIS consultant to terminate the run.
    Regards,
    SudhaReddy.

  • "The transaction log for database 'speakasiaonline' is full." I'm getting this message when I m trying to login to speakasia website and am unable to open it. Pl help.

    The transaction log for database 'speakasiaonline' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

    What does it return?
    SELECT log_reuse_wait_desc FROM  sys.databases WHERE database_id=2
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • "Error Message" without interrupting the transaction

    We use a VB application to insert/update records in a Oracle database.
    Any user is allowed to see all fields, but not every user is allowed to update all fields. We check the right to update in a database trigger and raise an error if a user wants to update a field for which he has no rights.
    User X has the right to update field A, but he has not the right to update field B.
    Now we want to change the application
    If X tries to update fields A and B, we want to accept the new value for A, leave B unchanged and inform the user with a message like an error message without interrupting the transaction.
    Has anybody an idea how to implement this?

    In the project it's presented:
    1) how the servlet can send JSON data depending on the request's parameter
    2) how to obtain this data on the client side and show in on the page using jQuery without refreshing the whole site
    What You need to do is just to send the error (as JSON data) insetad of the values that are passed now and display this error on the page.

  • Error Message : " No value could be determined for Customer Exit Variable "

    Hello BI Experts ,
    I have created a "ZYTD_PERIOD" Customer Exit Variable  Interval  Mandatory and ready for input check mark removed.
    The reference character is '0FISCPER' .
    I want to have YTD figures when the user enter single Fiscal Year Period for variable 0P_FPER.
    So I have written below code in SE37 : EXIT_SAPLRRS0_001 and include program : ZXRSRU01
    ==================================================================
      case i_vnam.
                  WHEN 'ZYTD_PERIOD'.
                  IF I_STEP = 2.
                  LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE WHERE VNAM = '0P_FPER'.
                  CLEAR L_S_RANGE.
                  L_S_RANGE-LOW0(4) = LOC_VAR_RANGE-LOW0(4).
                  L_S_RANGE-LOW+4(3) = '001'.
                  L_S_RANGE-HIGH = LOC_VAR_RANGE-LOW.
                  L_S_RANGE-SIGN = 'I'.
                  L_S_RANGE-OPT = 'BT'.
                  APPEND L_S_RANGE TO E_T_RANGE.
                  EXIT.
                  ENDLOOP.
                  ENDIF.
    ===================================================================
    After that I use this 'ZYTD_PERIOD' variable in the query .
    Also I have used the variable 0P_FPER in another structure.
    When I execute the query by entering the value of 0P_FPER as 010.2009 or any other value ,
    I am getting below error message ,
    *No value could be determined for variable ZYTDPERIOD*_
    Below is details of this Error message ,
    Note that I have proper Master and Text data for 0CO_AREA and 0COMP_CODE loaded into BI.
    =======================================================================
    Diagnosis
    This error diagnosis is specific only to the variables 0P_FVAEX or 0P_CTPCA !
    Termination message BRAIN 632 appears:
    Could not determine value for variable 0P_FVAEX (or 0P_CTPCA).
    System Response
    1. Operation method of SAP-Exit-Variables 0P_FVAEX or 0P_CTPCA
    With queries from the CO application, both SAP-Exit-Variables look for an entry for 'controlling area'. With this controlling area from the selection screen, the SAP-Exit-Variables program reads the attributes for InfoObject 0CO_AREA (controlling area).
    With queries from the FI application, the SAP Exit Variable 0P_FVAEX looks for an entry for 'company code'. With this company code from the selection screen, the SAP Exit Variables program reads the attributes for InfoObject 0COMP_CODE (Company Code).
    0P_FVAEX determines the fiscal year variant (attribute 0FISCVARNT) from the attributes for 0CO_AREA (CO queries) or 0COMP_CODE (FI queries). 0P_CTPCA determines the currency type of the profit center local currency (attribute 0CURTP_PCA) from the attributes for 0CO_AREA.
    2. Cause of Error
    The attributes for the controlling area (InfoObject 0CO_AREA) or company code (InfoObject 0COMP_CODE) were not loaded into the BW system, or the attributes for the controlling area are not active in the BW system.
    Check whether this is the cause of the error in your BW system. Display the contents of table /bi0/mco_area or /bi0/mcomp_code using transaction se16.
    Application CO:
    Check whether the attributes 'fiscal year variant' (field FISCVARNT) and 'profit center local currency currency type' (field CURTP_PCA) are filled in the 'A' version (field OBJVERS) for the selected controlling area. If the fiscal year variant in the OBJVERS = 'A' is empty, then the error is with variable 0P_FVAEX. If the currency type of the profit center's local currency in OBJVERS = 'A' is empty, then the error is with variable 0P_CTPCA.
    Application FI:
    Check whether or not the attribute 'fiscal year variant' (field FISCVARNT) is filled in the 'A' version (field OBJVERS) for the selected controlling area. If the fiscal year variant is empty in OBJVERS= 'A', then the error is with variable 0P_FVAEX.
    Procedure
    Using InfoSource 0CO_AREA, load the attributes for the controlling area or company code into your BW system.
    Afterwards, activate the attribute changes in your BW system. To do this, use transaction rsa1, path 'Tools > Hierarchy/Attribute changes', functions button 'InfoObject list'. Choose InfoObject 0CO_AREA or 0COMP_CODE from this list, and activate the attribute changes.
    =====================================================================================
    Is there any special settings needed before writing BEx Customer Exit ?
    I have already created a project in CMOD and assinged a proper RSR00001
    and EXIT_SAPLRRS0_001 and project is active.
    Any help please ....
    Regards ,
    Amol

    My Code is as below ,
              case i_vnam.
                  WHEN 'ZYTD_PERIOD'.
                  IF I_STEP = 2.
                  LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE WHERE VNAM = '0P_FPER'.
                  CLEAR L_S_RANGE.
                  L_S_RANGE-LOW0(4) = LOC_VAR_RANGE-LOW0(4).
                  L_S_RANGE-LOW+4(3) = '001'.
                  L_S_RANGE-HIGH = LOC_VAR_RANGE-LOW.
                  L_S_RANGE-SIGN = 'I'.
                  L_S_RANGE-OPT = 'BT'.
                  APPEND L_S_RANGE TO E_T_RANGE.
                  EXIT.
                  ENDLOOP.
                  ENDIF.
                  ENDCASE.

  • How to create a transaction code for a function group with screen 100 as st

    Hello ,
    I have requirement where I need to create a function group and create screen 100, 200, 300 and include the function in the screens.
    Customer asked me to create a transaction with the screen 100 as the starting screen.
    Can you please let me know how to create a transaction code for a function group with screen 100 as starting screen.
    [ It is not a module pool program ].
    Thanks
    Prashanth.
    Moderator message - Please ask a specific question and do not ask the forum to do your work for you - post locked
    Edited by: Rob Burbank on Jun 2, 2009 11:49 AM

    Go to transaction SE93, enter a transaction code that you want and click on "create". Enter a text and select the "Transaction with Parameters" button. In the Default Values section, enter START_REPORT in the transaction field. Check the "skip initial screen" box. In the Name of Screen field section enter the following lines:
    Name of screen field:                               Value
    D_SREPOVARI-REPORTTYPE                RW
    D_SREPOVARI-REPORT                        ZPCA
    Save and transport accordingly.

  • Transaction Variant for tcode SP01

    Hi All,
    I am trying to create the transaction variant for the tcode SP01 by using tcode SHD0.
    Steps I followed are:-
    1. Create tcode ZSP01
    2. In SHD0, tcode as ZSP01 and hit the Create
    3. Control goes to Screen SP01 inital selection screen
    I need to change 'created by' as display only and cannot get the screen attributes.
    Any help will be greatly appreciated.
    Regards,
    Azhar

    Thanks for the quick reply.
    I found that SP01 is a module pool program with screen 2000 then I should be able to create the transaction variant.
    I tried creating the tcode with your suggested authorization object getting warning message 'Check object has been maintained(Press enter to reset)'  and when I press enter the auth object field will get reset.
    Thanks for your quick response and suggestions.

  • Transaction Variant for VA01

    Hi All,
    I am able to create transaction variant for transaction code MM01, XD01 and XK01 successfully. But i am unable to create transaction variant for VA01.
    And also some times i am getting error message "SAP Object SCV1(short text of variant) cannot be assigned to package ZXXX". Can you pls let me know why i am getting this error and why i am unable to create transaction variant for VA01 successfully.
    Thanks,
    Raju

    Hi,
    There is no difference in creation of the transaction variant for VA01/02. But the way it works is different. It works at order type level instead of t-code level. You have to create the variant in SHD0 and assign the same in order type customization.
    Alternatively you can populate the field TVAK-VARIANT with the transaction variant name in MV45AFZZ subroutine USEREXIT_MOVE_FIELDS_TO_VBAK/USEREXIT_FIELD-MODIFY. With out this it wont work. Just try to change the TVAK-VARIANT value in debug mode and see if it works fine. Surpricingly it works fine if you individually execute the variant.
    The error you mentioned might be because you might have given one of the screen variant name not starting with Z or Y.
    Thanks,
    Vinod.

  • Error in FB60 - Additional account assignment required for field BSEG-HBKID

    Hi Experts
    While posting an Invoice for a particular company code in FB60, we are facing the following error :
    "Additional account assignment required for field BSEG-HBKID"
    Message no. F5A122
    Diagnosis
    Additional account assignment has to be carried out for some fields on the detail screen.
    System Response
    Error message
    Procedure
    Select the relevant items and call up the detail screen.
    We are unable to post any Non PO Based Invoices in this company code.
    Kindly guide us on possible methods to rectify this error.
    Regards
    MM

    Dear,
    First Check the setup as described by Atif,
    Also in OBC4 you will not find HBKID field, for this u need to select appropriate FSG, Under Payment Transaction Group please check if own Bank field is optional or not. by doing this as optional system will show House ban Field in Payment Tab of FB60, will be enabled and there will be two field one for House Bank and Other will be for Account ID.
    Hope this helps.
    Br, Vivek

  • Error message in trans code SMQ1(backend) for material replication

    Hi All,
    I am wandering if someone can help me with this query. I have basically followed all the customisation steps requried to replicate replicate material masters from R/3 to SRM. I had infact closley followed the advise posted on the blog: How to replicate material master from R/3 to SRM
    However, once I start the initial load in SRM with trans code R3AS and thebn goto trans code SMQ1(in R/3 backend), the load has failed with the 'status' or SYSFAIL. When I double click on this message, I get the error:
    "Exception condition" EBCDIC_PROBLEM__OSSNOTE_33300 8" raised.
    I have looked at note 333008 but cannot find any clues as to what is causing the load to fail. In trans code R3AM1, the job's status only remains as 'Running' and does not change.
    Any pointers as to the cause and required workaound would be appreciated!
    Thanks
    SW.

    Hi Muthu,
    Thank you for your feedback. I have just this moment implemented the note you recommended, but this does not appear to have resolved the error message, even though the consumer has been changed from CRM to SRM in r/3 and srm.
    I basically undertook the initial load for object 'dnl_cust_basis3' only with trans code R3AS, but the system still shows the following error message in the outbound que list (trans code SMQ1) in the sender R/3 backend system:
    ""Exception condition "EBCDIC_PROBLEM__OSSNOTE_33300
    8" raised""
    I am reluctant to implement the note number (333008) within the error message as the note heavily describes the CRM 2.0 component only and shows little relevance to SRM 5.0.
    Any feedback would be appreciated. I have pasted the note contents below.
    Thanks
    SW.
    Note 333008 - XML in R/3 Adapter
    Summary
    Symptom
    For the Plugin PI 2000.1 (R/3 OLTP) and the CRM 2.0B Support Package 08, the R/3 Adapter was enhanced by an XML support.As of CRM 2.0B Support Package 7, SAP recommends to use R3A XML as a standardAs of CRM 2.0C, XML is automatically the standard setting in the server, only in the OLTP PlugIn, you have to maintain a setting.
    Additional key words
    CRM, R/3 Adapter, XML, CRM_SEND_XML, BAPIMTCS, IBM, AS/400 OS/400 S/390, DBIF_RSQL_SQL_ERROR, SQL error -302 accessing table SMOAUSP
    Cause and prerequisites
    System requirement:Plugin PI 2000.1 with at least PlugIn patch 03 or higher and CRM 2.0B Support Package 08 or CRM 2.0C on the server.(XML is possible with CRM 2.0B Support Package 07, however, Support Package 08 is recommended:if you only use Support Package 07, parameter CRM_CONVERT_ENDIAN has to be maintained even if this has no effect - see Note 207264.)
    Solution
    Introduction
    To eliminate or minimize problems that occur during the data transfer between different operating and computer systems, an XML interface was implemented in the R/3 Adapter in addition to the binary transport, which has been used so far.
    This XML interface consists of an XML generating program on the OLTP-Plugin and an XML parser on the CRM.
    The generating program generates an XML document from the data stream to be sent to the CRM System and the XML parser converts this back into the original data stream. Except for the initial configuration, the mechanism is transparent and does not require further user activities.
    Activation
    To use XML in CRM 2.0B in the initial download, you have to enter the following new parameter in table SMOFPARSFA (Transaction SM30 or R3AC6) on the CRM server:
                 Key:             R3A_COMMON
                 Parameter name:  CRM_SEND_XML
                 Parameter value: 'X'
    In CRM 2.0C, table SMOFPARSFA does not have to be maintained since XML is automatically the standard setting.
    For the data transfer with XML in delta download you must do the following
    Maintain parameter table CRMPAROLTP in PlugIn Release PI 2000.1, patch 03:Newly enter parameter name CRM_SEND_XML_FOR_DEFAULT_DEST with parameter value 'X'.
    Maintain parameter table CRMRFCPAR as of PlugIn Release PI 2000.2:Transaction SM30, set field SEND_XML of CRMRFCPAR to value 'X' for the corresponding entries
    Advantage
    The data transport in the XML format solves both the endian problem (see Note 207264) and the code page problem which existed during a data transport from or to an IBM mainframe (AS/400, S/390) to or from an ASCII-based system (NT, UNIX).
    Deactivation
    Regarding the performance, the XML format has the disadvantage that the XML parser needs CPU time (which can be processed in parallel because no database access is made).If you want to do without the XML conversion in a specially defined system landscape, then set parameter CRM_SEND_XML to blank in the CRM System, and set table CRMPAROLTP (PI 2000.1) or CRMRFCPAR (PI 2000.2) without XML in the R/3 OLTP.In addition, parameter CRM_CONVERT_ENDIAN must be maintained correctly in the CRM System (see Note 0207264).
    You can do without the XML conversion under the following conditions.
    1. The OLTP system infrastructure and the CRM system infrastructure mustbe homogeneous. Example: all OLTP application servers UNIX and all CRMapplication servers NT.
    2. You must also make sure that no application servers with different operating systems are used in future.
    3. The OLTP system infrastructure must be homogeneous.In the CRM System it is possible to limit the application servers permitted for the processing of the queues by setting a specific server group.The application servers of these group servers must be homogeneous.However, the setting is valid for all inbound queues and cannot be restricted to specific queue names.
                  You can set up a server group with Transaction RZ12, and in Transaction SMQR you can set up the server group used for the processing via menu option 'Edit' -> 'Change AS group'. For details on this, see Note 369007.
    As SAP cannot check the customer's system landscape,this option is to be classified on project basis where the responsibility is the customer's and not SAP's.
    If homogeneous system infrastructures do not exist, the time required for saving data and documents can nevertheless be significantly reduced by carrying out the XML conversion in one asynchronous step.For this, you must maintain parameter CRM_XML_BACKGROUND_PROCESSING_ON in table CRMPAROLTP. For this purpose, refer to Note 350176.
    Notice
    Since the IPC is currently not able to process the XML document of the R/3 Adapter, XML must not be activated for IPC targets in CRMRFCPAR!
    Since, in addition to the existing data mapping and data transport, the XML generation and the XML parsing is included in the sequence of operations, you must expect a download runtime which might be twice as long as usual!
    Due to performance reasons, only the '&', '<' and '>' characters are converted into XML escape sequences at present.Therefore, other special characters in text fields might cause problems and might not be output correctly on the target system.
    The XML conversion does not solve problems with multi-byte texts, for example the data exchange between a Japanese and an English codepage is not supported.
    Source code corrections
    Header Data
    Release Status: Released for Customer
    Released on: 25.07.2001  22:00:00
    Priority: Recommendations/additional info
    Category: Special development
    Primary Component: CRM-MW-ADP Middleware Adapter
    Secondary Components: CRM-MW Middleware
    Affected Releases
    Software
    Component Release From
    Release To
    Release And
    subsequent
    MDM 200 200 200  
    COM_CRMMDM 40 4.0 4.0  
    UIFRW 40 4.0 4.0  
    CGVMIC 10 100 100  
    BBPCRM 2.0 20B 20C X
    BBPCRM 3.0 300 300 X
    BBPCRM 3.1 310 310 X
    BBPCRM 3.5 350 350 X
    BBPCRM 4.0 400 400 X
    Correction delivered in Support Package
    Support
    Packages Release Package
    Name
    BBPCRM 20C

  • Transaction variant for SM37

    Hi all,
    I am trying to create a transaction variant for the "job overview" screen - this is the screen after you have selected the list of jobs. I have the deactivated some items "menu functions" - program SAPLBTCH - status - JOV_STATUS, but there are not working when I test these.
    Any ideas ?

    Hi JC,
    This is how it works (sorry for the German :-):
    *   Pruefen der Loesch-Berechtigung,
    *   Eigene Jobs duerfen ohne weitere Pruefung gelscht werden.
    *   Jobs anderer Benutzer drfen nur gelscht werden, wenn Lsch-
    *   berechtigung bzw. Batchadministratorberechtigung vorliegt.
      IF tbtco-sdluname <> sy-uname.
        AUTHORITY-CHECK OBJECT 'S_BTCH_JOB'
          ID 'JOBGROUP'  FIELD '*'
          ID 'JOBACTION' FIELD 'DELE'.
        IF sy-subrc > 0.
          PERFORM check_batch_admin_privilege.
          IF batch_admin_privilege_given EQ btc_no .
            PERFORM deq_tbtco_entry
              USING
                jobname jobcount retcode.
            MESSAGE s125
              WITH
                tbtco-jobname sy-uname.
            RAISE no_delete_authority.
          ENDIF.
        ENDIF.
      ENDIF.
    ... and check_batch_admin_privilege is...
    *      FORM CHECK_BATCH_ADMIN_PRIVILEGE                               *
    * Prüfe, ob Benutzer Batchadministratorberechtigung hat. Diese Routine*
    * setzt die globale Variable BATCH_ADMIN_PRIVILEGE.                   *
    FORM check_batch_admin_privilege.
      AUTHORITY-CHECK
        OBJECT 'S_BTCH_ADM'
            ID 'BTCADMIN' FIELD 'Y'.
      IF sy-subrc EQ 0.
        batch_admin_privilege_given = btc_yes.
      ELSE.
        batch_admin_privilege_given = btc_no.
      ENDIF.
    ENDFORM. " CHECK_BATCH_ADMIN_PRIVILEGE.
    So, if you do not give up the S_BTCH_ADM to be able to use the S_BTCH_JOB job_action 'DELE', then you cannot.
    But it works like this for many of the S_BTCH_JOB checks, so perhaps the support users do not really need the S_BTCH_ADM?
    As a compensating control, you can consider SAP note 850885 with some organizational measures (e.g. training) around it.
    Cheers,
    Julius

Maybe you are looking for