Hi Harry,
I don't think this is possible to move only one entry, below screen shot see (*) key value field , Its not editable, if that is editable we can mentions particular BF and we can move particular BF. SAP not allowing to do edit because there may be dependencies and conflicts will come . *(star) means will move all BFs from this to SFW_ACTIVE_B2 to target system.
Thanks
Siva
Hi Siva,
Thanks again for quick response.
I compared table SFW_ACTIVE_B2 in Dev, Test and PROD environment.
Found that table SFW_ACTIVE_B2 in Dev has one extra entry which I activated today.
Now I am confident that I am not going to export any other BF.
Just a quick last question: What if user ask to activate BF in Dev and then changes his mind and dont export it to TEST/PROD? I think BASIS person should never activate BF if that BF is not going to PROD, What do you think?
Thanks,
Harry
Hello
Activating a business function is not just updating an entry in the SFW_ACTIVE_B2 table. If you want to be sure what the transport request contains then check the transport request after activating the business functions in the development system.
Switching on Business Functions (SAP Library - Switch Framework)
Regards
RB
Hi
I already have an ECC system connected to my BI system in RSA1.
But now i want to connect one more ECC system to my BI system
When i go in RSA1 --> source system -->SAP-->give the RFC and user details and then try to create a connection it gives an error that source system already exist.
I checked with my BI resource and he conformed that we can have more than one ECC system connected to BI system
Can someone let me know how to do that
Thanks
Tushar
Hi Alex,
In table RSSOURSYSTEM I have a different system source sysid assigned to 2 ECC systems.
I am trying to add source system UG1CLNT200 , but when i click on create and provide details it says t error "souce system already exist"
Also when i click on RSA1 source system i do not see UG1CLNT200 there
Any clue why ?
Thanks
Tushar
I believe this is due to the fact that there is an entry called UG1CLNT200 present in the table RSSOURSYSTEM which is preventing you from creating the source system called UG1CLNT200 in Tx RSA1. I would try removing the entry called UG1CLNT200 from the table RSSOURSYSTEM using the view V_RSSOURSYSTEM in Tx SM30 and see if that helps.
Tx SM30 - V_RSSOURSYSTEM
Also check the tips given in the SAP note 1850890 - Source System ID not found
Regards
RB
Thanks RB,
I looked in to Transport request and below are the screenshots for your reference:
clicked on the request to see more details:
double clicked to see table names and values:
clicked on the 1st entry to see further:
clicked on 2nd entry to see further:
Transport does not list newly activated BF. It list you these table entries only.
I went to 2nd table and found new FB with activation date of today along with other activated FB with past date. So it means everytime you export BF in to transport it always export all active BF's.
Let me know your thought on this.
Thanks,
Harry
Hi Tushar,
You have to remove the entry from RSSOURSYSTEM and then retry the steps.
Follow the below sap note and link
187479 - Assigning several source systems to the same ID
http://joeysbasisblog.blogspot.com/2013/01/connecting-two-bw-systems-to-same-ecc.html
With Regards
Ashutosh Chaturvedi
Hello Harry
There must be a reason why there are two tables (SFW_ACTIVE_B1 and SFW_ACTIVE_B2) involved in the transport request and most probably this could be due to the dependency in the ABAP objects. In that case the Transport functionality is working as designed. So the answer to your requirement is NO unless you perform manual update of tables involved. In that you can expect inconsistency in the system and also the whether you will achieve the expected result is another thing.
Regards
RB
Hi Aleks
When you create the connection from BitTalk to SAP, you will connect with an ID of some sort. That ID will register in the SAP Gateway (transaction SMGW). You need to create an RFC with the ProgramID as the ID in the gateway. All that is is a handle against which the connection is registered. Then you can test the RFC connectionfrom SAP to BizTalk. Once the systems are connected at a technical level, then you can look at sending the info from BizTalk.
Regards,
Graham
Hi,
You really want to be raising this question in the Security and Authorisation community.
Regards,
Graham
Yes that's right.
Alesks, you should register a Program ID in the gateway, following the indicated note and use the same Program ID to create the RFC.
BR,
Àlex
As dvradm user perform
> tnsping DVR
and attach output t message.
Hi
I thing SPRO you can do either display only or full access. for this you can create the Z role and assign to the user
BR
SS
Dheen,
According to the PAM, yes, you can upgrade directly from Solution Manager 7.0 to Solution Manager 7.1. Just check that your operating system and database version are supported for SolMan 7.1 before you start (http://service.sap.com/pam).
As Madasamy says, the upgrade guide will walk you through all the steps, and it will also list all the most important Notes to consider before you start your project. You can find the upgrade guide at http://service.sap.com/instguides -> SAP Components -> SAP Solution Manager -> Release 7.1 -> 5 Upgrade -> Upgrade Guide SAP Solution Manager 7.1 SR1. Also be sure to follow the link below that one for Update of SAP Systems Using Software Update Manager -> Update of SAP Systems Using Software Update Manager (ABAP + Java Systems) and then select for your operating system and database. You will use both of these guides in tandem.
If you don't yet have a DEV Solution Manager system, then I recommend you start by creating one as a copy of your productive Solution Manager, and then perform the upgrade in that system first, same as you would for your other landscape systems.
As for the question of upgrade vs fresh install, that's beyond the scope of this thread, and is not a simple answer that can be given without considering much more about your scenario. While much has changed about LMDB vs SMSY, etc, in SolMan 7.1, and a fresh install can seem very tempting, that will not be an option for you if you currently use other functions in SolMan such as Incident Management, etc. It also may not be an option if your SLD is integrated with Solution Manager and needs to remain available for productive usage of Portal applications like ESS/MSS.
The upgrade does work, but there will doubtless be some cleanup of the system landscape data afterwards. The System Preparation and Basic Configuration workcenter tools inside Solution Manager (after you upgrade), as well as the Managed System Configuration tool, will help you with this.
Good luck!
Best regards,
Matt
What is the patch level of the kernel you are using ?
Try using a different patch level of the kernel.
Regards
RB
Hi everyone,
We are upgradeing from BW 7.01 to BW 7.4 and facing a very long runtime in the phase PARMVNT_SHD (actual phase PARMVNT_TRANS). It has been running for 3 days!
In this phase nametab activations are taking place. The upgrade is not stuck, but there are many objects to process from table DDXTT. I have checked the following:
1. We are using the latest SUM tool SUM 1.0 sp10
2. We are using the latest TP and R3trans
3. Our database is on Oracle 11g, latest patches applied and parameters are set based on SAP note recommendations
4. The hardware is HPUX with 8 cpus and plenty of memory.
It is just very odd that this phase takes so long and that there are so many objects to process.
Please help if you have any information or suggestions.
Many thanks!
Imran
Hello,
Since these templates are not listed in the template list (PFCG T-Code). is there any way to add them manually or note to enable these templates.
Cheers,
F