ABAP Asynchronous LUW

hi ,
I need to create an asynchornous job to adapt a parallel processing .
my requirement will be like need to update two table information using BAPI via RFC and it has to update min 1 lakh records in 1 hours .. it was the exepectation .
my queries,
1. is it suggestable to go for a RFC aysnchornous job to adapt parallel processing for such requirement
2. i have created a program for this task but how to use the FM SPBT_INITIALIZE and from the output how i can proceed ... i mean proceed to initiate the task in parallel .
3. I am using the task group   parallel_generators
    CALL FUNCTION 'XXXXXXXXXXX' STARTING NEW TASK gv_taskname
    DESTINATION IN GROUP   parallel_generators
    PERFORMING set_functiona1_done ON END OF TASK.
please suggest this the 1st i am creating the aysynchornous job.
Thanks in advance,
Gurumoorthy G

yes of corse:
in IR
MessageType_IN
MessageType_OUT
MessageMapping between the 2 MT
a service interface SI_SP2FS_OUT Outbound and Async
a service interface SI_SP2FS_IN Inbound and Async
a Operation mapping between SI_SP2FS_OUT and SI_SP2FS_IN
In ID
Communication Channel to FTP folder
Receiver determination with follow parameter:
sender communication Component : SAP_DEV
sender Interface : SI_SP2FS_OUT
sender namespace : http://mynamespace
receiver party : *
receiver communication Component : *
Configured receivers: FTP_DEV
Interface Determination:
sender communication Component : SAP_DEV
sender Interface : SI_SP2FS_OUT
sender namespace : http://mynamespace
Receiver Agreement:
sender communication Component : SAP_DEV
receiver communication Component : FTP_DEV
receiver Interface : SI_SP2FS_IN
receiver namespace : http://mynamespace
In R3 abap side i created proxy pointing to SI_SP2FS_OUT with SPROXY transaction.

Similar Messages

Starting new database LUW inside ABAP during IDoc posting

Hi all,
During posting of an inbound IDoc, I am trying to update my Z-table in user-exit. I want to do it regardless of the result of IDoc posting. The problem is: if IDoc posted successfully - table is updated because COMMIT WORK is called at the end of the posting, however, if IDoc not posted - ROLLBACK WORK is called and table is not updated. So, my aim now is to commit the update of Z-table in any case, but it is the only thing that should be committed - no other prior update FMu2019s should be committed.
I'm aware about the following thread
http://forums.sdn.sap.com/thread.jspa?threadID=1884700
Author of this thread says that he solved a problem by means of RFC and STARTING NEW TASK. But ABAP help says
that starting asynchronous RFC triggers immediately a database commit in the calling program (which is unacceptable because all prior update FMu2019s will be committed ). I've checked and it is really the case.
From my point of view SET UPDATE TASK LOCAL with COMMIT WORK should work in such kind of tasks, but in case of IDoc processing the whole process runs in a local update (see SET UPDATE TASK LOCAL in FM 'IDOC_INPUT'), so writing once again SET UPDATE TASK LOCAL has no effect.
I tested SUBMIT statement as well. It had no effect and then I found out from ABAP help that SUBMIT ... AND RETURN starts new SAP LUW, but NOT a DB LUW. That is if I update my Z-table in the program called by SUBMIT - all ROLLBACK statements still affect my Z-table update.
Is there any simple solution? Please suggest.
Thanks in advance!

Hello,
Try SUBMIT VIA JOB.....
Sample Code
call function 'JOB_OPEN'
exporting
jobname = name
importing
jobcount = number
exceptions
cant_create_job = 1
invalid_job_data = 2
jobname_missing = 3
others = 4.
if sy-subrc = 0.
submit z_idoc_create_process_order and return
via job name number number
with p_aufnr = it_header1-aufnr
with p_werks = it_header1-werks
with p_autyp = c_autyp
with p_auart = it_header1-auart
with p_dispo = it_header1-dispo
with p_opt = c_opt
with p_mestyp = c_mestyp.
if sy-subrc = 0.
call function 'JOB_CLOSE'
exporting
jobcount = number
jobname = name
strtimmed = 'X'
exceptions
cant_start_immediate = 1
invalid_startdate = 2
jobname_missing = 3
job_close_failed = 4
job_nosteps = 5
job_notex = 6
lock_failed = 7
others = 8.
if sy-subrc 0.
endif.

What is LUW? How do we use it in SAP ABAP coding?

Hi Friends,
Kindly explain me what is LUW with examples and how do we use it in our ABAP coding with scenarios why and when we use it?
Regards,
Pradeep

Hi,
SAP LUW
Die Verbuchungsverwaltung
The Open SQL statements INSERT, UPDATE, MODIFY, and DELETE allow you to program database changes that extend over several dialog steps. Even if you have not explicitly programmed a database commit, the implicit database commit that occurs after a screen has been processed concludes the database LUW. The following diagram shows the individual database LUWs in a typical screen sequence:
Under this procedure, you cannot roll back the database changes from previous dialog steps. It is therefore only suitable for programs in which there is no logical relationship between the individual dialog steps.
However, the database changes in individual dialog steps normally depend on those in other dialog steps, and must therefore all be executed or rolled back together. These dependent database changes form logical units, and can be grouped into a single database LUW using the bundling techniques listed below.
A logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW is called an SAP LUW. Unlike a database LUW, an SAP LUW can span several dialog steps, and be executed using a series of different work processes. If an SAP LUW contains database changes, you should either write all of them or none at all to the database. To ensure that this happens, you must include a database commit when your transaction has ended successfully, and a database rollback in case the program detects an error. However, since database changes from a database LUW cannot be reversed in a subsequent database LUW, you must make all of the database changes for the SAP LUW in a single database LUW. To maintain data integrity, you must bundle all of you database changes in the final database LUW of the SAP LUW. The following diagram illustrates this principle:
Database Logical Unit of Work (LUW)
From the point of view of database programming, a database LUW is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed by the database system or not at all. Once a database LUW has been successfully executed, the database will be in a consistent state. If an error occurs within a database LUW, all of the database changes since the beginning of the database LUW are reversed. This leaves the database in the state it was in before the transaction started.
The database changes that occur within a database LUW are not actually written to the database until after the database commit. Until this happens, you can use a database rollback to reverse the changes. In the R/3 System, database commits and rollbacks can be triggered either implicitly or using explicit commands.
Implicit Database Commits in the R/3 System
A work process can only execute a single database LUW. The consequence of this is that a work process must always end a database LUW when it finishes its work for a user or an external call. Work processes trigger an implicit database commit in the following situations:
When a dialog step is completed
Control changes from the work process back to the SAP GUI.
When a function module is called in another work process (RFC).
Control passes to the other work process.
When the called function module (RFC) in the other work process ends.
Control returns to the calling work process.
When a WAIT statement interrupts the work process.
Control passes to another work process.
Error dialogs (information, warning, or error messages) in dialog steps.
Control passes from the work process to the SAP GUI.
Explicit Database Commits in the R/3 System
There are two ways to trigger an explicit database commit in your application programs:
Call the function module DB_COMMIT
The sole task of this function module is to start a database commit.
Use the ABAP statement COMMIT WORK
This statement starts a database commit, but also performs other tasks (refer to the keyword documentation for COMMIT WORK).
Implicit Database Rollbacks in the R/3 System
The following cases lead to an implicit database rollback:
Runtime error in an application program
This occurs whenever an application program has to terminate because of an unforeseen situation (for example, trying to divide by zero).
Termination message
Termination messages are generated using the ABAP statement MESSAGE with the message type A or X. In certain cases (updates), they are also generated with message types I, W, and E. These messages end the current application program.
Explicit Database Rollbacks in the R/3 System
You can trigger a database rollback explicitly using the ABAP statement ROLLBACK WORK. This statement starts a database rollback, but also performs other tasks (refer to the keyword documentation for COMMIT WORK).
From the above, we can draw up the following list of points at which database LUWs begin and end.
A Database LUW Begins
Each time a dialog step starts (when the dialog step is sent to the work process).
Whenever the previous database LUW ends in a database commit.
Whenever the previous database LUW ends in a database rollback.
A Database LUW Ends
Each time a database commit occurs. This writes all of the changes to the database.
Each time a database rollback occurs. This reverses all of the changes made during the LUW.
Database LUWs and Database Locks
As well as the database changes made within it, a database LUW also consists of database locks. The database system uses locks to ensure that two or more users cannot change the same data simultaneously, since this could lead to inconsistent data being written to the database. A database lock can only be active for the duration of a database LUW. They are automatically released when the database LUW ends. In order to program SAP LUWs, we need a lock mechanism within the R/3 System that allows us to create locks with a longer lifetime (refer to The R/3 Locking Concept).
The bundling technique for database changes within an SAP LUW ensures that you can still reverse them. It also means that you can distribute a transaction across more than one work process, and even across more than one R/3 System. The possibilities for bundling database changes within an SAP LUW are listed below:
The simplest form of bundling would be to process a whole application within a single dialog step. Here, the system checks the users input and updates the database without a database commit occurring within the dialog step itself. Of course, this is not suitable for complex business processes. Instead, the R/3 Basis system contains the following bundling techniques.
Bundling using Function Modules for Updates
If you call a function module using the CALL FUNCTION... IN UPDATE TASK statement, the function module is flagged for execution using a special update work process. This means that you can write the Open SQL statements for the database changes in the function module instead of in your program, and call the function module at the point in the program where you would otherwise have included the statements. When you call a function module using the IN UPDATE TASK addition, it and its interface parameters are stored as a log entry in a special database table called VBLOG.
The function module is executed using an update work process when the program reaches the COMMIT WORK statement. After the COMMIT WORK statement, the dialog work process is free to receive further user input. The dialog part of the transaction finishes with the COMMIT WORK statement. The update part of the SAP LUW then begins, and this is the responsibility of the update work process. The SAP LUW is complete once the update process has committed or rolled back all of the database changes.
For further information about how to create function modules for use in update, refer to Creating Function Modules for Database Updates
During the update, errors only occur in exceptional cases, since the system checks for all logical errors, such as incorrect entries, in the dialog phase of the SAP LUW. If a logical error occurs, the program can terminate the update using the ROLLBACK WORK statement. Then, the function modules are not called, and the log entry is deleted from table VBLOG. Errors during the update itself are usually technical, for example, memory shortage. If a technical error occurs, the update work process triggers a database rollback, and places the log entry back into VBLOG. It then sends a mail to the user whose dialog originally generated the VBLOG entry with details of the termination. These errors must be corrected by the system administrator. After this, the returned VBLOG entries can be processed again.
For further information about update administration, see Update Administration
This technique of bundling database changes in the last database LUW of the SAP LUW allows you to update the database asynchronously, reducing the response times in the dialog work process. You can, for example, decouple the update entirely from the dialog work process and use a central update work process on a remote database server.
Bundling Using Subroutines
The statement PERFORM ON COMMIT calls a subroutine in the dialog work process. However, it is not executed until the system reaches the next COMMIT WORK statement. Here, as well, the ABAP statement COMMIT WORK defines the end of the SAP LUW, since all statements in a subroutine called with PERFORM ON COMMIT that make database changes are executed in the database LUW of the corresponding dialog step.
The advantage of this bundling technique against CALL FUNCTION... IN UPDATE TASK is better performance, since the update data does not have to be written into an extra table. The disadvantage, however, is that you cannot pass parameters in a PERFORM... ON COMMIT statement. Data is passed using global variables and ABAP memory. There is a considerable danger of data inconsistency when you use this method to pass data.
Bundling Using Function Modules in Other R/3 Systems
Function modules that you call using CALL FUNCTION... IN BACKGROUND TASK DESTINATION... are registered for background execution in another R/3 System when the program reaches the next COMMIT WORK statement (using Remote Function Call). After the COMMIT WORK, the dialog process does not wait for these function modules to be executed (asynchronous update). All of the function modules that you register in this way are executed together in a single database LUW. These updates are useful, for example, when you need to maintain identical data in more than one database.
For further details, refer to the keyword documentation.
For more details of RFC processing, refer to the Remote Communications section of the Basis Services documentation.
Pls. reward if useful....

DB-LUW in ABAP-OO (Transaction-concept)

Hi Experts,
how can i use the transactionconcept in ABAP Object?
In normal abap we use for example :
CALL FUNCTION update_function1 IN UPDATE TASK
CALL FUNCTION update_function2 IN UPDATE TASK
commit work.
Are there any possibilities to use such concept in ABAP OO?
I have created some save-methods, which contains "insert" or "update" .
I call this save methods one after another, in following form
r_object->save_method1() .
r_object->save_method2() .
r_object->save_method3() .
How can I realize the LUW concept here?
Thanks in advance
Cetoman

Hello Naimesh,
Methods don't support Update Module, RFC module
Having said that, can we not wrap the method call inside an Update Module
Cheers,
Suhas

Synchronous-asynchronous PI in WD-ABAP

Hi
I am new to PI in WD ABAP . Any pointers regarding synchronous and asynchronous PI would be appreciable .

In regards to calling proxy objects, anything you can do from standard ABAP coding in normal program can also be done in Web Dynpro ABAP. Nothing really WDA specific here. We do have a special service call wizard for proxies, but everything it does can be coded manually as well.
Here is a video where we sho synchronous and asynchronous processing in PI 7.1 along with how to use these proxies in Web Dynpro ABAP:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/20eb3174-41ab-2a10-a383-907faf60eed3

JDBC to ABAP PROXY ASYNCHRONOUS SENARIO

Hi Experts
JDBC to ABAP PROXY ASYNCHRONOUS SENARIO IN PI 7.4 ?
Can you tell me any one step by step procedure
BR,
Sagar

Hi Sagar
Check the documents below and you will be able to create the whole scenario.
JDBC sender part:
SAP PI Adapter Series: JDBC Adapter Configuration
ABAP proxy receiver part:
Step-by-step FTP to ABAP Proxy - Process Integration - SCN Wiki

Timeout Error in Call Transaction on Asynchronous Abap Proxy

Hi Gurus!!
We have a problem with a Call Transaction on Asynchronous Abap Proxy. When the process of Call Transaction (transaction CO02) takes more than 10 minutes, the process is cancelled with sy-subrc 1001 and the Abap Proxy continues with the execution. Strangely, there is a short dump in ST22 on transaction CO02, although on the ABAP Proxy we don't get any dump.
When this process is called from a Background Job no dumps are get.
Somebody knows if there is a problem with the Asynchronous ABAP Proxy executing CALL TRANSACTION statementent?
Thanks and regards,
Manuel.

and the message after recording is
Number               1
Transaction          F-22
SY-SUBRC             0
Messages
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0330WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
S F5 312                   Document 100001677 was posted in company code 3100

Call mode types: Synchronous and Asynchronous in ABAP process for a chain

Hello,
I have a doubt about the call mode type for a abap type process in a process chain. It has two options:
1.Synchronous
2.Asynchronous
Would like to know the diferences between these two; advantages and disadvantages of using them.
Thanks in advance for your help...
Regards,
Anuj

hi anuj,
pls refer the following link.
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c5/eed63b54e56276e10000000a11402f/content.htm
hope it will help u to understand well the synchronous and asynchronous process chains call mode.
thanks

Fault message in asynchronous ABAP Proxy

Hi,
I have a question about fault messages in asynchronous ABAP proxy server.
The configured scenario is SOAP XI ABAP Proxy. Between XI and the ABAP Proxy I have configured an inbound asynchronous interface with a fault message, and then I have generated all the classes and implemented some code for exception handling in the ABAP Proxy side successfully.
When I tested negative cases, the exception raises and it is visible in the SXMB_MONI transaction in the R/3 side, but this exception is not displayed in the SXMB_MONI of XI it just displays a successful delivery to the ABAP Proxy message.
According the XI documentation it says In the asynchronous case, you can see a fault message in the monitoring of the Exchange Infrastructure. But this is not working.
Am I missing something?

Hi,
This parameters are form group RUNTIME.
Please check it:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/49543b1e49bc1fe10000000a114084/content.htm
Regards,
Wojciech

Starting new SAP LUW inside ABAP method

I am calling a ABAP method and in that I want to start a new SAP LUW and do commit when leaving the method.
The requirement is that all update function modules called inside the method should only be committed and no other prior update FMu2019s(before calling the method) should not be committed.
Any idea if itu2019s possible to do that in ABAP OO and how do we do it.
Thanks & Regards,
Anand.

HI ,
Thanks for the quick replies. I tried using SET UPDATE TASK LOCAL but it was also committing all the prior update FM's before calling this method.
I also tried using the RFM - CALL FUNCTION 'ABC' IN BACKGROUND TASK DESTINATION 'NONE' . and then
COMMIT WORK AND WAIT.
Now when i do commit work it commits all the previous update tasks also.
And if i do not call COMMIT WORK right after the call to RFM, then the object that i am trying to create inside the RFM will not be committed.And then if i proceede some validations will fail as the objects were not created.
Is there a way to commit immediately when the RFM is called without commiting the calling transaction from where this RFM is called.
Any examples would be highly appreciated ..
Regards,
Anand.
Edited by: Anand Ajitsaria on Feb 4, 2011 9:54 AM

ABAP proxy transmit data to XI asynchronous,how to capture the status

We are facing a problem when using ABAP proxy to transmit record asynchronous to XI system. Situation is we canu2019t capture the status in   XI system , as if XI failed to receive the record, in R3 we need to update the record as not successful received.
Kindly let me know if you have this similar experience in your project.
Thanks in advance.

-Create object and suboject in SLG0 transaction
- In program
*Call function to create log
      CALL FUNCTION 'BAL_LOG_CREATE'
*Call function to add messages
        CALL FUNCTION 'BAL_LOG_MSG_ADD'
*Call function to save all the messages to database
        CALL FUNCTION 'BAL_DB_SAVE'
-View the log in SLG1 transaction

How to make an ABAP Proxy public as an asynchronous WebService

Hello together,
i have made an ABAP-Proxy public as an WebService by generating the WSDL from the directory for my asynchronous outbound interface. This outbound interface is mapped to the ABAP-inbound interface and so on. This works fine.
But actually i don't need any mapping. So i'm thinking about to how to send the WebService directly and to the ABAP-Inbound-Interface asynchron.
1. Is this possible at all (and how), and if so
2. does it makes sense in order to improve the performace (there is a mass-processing in behind)?
Gunnar

Gunnar,
I guess its simple...go for SOAP to Proxy scenario.
If ur source and target structure is same ..u need not require mapping.u can execute the scenario without mapping also.
I have done same scenario 2 months ago.....
following things u need to do.
1)create outbound message interface
2)create inbound message interface
3)No need of message mapping and interface mapping(if u dont require any transformation of source structure)
4)create WSDL for outbound message interfce
5)create proxy for inbound MI
6)write the necessare code in ur proxy
7)using any SOAP editor like XML spy send data to proxy...
u have done the work!!!!
All the best
regards
biplab

ABAP Proxy Receiver Asynchronous EOIO

Hi,
Is it possible to Guaranteeing the Sequence of Asynchronous Messages for ABAP Proxy Receiver(EOIO)?
If yes, how can I configure?
Thanks,
Kiara.

Hi Stefan,
Thank you.
One quick question.
In case if I use JMS>PI>RFC(Async) then also no need of maintaining EOIO for RFC Receiver Async?
On JMS sender we are maintaining EOIO.
Reason for this request is currently we are using JMS>PI>RFC Async. We are using EOIO on JMS sender, but some times sequence of messages is missing.
Can you please let us know the cause of this issue.
Thanks,
Kiara.

Is Asynchronous ABAP proxy client possible without XI ?

Hi there,
Does anyone of you know if it is possible to create an asynchronous ABAP proxy client, without XI, thus directly in a SAP ERP 60 ABAP ?
Karim

Hi Anton,
thanks for your answer, it confirmed what I was thinking (asynchronous not possible in that case).
Now this leads me to a second question:
I would like to implement the scenario "acknowledge only and receive full answer later".
As you indicate: "...additionally to your webservice client you have to provide a webservice, which the receiver calls once it completes your request..."
In order to do this, I must practice as follows:
The service I call is using the WS-Addressing specifications.
Therefore, the information regarding the webservice that will be called when the request is completed should be sent as a special SOAP WS-addressing parameter, that should be indicated in the header of the SOAP Message, here is an example:
(001) <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
 xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
(002) <S:Header>
(003) <wsa:MessageID>
(004) uuid:6B29FC40-CA47-1067-B31D-00DD010662DA
(005) </wsa:MessageID>
(006) <wsa:ReplyTo>
(007) <wsa:Address>http://business456.example/client1</wsa:Address>
(008) </wsa:ReplyTo>
(009) <wsa:To>http://fabrikam123.example/Purchasing</wsa:To>
(010) <wsa:Action>http://fabrikam123.example/SubmitPO</wsa:Action>
(011) </S:Header>
(012) <S:Body>
(013) ...
(014) </S:Body>
(015) </S:Envelope>
You can see that the WS-A specific part is in the header of the SOAP Message, not in the body, so not covered by the WSDL.
Question: Is it possible to include this in the header of the SOAP Message generated by the ABAP proxy client ???

How to reset an failed asynchron abap-process in a process-chain?

Hi specialists,
I've got a process-chain which triggers (as one of its steps) an abap-program.
The program should run asychroniously, so the process-chain waits until the programm reports its ending.
When the abap-program fails/crashes/dumps, then the endings is never reported and the process-chain gets stuck.
If I try to re-run that process-chain, it fails again with the message "Variant XYZ still executing from previous run".
What I already found so far is the following note:
The process chain management will not know if your program terminates!
Thus if you re-start the chain, this will also terminate, because the old run would not have finished yet. To avoid this, you need to manually set the process in the chain log view in the process monitor to terminate before you start again.
My problem: I cannot find any possibility to set the process to "terminate" in the chain's log view.
Could you please gimme a hint where I can find that option?
Best regards,
Marco

Hi,
You can remove the process chain from scheduling before staring the process chain again.
Also can edit the entries in RSPROCESSLOG table before running the process chain.
Alternatively you can create a custom ABAP process type which handles the success as well as fail cases.
Refer : [How To- Trigger subsequent processes in a Process Chain based on the Success or Failure of ABAP program|/people/balaji.venugopal/blog/2009/04/07/how-to-trigger-subsequent-processes-in-a-process-chain-based-on-the-success-or-failure-of-abap-program]
Hope this helps,
Regards,
anil

ABAP Asynchronous LUW

Similar Messages

Maybe you are looking for