Tcode So01

[Aron Eugine]

InECC 6.0 I found that when users have a mail in their SAP mail inbox and try to login to the SAP, a popup comes informing them regarding a new mail arrival in their SAP inbox and when they click OK, it calls transaction code SO01, those user who do not have the tcode SO01 would receive an authorization error. We did not have this problem with SAP r/3 4.7.

Both Tcode trigger to Business work place of the User or SAP inbox, and giving authorisation for SO01 and SBWP will not effect to any thing , you needs to all this new tcode in to their authorisation matrix.

Many transactions have been deprecated in SAP S/4HANA from ERP6.0. In fact, there are too many obsolete transactions in S4HANA to list in this article. One of the frustrations is that SAP does not really provide an easy way of identifying these obsolete tcodes.

The main transactions which are obsolete in S/4HANA around the general settings area are those related to customers and vendors and other partners. These have all been deprecated in favor of the SAP business partner concept. As a result, a whole host of transactions have been rendered obsolete and pointed directly at the new SAP transaction BP.

If you are undergoing a conversion from ERP6.0 to S/4HANA, then I assume you have access to your originating ERP6.0 system, or you have access to the below information from your basis team (if not, you can sign up for our live SAP ECC 6 access here).

There are other ways of finding this information, but they are more long-winded. The simplest way is to read the SAP Simplification list for the latest version of S/4HANA. Here is a link to the 1909 simplification list.

We've done the work for you already and compiled a list of all new S4HANA transaction codes in an Excel list. You can simply download the entire spreadsheet with all the new transaction codes that are includes in S/4 here:

I am having 2 systems - SAP Solution Manager 7.1 and SAP NetWeaver 7.3 and the corresponding RFC connections betweeen them.

I am trying to configure the BW based reporting over the test management of the SolMan system using the solman_workcenter t-code.Idea is that the external BW system should be used for reporting.

The RFC connection from Solution Manager to BW seems to be fine. But the field, where the RFC Connection from BW to Solution Manager should be entered, remained empty and is now shown as inactive.

That's why an error: "Cannot read the destination from the BI to the Solution Manager" occurs.

I have to apply abap support packs, and want to calculate the support packs queue can anyone pleas guide me step by step procedure to calculate the queue using solman and after that how to proceed further to apply support packs.

I have configured HTTP and SMTP in SAP Solution Manager 4.0 and it is working properly. However, when I created an entry for HTTPS with a different port which is not in use, and tried to activate HTTPS, got error: Operation failed (rc=1) Message no. ICM006. Plz help in this regards. We are using integrated ITS 700 version.

from which client I have to configure solman_setup for MOPZ purpose?As I have tried from 001 and 100 client and the user as ddic and solman_admin as well,While I run the tcode solman_setup and press the edit button then the browser is getting hanged.I cannot go ahead after this.I have attached the screenshot for the same.Can anyone help me out for the same?It is really urgent.

For upgrading to Solution manager 7.1 SPS8, I didn't find any useful information in upgrade guide i.e. regarding which upgrade DVDs I need to download. Only information which I found useful is to use SUM instead of SOLMANUP.

Would the settings under "Approval Settings" sufficient to receive the email notofocation for Approval Procedure? I performed the activities and what I see is workflow/email coming to my SAP Inbox (So01 txn code) but not to my email inbox (outlook). When I see in SCOT, no email is generated for Approval workflow. What could be the reason behind it? Any inputs are appreciated.

There is instruction from SAP that SAP Solution Manager 7.0, Ehp1 will come to end of mainstream maintenance by 31st Dec 2013, and there is no extended maintenance for this product, and advised to either upgrade or go in for a fresh installation of Solution Manager 7.1.

My D.B is on oracle 10g, gurus please suggest me how to proceed, which approach would be more easier upgrade or fresh installation, if i upgrade i need to perform D.B upgrade so i think i should go for fresh installation. As i am new to SAP please guide me the easiest approach...

I read the instruction I downloaded from market. I also read it on internet. Both of sites say I have to run SAPinst to install related products before I move to next step, which install entire product, Solution Manager 7.1. However, I didn't see this executable file. I am wondering where I can find it and then install it. I had already followed the steps I found on internet, but I didn't discover it in DVD even the file I downloaded from SAP market.

Currently on Step 7 Configure Automatically on SOLMAN_SETUP on a Java Based System (Biller Direct for UCES) when I'm running into an error on the Automatic Activity Byte Code Adapter Installation for the Wily Introscope setup.

The script is returning an error: IS Agent Set up on node faysapbdx Remote Operation failed - the script is successful in Logical Host name handling and then Introscope Agent Extraction (SMDAgent and wilyByecodeAgent are installed) and then is successful in Updating Introscope Agent Profiles

But the script then fails and this is the error message: Operation Failed - BDX - 14031850: - java.lang.NullPointerException: while trying to invoke the method java.util.Properties.getProperty(java.lang.String) of an object loaded from local variable 'vmProperties'

When I go to Introscope Agent in Root Cause Analysis I see that the SMD Agent is Running (although the IS Agent State on the dashboard is set to Unknown). DAA is running on both the Biller Direct server and the Solutioin Manager server.

Not much luck in getting any hits on searching the error message and I found nothing in SAP Notes to suggest this is a known problem. I did find SAP Note 797147 - Wily Introscope Installation for SAP Customers and tried deploying the ISAGENT24_*.SCA onto the managed system and it did deploy successfully but after re-running the step I still received the same error in Solution Manager.

3a8082e126