LUWF & LUW

HI ALL
1.what is LUW? what is the use,,& where we used ?
2.what is use of LBWF(bw log) in LO? why &where we used ?
any one tell me scenario of these two pls...
thnks

LUW
Let one user is modifying a record and the second user is trying to delete the same record at the same time.
If the second user is successful in deleting the record, then the first user will face problem in modifying the record.
To avoid such problems, SAP has introduced LUW (Logical unit of Work)
LUW is defined as Locking Mechanism to protect transaction integrity.
Types of LUWs:
Database transaction or LUW.
Update transaction or SAPLUW.
ABAP/4 Transaction.
database transaction
Database transaction or LUW is defined as a period in which operation requested must be performed as one unit.
At the end of LUW, either the database changes are committed or rolled back.
SAP LUW
One SAP LUW can have several databases LUW. So a set of database transactions either committed or rolled back.
The special ABAP/4 command Commit work marks the end of SAP LUW.
ABAP/4 Transaction
It is made up of a set of related task combined under one transaction code.
ABAP/4 transaction functions like one complete object containing screens, menus and transaction code.
Check this documentation..
http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bfa79e11d1950f0000e82de14a/content.htm
And LBWF is the LO's log where yoou can find the info about all the extraction related tasks.
Assign points if usefull
Regards,

Similar Messages

Diff b/w SAP LUW and DB LUW?

2. what is the diff b/w SAP LUW and DB LUW?

Database LUW : <a href="http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm">LInk</a>
Sap LUW : <a href="http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm">Link</a>
Thanks
Mahesh

Issue in CIF - Execute LUW again

Hi ,
   I created an integration model for stock transfer and when i try to activate it , it gives error. In SMQ1 (outbound queue from ECC to SCM) an entry is shown with status "RETRY" and it says "Command to tRFC/qRFC Execute LUW again" . In the queue manager in SCM (cq) it shows the same error ie., "Execute LUW again".
     I tried looking at the application log but it says "no application log available" .
     When i try to execute the LUW from SMQ1 it keeps giving me the same error again and again. I tried deleting the LUW from SCM using "queue manager /n/sapapo/cq". But it is not allowing me to delete the LUW.
      Since the queue is blocked it does not allow me to execute any other integration model. Kindly suggest a solution.

Hi
Should you not try deleting the blocked queue from TA SMQ1 itself and try to activate the integration model again if you are not able to debug the problem. I do not know the effects of doing this in your scenario but usually we delete the blocked queues from smq1. This method works for us most of the times.
To do this select the queue ( identified by a part of your document no. ) line and press delete button in std application tool bar.
What error are you getting when trying to delete the queue from /sapapo/cq?
regards
Mohan Chunchu
Edited by: Mohan V R Chunchu on Jan 29, 2008 10:58 PM

How can i check all the data in LUW's of RSA7

Hi All,
Iam trying to see the contents of LUW's for my data source in RSA7, but it keeps on giving me only data from data packet 7, even if i changed different numbers in
in option " choose" and different options in " extraction parameters"
its only displaying data when i select update mode as " repetition" no records when i select "delta"
i can imagine thats bcoz my last delta was failed. is that right??
How can i select data from different packagaes( as it shows in BW)???
any help pls.
Regards
Robyn.

Thanks guys
Actually i was trying to figure out the error data coming from my datasource failing my data load. the error is
<b>" Value '60306XZED ' from field ANZVERTR is not convertible into the DDIC
data type DEC in data record 1 . The field content could not be
transferred into the typed transfer structure."                           </b>
that field ANZVERTR has type DEC & length 6 is assigned to infoobject 0UCCNTRCNT of data element /BI0/OIUCCNTRCNT ( DEC & length 17)that has type Number, data type DEC (Counter or Amount field with comma and sign.
I guess this assignement is correct but i cudnt able to understand how this valus "60306XZED" is coming to this field. at the first place ANZVERTR has length only 6 then how come it bring this value from R/3.
I cudnt able to figure out is this error from R/3 or BW.
Pls anybody help.
Regards
Robyn.

Error while executing LUW in SM58 - Mess.No.SY359

hi,
error while executing LUW in SM58
Error. Mess.No.SY359
"Function module does not exist or EXCEPTION raised-sy359"
trfc has been configured and try to push the Idoc through SM58 need help on this.
Regards
Leo

Hi,
This error is related to RFC settings and also the logon group in RZ12
Kindly generate the appropriated logon groups and confirm if the idocs are flowing
Thanks

Transaction VA01 separate LUW / commit DB when creating in Background PO

Hi experts,
I have a request to create a PO for a particular item of a sales document, and for the PO created I need to fill one component and to lock it. I found out that the only way to create for sure a PO is the FM BAPI_ORDER_CREATE. To update the components and to lock it I need a BDC. I did not found any FM which might do something like this.
The place where I trigger the creation of PO is user_exit_save_document. My logic is the following: I create the PO with BAPI_ORDER_CREATE in another LUW then trigger commit both with BAPI commit and commit work for this separate LUW, In the same LUW in which I created the PO, after the commit, I call a BDC Function Module that updates the component and locks the PO.
I observed that the BAPI ORDER CREATE works fine - it always creates me a PO. When running in the next step the BDC FM , it always returns me the message "PO (before created) does not exist". In debug Mode everything works fine, PO is created and also BDC FM does not return me any error.
It seems to me that when the logic runs in dialog mode all the PO tables are not updated before I run the BDC. As I am openning a separate LUW and I trigger explicitly COMMIT in this separate LUW I was wondering why does not the update of PO tables take place? Is this because the transaction VA01 does not allow any commits for the programms that are called from the transaction? Or what am I missing?
I did a kind of workaround and I don#t run the BDC only after the batch input is created, but I was wondering why am I wrong.
Thank you for the support,
Florin

Hi
I suppose the problem is the time taken to run the saving process, this process is still running while your BDC is starting.
U should use a COMMIT WORK and WAIT in order to be sure the saving process is over before calling the BDC.
Now I don't understand where you have place the COMMIT for the BAPI
Max
P.S.: BAPI ORDER CREATE doesn't exist in my systen, I have BAPI_PO_CREATE1
Max
Edited by: max bianchi on Aug 15, 2011 1:40 PM

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

What is luw (logical unit of work)

pls tell me what is luw (logical unit of work)
what r the types of luw .
2 what ispurpose of code inspector and extended program check
pls expalin the diffrence b/w those two
3what are the candidate keys in db tables
4 what is the difference b/w occurs 1 and occurs 2 clauses
data : begin of itab occurs 0 .
data : itab type standard table of structure type initial size 1 with header line
pls tell diffrence between theese two statements
5can u pls tell what is the client in sap
pls tell answers to questions
pls dont give any websites addresses to see answers
6 what is the transaction from database point of view
7 what is the variant in alv reports
how do we use reuse_alv_grid_variant_get fun module in alvs

hi,
this gives complete idea
SAP LUW
Since, as a rule, an application program is processed by several work processes in succession, and every change of the work process is linked with an implicit database commit , an application program is not automatically linked with a single database LUW. This applies in particular to dialog-oriented applications, in which one database LUW is assigned to one dialog step.
To ensure the data consistency of application programs that are executed across different work processes, the application statements are not directly executed in an SAP LUW, rather, are first registered and then executed by a single work process, that is, in a single database LUW.
Two techniques are available for bundling the change statements in a database LUW:
Bundling via function modules (update)
Through the statement CALL FUNCTION...IN UPDATE TASK, an update function module is registered for subsequent execution in an update work process.
Bundling via function modules (transactional RFC)
Through the statement CALL FUNCTION... IN BACKGROUND TASK DESTINATION, a remote- compatible function module is registered for subsequent asynchronous execution via the RFC interface (transactional RFC ).
Bundling via subprograms
Through the statement PERFORM ... ON COMMIT, a subprogram is registered for subsequent execution in a different work process.
Statements for SAP LUWs
A SAP LUW is controlled via the Open SQL statements COMMIT WORK, ROLLBACK WORK and SET UPDATE TASK LOCAL.
Note
A function module can be classified either as an update function module or remote-compatible, but not both at the same time. The update helps realize SAP LUWs within an SAP System, while the transactional RFC creates LUWs in distributed systems.
COMMIT WORK
Variants:
1. COMMIT WORK [AND WAIT].
2. COMMIT CONNECTION con.
Effect
Terminates an SAP LUW and stores the changes.
Variant 1
COMMIT WORK [AND WAIT].
Effect
The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the currenta SAP LUW in the process. In this case, COMMIT WORK performs the following actions:
It executes all subroutines registered using PERFORM ON COMMIT.
It triggers an internal event in Object Services that ensures the registration of changes in persistent objects as the last update function module, as well as the subsequent initialization of persistent object attributes.
It initiates the processing of all registered update function modules in the update work process.
This executes all high-priority update function modules registered using CALL FUNCTION ... IN UPDATE TASK in the order of their registration and in a common database LUW. If you do not specify the addition AND WAIT, the program does not wait until the update work process has executed it (asynchronous updating). If you specify the addition AND WAIT, however, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).
If all high-priority update function modules are completed successfully, the statement executes the low-priority update function modules together in a common database LUW.
In parallel, it also executes the individual function modules registered using CALL FUNCTION ... IN BACKGROUND TASK DESTINATION in a separate database LUW for each destination.
It handles all SAP locks set in the current program according to the value of the formal parameter _SCOPE of the corresponding lock function modules.
It triggers a database commit that also terminates the current database LUW.
The completion of statement COMMIT WORK triggers the event TRANSACTION_FINISHED of the system class CL_SYSTEM_TRANSACTION_STATE, where the parameter KIND has the value of the constant CL_SYSTEM_TRANSACTION_STATE=>COMMIT_WORK.
If the statement COMMIT WORK is executed by calling special programs, be aware of the following:
In a program executed using batch input, or if you have called the program using the USING addition of the statement CALL TRANSACTION, COMMIT WORK terminates the batch input processing when using the corresponding settings.
In a program called using CALL DIALOG, COMMIT WORK initiates the processing of subroutines or updated function modules registered using PERFORM ... ON COMMIT and CALL FUNCTION ... IN UPDATE TASK. Therefore, it does not complete the current SAP LUW. The SAP LUW cannot be completed until you execute the COMMIT WORK statement in the calling program.
You cannot execute the COMMIT WORK statement during the updating procedure or during the execution of subroutines registered using PERFORM ... ON {COMMIT|ROLLBACK}.
System fields
sy-subrc Meaning
0 You have specified the AND WAIT addition, and the updating of the update function modules was successful.
4 You have specified the AND WAIT addition, and the updating of the update function modules was not successful.
The COMMIT WORK statement always sets sy-subrc to 0 if the AND WAIT addition is not specified.
Note
The COMMIT WORK statement closes all database cursors . Open SQL statements that access a database cursor later ( SELECT loop and FETCH) raise an exception that cannot be handled.
Variant 2
COMMIT CONNECTION con.
Note
This statement is for internal use only.
It cannot be used in application programs.
Effect
The COMMIT command is not executed on the standard database, but only on the secondary database connection specified by con. con is the name of the database connection as it was specified in the table DBCON in the column CON_NAME. The database connection con can also be specified dynamically in the form (source_text) - the source_text field contains the name of the database connection. The source_text field must be of the type C or STRING.
On the specified secondary database connection, the database commit:
Closes all open database cursors (OPEN CURSOR)
Releases all database locks
Note
Note that the COMMIT CONNECTION DEFAULT statement unlike COMMIT WORK executes a pure database commit on the DEFAULT connection.
Exceptions
Non-Catchable Exceptions
Cause: COMMIT WORK is not possible in a FORM that was called using PERFORM ... ON COMMIT.
Runtime Error: COMMIT_IN_PERFORM_ON_COMMIT
Cause: COMMIT WORK is not allowed in the update.
Runtime Error: COMMIT_IN_POSTING
ROLLBACK WORK
Variants:
1. ROLLBACK WORK.
2. ROLLBACK CONNECTION con.
Effect
Terminates a SAP-LUW without storing the changes.
Variant 1
ROLLBACK WORK.
Effect
The statement ROLLBACK WORK closes the current SAP-LUW and opens a new one. In doing so, all change requests of the current SAP-LUW are canceled. To do this, ROLLBACK WORK carries out the following actions:
Executes all subprograms registered with PERFORM ON ROLLBACK.
Deletes all subprograms registered with PERFORM ON COMMIT.
Raises an internal exception in the Object Services that makes sure that the attributes of persistent objects are initialised.
Deletes all update function modules registered with CALL FUNCTION ...IN UPDATE TASK from the VBLOG and deletes all transactional remote Function Calls registered with CALL FUNCTION ... IN BACKGROUND TASK from ARFCSSTATE and from ARFCSDATA.
Removal of all SAP locks set in the current program in which the formal parameter _SCOPE of the lock function module was set to the value 2.
Triggers a database rollback, which also ends the current database-LUW.
After completion of the statement COMMIT WORK, the event TRANSACTION_FINISHED of the system class CL_SYSTEM_TRANSACTION_STATE is raised, in which the parameter KIND has the value of the constant CL_SYSTEM_TRANSACTION_STATE=>ROLLBACK_WORK.
Variant 2
ROLLBACK CONNECTION con.
Note
This statement is for internal use only.
It cannot be used in application programs.
Effect
The ROLLBACK-statement is not executed on the standard database but only on the secondary database connection, specified through con. con is the name of the database connection as it was specified in table DBCON in column CON_NAME. The database connection con can also be specified dynamically in the form (source_text), in which the field source_text contains the name of the database connection. The field source_text must be of the type C or STRING.
Notes
As all opened database cursors on the respective database connections are closed at ROLLBACK, the attempt to continue a SELECT-loop after a ROLLBACK, leads to a runtime error. Due to the same reason, a FETCH after a ROLLBACK to the then closed cursor, leads to a runtime error. You have to make sure that cursors that are still open, are no longer used after ROLLBACK.
After execution of the statement ROLLBACK, SY-SUBRC is always equal to 0. It is not necessary to check if SY-SUBRC is unequal to 0 after ROLLBACK.
ROLLBACK must not be used during update (CALL FUNCTION ... IN UPDATE TASK) or during the execution of FORMs, which were registered with PERFORM ... ON COMMIT resp. PERFORM ...ON ROLLBACK.
The statement ROLLBACK WORK is implicitly executed if a message of the type A is treated with the addition ERROR_MESSAGE when calling a function module with CALL FUNCTION.
Exceptions
Non-Catchable Exceptions
Cause: ROLLBACK WORK is not allowed within a FORM that is called with PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK.
Runtime Error: ROLLBACK_IN_PERFORM_ON_COMMIT
Cause: ROLLBACK WORK is not allowed within an update.
Runtime Error: ROLLBACK_IN_POSTING
SET UPDATE TASK LOCAL
Syntax
SET UPDATE TASK LOCAL.
Effect
This statement specifies that the high-priority update function modules - registered during the current SAP LUW using CALL FUNCTION ... IN UPDATE TASK - are registered in the ABAP memory instead of the VBLOG database table. In addition, it specifies that the current work process and not the update work process run these modules during the current database LUW, when the COMMIT WORK statement is executed. This statement has no effect on low-priority update function modules.
At the beginning of every SAP LUW, the local update function is deactivated. If you wish to use it, you must reactivate it again before the first update function module is registered.
System fields
sy-subrc Meaning
0 The local update function is activated.
1 The local update function has not been activated, because the program has already registered at least one update function module for the normal updating procedure in the current SAP-LUW.
Notes
The local update function performs a synchronous update according to the COMMIT WORK statement, independent of the addition AND WAIT.
The occurrence of a database rollback during the local update affects all previous change requests.

RFC in background task LUW

Hello,
I've two RFC in user-exit. Both, using IN BACKGROUND TASK DESTINATION XI
When i execute the transaction, the user-exit is raising and i can see the follow error in SM58:
maximum size of requests for one LUW has been reached(1).
I've changing in the CC the parameter Maximum Conecction, however the error continue.
If i comment the second call function in the user-exit, the first call function is executed OK, the interface is right,
¿how can i do to execute two functions in the same LUW?
thanks

Hi,
>>¿how can i do to execute two functions in the same LUW?
you cannot - you need to do "commit work." after each RFC call
Regards,
Michal Krawczyk

Multiple RFC calls in one LUW

Hi Guys,
Is it possible to do multiple RFC(receiver) calls in a single LUW(Logical Unit ofWork) in PI 7.0??
If yes, can any1 pls tell me from which SP level has this been enabled??Also what settings do i need to do to create the scenario??
Thanks
Varun

hi
i think its possible.please refers to the link hope it will help u.
1.https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
2.http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
3.http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
regards
kasturika

Error in RFC Adapter PI 7.10 maximum size of requests for one LUW

Hello all,
I have a big issue on our Development - SAP PI 7.10 System. If I try to push a RFC from a Client System
I get follow error messagei in the Runtime Workbench (RWB) back:
processing error to be caused by: com.sap.aii.adapter.rfc.core.server.RfcServerException: maximum size of requests for one LUW has been reached (1). handling of request for tRFC (TID: 0AA001B8712C49D35D4D06C2) not possible (server: RfcServer[PKG_R3_D07_600_RFC_SND]1)
But I don't know why. I checked follow OSS Notes:
730870 and 774705 w/o success. It will be nice somebody can help me.
Thanks
S. Kohler
P.S. We have the same scenario in our Quality SAP XI System and there works. I couldn't find any
differences between the Adapters. Is there a problem with the parameters ????

Hello Tarang Shah,
okay. Here again ( I thought I mentioned above):
in Q50 (SAP PI 7.10 System) we create a RFC Server with the program ID RFC_Q50.
in D64 (SAP PI 7.10 System) we vreate a RFC Server with the program ID RFC_D64
in D07 (SAP R/3 4.7 x110) we create a RFC Connection to D64 with the program ID RFC_D64.
The testconnection works well. I see in our Dev. SAP PI System (D64) that the connection works.
The problem is here, if you start in the application (System D07) the push, you get the error :
maximum size of requests for one LUW has been reac hed (1). handling of re
in Q50 (SAP R/3 4.7 x110) we create a RFC Connection to Q50 with the program ID RFC_Q50.
The testconnection in Q17 works well. Also the push from the application (System Q17.)
This means, the functionallity is okay on both sides (Q17 and D07) only the application sending
process from D07 makes trouble ( you see in Transaction SM 58 on Client Site, the error as I mentiond above and in SAP PI side.) It seems that SAP PI could't accept more as one LUWs
in the same time. Q50 (Q- System) accepted.
So, this is the reason in my point of view, that the problem isn't the connection, seems more
an paramter problem in D64 side. But I don't know which parameters. I checked the OSS Note 730870 and 774705 w/o success.
Thanks
S. Kohler

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.

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

How to do LUW in OO concept?

Hi everyone,
I have a question: how to do luw in OO concept?
I know that in SAP ABAP, there are two ways to do LUW
first is function module ,the other is subroutine.
And now, I have a method of my class. In this method,
I will do some database updating, and I want to do these database
operations in a SAP LUW, I don't know how to do that.
Because in method attributes, it seems there is not an attribute
in update model. And I try to create a function module ,pass a reference
to it, and call the method in the function module,but when a function
module is in update module , reference can not be passed.
is there anyway to accomplish LUW in OO way?
Thanks for your help.

http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/content.htm
http://www.*******************/2007/08/lesson-46-lws-and-clientserver.html
http://help.sap.com/saphelp_nw70/helpdata/EN/41/7af4bfa79e11d1950f0000e82de14a/content.htm

LUW data for smq2--Error During Delivery: Ibound processing locked

Hi all,
There are lot of messages(more than 7000) stucked in d Inbound queues, as viewed by SMQ2, and are in the retry mode for long.
In the LUW data the status of the queue is showing error during delivery and the error text is <b>Inbound Processing Locked for example Deadline Processing </b>
can anyone please suggest what this problem is about and suggstions for removing this problem will be really appreciated.
This is urgent as the problem is in production.
Regards,
Rookie.

Hi Prateek,
The BPM involved is a dicesion making BPM which is creting large Idocs.
We have checked in SM12 and the messages are locked there. Can you please advice how can we unlock the messages from SM12.

LUWF & LUW

Similar Messages

Maybe you are looking for