"in update task" and "strings"

Hi guys,
I tried to extend a table by a string. this table is updated via a function module (Verbuchungsbaustein = in update task). The new rows are submited via the tables option. But this leads to a dump, could it be that it is not possible to use a string there?
Tanks Christian

can u send the snap shot of the dump so that we can figure out what went wrong?
Usually dumps will occur when there is a mis match of parameters in the function module.
please cross check the type of the parameters u r passing to the function module. this will solve the problem.
Satish

Similar Messages

Tech architecture of CM&RM update tasks and MM update tasks

Hi all!
I'm experiencing a problem to make a correct technical architecture of such a functionality: when the user update MM document (MIRO, which is parked or when a reversal is made) I need to update the linked case(s) (Case Management document).
How to make a real transactional behavior (e.g. if something with saving MM doc went wrong all the changes in MM AND CM is rolled back and vise versa). Which methods of CL_SCMG_CASE_API I need to use? How to use CL_SCMG_CASE_API -> G_UPDATE_TASK? When to call IF_SCMG_CASE_API~SAVE? When CLOSE? Where I can read about this?
I'm using in business logic this CM and RM methods:
IF_SCMG_CASE_API~CREATE
IF_SCMG_CASE_API~ATTRIBUTE_CHANGE
IF_SCMG_CASE_API~ELEMENT_INSERT
IF_SRM_SP_RECORD~ELEMENT_DELETE_BY_ID
IF_SRM_SP_RECORD~SAVE
I will be very much appreciated for architecture example.
Paul.

Hi all!
I'm experiencing a problem to make a correct technical architecture of such a functionality: when the user update MM document (MIRO, which is parked or when a reversal is made) I need to update the linked case(s) (Case Management document).
How to make a real transactional behavior (e.g. if something with saving MM doc went wrong all the changes in MM AND CM is rolled back and vise versa). Which methods of CL_SCMG_CASE_API I need to use? How to use CL_SCMG_CASE_API -> G_UPDATE_TASK? When to call IF_SCMG_CASE_API~SAVE? When CLOSE? Where I can read about this?
I'm using in business logic this CM and RM methods:
IF_SCMG_CASE_API~CREATE
IF_SCMG_CASE_API~ATTRIBUTE_CHANGE
IF_SCMG_CASE_API~ELEMENT_INSERT
IF_SRM_SP_RECORD~ELEMENT_DELETE_BY_ID
IF_SRM_SP_RECORD~SAVE
I will be very much appreciated for architecture example.
Paul.

Function in update task goes to dialog process(seen by sm50)

Hi Forum,
I wrote a simple test to invoke a function module in update task, and the execution of the module takes several minutes (updating database using opensql) . The test looks simply like described in the following link:
http://www.****************/Tutorials/ABAP/Debug/Index.htm
During the run, I used transaction sm50 to view the working processes and expect to find a running "UPD" process. However it is not found, instead my dialog process is always seen running. Any hints on why?
Thanks,
Yang

got the answer. The reason is that sm50 can not display UPD process so promptly. For a more thorough tracing, transaction "stad" can be used. (where I see the DB access executed in UPD process)

SAVE_TEXT in update task

hi,
In my program i have a requirement to save all the text after using COMMIT_TEXT.
can anyone give me a sample code for using COMMIT_TEXT after SAVE_TEXT or give me an idea how and which FM to call in UPDATE TASK and do i required to use explicitly COMMIT WORK after calling FM COMMIT_TEXT.
<< Please do not offer rewards >>
sandy
Edited by: Rob Burbank on Mar 26, 2009 10:28 AM

Hi,
do this like this.
u don't need to call as Update task and no need to have COMMIT WORK also.
CALL FUNCTION 'SAVE_TEXT'
    EXPORTING
*     CLIENT                = SY-MANDT
     header                = gs_comm_thead
     insert                = 'X'
     savemode_direct       = 'X'
*     OWNER_SPECIFIED       = ' '
*     LOCAL_CAT             = ' '
*   IMPORTING
*     FUNCTION              =
*     NEWHEADER             =
    TABLES
      lines                 = gt_commtline
   EXCEPTIONS
     id                    = 1
     language              = 2
     name                  = 3
     object                = 4
     OTHERS                = 5.
Regards,
Bharat.

Call transaction in update task

Hi,
I'm trying to call t-code V_V2 on update task but the update terminates with error "POSTING_ILLEGAL_STATEMENT". I've tried the same below code but without "In update task" and it worked correctly. Can anyone help me please?
DATA:   bdcdata LIKE bdcdata    OCCURS 0 WITH HEADER LINE.
"Open the 1st screen of transaction V_V2...
CLEAR bdcdata.
bdcdata-program = 'SDV03V02'.
bdcdata-dynpro   = '1000'.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.
"Position the cursor on the material number field...
CLEAR bdcdata.
bdcdata-fnam = 'BDC_CURSOR'.
bdcdata-fval = 'S_MATNR-LOW'.
APPEND bdcdata.
"Enter the material number on its field...
CLEAR bdcdata.
bdcdata-fnam = 'S_MATNR-LOW'.
bdcdata-fval = matnr.
APPEND bdcdata.
"Position the cursor on the plant field...
CLEAR bdcdata.
bdcdata-fnam = 'BDC_CURSOR'.
bdcdata-fval = 'S_WERKS-LOW'.
APPEND bdcdata.
"Enter the plant on its field...
CLEAR bdcdata.
bdcdata-fnam = 'S_WERKS-LOW'.
bdcdata-fval = plant.
APPEND bdcdata.
"Position the cursor on the simulation checkbox field...
CLEAR bdcdata.
bdcdata-fnam = 'BDC_CURSOR'.
bdcdata-fval = 'P_SIMUL'.
APPEND bdcdata.
"Clear the simulation checkbox field...
CLEAR bdcdata.
bdcdata-fnam = 'P_SIMUL'.
bdcdata-fval = ' '.
APPEND bdcdata.
"Execute the program...
CLEAR bdcdata.
bdcdata-fnam = 'BDC_OKCODE'.
bdcdata-fval = 'ONLI'.
APPEND bdcdata.
"A popup window will raise for change confirmation...
CLEAR bdcdata.
bdcdata-program = 'SAPLSPO1'.
bdcdata-dynpro   = '100'.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.
"Position the cursor on this popup window...
CLEAR bdcdata.
bdcdata-fnam = 'BDC_CURSOR'.
bdcdata-fval = 'SPOP-OPTION1'.
APPEND bdcdata.
"Press the "YES" button...
CLEAR bdcdata.
bdcdata-fnam = 'BDC_OKCODE'.
bdcdata-fval = 'YES'.
APPEND bdcdata.
CALL FUNCTION 'ABAP4_CALL_TRANSACTION_VB' IN UPDATE TASK
EXPORTING
    tcode                         = 'V_V2'
SKIP_SCREEN                   = ' '
    MODE_VAL                      = 'N'
    UPDATE_VAL                    = 'S'
TABLES
    USING_TAB                     = bdcdata
SPAGPA_TAB                    =
MESS_TAB                      =
EXCEPTIONS
    CALL_TRANSACTION_DENIED       = 1
    TCODE_INVALID                 = 2
    OTHERS                        = 3.

Hi,
use the following stmt. instead of calling FM ''ABAP4_CALL_TRANSACTION_VB'
CALL TRANSACTION 'V_V2' USING BDCDATA MODE 'N' UPDATE 'S'......
Hope it will work.

Calling RFC FM in update task / background task

hi experts,
I have a RFC FM in system B and i want to call it from system A. if the system B is down when the call happens then the call is lost. basically i want the call happen when the system B is up. somewhere i have read that when u call the RFC FM in update task/ background task , SAP will try to make the call to system B at periodic intervals of time till the system B is up. is that so? what is the difference between calling the RFC in update task and background task?
thanks

no replies

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.

Regarding Error in Function Module in Update Task

Hi All,
If a function module is called in Update Task and there is some error generated from it, it comes as an exit message unlike in a normal function module.
Is there any possible way to avoid such an exit message?
Thanks in advance.
Regards,
Garima

Hi,
The problem is I am updating Z tables in a function and also calling a function in Update task to update a different set of tables.
Now, if for some reason there is an error in Update Function module, then my requirement is that rather than throwing an Exit message (which it is presently doing) the errors coming from the function should be captured so that the user knows what was wrong with the data he entered.
Is there any work around to the above requirement? Either all the tables should be updated or none of them should be updated.
Regards,
Garima Thapar.

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

Error thrown in update task

Hello all,
An error is getting thrown in a function module in update task and it is displayed as an Express Document. I want to trace where this error is thrown. Is there any easy way to do that other than degugging from the start.
Please give suggestions.
Thanks in advance
Sudha
Message was edited by:
Sudha Naik

Hi,
Goto SM14 tcode ->press on ALL UPDATE REQUESTS BUTTON->Check ur USER ID->Double click on it,it will take to other screen->now in the appication tool bar u can find the abap editor symbol,click on it and see why u got the update termination error.
Regards,
Nagaraj

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

What is Update Task Capability of a Function Module

Hi Folks,
My client wants me to create a function module with Update Task Capability.
Can you please know what is this and how to use this? I am completely new to this Update Task part. So please guide me accordingly.
Thanks in advance,
Siddarth

Hi Sir,
Please have a look below to understand update task capability of FM.
Plz do reward if useful
Thankx.
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.
The system logs your request and executes the function module when the next COMMIT WORK statement is reached. The parameter values used to execute the function module are those current at the time of the call.
a = 1.
CALL FUNCTION 'UPD_FM' IN UPDATE TASK EXPORTING PAR = A...
a = 2.
CALL FUNCTION 'UPD_FM' IN UPDATE TASK EXPORTING PAR = A...
a = 3.
COMMIT WORK.
Here, the function module UPD_FM is performed twice in the update task: the first time, with value 1 in PAR, the second time with value 2 in PAR.
Check the SAP Help :
http://help.sap.com/saphelp_nw04s/helpdata/en/41/7af4bfa79e11d1950f0000e82de14a/frameset.htm

Regarding calling the fuctional module Using 'in update task'

Hi ,
I want to call a Functional module Z-PS_VK11_FRC using the statement IN UPDATE TASK .
What is procedure to work with . can anybodt tell me how to proceed or give me some sample program .
Regards,
Shilpa Talluri

Function modules that run in update task can not return any values because your program has no longer control over the function module (the update task has).
UPDATE TASK fm mostly used to update database tables.
You don't any special coding other than calling fm UPDATE TASK
And in the attributes of function module you need to tick the Update mode and "Coll Run" so that it can be used to run individually in the V2 update process can be grouped together and run collectively.
a®

BDOC Stored before update task error

Hi Experts,
I am using FM CRMXIF_PRODUCT_MATERIAL_SAVE to update one of the custom aatributes in COMMPR01.
once i run this FM i see an entry of bdoc in SMw01 with the below error
"BDOC stored before update task(intermediate state).
I checked ST22 and i saw no dumps, i checked Sm13 and i didnt see any update tasks. Cananyone help me?
Thanks!

HI Divya,
BDoc Message was not written to qRFC queue, yet. Search for update tasks in transaction
SM13. The sender creates a BDoc message to post data to the receivers. The application
calls the messaging flow.
Detection:
Check if there are any update terminations which occurred in the update task
by using transaction SM13. Check if there are inbound messages related to
that outbound message, double-click u2018Original BDocu2019 field to display the
original inbound message. Typically the inbound message (s-BDoc in flow
context SI1 or m-BDoc in flow context MI0) is already on a final state F02, i.e.
the validation was successful but the asynchronous update failed. The
original inbound message in final state might have been already reorganized.
Solution:
Solve the problem with the open update tasks and then execute them again
in SM13. Check whether after succesful reexecution in SM13 the BDoc state
has been changed.
If not, or if you donu2019t find any open updates, but you do find a corresponding
original message, proceed as following:
· Variant 1: Try to reprocess the inbound message to check if the newly
created outbound message has also status I04. If BDoc is processed, no
retry of the failed BDoc is allowed. Set the message as deleted.
Reprocessing the related inbound message is sometimes not possible,
because the state is final. In this case copy the inbound message using
transaction SMW19 and set the new state of the copied message to I01.
Then you can reprocess it.
· Variant 2: Use the solution from SAP notes 876855 (CRM 3.X) or 835761
(CRM 4.0) to convert the inbound s-BDoc into an error state E09.
Advantage is, that in this state the inbound message does not get
reorganized. More important, it also allows you to restart the inbound
processing after the error situation has been resolved. However, in that
case you need to delete the already pending update tasks from the
previous run in transaction SM13.
When there are no open update tasks anymore, check whether the data
changes according to the inbound BDoc message have actually been posted
to the CRM online application tables. If the changes are present (i.e. a new
application object was succesfully created), you should not use variant 2,
because you might get a problem of posting the same data again (i.e. getting
an "insert duplicate record" situation).
For more info about error analysis. please refer to
http://saptricks.com/wp-content/uploads/2010/05/BestPractice-BDoc-Analysis-V2.pdf
Cheers, Satish

REST API to get and update Task Data

On CPSC 9.4.1 R2, I am unable to find any REST API operation to get and update task data details (all the service form and dictionary fields).
Task operations only return limited task meta-data not the details of the task/requisition data submitted, fields, etc.
Does anyone know if such thing exist?
Thanks.

Hi Rakesh,
To enable anonymous Search REST queries, we need to create queryparametertemplate.xml and upload it to the correct library in SharePoint.
From your description I can know that you have created the file, then I recommend to check the things below:
Please use “QueryTemplatePropertiesUrl” instead of “queryparametertemplate” in the Search REST API query as following: &QueryTemplatePropertiesUrl='spfile://webroot/queryparametertemplate.xml'.
Make sure that the Query Properties you need have been added to the QueryProperties element in the queryparametertemplate.xml file.
Make sure that the query parameters you need have been added to the WhiteList element in the
queryparametertemplate.xml file. For example, if you want to use Refiners in the REST API, then the Refiners should be added to the
WhiteList element in the queryparametertemplate.xml file as following:
<a:string>Refiners</a:string>.
You can also debug setting properties in anonymous Search Rest queries following the link below:
http://www.mavention.com/blog/debugging-setting-properties-anonymous-search-rest-queries
More references about anonymous Search REST:
http://blog.mastykarz.nl/configuring-sharepoint-2013-search-rest-api-anonymous-users/
http://msdn.microsoft.com/en-us/library/office/jj163876%28v=office.15%29.aspx#bk_AnonymousREST
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

"in update task" and "strings"

Similar Messages

Maybe you are looking for