Authority-Check in UPDATE TASK CALL

Hi Gurus,
Does anybody know, from the Technical point of view, if there is any special issue with an Authority-Check put in a user-exit called in UPDATE TASK?
Thanks & Regards
Ernesto.

Hello Michael,
Thank you for your reply. I was asking this because I have a problem regarding an Authority Check and I do not know what the problem is. In user exit EXIT_SAPLL03T_002 (executed in Update TASK) I want to check for Storage Type condition from the object L_LGNUM. The user that executes LT12 transaction has one role only that has object L_LGNUM like this:
Object L_LGNUM
Warehouse Number - LNUM = 200
Storage Type - LGTYP = 100, 200, 300, 400, 500, 600, 700, 800
The two checks I am doing are:
Check Source Storage Type
    AUTHORITY-CHECK OBJECT 'L_LGNUM'
             ID 'LGNUM' FIELD i_ltak_vb-lgnum (200)
             ID 'LGTYP' FIELD ls_ltap_vb-vltyp (902)
    Check Destination Storage Type
      AUTHORITY-CHECK OBJECT 'L_LGNUM'
               ID 'LGNUM' FIELD i_ltak_vb-lgnum (200)
               ID 'LGTYP' FIELD ls_ltap_vb-nltyp (002)
And for no reason SAP doesn't return sy-subrc NE 0 when it should. I've checked the role and it has no conflict with another one as it is the only role the user has. Any idea?
Thanks & Regards
Ernesto

Similar Messages

CHECK OF UPDATE TASK Errors and RETURN CODE in RSVBCHCK.MX1

hi ia m getting this error during the upgrade .i did checked in sm12 for any failed updates but there arent any .so i think there should be a table that i need to alter.should this be done in se16 ? and i think the table name is TRAN.LBWG any ideas.
CHECK OF UPDATE TASK Errors and RETURN CODE in RSVBCHCK.MX1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long tex
Long text:
    Cause
      Changing the extract structure &V#& for application &V#& is not
      permitted, because the restructure table &V#& for the extractor still
      contains data in &V#&.
      You cannot change the structure in this status, because when you load
      an InfoPackage from BW, this leads to errors.
    What to do
      <DS:TRAN.LBWG>Delete</> the entries for all restructure tables for
      application &V#&.
1 ETH010XRSVBCHCK: Check of open update requests
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long tex
t" ""MC02M_0HDRSETUP""100"
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long tex
t" ""MC02M_0ITMSETUP""100"
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long tex
t" ""MC02M_0SCLSETUP""100"
A2EEMCEX 141 Struct. appl. "03" cannot be changed due to setup table -> Long tex
t" ""MC03BF0SETUP""100"
A2EEMCEX 141 Struct. appl. "03" cannot be changed due to setup table -> Long tex
t" ""MC03BX0SETUP""100"
A2EEMCEX 141 Struct. appl. "03" cannot be changed due to setup table -> Long tex
t" ""MC03UM0SETUP""100"
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long tex
t" ""MC11VA0HDRSETUP""100"
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long tex
t" ""MC11VA0ITMSETUP""100"
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long tex
t" ""MC11VA0STHSETUP""100"
A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long tex
t" ""MC11V_0SSLSETUP""100"
A2EEMCEX 141 Struct. appl. "13" cannot be changed due to setup table -> Long tex
t" ""MC13VD0ITMSETUP""100"
4 EPU202XEND OF SECTION BEING ANALYZED

1. Call transaction SMQ1 and check whether all queues in all clients (client = '', queue name 'MCEX') have been processed. To process the queues, start the collective run report for each application in the displayed clients. If you no longer need the data in the BW system, deactivate the relevant extraction queues and DataSource in the LO cockpit (transaction LBWE) and delete the queue entries in transaction SMQ1.
2. If you use the V3 update that is not serialized (usually only for application 03): Start collective run report RMBWV303. Then check the update orders in transaction SM13. If there are incorrect update orders in transaction SM13, correct the orders and then start the collective run report again. If you no longer require the update orders, you can delete them. There may be inconsistencies between tables VBMOD and VBHDR. For further information about this, see Notes 652310 and 67014.
3. Before the upgrade, delete the contents of the setup tables. Execute report RMCEX_SETUP_ENTRIES to find out which setup tables still contain entries. You can use transaction LBWG to delete the contents of the setup tables for all clients.
Unfortunately the check that the system carries out during the upgrade or when you import a Support Package does not display all affected applications. Therefore, Note 1083709 provides a check report that you can use to determine all affected applications and tables or queues.

Whats the check for updates button called in the spanish version of firefox?

in 3.6.11 and Firefox 4 beta 6

Such a download is usually saved in an updates or updated folder in the Firefox program/application folder.
You can delete this folder to cancel the download.
If files already have been downloaded then remove the files in the updates and updates\0 folder.
*http://kb.mozillazine.org/Updates_reported_when_running_newest_version
*http://kb.mozillazine.org/Software_Update
Mac: /Applications/Firefox.app/updates "/path_to/Firefox.app/Updated.app"
Linux: "/path_to/firefox/updated"
Windows: C:\Users\<user>\AppData\Local\Mozilla\Firefox\Mozilla Firefox\updates

Call function in update task empty variables error

Hello,
I'm experiencing a weird error while using the addition "In update task".
My Scenario is the following:
Use the bapi_goodsmvt_create -> if there are no errors, fill some values and call my function and then commit everything.
The problem is, when the function runs in update task, all import parameters are empty!
Also, this only happens in the following code structure
CALL METHOD run_migo( IMPORTING bapireturn = t_bapireturn).
IF t_bapireturn IS INITIAL.
CALL METHOD save_custom_tables. "this runs my function 'IN UPDATE TASK'
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.
ENDIF.
if I commit inside the method SAVE_CUSTOM_TABLES, the data is passed normally to the function, if I commit like the code above, everything is empty.

Here's the code:
METHOD save_partial.
DATA: t_wegritm    LIKE gt_wegritm,
        t_tegrp_parc TYPE TABLE OF ztegrp_parc,
        w_tegrp_parc TYPE ztegrp_parc,
        w_tegrk_parc TYPE ztegrk_parc.
FIELD-SYMBOLS <w_wegritm> LIKE LINE OF t_wegritm.
t_wegritm = gt_wegritm.
DELETE t_wegritm WHERE mengee IS INITIAL.
CHECK NOT t_wegritm IS INITIAL.
*-->save xml iten
LOOP AT t_wegritm ASSIGNING <w_wegritm>.
    MOVE-CORRESPONDING <w_wegritm> TO w_tegrp_parc.
    w_tegrp_parc-id = gw_tegrk-id.
    w_tegrp_parc-gr_docto = <w_wegritm>-gr_docto.
    w_tegrp_parc-gr_mjahr = <w_wegritm>-gr_mjahr.
    w_tegrp_parc-gr_zeile = <w_wegritm>-gr_zeile.
    APPEND w_tegrp_parc TO t_tegrp_parc.
ENDLOOP.
MOVE-CORRESPONDING gw_tegrk TO w_tegrk_parc.
CALL FUNCTION 'Z_SAVE_PARTIAL'
    IN UPDATE TASK
    EXPORTING
      iw_tegrk_parc = w_tegrk_parc
    TABLES
      it_tegrp_parc = t_tegrp_parc.
ENDMETHOD.
I tried to re-create this scenario with a local class, but the code that I originally sent worked(the commit work outside of the routine).

BDOC Error : "BDoc stored before update task (intermediate state)"

Hi Experts,
I have stuck BDOCs under BDOC type "BUS_TRANS_MSG" and the error msg as "BDoc stored before update task (intermediate state)". The error occurs when BDoc Message was not written to qRFC queue. I checked the update tasks in transaction
SM13 and could find the entries there. I opened one of the entry and was able to spot the error in one of the function module.
The error was encountered at some later point in time and is been fixed. I now want to re-send the update so that the new update is written and the BDOCs are processed.
Kindly guide me through the steps that need to be performed in order to re-process the BDOCS.
Thanks,
Chaudh

Hi,
BDocs were stuck at time when we really had a problem; now the problem is re-solved. I have checked SM13 we have entries highlighting the problem, but i really don't know how to re-update the error entries in SM13.
I believe once that is done then i might possibly be able to re-process the BDOCs in SMW01.
Thanks,
Chaudh

Help with authority-check

Hello ppl,
On my selection screen for a report, I have the field Sales Org. SELECT-OPTIONS: s_vkorg FOR gs_selscr-vkorg
                              OBLIGATORY, "Sales Org.
I need to check whether the user has the authorization for the selected sales organisations. So, I am using:
AUTHORITY-CHECK OBJECT 'V_VBAK_VKO'
           ID 'VKORG' FIELD s_vkorg
           ID 'ACTVT' FIELD '03'.
IF sy-subrc NE 0.
    MESSAGE e013.    " No authorization
    SET CURSOR FIELD 'S_VKORG-LOW'.
ENDIF.
But, will this code handle a range of sales organisations?
Also, how will I be able to display an error message displaying the sales org for which the user has no authorization?
Please help.
Thanks.

selection-screen begin of block b1 with frame .
select-options : so_bukrs for bsid-bukrs obligatory,
so_kunnr for bsid-kunnr,
so_hkont for bsid-hkont,
so_prctr for bsid-prctr ,
so_ktokd for kna1-ktokd.
selection-screen end of block b1.
initialization.
*Clearing the work area.
clear gs_bsid.
Refreshing the internal tables.
refresh gt_bsid.
*comm1 = 'Post Dt'.
*comm2 = 'Doc Dt'.
*comm3 = 'Bline Dt'.
*******AUTHORITY-CHECK ***********************************************
at selection-screen .
call function 'ZCAGL_COUNTRYCODE'
exporting
IM_WERKS =
IM_SPART =
IM_PRCTR =
im_bukrs = so_bukrs-low
importing
e_land1 = e_land1.
if e_land1 ne 'IN'.
message i004(yfi02) with 'This Company Code' so_bukrs-low
'doesn''t belong to INDIA'.
leave program.
else.
authority-check object 'ZPRCHK_NEW' :
id 'BUKRS' field so_bukrs-low.
if sy-subrc ne 0.
message e001(yfi02).
leave program.
endif.
endif.
if so_prctr-low is not initial.
call function 'ZCAGL_COUNTRYCODE'
exporting
IM_WERKS =
IM_SPART =
im_prctr = so_prctr-low
IM_BUKRS =
importing
e_land1 = e_land1.
if e_land1 ne 'IN'.
message i004(yfi02) with 'This Profit center'
so_prctr-low 'doesn''t belong to INDIA' .
leave program.
else.
authority-check object 'ZPRCHK_NEW' :
id 'PRCTR' field so_prctr-low.
if sy-subrc ne 0.
message e002(yfi02).
leave program.
endif.
endif.
endif.
this will help u....
Regards
Anbu

Function module for se16 with out authority check for se16

Hi ,
I am creating a tode YSE16 which has same functionality as SE16 but having its own authority check. I am calling a function module RS_TABLE_LIST_CREATE function module to get the functionality of SE16. But is there any way that i can get the function module which do not check for the authorization for se16 and execute my tcode.
Regards,
Sri.

Hi Sri,
If I am not wrong this is the question?
Guys , Sri is modifying the YSE16 as per this requirement. Do u have some other solution? Thanks.
Requirement is to create customized tcodes YSE16, YSM30 and YSE38 for se16, sm0 and se38. Lets start with YSE16.
Client want YSE16 tcode to restrict users based on some tables within a authorization group or even * value for auth group field.
SE16 restricted on:
S_TABU_DIS
Auth Group and Activity
As per Requirement YSE16 tcode sld be restricted on :
Y_TABU_DI2 (customized object)
Auth Group, Activity and Table name
We dont want to give SE16 to users in Production. So basically requirement is to restrict users on table name with YSE16 irrespective on authorization group. User sld only be able to access the table mentioned in Table name field.
so Srilu is trying to modify the Program. Can you please suggest some other way to modify it.
Thanks.
Regards,
Naveen Dalal

Calling function in Update Task problem

Hello Friends,
I'm calling FM 'REVISION_LEVEL_POST' in Update Task to insert a revision level for a material when saving a Change Master (CC02 T-Code). But the calling is triggered a bit early (Before updating the Data Base AEOI Table!). An Update Task FM is called right after the COMMIT WORK is executed. Here in my case, a commit work is done but not for my change Master but for a text... So my FM does not find the record to be updated.
Is there a way to solve this ?
Thank you for your Help!

Check the log in VBLOG table ..

Call function '' in update task - code inside is BDC

hi to all,
in using call function '' in update task
the code inside is bdc. is this possible?
my scenario is from VA01 then post billing to VF01,
i am using user-exit MV45AFZZ in subroutine userexit_save_document.
i need to post billing after va01 save.
thanks to all.

To debug in the update task, you have to set that option on in the debugger.
If the user exit runs in the update task, then you must have something like: CALL FUNCTION MODULE my_fm_to_do_BDC STARTING NEW TASK. ( This function module should wait until the SD is created. You might want to check in a loop, with a WAIT command. Once it is created, then you start your BDC and CALL TRANSACTION. ) This is NOT an update function module. It may need to be RFC enabled - I'm not certain at the moment.
If the user exit doesn't run in the update task, you need to create, and call from the user exit, an update function module that calls your function module "my_fm_to_do_BDC" STARTING NEW TASK.
The attribute "collective run", which is V3, means that the update task won't run that function module until a regularly scheduled job on the application server runs. For processing to run during the rest of the SD save, you must use V1 (could be run in any order with other V1s) or V2 (Will run after V1, but in any order with other V2s). Typically, I use V2 for this kind of task.
matt

Call function module in update task

Hi
I am using the follwoing logic in my prog
CALL FUNCTION 'Z_Update _Task'    In update task
EXPORTING
    t_vbak        = t_vbak.
But the program goes to dump at call function
Please let me know if the syntax i am using is correct.
Edited by: kittu reddy on Feb 28, 2008 5:29 AM

It might be the type conflict . Please check once .
Here am giving some information abt UPDATE TASK.
Why do we use this " In Update Task " ??
The main update technique for bundling database changes in a single
database LUW is to use CALL FUNCTION... IN UPDATE TASK.
How do we Use ??
A typical R/3 installation contains dialog work processes and at least one update work process. The update work processes are responsible for updating the database. When an ABAP program reaches a COMMIT WORK statement, any function modules from CALL FUNCTION... IN UPDATE TASK statements are released for processing in an update work process. The dialog process does not wait for the update to finish. This kind of update is called asynchronous update.
What is the Use... ??
Asynchronous update is useful when response time from the transaction is critical, and the database updates themselves are so complex that they justify the extra system load
Thanks
Jagadeesh

Calling Function Module in Update Task

Hello Experts,
Can anyone let me know about
Calling Function Module in Update Task.
Why do we use this " In Update Task " ??
How do we Use ??
What is the Use... ??
Kindly let me know....
Thanks and Regards
Pramod

hi,
Why do we use this " In Update Task " ??
The main update technique for bundling database changes in a single database LUW is to use CALL FUNCTION... IN UPDATE TASK.
How do we Use ??
A typical R/3 installation contains dialog work processes and at least one update work process. The update work processes are responsible for updating the database. When an ABAP program reaches a COMMIT WORK statement, any function modules from CALL FUNCTION... IN UPDATE TASK statements are released for processing in an update work process. The dialog process does not wait for the update to finish. This kind of update is called asynchronous update.
What is the Use... ??
Asynchronous update is useful when response time from the transaction is critical, and the database updates themselves are so complex that they justify the extra system load
Real time scenario.
Suppose a user wants to change an entry in a database table, or add a new one. He or she enters the necessary data, and then starts the update process by choosing Save. This starts the following procedure in the ABAP program:
Firstly, the program locks the database entry against other users, using the enqueue work process (or the message server in the case of a distributed system). This generates an entry in the lock table. The user is informed whether the update was successful, or whether the lock could not be set because of other users.
If the lock is set, the program reads the entry that is to be changed and modifies it. If the user has created a new entry, the program checks whether a record with the same key values already exists.
In the current dialog work process, the program calls a function module using CALL FUNCTION... IN UPDATE TASK, and this writes the change details as an entry in table VBLOG.
When the program is finished (maybe after further dialog steps), a COMMIT WORK statement starts the final part of the SAP LUW. The work process that is processing the current dialog step starts an update work process.
Based on the information passed to it from the dialog work process, the update work process reads the log entries belonging to the SAP LUW from table VBLOG.
The update work process passes this data to the database for updating, and analyzes the return message from the database. If the update was successful, the update work process triggers a database commit after the last database change and deletes the log entries from table VBLOG.
If an error occurred, the update work process triggers a database rollback, leaves the log entries in table VBLOG, flags them as containing errors, and sends a SAPoffice message to the user, who should then inform the system administrator.
The corresponding entries in the lock table are reset by the update work process.
Hope this is helpful, Do reward.

Update termination error while calling FM in Update task

Hi Friends,
I am calliing my Z Function Module in update task from my report, my function module contain reuse alv list display fm which should create a Spool in the spool list.
When ever i am directly executing my Z function module i am getting spool in SP01, but when ever i am calling the Z Function Module in update task from my report i am getting a message as "Express document "Update was terminated" received from author.
I want to call the Function module in update task and it should generate spools .
Syntax:
CALL FUNCTION 'ZLOK_TEST' IN UPDATE TASK.
Commit work.
Thanks Regards,
Sandipan jena

Hi sandipan jena,
a function called in update task will not create a spool list if not told so to to. Only reports scheduled in a JOB will put the output into spool.
Make sure you have no COMMIT WORK and no MESSAGE output when in UPDATE TASK. You can enter /h and in debugger switch on UPDATE debugging. This will lead you to any error occurring.
You should analyze the errors you get. Mabe NEW-PAGE PRINT ON can help you.
Regards
Clemens

Function Module called in Update Task

Hi Gurus,
We are calling Sales Order Change in update task inside the user Exit MV50FZ1. We can see that the FM is called in update task after the commit work and the return of the FM shows the success message. But still the changes are not saved to the DB.
Can any one help me out with this one.
Rashit

Hi,
If two commit works are called in update task the update will end up with error. Check whether any Commit work is present in the funtion module? If so you may use it in some other method like at save or something like that.
Regards,
Renjith Michael.

Problem when using Call FM IN UPDATE TASK.

we plan to update ztable using Call FM in update task, and write the success/error message into log.
Does below is right?? I found the commit work can not be used here. Thanks..
CALL FUNCTION 'ENQUEUE_ETABLE'.
IF sy-subrc = 0.
CALL FUNCTION 'update_ztable'' IN UPDATE TASK.
Endif.
COMMIT WORK and wait.
IF sy-subrc <> 0.
     ROLLBACK WORK.
     write error log.
Else.
    Write successful log.
Endif.
CALL FUNCTION 'DNQUEUE_ALL'.

Hi ,
Please see the refernce of UPDATE FUNCTION MODULES:
UPDATE FUNCTION MODULE
-In the attributes tab, under processing type, choose Update Module,
Start Immediately. Define your import parameters, enter the source
code, All validations should have been done prior to the call to this
function module, so all you need in the source, is the updating of the
database, INSERT, MODIFY, UPDATE, whatever.
-When you call you function module, use IN UPDATE TASK, after the call,
COMMIT WORK. The commit work will trigger the db update.
Why do we use this " In Update Task " ??
The main update technique for bundling database changes in a single
database LUW is to use CALL FUNCTION... IN UPDATE TASK.
How do we Use ??
A typical R/3 installation contains dialog work processes and at least one update work process. The update work processes are responsible for updating the database. When an ABAP program reaches a COMMIT WORK statement, any function modules from CALL FUNCTION... IN UPDATE TASK statements are released for processing in an update work process. The dialog process does not wait for the update to finish. This kind of update is called asynchronous update.
What is the Use... ??
Asynchronous update is useful when response time from the transaction is critical, and the database updates themselves are so complex that they justify the extra system load
Real time scenario.
Suppose a user wants to change an entry in a database table, or add a new one. He or she enters the necessary data, and then starts the update process by choosing Save. This starts the following procedure in the ABAP program:
Firstly, the program locks the database entry against other users, using the enqueue work process (or the message server in the case of a distributed system). This generates an entry in the lock table. The user is informed whether the update was successful, or whether the lock could not be set because of other users.
If the lock is set, the program reads the entry that is to be changed and modifies it. If the user has created a new entry, the program checks whether a record with the same key values already exists.
In the current dialog work process, the program calls a function module using CALL FUNCTION... IN UPDATE TASK, and this writes the change details as an entry in table VBLOG.
When the program is finished (maybe after further dialog steps), a COMMIT WORK statement starts the final part of the SAP LUW. The work process that is processing the current dialog step starts an update work process.
Based on the information passed to it from the dialog work process, the update work process reads the log entries belonging to the SAP LUW from table VBLOG.
The update work process passes this data to the database for updating, and analyzes the return message from the database. If the update was successful, the update work process triggers a database commit after the last database change and deletes the log entries from table VBLOG.
If an error occurred, the update work process triggers a database rollback, leaves the log entries in table VBLOG, flags them as containing errors, and sends a SAPoffice message to the user, who should then inform the system administrator.
The corresponding entries in the lock table are reset by the update work process.
Q:We are calling Sales Order Change in update task inside the user Exit MV50FZ1. We can see that the FM is called in update task after the commit work and the return of the FM shows the success message. But still the changes are not saved to the DB.
A: check sm21 or sm13 to see if the update was successful .. In SM21 I checked. It is giving me the error Transaction Failed
Reward if useful
Thanks
Jagadeesh.G

Call FM in update Task ?

Dear All,
I've created a custom FM and I want to call this FM in update task.
I'm passsing a tables parameter to this FM in update Task.
Everything is fine but when I'm coming back to the main program the tables paramter is not having any value.
It's becoming null.
Can you tell me the reason y it's so ?
Regards,
Deepu.K

Hi deepu,
in update task only starts after the commit instruction of your program and it doesn't accept importing, changing parameters or exceptions. And table parameters are only valid for input.
You might want to check the starting new task mode:
CLEAR w_end.
ltask = 'HELLOWORLD'.
CALL FUNCTION 'Z_UPDATE_ZDSDM01' STARTING NEW TASK ltask PERFORMING f_go ON END OF TASK
    EXPORTING
      in = lin.
WAIT UNTIL w_end IS NOT INITIAL.
WRITE: 'Hi', lnew, l_subrc.
*&      Form f_go
FORM f_go USING par TYPE clike.
w_end = 'X'.
RECEIVE RESULTS FROM FUNCTION 'Z_UPDATE_ZDSDM01'
          CHANGING xnew    = lnew
                  EXCEPTIONS lixo = 1 system_failure = 2 communication_failure = 3 OTHERS = 9.
l_subrc = sy-subrc.
ENDFORM.                    "f_go
regards,
Edgar

Authority-Check in UPDATE TASK CALL

Similar Messages

Maybe you are looking for