Integration of PLC(programming logic unit) in SAP

i'm facing problem with this, our client is using PLC (programming logic unit) for there manufacturing ,so with out third part tool how can we integrate in SAP plz any one can help

kishore.
i am just throwing ideas now, its impossible to debug over forum.
go ahead and just check all switches between qa and prod in OOAC, confirm they are all the same,
check OOSB - check that the user profile is in both environments, with same dates, and eval paths (display objects).
DFCON = 1 means Deny 99999999, but Evaluate Organizational Unit (if available). Check if there are any differences in IT0001 of the org unit ids, in production perphas Org unit ID is not filled on the record where position is = 99999999.
in general your team should review this link: http://help.sap.com/saphelp_47x200/helpdata/en/56/db5bc71a64c94f9f2e3cb63e14c867/content.htm
review orgpd switch as well:
http://help.sap.com/saphelp_47x200/helpdata/en/c7/4aba3b3bf00152e10000000a114084/content.htm
review how org key works (different than org ID previously mentioned):
http://help.sap.com/saphelp_47x200/helpdata/en/7f/1a7d3c8015d10ee10000000a11405a/frameset.htm
run this in both qa and production. check transaction oosb after as well.
1) Call program RHBAUS02 for uploading Table T77UU and enter users.
2) Call program RHBAUUS00 for generating an index for structural authorization profile

Similar Messages

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.

Logical unit of work

Hi all,
Can help me regarding LUW(logical unit of work) and its importance in r/3 ?
Thanks and Regards
Ravi

Hai Ravi Charan
There are 3 types of LUW's available in SAP
1)Database Transaction or DBLUW
2)SAP      Transaction or SAPLUW
2)ABAP     Transaction or ABAPLUW
1) DBLUW : when it is called it locks the rows , Update the rows & commit the rows issued by auto Commit
2) SAPLUW : collection of Business reports is called SAPLUW and Issuing the Commit
here UPDATE,INSERT,MODIFY statements are valid
Commit work is given by Developer Side.
3) ABAPLUW : What ever Transaction Code we are creating is called ABAPLUW it is belongs upon Developers
here 3 types of updates available
1) Bundled Updates
2) Un-Bundled Updates
1) Bundled Updates :
    in Bundled Updates all your updates in a single unit of work present in a PERFORM 'XYZ'
PERFORM 'XYZ' on Commit.
here PERFORM-kept in Buffer 'XYZ' this form having all your update statements
Priarities of execution.
Perform xy on comit it will execute first
perform ab on comit it will execute second
I want to change this execution Order
Perform xy on comit Level 2 it will execute second
perform ab on comit Level 1 it will execute First
because it will depends on Level command
Using in Function Modules
Call Function XYZ in Update Task.
Commit work.
In this case it stores in a buffer once encounters the commit statement this will executes from the buffer
so it is an asynchronos method
2) Un Bundled Updates
these are two types
1) Inline Updates
2) Buffered Inline Updates
1) Inline Updates : INSERT,UPDATE
when update statement found in a program then it is called inline update and you should give the 'commit work'after a update statement
inthe inline update if you not issue a commit work the system will automatically issues the commit work.
2) Buffered Inline Updates:
you will buffer all your inline updates and executes after Encounter the 'COMMIT WORK'
100
   XYZ --> we can not roll back here
200
   ABC---> if here is using commit
Thanks & Regards
Sreenivasulu P

Logical unit of works

Can some one tell me abt logical unit of work(LUW).

Hi,
A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit.
LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started.
An LUW begins
o each time you start a transaction
o when the database changes of the previous LUW have been confirmed (database commit) or
o when the database changes of the previous LUW have been cancelled (database rollback)
An LUW ends
o when the database changes have been confirmed (database commit) or
o when the database changes have been canceled (database rollback)
Two types of LUW are:
1) DB LUW - A database LUW is the mechanism used by the database to ensure that its data is always consistent. 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 had before the transaction started.
2) SAP LUW - 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.
More on this .
http://help.sap.com/saphelp_nw2004s/helpdata/en/41/7af4b9a79e11d1950f0000e82de14a/frameset.htm
Regards,
Raghav

Differences between Commit work, Logical Unit of Work and Roll back work

Hi all,
Can any one explain me in details what is the difference between Commit Work, Logical Unit of Work and Roll back work. Pls explain by providing some example.
and also explain me where and when these are used and what are the importance of using these.
Thanks in advance.
Regards
Ramana Prasad.T

Hi Ramana Prasad,
A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit.
LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started.
An LUW begins
o each time you start a transaction
o when the database changes of the previous LUW have been confirmed (database
commit) or
o when the database changes of the previous LUW have been cancelled (database rollback)
An LUW ends
o when the database changes have been confirmed (database commit) or
o when the database changes have been canceled (database rollback)
COMMIT WORK.
Executes a database commit and thus closes a logical processing unit or Logical Unit of Work ( LUW ) (see also Transaction processing ). This means that
all database changes are made irrevocable and cannot be reversed with ROLLBACK WORK and
all database locks are released.
COMMIT WORK also
calls the subroutines specified by PERFORM ... ON COMMIT * executes asynchronously any update requests (see CALL FUNCTION ... IN UPDATE TASK ) specified in these subroutines or started just before,
processes the function modules specified in CALL FUNCTION ... IN BACKGROUND TASK ,
cancels all existing locks (see SAP locking concept ) if no update requests exist,
closes all open database cursors (see OPEN CURSOR ) and
resets the time slice counter to 0.
COMMIT WORK belongs to the Open SQL command set.
Return code value
The SY-SUBRC is set to 0.
ROLLBACK WORK.
Closes a logical processing unit by reversing all database changes made since the last COMMIT .
You use this statement if you cannot be certain that all the database changes have been executed correctly.
The update routines are not performed.
ROLLBACK WORK belongs to the Open SQL command set.
Note
If the ROLLBACK statement occurs within a SELECT loop, the processing cannot continue because the database cursor is invalid. After the ROLLBACK statement, you should therefore ensure that all SELECT processing has been explicitly terminated.
Plz. Avoid Duplicate Threads.
Hope this resolves your query.
Reward all the helpful answers.
Regards

Bapi and Logical Unit of Work

Hi all,
I am using Bapi to post records in a loop on internal table itab. After posting records, I am again looping at itab and populating those records to my custom table.
Does this scenario use 2 logical unit of work?
If yes, then please tell me how do I use one logical unit of work.
Thanks,
Ridhima

Hey,
You should not post records to the custom table if the BAPI posting has failed.
In order to maintain data consistency the logic in your program should be as below:
LOOP AT itab.
CALL BAPI.
IF BAPI Call is successful
Post data to Custom table.
CALL BAPI_TRANSACTION_COMMIT.
ELSE.
CALL BAPI_TRANSACTION_ROLLBACK.
ENDIF.
ENDLOOP.
Talking about LUW's, any program uses 1 SAP LUW and Multiple Database LUWs depending on the number times you COMMIT the data to the database.
If in your program you were to use only one COMMIT statement or no COMMIT statement at all, your program would use 1 SAP LUW and 1 database LUW.
-Kiran
*Please mark useful answers

RE:logical unit of work

Hi guys,
What do u mean by logical unit of work...Can anyone explain me with an example.
Regards,
Alex.

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.
Regards
vasu

Related to LUW(logical unit of work)

Hi Experts,
 Based on an inbound idoc i need to change some data in delivery. SD_DELIVERY_UPDATE_PICKING is used to update delivery(PGI details). And also i need to change some other data(which is not possible with the above function module), so i used WS_DELIVERY_UPDATE.
 But the problem is these 2 function modules are calling the standard SAP routines which are used in the program(SAPLV50L) which used for VL02N.
 Now i changed my code, instead of FM WS_DELIVERY_UPDATE i used BDC, now it is giving error like 'This delivery(number) is currently processed by another user (my user id) which means i am trying to change it in same program.
 How can i use these above 2 Function modules in my program. Even i am using COMMIT WORK it creates problem.
 Is there any Function module or any command(other than COMMIT WORK) to ends a LUW(Logical Unit of Work).
 I need your inputs.
cheers,
Bujji

Hi,
 You can do one thing to over come this problem.....
After calling the 1st function module .....using do --while loop check if the update has taken place by checking the tables.......Once its done you can call the second function module......
I think we can also check for locked objects ....let me think over it
regards,
vijay

Problem converting Integration Process to ALE logical system(acknowledgmen)

Hello,
I have a scenario where a sender SAP system sends an IDoc via an Interface Mapping to an Integration Process.
This worked perfectly fine on our development environment, but after transporting the scenario to our quality systems I got the following acknowledgement error:
Unable to convert the sender service name of integration process to an ALE logical system.
What could be the reason for this? We have a logical system on the sender SAP system set up for the XI system itself but not for the Integration Process.
We also use SYSTAT IDocs and there we set the the logical sender system name to the logical system for SAP XI and not for the integration process.
Is this also necessary for acknowledgements? Where could this be done. Strange thing is that it works perfectly fine on our development environment.

I raised the same question a few months back.Answer to this question is in the same thread.
Idoc Acknowledgements - Logical System Name
You will have to select option "Restore Original Parties for Idoc Acknowledgments " in the Acknowledgment Idoc adapter.
Regards
Bhavesh

Solution Manager - Logical Component for SAP Netweaver EHP2

Hello,
I installed the newest SAP Netweaver Ehp2 (with usage type AS ABAP only) for a future integrating with BI_CONT (SAP BI requirement). So... what I want to know is... I want to do an update of support packages to the latest Stack (SPS) and in this product version (NW EHP2) the latest stack is stack 06 !! But I ´m facing with a problem which is, because I have to maintain this system in Solution Manager (for Maintenance Optimizer activity)...so what I want is configure this new system on Solution Manager Ehp1 (with SPS 23) but in tcode SMSY I didn´t found this Product in Logical Components for I can apply this system to my Solution... I only see SAP Netweaver with EHP1 and not with EHP2 which is the version that I want to apply this new system. (This is mandatory task, because without it, I will not be able to download the support packages for NW 7.0 EHP2)
Tell me two things... first if this level version of Solution Manager that I have here (SPS 23) have this product in logical components, and two... if not it, is necessary to raise the level of Solution Manager support packages (to latest stack SPS 25) for I can see that logical component SAP Netweaver EHP2?!
Thank you very much
João Dimas - Portugal

Hi João,
You can verify if the EHP2 is available (if) in your system, this can be done once you are in SMSY -> Product Definitions -> SAP Netweaver where you should able to see the EHP2. If so, then it's a matter of marking the leading Product & Product Version under the Header Data ->Change Product Assignment where you can use the drop down arrow to select the Product and Product Version. If it's not available, then by checking the 'Free Product / Select Product Version' then use the drop down arrow to select the product & Product Version, once you selected that then click on copy and mark that as active and save.
Then you need to create a new logical component in System Group & logical Component under SAP Netweaver, then assign the system to the logical component. Once this is done you can use the logical component in a solution and create a maintenance transaction.
I hope this help you to proceed further, thanks.
Jay Soma.

Program/Logic behind the Copy functionality in SE38 Transaction

Hi,
In SE38 by using the copy option, Program along with sub-objects can be copied to another object.
Please let me know the Program/Logic behind that functionality.
Also let me know is there any option in SAP to copy program from one system to another system.
Thanks,
Madhuri.

Hi Madhuri
This is tha Program logic behind copying object thru se38
where p_operation would have the value 'COPY'' in it.
DATA: l_request TYPE REF TO cl_wb_request,
        l_wb_todo_request TYPE REF TO cl_wb_request,
        l_object_name TYPE seu_objkey,
        l_object_type TYPE seu_objtyp,
        l_program_state TYPE REF TO cl_wb_program_state.
IF trdir-subc = 'I'.
    l_object_type = swbm_c_type_prg_include.
    CALL METHOD cl_wb_object_type=>get_concatenated_key_from_id
      EXPORTING
        p_key_component1 = space
        p_key_component2 = rs38m-programm
        p_external_id    = l_object_type
      RECEIVING
        p_key            = l_object_name.
ELSE.
    l_object_type = swbm_c_type_prg_source.
    l_object_name = rs38m-programm.
ENDIF.
CREATE OBJECT l_program_state.
CREATE OBJECT l_request
      EXPORTING p_object_type = l_object_type
                p_object_name = l_object_name
                p_operation   = p_operation
                p_object_state = l_program_state .
CALL METHOD
    wb_pgeditor_initial_screen->mngr->request_tool_access
    EXPORTING
      p_wb_request      = l_request
    IMPORTING
      p_wb_todo_request = l_wb_todo_request
    EXCEPTIONS
      action_cancelled = 1
      no_tool_found     = 2.
IF sy-subrc NE 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
    EXIT.
ENDIF.

Clarification of the logical structure of sap system & enterprise structure

Dear Sap Gurus,
Kindly help me to clarify the following words.I am grateful for answers.Answers will be rewarded with points.Simple & brief explanatios are highly appreciate.Thank you.
1.FI Enterprise Structure
my answers:Collection of organization units is called fi enterprise structure.
2.Organization Units
a.An element in the logical structure of sap system is called organization unit.
3.The Logical Structure Of Sap System=?
Best Regards
priya desai

Hi Priya,
The Enterprise Structure represents the structure of a company according to personnel administrative, time management and payroll perspectives. The company structure describes elements of the company and there dependencies.
The 'Organizational Units' in SAP, are the elements or structures representing the business functions, and are used in reporting. for example, Client (across the various modules), Company Code (FI), Controlling area (CO), Plant (logistics), sales organization (SD), Purchasing organization (MM), Employee Group (HR) etc.
Thanks
Para

Prigramming Logic details for SAP APO Planning Models

Hi All,
I need to learn more about different model available in SAP APO - DP, SNP and their behaviour.
Request to please share any link or document associated with programming logic in different planning models available in APO.
Thanks in Advance.

Hi Senthil,
Thanks dear for your response.
What I am looking in programming details of exisiting DP forecasting models like Trend Analysis, Linear Regression.
What I know about MLR is that system uses below equation
Yi = bo + b1X1 + b2X2... + bn Xn
where Yi = Sales History
bo = Mean
b2 = co-efficients
x2 = causal factor etc.
Do you have document which details out how the figures are computed using these planning models?
Once again thanks for your quick reply brother.

Sequencing 3 sceanrios as one logical unit of work

Hi,
I have 3 business services BS1,BS2,BS3
BS1 is source database DB1 which has 2 tables DB1_table1,DB1_table2
BS2 is another source datbase DB2 which has one table DB2_table1
BS3 is target database DB3 which has 2 tables DB3_table1,DB3_table2
And the three scenarios are as below
1.Data from DB1_table1 has to be inseted into DB3_table1 -
from BS1 to BS3
2.Data from DB1_table2 hasto be inserted into DB3_table2 -
from BS1 to BS3
3.Data from DB2_table1 has to be inserted into DB3_table2 -
from BS2 to BS3
But i want all these 3 sceanrios as one logical unit of work and 1,2,3 should be in a sequence.If any one of these fails remaining processes should fail. for ex if 1 fails 2,3 should not occur.
How can i achieve this?
Thanks & Regards,
Jyothsna

Hi,
you can able to achive this using BPM.Check the below links for creating BPM scenarios..
[https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]]
[Schedule Your BPM]
[Walkthrough with BPM]
[The specified item was not found.]
[RFC Scenario using BPM --Starter Kit]
[/people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi]
[The specified item was not found.]
[One Logical System Name for serveral BPM Acknowledgements]
[Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure]
[Posting multiple IDocs with Acknowledgement]
Regards,
Prakasu

Can I create my own logical unit of work (LUW)?

Good day, everyone!
This is an off-shoot to a Why does the NOCOMMIT parameter not work in HR_INFOTYPE_OPERATION? yesterday in this forum.
It appears that the FM I'm calling is going to do a commit, no matter what. The only thing I can tell is that the NOCOMMIT parameter is used to do a rollback only in the event of a problem.
What I'd like to do is somehow "encapsulate" my call to this function with my own "LUW" designation so that, depending on what a user selects in a selection screen (run as test only? checkbox) I can rollback changes on my own. Unfortunately, I don't know if this is even possible and, if so, how to do it. I need to do something because the end users running this function would like to be able to do a "test run" of all the address transactions to see if there's any errors, data that still needs cleaned up, etc.
Any ideas? Points awarded for all helpful answers, as always.

Hai Dave Packard
Go through the following Link
For Logical database
Logical Unit of Work (LUW)
A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit.
LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started.
An LUW begins
each time you start a transaction
when the database changes of the previous LUW have been confirmed (database commit) or
when the database changes of the previous LUW have been cancelled (database rollback)
An LUW ends
when the database changes have been confirmed (database commit) or
when the database changes have been canceled (database rollback)
Database commit and rollback
Within an LUW, database changes are not made until after a database commit. Prior to this, any database change can be canceled by a database rollback.
In the R/3 System, a database commit is triggered either automatically or by the ABAP/4 command COMMIT WORK or the appropriate Native SQL command for the database system.
Similarly, a database rollback is triggered either automatically or by the ABAP/4 command ROLLBACK WORK or the appropriate Native SQL command for the database system.
A database commit is triggered automatically by
each screen change, and especially after the ABAP/4 commands CALL SCREEN, CALL DIALOG, CALL TRANSACTION, MESSAGE or
a Remote Function Call
A database rollback is triggered automatically by
errors which occur at runtime or
the ABAP/4 command MESSAGE with the message type 'A'
After each database commit or rollback, the database locks set in the LUW are released (see Database Locking).
Thanks & regards
Sreenivasulu P
Message was edited by: Sreenivasulu Ponnadi

Integration of PLC(programming logic unit) in SAP

Similar Messages

Maybe you are looking for