CLarification about Obsolete Transactions

Hi,
We are Upgrading 4.6C to ERP2005 for our client. The client wants to move away from Obsolete transactions which they are currently using... But the question is What is an obsolete transaction for a higher version?
1. The transactions which doesnt appear in the SAP area tree menu (or)
2. The transaction code which doent open in command box and gives an message suggesting an alternative/ new transaction (or)
3. The transaction codes for which a new Enjoy transaction exists
Please clarify which are all the points applicable for the definition of an Obsolete transaction according to SAP. Is there anything like that ' SAP doent Provide support for obsolete transaction' and if so is there any list of those transactions in form of a SAP note or otherwise??
Regards,
Kathir

Intelligroup has a tool named <a href="http://www.intelligroup.com/ig_ser_tools_uptimizer.html">Uptimizer</a> that helps in listing the obsolete and their corresponding new transactions and much more relavant data with reference to such transactions.
There is nothing like SAP does not support the old t-code or so. All it provides is that the new ones are better. As long as the old t-codes are still available you may still use them. SAP's support pertains to the whole Release and not at transaction level.

Similar Messages

Clarification about Database_Buffer_cache workings

Hi All,
Clarification about Database_Buffer_cache workings:(This statement from my course material)
*1.The information read from disk is read a block at a time,not a row at a time,because a database block*
is the smallest addressable storage space on disk.
Before answering, my please check whether my above statement is correct or not,becoz i get this from My course material.
If i am querying ,
select * from emp;
Whether server_process bring the whole block belongs to EMP table right or it just bring the table itself?
Thank you,
Regards,
DB
Edited by: DB on May 30, 2013 3:19 PM
Edited by: DB on May 30, 2013 4:35 PM

Both happens, the LGWR may call the DBWR to write dirty blocks from the buffer cache to disk. Dirty in this context means, that the blocks in the buffer cache have been modified and not yet written to disk, i.e. their content differs from the on disk image. Conversely the DBWR can also call LGWR to write redo records from the redo log buffers (in memory) to the redo log files on disk.
To understand why both is possible, you need to understand the mechanics how Oracle does recovery, in particular REDO and UNDO and how they play together. The excellent book "Oracle Core" from Jonathan Lewis describes this in detail.
I'll try to sketch each of the two cases. I am aware that this is only an overview which leaves out many details. For a complete description please look at the various Oracle books and documentation that cover this topic.
1. LGWR posts DBWR to write blocks to disk
As you probably know, any modifications done by DML (which modify data blocks) are recorded in the redo. In case of recovery this redo can be used to bring the data blocks to the last committed stated before failure by re-applying modifications that are recorded in the redo. Redo is written into redo log files and the redo log files are used in a round robin fashion. As the log files are used in a round robin fashion, old redo data is overwritten at some point in time - thus the corresponding redo records are not longer available in a recovery scenario (they may be in the archived redo logs, which may however not exist if your database runs in NOARCHIVELOG mode and even if your database runs in ARCHIVELOG mode, the archived redo log files may not be accessible to the instance without manual intervention by the DBA).
So before overwriting a redo log file, the Oracle instance must ensure, that the redo records being overwritten will not be used in a potential instance recovery (which the instance is supposed to do automatically, without any action by the DBA, after instance failure, e.g. due to a power outage). The way to ensure this is to have the DBWR write all modifications to disk that are protected by the redo records being overwritten (i.e. all data blocks where the first modification that has not yet been written to disk is older than a certain time) - this is called a "Thread checkpoint".
2. DBWR posts LGWR to write redo records to disk
Oracle uses a write ahead protocol (see http://en.wikipedia.org/wiki/Write-ahead_logging and Write Ahead Logging.... This means, that for any modification the corresponding redo records must been written to disk before the actual modification to the data blocks is written to disk (into the data files). The purpose of this I believe is, to ensure that for any data block modification that makes it to disk, the corresponding UNDO information can be restored (from redo) in case of recovery, in order to reverse uncommitted changes in a recovery scenario.
Before writing a data block to disk, the DBWR must thus make sure, that all redo for modifications affecting this block has already been written to disk by the LGWR. If this is not the case, the DBWR will post the LGWR and only write the data block to the datafile once the redo has been written to the redo log file by LGWR.

Peter: A question about XA transactions across weblogic servers

Peter,
          I just read your article about "javax.transaction.HeuristicMixedException"
          problem on WDJ.
          In the article, you said this case applies to WLS 6.1.
          I'd like to know does this applies to WLS 7.0?
          If not, what is the mechanism in WLS7.0 to cope with such problem?
          Thanks,
          William


William,
          The same arguments that I ran through in the article apply to WLS 7. The
          solution is diferent, however since WLS 7 has no "system" user per se.
          Take a look at http://edocs.bea.com/wls/docs70/adminguide/managetx.html#1050458
          for the description of what you need to configure to get cross domain
          transactions with WLS 7.0
          Regards,
          Peter.
          william lee wrote:
          > Peter,
          >
          > I just read your article about "javax.transaction.HeuristicMixedException"
          > problem on WDJ.
          > In the article, you said this case applies to WLS 6.1.
          >
          > I'd like to know does this applies to WLS 7.0?
          >
          > If not, what is the mechanism in WLS7.0 to cope with such problem?
          >
          > Thanks,
          >
          > William
          >
          >
          >

My apple ID was hacked and a game by GodGame Inc was bought and installed. When I try to report a problem about this transaction, the link automatically sends me to the apple store support. The application is bugged. Please help.

My apple ID was hacked and a game by GodGame Inc was bought and installed. When I try to report a problem about this transaction, the link automatically sends me to the apple store support. The application is bugged. Please help.

thanks for your response roaminggnome. I changed my password immediately after it happened and I have contacted i tunes to let them know of this dillemma.
The I-tunes credit was a promotional thing by Apple to buy their laptop. So I didn't pay for the i-tunes credit in the first place. Do you think my bank will be able to reinburse Itunes credit then? I will ask support when they get back to me.

Documentation about the transactions

Hello,
I'm looking for documentation about the transactions
CG3Y or CG3Z. My problem is that it doesn't update
existing files.
Thanx a lot

hi
Both CG3Y and CG3Z transactions are a part of EH&S.
CG3Y = EHS: Download appl. to frontend
Source file on application server Path of the file on the applicationserver
Target file on front end Path of the file on the frontend server (PC)
Transfer format for data Download the file as text (ASC) or in a binaryformat (BIN)
Overwrite file Overwrite the target file if it already exist (withoutprompting)
To start the download: <SHIFT-F1> (left button)
To cancel: <F12> (right button, red X)
CG3Z = EHS: Upload from frontend to appl.
Source file on front end Path of the file on the frontend server (PC)
Target file on application server Path of the file on the applicationserver
Transfer format for data Download the file as text (ASC) or in a binaryformat (BIN)
Overwrite file Overwrite the target file if it already exist (withoutprompting)
To start the upload: <SHIFT-F2> (left button)
To cancel: <F12> (right button, red X)
hope it willl help you
regards
sreelatha gullapalli

How to find out obsolete transaction codes?

Hi,
Is there any way we can find the obsolete transaction codes in a system.
Thank you.
Regards,
Soumya

You can try using these tables.
PRGN_CORR2
RODIR.

Obsolete transaction codes in SAP 4.7 and above

Hi,
Need your assistant here as I need to know the full list of obsolete transaction codes in SAP 4.7 above which mean what are the transaction codes not in use anymore in ECC.
It could be great if can point me to the relevant URL. Thanks

Please check the table PRGN_CORR2 which gives the list of transactions that were changed from different versions from 3.1G to 4.70 and also above till ECC 6.0.
Please also refer to the Oss Note - 991377 for the above table which has a text file with some more transactions. These transactions are missed out in the above table.
Hope this helps you.

Excellent resources about EJB Transactions

Is there any good (better, excellent) web resource (or book) about EJB Transactions, covering topics like
- Flat Transactions vs. Nested Transaction
- Using EJB EntityBeans & Hibernate together: pay attention to Transaction Isolation
- Transaction Isolation examples, especially when having suspended transactions?
Thank you for any hint.
Michael

Nothing's better than Google.
Rich

Some Quick clarification about 2012 and always on Availability groups

Hi guys, just need some clarification about always on.
I've got plenty of experience with normal SQL Clusters, but just need some clarification around always on availability groups.
I presume with AG, you setup a listener and this becomes your point of connection, IE this is what you use in the you connection string for you applications, so can I use this when I am setting up a new application, and will this automatically make the Database
that's created by the APP, Highly available. ? or do you still have to add it to the AG afterwards. ?
I have also read that you can still point to the installed SQL instance, and you don't need to use the AG group listener, but how does this make your DB HA ? how does the failover work.
I also presume you don't need to use any roles under the MSC anymore.
Kind regards
Mark.G

Hi Mark
I presume with AG, you setup a listener and this becomes your point of connection
That's right, the listener is a virtual network name and you can use this to connect to the primary or secondary replica. Your connections will go in against the primary unless you're using
read-only routing.
so can I use this when I am setting up a new application, and will this automatically make the Database that's created by the APP, Highly available
The first thing you'll have to do is set up the availability group (AG). You can then associate a listener to the AG. I know you're familiar with failover clustering but the mechanics of this are much closer to database mirroring. For every database that's
part of the AG you'll have at least one secondary replica, it's possible to automatically failover to this if you're in synchronous mode.
I have also read that you can still point to the installed SQL instance, and you don't need to use the AG group listener, but how does this make your DB HA ? how does the failover work.
Yes you can do, but from an application perspective you should only do this for databases that are not part of an AG. If you connect to the instance directly and you have a failover your app will no be able to connect to the database (on the assumption your
secondary isn't read-only). App connections should always be via the Virtual Network Name.
I also presume you don't need to use any roles under the MSC anymore.
Not sure I understand this? Do you mean will roles be available in cluster manager? Each AG group will have a role but failover is now controlled through the SQL Server rather than the cluster manager.

Clarification about plant and terms of payment In Master Data:

Hello Gurus,
I have a doubt as follows:
1) In Material master (MM01) we are maintaining Plant as two types.
     a) Plant at organisation leve pop up at the begining
     b) Delivering plant at Sales organisation 1.
So, is there any difference between plant and delivering plant or are they different objects ?
2) Terms of payment in Customer master (XD01)
     a) we maintain Terms of payment customer master at company code level in "Payment transaction"
     b) we also maintain Terms of payment in customer master at sales area data in "Billing Documents" tab
Now Why do we need to maintain at these to levels.
FYI: I have also tried to maintain two different Terms of payment and without any hesitation the system accepts, why ?
What is the significance of it.
Please clarify the above.
Thanks,
Venky.

Hello Venky,
1. Material / Plant
A Material is always stored in a Plant & there would be various parameters to be entered for that particular Plant. E.g. Storage Bin, Picking Area, Negative Stocks allowed in Pant, GR Processing time, etc..
Now the same Material may or may not be sold from the same plant, or even if it is sold from the same plant, there would be different Sales parameters for each combination Sales Organisation & Plant. There Sales Organisation specific parameters are entered in Sales Organisation/PLant view. Tax classification Data, Cash Discount indicator, Sales Unit, Delivering Plant, Division, Minimum Order & Minimum Delivery quantity.
2. Payment Terms
The Payment Terms entered in Billing tab in Sales Area data is copied into Sales order & Invoice.
The Payment Terms in Company Code data are used by FI department when posting direct payment (without reference to Sales Document). e.g. to Offer Cash Discount for paying in advance.
Hope this clarifies,
Thanks,
Jignesh Mehta

Clarification about parameters to be changed for max no of 100 conv excd

Hi,
In our system we had received the error:
Connect to SAP gateway failed
Connect_PM TYPE=B MSHOST=xxxxxxxxxxxxxx GROUP=PUBLIC R3NAME=xxx MSSERV=sapmsXXX PCS=1
LOCATION CPIC (TCP/IP) on local host
ERROR max no of 100 conversations exceeded
due to which some users were unable to work in the system.
The threads that i have found while searching on the topic have suggested changing the parameter CPIC_MAX_CONV=500 (or greater) as per the note 314530.
And as mentioned in the SAP note 316877:
" Reduce ~timeout on the ITS machine to enforce the automatic termination of unused sessions."
Now in SMGW i can see the "Active Connections" (first page of the transaction) and also the drop down option "logged on clients" which gives another list.
I am now trying to understand which timeout parameter controls which list.
Most of the entries in the Active connections list are from the TP jlaunch (and seem to be coming from the java stack of the same system). And most of the entries in the Logged on clients list are from the TP SAPSLDAPI.
I need to know which timeout parameter (as per note 316877) needs to be changed for the problem being faced.
Or have i misunderstood this ~timeout parameter and it should be set in Windows environment similar to the CPIC_MAX_CONV parameter ?
Regards,
Rohan.

Hi,
Thanks for your responses.
I will be changing the CPIC_MAX_CONV parameter.
But I would still like to clarify about the other parameter : "~Timeout"
and be prepared to take action on this as well.
As per the (conflicting) information I have so far this seems to be some parameter that is to be maintained in each individual service in SICF ?
Or do we have any synonymous itsp* or gw* parameter which I can set for the timeout?
Regards,
Rohan.

Obsolete Transactions in ECC 6.0

Dear All,
How to find what are the Transactions are obsolete in ECC 6.0 ?
Note:PRGN_CORR2 Table doesn't contains all Transaction Details. and RODIR table contains only obsolete Function Module names.
Thanks in Advance.
Kanagaraja L

Hi,
check here
https://wiki.sdn.sap.com/wiki/display/ERP6/TransactionsChangedinECC6.0
OR
check release notes for ERP 6 at http://service.sap.com/releasenotes.
Regards,
Amit

Urgent: About Obsolete ABAP statements in Netweaver 4.0?

Can any body please help us about the obsolete ABAP statements in Netweaver 4.0 corresponding to SAP 4.6?

Hi,
Pls read first the rules of engagement.
Anyway, open an editor and choose Utilities->Help on->New features in ABAP.
Or check notes like
367676 and 689951
Eddy

Question about VF03 transaction / billing document

on VF03 transaction, does Billing document number need to be always invoice number?
Please clarify.
Thanks,
Krishen

In most scenarios yes.
You create a billing document and it generates a invoice number. You can also say billing invoice number.
Hope you are taking about the billing & invoice in your system. The invoice number in the bill from your vendor will not be found in VF03 in your system.
-Vishal

About nace transaction

explain me about nace.give me the steps for modifying existing form using subroutines with syntax.plz.

Hi
NACE is the transaction code to track the print program and forms.
the procedure for this is:
NACE->SELECT THE RELEVANT APPLICATION (SUPPOSE V1 FOR SALES)->OUTPUT TYPES->SELECT THE OUTPUT TYPE RELATED TO APPLICATION->.->PROCESSING ROUTINES->GIVE THE MEDIUM,PRINT PROGRAM AND FORM NAME AND FORM ROUTINES NAME(IN CASE IF IT IS THERE).SAVE AND TRANSFORT
NOW GOTO THE RELATED TRANSACTION CODE
IF U WANT TO CONFIGURE THE OUTPUT TYPE
FOLLOW THE PROCEDURE
Ex: SPRO--> sales and Distribution --> basic Functions --> output control --> output determination --> output determination using condition technique --> maintain output type determination for billing documents --> maintain output types(this is how functional peope does).
form routines:
FORM .. ENDFORM is used when retrieved data
needs to sent back to print program.
In SAPscript:
PERFORM < routine_name> in <report_name>
            USING &var1&
        CHANGING &var2&.
ENDPERFORM.
In Report:
FORM < routine_name> in_tab type ITCSY
                            out_tab type ITCSY
READ TABLE in_tab WITH KEY NAME = var1.
{Data Selection based on above value. It returns ret_value.}
READ TABLE out_tab WITH KEY name = var2.
            out_tab-value = ret_value.
            MODIFY out_tab.
ENDFORM.
reward points ifuseful..
Thanks,
Usha

CLarification about Obsolete Transactions

Similar Messages

Maybe you are looking for