Is remove() Guaranteed Transactional?

We want to process items in a distributed cache and make sure they are only processed by a single node. If we use remove() to get the item from the cache, is it guaranteed that only one node can do so and that any other node would throw an exception? Is this true of all cache types or just certain types.
Thanks.
--Tim

Where do NearCache's fall into this? If a value is near in more than one cache and they both remove it, can they both get non-null values?
--Tim

Similar Messages

Bank Guarantee transactions

Dear All,
We are entering into Bank Guarantee transactions regularly.
It happens in such a way is that ,
There will be a limit of Bank guarantee with the bankers based on various conditions .
When we enter a bank guarantee with a party, we pay some charges to Bankers .
We want to track the bank guarantees issued to various parties .It is not really a finance transaction but the information needs to be captured to make sure we does not cross limit.
This is normally used in Indian Context.
Is there any workaround in Oracle Financial to generate transactions and generate report?
Thanks
Jogendra

Hi Jogendra
As per my openion there are two alternatives.
1. Do Forms Personalisation in Invoice workbunch. Eg. Rename one Unused field in Invoice workbunch. Enter the Guarantee amount used for that sepecfiic supplier (Bank is created as a Supplier). Create a new report to add the that field for the specific Bank. Take the report and see regulary or when required and see that the whether it is apporching the Limit
2. Create a DFF for with different bank and their details like Guarantee Limit, invoice guarantee used, etc, enter these field while entering the invoice Create a report and compare it.
Regards
Sunil Kumar

Removing single transactions from roles

I hope this is the right forum... having problems finding a better one.
Here is my question: If I have a role that includes wide open authorizations (like SAP_ALL) what would be a good way to exclude certain transactions, like SE10 for example?
Many thanks in advance.
Edit -- nevermind, found my answer.
Edited by: MMPP on Jan 29, 2010 5:13 PM
Edited by: MMPP on Jan 29, 2010 5:13 PM

I hope this is the right forum... having problems finding a better one.
Here is my question: If I have a role that includes wide open authorizations (like SAP_ALL) what would be a good way to exclude certain transactions, like SE10 for example?
Many thanks in advance.
Edit -- nevermind, found my answer.
Edited by: MMPP on Jan 29, 2010 5:13 PM
Edited by: MMPP on Jan 29, 2010 5:13 PM

How to remove "start transaction" setting

Hi,
this is probably easy to answer, but I couldn't find an answer anywhere...
I have a couple of systems where a transaction runs everytime a user logs on.
I don't have anything set on the menu option "Extras" - "Set start transaction" nor on the SU01 default settings.
Where else can something like this be set?
thanks
Antonio

This is the correct answer to my question:
We can do it globally for all users.
Check Function module exit EXIT_SAPLSUSF_001.
Simply use CALL TRANSACTION 'ZTEST'. inside it and assign it to a project.
Follow below steps:
Goto -> Tcode SMOD ->Enter SUSR0001 -> Click display -> Click Components -> Double click on EXIT_SAPLSUSF_001 -> Double click ZXUSRU01 -> goto change mode -> Enter code CALL TRANSACTION 'ZTEST'. (Your 'Z' transaction) -> Activate.
Now Goto -> Tcode CMOD ->Enter Project name -> Click create ->Enter Short text ->Click Enhancement assignments -> Enter SUSR0001 -> Save -> Click Components -> Click activate.
Log off and login again.
thanks, Divyanshu Srivastava

Removing the entity object commit from transaction handler

Hi,
The business reuirement of the OAFWK page developed by us is as explained below:
The basic functionality is of updating the attributes of items attached to the change order.
The UI components displayed in the page(Item attribute changes region) are built based on the properties of the item attributes as LOV,poplist,textbox etc..
The dynamic VO mapped to these UI components is based on a standard entity object.
User operation:Select any attribute group and click on Go button.The Item attributes of the attribute group are displayed.Enter values in the Item Attributes and click on Apply button of the region.(changes made in the attributes related to the attribute group are committed to the database using
<Root AM>.getTransaction.commit()).
Now we have two such regions in the same page.
On top of the page the item attributes of _{color:#800000}<Item Type X>{color}_ are displayed.
Down the page, the item attributes of {color:#0000ff}<_Item Type Y_>{color} are displayed.
In few special cases i.e for few item attributes, on click of Apply button for {color:#0000ff}_Item Y_{color} , the attributes of {color:#800000}I_tem X_{color} are to be updated by calling a PLSQL API.When Apply button in the Item attributes of _{color:#0000ff}Item Type Y{color}_ is clicked,the execution of controllers is :
1.Controllers of Item attribute changes region of {color:#800000}<Item Type X> {color}The dynamic VO is built for the item attributes of Item Type X
2.Controllers of the Item attribute changes region of {color:#0000ff}Item Type Y{color} The dynamic VO is built for the item attributes of Item Type Y.In the last controller of the hierarchy, the PLSQL API call is included(by invoking the method in AM) to update few attribute values of {color:#800000}Item Type X and finally <Root AM>.getTransaction().commit().
Problem : The updated values by PLSQL API for {color:#800000}_Item Type X_{color} are not reflected in the database but indeed the values entered by user for {color:#800000}_Item Type X_{color} in the top of the page are committed(The Apply button for {color:#800000}_Item Type X_{color} is not clicked).
_>>Please note that the dynamic VOs of both the Item Types are built on the same standard Entity Object_
I am struggling to know the reason why the values updated by PLSQL API are overwrittem by the values in the entity object even though the PLSQL API is called in the last controller of execution.Please let me know if there is any OAFWK constraint.
I tried the approach of removing the commit of the dynamic VO built in the region of {color:#800000}_Item Type X>_ {color}{color:#000000}I fetched the entity implementation of the dynamic VO row and used removeandRetain(),revert().But this approach failed.I am referring to the jdevdoc for the built-in methods.
{color}
Now the requirement is the latest values updated by API (for {color:#800000}_Item Type X_{color}) should be committed in the database but not the values updated by the entity object for {color:#800000}_Item Type X_ {color}{color:#000000}in the item attributes region{color}.
There should a single commit for the entire transaction of the page.
Is there any chance to remove the commit of item attributes of {color:#800000}_Item X_{color} alone from the transaction handler?There are few methods in oracle.jbo.server.EntityImpl class such as doRemoveFromTransactionManager().But these methods are either protected or private.So classes of other packages cannot access them.
So pelase suggest me if there is a workaround for this scenario.
Thanks and Regards,
Kiran
Edited by: Kiran.A on Sep 20, 2008 3:34 AM

Hi Sumit,
Yes I agree on that front that updating the same record through PLSQL and EO is not the right approach.
But the business requirement is as such and we do not have any workaround for this.
Please let me know if there is any way to avoid the EO commit by removing from transaction listener.
Regards,
Kiran

How to remove transaction that was added under Menu - Role Menu

We have roles that we need to remove some transactions.
These transactions were added under Menu - Role Menu and expanded for ex: Logistics and Picked Miro transaction.
When I go to PFCD and check under s_tcode I cannot remove Miro transactions since it's grayed out.
The only way to remove this is to go back to the Menu and do a find on miro and work through the menu until I get to Miro transaction and then delete it.
Is there another way to accomplish this.
Thanks
Joe

This is the intended way a role built from a menu works. What might be the use of an authorization without any corresponding transaction to start it? It is only a risk...
Unless of course you know better or design differently and don't make the effort to adjust SU24, then you can insert manually or cause "changed" authorizations, but PFCG will not look at it from a "your own fault" view and not adjust it or protect it against illogical changes.
To use the discipline of the one approach but keep the flexibility of manual authorizations is not possible for S_TCODE, S_RFC and S_SERVICE objects (the entry points).
Cheers,
Julius
PS:
> Total Questions: 42 (36 unresolved)
Please follow-up on your unresolved questions. There is a limit now of 10 open questions asked since July 2008.

ORA-01591 -- How to remove blocking distributed transaction?

Hi at all,
I've got a big problem! There is a transaction lock on a table and I can't access / update the table. The following error occures: ORA-01591: lock held by in-doubt distributed transaction 140.12.34934.
So, I decided to kill this transaction. But I can't find any transaction with that number. How can I remove this transaction. A restart of the database does not kill this trransaction.
Thanks for you help
Message was edited by:
user573407

ORA-01591 lock held by in-doubt distributed transaction string
Cause: An attempt was made to access resource that is locked by a dead two-phase commit transaction that is in prepared state.
Action: The database administrator should query the PENDING_TRANS$ and related tables, and attempt to repair network connection(s) to coordinator and commit point. If timely repair is not possible, the database administrator should contact the database administrator at the commit point if known or the end user for correct outcome, or use heuristic default if given to issue a heuristic COMMIT or ABORT command to finalize the local portion of the distributed transaction.

PFCG issue - removing transaction codes from menu and not clearing up the authorization tab

I’m using SAP ERP version ECC6 and EHP5 and also we have updated our system with the PSCD FI module.
I’m having the following issue in PFCG transaction code - I have created a new single role by copied other or from scratch and added few transaction codes into the menu. After that, I went in the authorization tab using the "Change Authorization Data" and I felled all the missing information until the role was green out. I generated the role then I totally went out. I come back to the same role that I created earlier and I did removed all the transaction codes from the menu and I did find the following:
- the Authorization tab light didn't change from green to red
- I went into the Authorization tab by "Change Authorization Data" and a part of the objects were still in.
Normally behave should be:
- when we remove one transaction code from the menu the light from Authorization tab should change from green to red. When you empty the menu then the light color should change also, but the authorization tab should be also empty.
Could please give me some idea how to do it next?

Hi Gabriela,
Most of the times standard roles contains manually added authorization objects. When ever you are creating a new role by copying the existing standard role so by default, these objects will come in to new role.
Now, coming to your role. After removing t code from role if nothing has changed in Authorization tab means.
Here are the possible reasons.
1. The t code which you have removed might not have any checked and maintained authorization objects, that's why your Authorization tab still in unchanged.
2. Rememeber, when ever you are adding or removing t code from menu always use expert mode for profile generation option along with "Read old status and merge with new data" Option.
This will bring the all checked and maintained data for each t code.
3. After removing the t codes from menu and if you generate the Authorization tab by using expert mode option still if you find authorization objects means, those are manually added authorization objects that's why those were not removed.
I hope this will give some clue to your issue.
Thanks,
Siva

Stateful SessionBean - force passivation or removal

Is there any way of forcing passivation or removal of stateful session beans
once their idle-timeout-seconds has been exceeded? Alternatively, can a
stateful session bean get notification of a client disconnection?
We have a special requirement for stateful session beans to hold a
transaction open over multiple calls (using bean-managed transactions),
which means keeping a connection open. Therefore, we have a connection as a
(transient) member variable, and when the bean is passivated or removed, the
transaction is rolled back and the connection is closed... OK, so far no
problem. However, during this transaction, the session bean maintains a lock
on part of the database preventing others from interfering with the updates.
A problem arises if the client crashes or is disconnected somehow, as the
session bean still remains active, only becoming eligible for passivation or
removal after it's idle timeout has expired.Unfortunately, even when the
idle timeout expires, the session bean is not passivated or removed, even if
the max number of beans in the cache is exceeded... In fact, there is no
guarantee it will ever be passivated or removed unless the server runs short
of memory.
We would like to be able to force passivation or removal of stateful session
beans whose idle timeout has expired or where the client has disconnected.
Any ideas?
Dave

Thanks for the suggestion Barry, but since we are using a client application
that creates the SSB directly, there's no servlet or intermediate
server-side bean to implement HttpSessionBindingListener. I'll check, but
I'm pretty sure the SSB can't implement it itself. Still, it's food for
thought...
Cheers,
Dave
"Barry Munro" <[email protected]> wrote in message
news:[email protected]..
On 03 Dec 2001, Dave Lorde wrote:
We would like to be able to force passivation or removal of stateful
session beans whose idle timeout has expired or where the client has
disconnected. Any ideas?To remove them when your user session expires you could use
javax.servlet.http.HttpSessionBindingListener so that you are informedwhen
the user's session is unbound from the session. Then you could call the
remove method of your stateful session bean which calls the ejbRemove
method on the SSB.
Barry

How to handle a failed transaction in Syclo Agentry SAP Work Manager 5.3

Hello Experts,
I have a transaction created on work order time entry.
For some reason, when the transactions fails (when clicked on transmit button), the transmit stops as soon as the error is thrown from ECC.
However, this transaction remains on the client and is not deleted.
when a new transaction is created on another object and transmitted, it still retains the previously failed transaction and tried to transmit it again.
Because of this, the transmit stops again and it fails.
Is there anyway to remove a transaction which has failed already? What is the best way to handle such scenario.
Thanks for the help!
Best,
Arihant Kothari
Message was edited by: Michael Appleby

Arihant,
The Error handling within the application / editor does not have a one click type solution to just remove a pending transaction. As Jason mentioned the behavior is to stop when an error occurred so the user can correct and continue. In some cases this may mean removing the transaction through the removal of the associated object from the mobile device (clear option frequently) that when the object is cleared the associated transaction is also deleted allowing the pending transactions behind the current one to proceed.
The editor allows for error handling steps to be defined to execute upon error so that potentially you could log the transaction data off to the side for handling later and then continue processing. This of course requires there to be manual back office involvement monitoring the logged data for resolution and next steps.
--Bill

A question about transaction consistency between multible target tables

Dear community,
My replication is ORACLE 11.2.3.7->ORACLE 11.2.3.7 both running on linux x64 and GG version is 11.2.3.0.
I'm recovering from an error when trail file was moved away while dpump was writing to it.
After moving the file back dpump abended with an error
2013-12-17 11:45:06 ERROR   OGG-01031 There is a problem in network communication, a remote file problem, encryption keys for target and source do
not match (if using ENCRYPT) or an unknown error. (Reply received is Expected 4 bytes, but got 0 bytes, in trail /u01/app/ggate/dirdat/RI002496, seqno 2496,
reading record trailer token at RBA 12999993).
I googled for It and found no suitable solution except for to try "alter extract <dpump>, entrollover".
After rolling over trail file replicat as expected ended with
REPLICAT START 1
2013-12-17 17:56:03 WARNING OGG-01519 Waiting at EOF on input trail file /u01/app/ggate/dirdat/RI002496, which is not marked as complete;
but succeeding trail file /u01/app/ggate/dirdat/RI002497 exists. If ALTER ETROLLOVER has been performed on source extract,
ALTER EXTSEQNO must be performed on each corresponding downstream reader.
So I've issued "alter replicat <repname>, extseqno 2497, extrba 0" but got the following error:
REPLICAT START 2
2013-12-17 18:02:48 WARNING OGG-00869 Aborting BATCHSQL transaction. Detected inconsistent result:
executed 50 operations in batch, resulting in 47 affected rows.
2013-12-17 18:02:48 WARNING OGG-01137 BATCHSQL suspended, continuing in normal mode.
2013-12-17 18:02:48 WARNING OGG-01003 Repositioning to rba 1149 in seqno 2497.
2013-12-17 18:02:48 WARNING OGG-01004 Aborted grouped transaction on 'M.CLIENT_REG', Database error
1403 (OCI Error ORA-01403: no data found, SQL <UPDATE "M"."CLIENT_REG" SET "CLIENT_CODE" =
:a1,"CORE_CODE" = :a2,"CP_CODE" = :a3,"IS_LOCKED" = :a4,"BUY_SUMMA" = :a5,"BUY_CHECK_CNT" =
:a6,"BUY_CHECK_LIST_CNT" = :a7,"BUY_LAST_DATE" = :a8 WHERE "CODE" = :b0>).
2013-12-17 18:02:48 WARNING OGG-01003 Repositioning to rba 1149 in seqno 2497.
2013-12-17 18:02:48 WARNING OGG-01154 SQL error 1 mapping LS.CHECK to M.CHECK OCI Error ORA-00001:
unique constraint (M.CHECK_PK) violated (status = 1). INSERT INTO "M"."CHECK"
("CODE","STATE","IDENT_TYPE","IDENT","CLIENT_REG_CODE","SHOP","BOX","NUM","KIND","KIND_ORDER","DAT","SUMMA","LIST_COUNT","RETURN_SELL_CHECK_CODE","RETURN_SELL_SHOP","RETURN_SELL_BOX","RETURN_SELL_NUM","RETURN_SELL_KIND","INSERTED","UPDATED","REMARKS")
VALUES
(:a0,:a1,:a2,:a3,:a4,:a5,:a6,:a7,:a8,:a9,:a10,:a11,:a12,:a13,:a14,:a15,:a16,:a17,:a18,:a19,:a20).
2013-12-17 18:02:48 WARNING OGG-01003 Repositioning to rba 1149 in seqno 2497.
The report stated the following:
Reading /u01/app/ggate/dirdat/RI002497, current RBA 1149, 0 records
Report at 2013-12-17 18:02:48 (activity since 2013-12-17 18:02:46)
From Table LS.MK_CHECK to LSGG.MK_CHECK:
       #                   inserts:         0
       #                   updates:         0
       #                   deletes:         0
       #                  discards:         1
From Table LS.MK_CHECK to LSGG.TL_MK_CHECK:
       #                   inserts:         0
       #                   updates:         0
       #                   deletes:         0
       #                  discards:         1
At that time I came to the conclusion that using etrollover was not a good idea Nevertheless I had to upload my data to perform consistency check.
My mapping templates are set up as the following:
LS.CHECK->M.CHECK
LS.CHECK->M.TL_CHECK
(such mapping is set up for every table that is replicated).
TL_CHECK is a transaction log, as I name it,
and this peculiar mapping is as the following:
ignoreupdatebefores
map LS.CHECK, target M.CHECK, nohandlecollisions;
ignoreupdatebefores
map LS.CHECK, target M.TL_CHECK ,colmap(USEDEFAULTS,
FILESEQNO = @GETENV ("RECORD", "FILESEQNO"),
FILERBA = @GETENV ("RECORD", "FILERBA"),
COMMIT_TS = @GETENV( "GGHEADER", "COMMITTIMESTAMP" ),
FILEOP = @GETENV ("GGHEADER","OPTYPE"), CSCN = @TOKEN("TKN-CSN"),
RSID = @TOKEN("TKN-RSN"),
OLD_CODE = before.CODE
, OLD_STATE = before.STATE
, OLD_IDENT_TYPE = before.IDENT_TYPE
, OLD_IDENT = before.IDENT
, OLD_CLIENT_REG_CODE = before.CLIENT_REG_CODE
, OLD_SHOP = before.SHOP
, OLD_BOX = before.BOX
, OLD_NUM = before.NUM
, OLD_NUM_VIRT = before.NUM_VIRT
, OLD_KIND = before.KIND
, OLD_KIND_ORDER = before.KIND_ORDER
, OLD_DAT = before.DAT
, OLD_SUMMA = before.SUMMA
, OLD_LIST_COUNT = before.LIST_COUNT
, OLD_RETURN_SELL_CHECK_CODE = before.RETURN_SELL_CHECK_CODE
, OLD_RETURN_SELL_SHOP = before.RETURN_SELL_SHOP
, OLD_RETURN_SELL_BOX = before.RETURN_SELL_BOX
, OLD_RETURN_SELL_NUM = before.RETURN_SELL_NUM
, OLD_RETURN_SELL_KIND = before.RETURN_SELL_KIND
, OLD_INSERTED = before.INSERTED
, OLD_UPDATED = before.UPDATED
, OLD_REMARKS = before.REMARKS), nohandlecollisions, insertallrecords;
As PK violation fired for CHECK, I've changed nohandlecollisions to handlecollisions for LS.CHECK->M.CHECK mapping and restarted an replicat.
To my surprise it ended with the following error:
REPLICAT START 3
2013-12-17 18:05:55 WARNING OGG-00869 Aborting BATCHSQL transaction. Database error 1 (ORA-00001:
unique constraint (M.CHECK_PK) violated).
2013-12-17 18:05:55 WARNING OGG-01137 BATCHSQL suspended, continuing in normal mode.
2013-12-17 18:05:55 WARNING OGG-01003 Repositioning to rba 1149 in seqno 2497.
2013-12-17 18:05:55 WARNING OGG-00869 OCI Error ORA-00001: unique constraint (M.PK_TL_CHECK)
violated (status = 1). INSERT INTO "M"."TL_CHECK"
("FILESEQNO","FILERBA","FILEOP","COMMIT_TS","CSCN","RSID","CODE","STATE","IDENT_TYPE","IDENT","CLIENT_REG_CODE","SHOP","BOX","NUM","KIND","KIND_ORDER","DAT","SUMMA","LIST_COUNT","RETURN_SELL_CHECK_CODE","RETURN_SELL_SHOP","RETURN_SELL_BOX","RETURN_SELL_NUM","RETURN_SELL_KIND","INSERTED","UPDATED","REMARKS")
VALUES
(:a0,:a1,:a2,:a3,:a4,:a5,:a6,:a7,:a8,:a9,:a10,:a11,:a12,:a13,:a14,:a15,:a16,:a17,:a18,:a19,:a20,:a21,:a22,:a23,:a24,:a25,:a26).
2013-12-17 18:05:55 WARNING OGG-01004 Aborted grouped transaction on 'M.TL_CHECK', Database error 1
(OCI Error ORA-00001: unique constraint (M.PK_TL_CHECK) violated (status = 1). INSERT INTO
"M"."TL_CHECK"
("FILESEQNO","FILERBA","FILEOP","COMMIT_TS","CSCN","RSID","CODE","STATE","IDENT_TYPE","IDENT","CLIENT_REG_CODE","SHOP","BOX","NUM","KIND","KIND_ORDER","DAT","SUMMA","LIST_COUNT","RETURN_SELL_CHECK_CODE","RETURN_SELL_SHOP","RETURN_SELL_BOX","RETURN_SELL_NUM","RETURN_SELL_KIND","INSERTED","UPDATED","REMARKS")
VALUES
(:a0,:a1,:a2,:a3,:a4,:a5,:a6,:a7,:a8,:a9,:a10,:a11,:a12,:a13,:a14,:a15,:a16,:a17,:a18,:a19,:a20,:a21,:a22,:a23,:a24,:a25,:a26)).
2013-12-17 18:05:55 WARNING OGG-01003 Repositioning to rba 1149 in seqno 2497.
2013-12-17 18:05:55 WARNING OGG-01154 SQL error 1 mapping LS.CHECK to M.TL_CHECK OCI Error
ORA-00001: unique constraint (M.PK_TL_CHECK) violated (status = 1). INSERT INTO "M"."TL_CHECK"
("FILESEQNO","FILERBA","FILEOP","COMMIT_TS","CSCN","RSID","CODE","STATE","IDENT_TYPE","IDENT","CLIENT_REG_CODE","SHOP","BOX","NUM","KIND","KIND_ORDER","DAT","SUMMA","LIST_COUNT","RETURN_SELL_CHECK_CODE","RETURN_SELL_SHOP","RETURN_SELL_BOX","RETURN_SELL_NUM","RETURN_SELL_KIND","INSERTED","UPDATED","REMARKS")
VALUES
(:a0,:a1,:a2,:a3,:a4,:a5,:a6,:a7,:a8,:a9,:a10,:a11,:a12,:a13,:a14,:a15,:a16,:a17,:a18,:a19,:a20,:a21,:a22,:a23,:a24,:a25,:a26).
2013-12-17 18:05:55 WARNING OGG-01003 Repositioning to rba 1149 in seqno 2497.
I've expected that batchsql will fail cause it does not support handlecollisions, but I really don't understand why any record was inserted into TL_CHECK and caused PK violation, cause I thought that GG guarantees transactional consistency and that any transaction that caused an error in _ANY_ of target tables will be rollbacked for _EVERY_ target table.
TL_CHECK has PK set to (FILESEQNO, FILERBA), plus I have a special column that captures replication run number and it clearly states that a record causing PK violation was inserted during previous run (REPLICAT START 2).
BTW report for the last shows
Reading /u01/app/ggate/dirdat/RI002497, current RBA 1149, 1 records
Report at 2013-12-17 18:05:55 (activity since 2013-12-17 18:05:54)
From Table LS.MK_CHECK to LSGG.MK_CHECK:
       #                   inserts:         0
       #                   updates:         0
       #                   deletes:         0
       #                  discards:         1
From Table LS.MK_CHECK to LSGG.TL_MK_CHECK:
       #                   inserts:         0
       #                   updates:         0
       #                   deletes:         0
       #                  discards:         1
So somebody explain, how could that happen?

Write the query of the existing table in the form of a function with PRAGMA AUTONOMOUS_TRANSACTION.
examples here:
http://www.morganslilbrary.org/library.html

How to remove the complete ALE configuration for a given system

Hello everybody,
Through ALE ,data is transferred between a number of SAP systems and the necessary ALE setups are in place.
Now,a particular SAP system,which used to be a receivor to the central SAP system,is to be retired.
Hence,the associated ALE set up is to be completely removed from the central SAP system.
Is the following sequence correct?If not and I have missed something,please enlighten me with the correct sequence.
1.Removal of the receivor logical system and its assignment to client ,through transaction SALE.
2.Removal of partner profile, through transaction WE20.
3.Removal of RFC destinations,through transaction SM59.
4.Removal of transactional ports for the logical system,through transaction code WE21.
5.Removal of Distribution model between the retiring system and the central SAP system.
(a)Regarding distribution model,I have a question-if the distribution model is maintained such that it contains the linking relationships between the central system and several receivor systems(in addition to the one I wish to remove),then is it possible to remove only the desired linkage and not touch the rest?
(b)Through BD64,I have tried but I am able to delete only the entire distribution model as a whole,while I would like to keep the distribution model and delete just one of the nodes,so as to cut the connection between only central system and the retiring system.
This is so because the other receivor systems are working fine,involving a lot of batchjobs and I am afraid that deleting the distribution model wholly will create unnecessary trouble.
Any help will be appreciated.Thanks
Papri

HI Nicolas,
I chatted with Rev-Trac support earlier today and here is what they have come back to me with.
Assuming the change in question was carried out in the development system. Changes to fields in tables should in most cases be captured in transports. Assuming it was a transportable change then go to the development system and execute transaction SE16 and query Rev-Trac table /RSC/T_MFM_4T filtering by TABLENAME.
On executing the query you should see a list of transports involved with changes to the transport. You can then check to see if there is a recent transport associated with the change - if so then you can find out who created the transport by using standard SAP functionality."
If you find this doesn't help, then please contact your Rev-Trac Administrator who can then log a support request on our support portal at www.xrsc.com
Hope this helps, Rick

How to stop user from using 961 mvt type in MB1C transaction code?

Hi Friends,
We have two companies. Already we have restricted end user for using 961 & 962 mvt type in MB1C transaction code in one company code 1000. Now, we want to restrict end user for using 961 & 962 mvt type in MB1C transaction code in other company code 1200.
I have checked configuration using OMJJ transaction. But, it is there so there may be some different way of control.
Can any body help me?
Regards
Siva

Hi,
To restrict/block the movement type, the steps are:
1. use transaction code OMJJ.
2. Enter the movement type you want to block.[From 961 To 961](do for both961& 962)
3. Select the Second option in the List which appears in the left. (Allowed Transaction).
4. Remove the transaction codes (MB1C)from where you do not want to use that particular movement type& save.
For user specific to block the movement type, pl consult Basis Consultant.
Regards,
Biju K

INV_IFACE=Y 임에도 PICK TRANSACTION이 PENDING에 걸려 있는 경우 해결 방법

제품 : MFG_SE
작성날짜 : 2005-05-06
INV_IFACE=Y 임에도 PICK TRANSACTION이 PENDING에 걸려 있는 경우 해결 방법
========================================================================
PURPOSE
WSH_DELIVERY_DETAILS table의 INV_INTERFACED_FLAG = Y 임에도 불구하고
MTL_MATERIAL_TRANSACTIONS_TEMP table에 Sales Order Pick Transaction이
pending 상태로 남아 있는것을 볼 수 있다.
이런 경우의 해결 방법을 알아본다.
Problem Description
Sales Order Pick transactions이 Pending Transaction table(MMTT)에
pending 상태로 있다.
이런 stuck transaction은 Order Details report(OMSE11i.sql note.133464.1)
에서도 볼 수 있고 Close Period report(INVPeriodCLose115.sql note.206576.
1)에서도 볼 수 있다.
Stuck transactions은 onhand quantity를 reserve 하고 있으며 이 reserve
quantity는 다른 order를 위해서도 ship 되어야 한다.
이 경우,OMSE11i.sql report는 struck transactions은 보여주지만 관련된
move orders는 보여주지 않는다. Transact Move Order 화면에서 관련된
move orders를 조회해 보기 위해 Sales Order Number를 입력해 보기도 하지만
어떤 결과도 나오지 않는다.
OMSE11i.sql report는 또한 Order line은 completed, closed, shipped 되고,
delivery details section(WSH_DELIVERY_DETAILS)의 inventory interface
flag(INI)는 'YES'인 것을 보여준다.
STEPS :
1. Go to Inventory > Pending Transactions screen.
2. Query records in error.
3. See stuck records but no error message.
Workaround
Solution Description
1. Order Details report(OMSE11i)을 검토하여 모든 transactions이 각 line
별 complete 되어 있는지 확인한다.
1) OMSE11i.sql결과가 order lines이 completed, closed, shipped이고
wsh_delivery_details table의 inv interface flag가 'YES'임을 보여주는
지 확인한다.
2) 모든 필요한 history transaction records를 볼 수 있는지 확인한다.
하나의 order line은 mtl_material_transactions table에 세개의 records
를 가지고 있어야 한다.
하나의 record는 warehouse에서 onhand qty를 remove 한 것이고,하나는
staging subinventory에 onhadn qty를 입력하는 것이며, 다른 하나는
staging 창고에서 onhand qty를 issue 하는것으로 이는 product이 고객에
게 shipped 되었고 그로인해 inventory가 감소하는 것을 의미한다.
3) 만약 각각 이러한 transactions이 각 order lines에 따라 존재한다면,
추가적인 move order lines이 duplidates 된 것이므로 이는 cancel 되어
야 한다.
2. 만약 이러한 pending transactions이 remove 되야 한다고 확신한다면,
move orders에 대한 move order line id를 결정한다.
OMSE11i의 pendgind section(MMTT)에서 제공하는 move order line id column
을 이용한다.
3. 각 move order id에 연결된 move order number를 아래의 script를 이용하
여 찾는다. 조회문의 Request_number가 Move Order number이다.
set pages 200
set head on
set lines 200
select
REQUEST_NUMBER,
to_char(toh.last_update_date, 'HH24:MI:SS') "HTimeU",
to_char(toh.creation_date, 'HH24:MI:SS') "HTimeC",
to_char(tol.last_update_date, 'HH24:MI:SS') "LTimeU",
to_char(tol.creation_date, 'HH24:MI:SS') "LTimeC",
tol.organization_id "OrgID",
toh.request_number,
toh.header_id,
tol.LINE_number,
tol.LINE_ID,
tol.INVENTORY_ITEM_ID,
substr(toh.description,1,20) "Descr",
toh.move_order_type,
tol.line_status,
tol.QUANTITY,
tol.QUANTITY_DELIVERED,
tol.QUANTITY_DETAILED
from
mtl_txn_request_headers toh,
mtl_txn_request_lines tol
where tol.line_id IN (&move_order_line_id)
AND toh.header_id = tol.header_id
AND toh.organization_id = tol.organization_id
4. 위에서 찾은 move order(request number) no를 가지고 INV: Move Orders>
Trasnact Move Order 화면으로 이동한다.
문제의 move order를 찾으면 menu 중 'Tools > Cancel the aollocations'를
실행한다. Cancelling the allocation은 pending transaction을 remove 할
것이며,pending transaction이 remove 되었는지 확인한다.
Reference Documents
Note 281155.1

Need sugetion for deleting credit card Transaction (i-Expense)

Hi,
I have few credit card transaction records in i-expense .
these records are not required by customer and he want to delete these data.
is there any API available for deletion of these records or any work arround.
Thanks in Advance,
Ajit

Not aware of any supported methods to delete the Credit Card transactions. Instead you could run the "Credit Card Historical Transactions Management" program with a value for the parameter Process set as "Deactivate Transactions" for a range of posted dates, for a specific card number. This will remove the transactions from the available list of transactions for the user

Is remove() Guaranteed Transactional?

Similar Messages

Maybe you are looking for