Upgrade to SRM 5.0- Downtime on production system

Hi,
We are planning an upgrade to SRM 5.0. Currently we areon SRM 3.0 (EBP4.0), classic scenario.
I dont have much idea about upgrades. I went thro the upgrade guide for SRM. I can see that there are 2 main strategies for upgrade downtime minimized and resource minimized.
Can anyone give me an estimate or way to arrive at the downtime requirement for the production system if I use any of the strategies? is there a way to arrive at an approximate downtime which should be planned?
We currently have only the scenario self service procurement with classic scenario. All other follow on activities like GR, Invoicing etc. happens in R/3. SRM only stores shoppinng carts. On an average there are about 7000-8000SC's created in a month.
Thanks,
Srivatsan

Hello Srivatsan,
The differences between downtime minimized and the resource minimized is the first shutdown of the production system. For downtime minimized strategy it's the phase MODPROF_TRANS. And for resource minimized, it's either EU_import, or the START_SHDI_FIRST. But you can restart the soruce system(but not in production mode) after that until MODPROF_TRANS.
The downtime actually is depend on the hardware and the size of the database. It has nothign to do with the application. It's doing the table conversion and changing and keep them consistent.
To be safe, I would recommend you to plan at least a weekend for the downtime (after MODPROF_TRANS) if the database is not too big.
Regards,
Joe

Similar Messages

Best practice to reduce downtime for fulllaod in Production system

Hi Guys ,
we have options like "Initialize without data transfer ", Initialization with data transfer"
To reduce downtime of production system for load setup tables , first I will trigger info package for Initialization without data transfer so that pointer will be set on table , from that point onwards any record added as delta record , I will trigger Info package for Delta , to get delta records in BW , once delta successful, I will trigger info package for the repair full request to get all historical data into setup tables , so that downtime of production system will be reduced.
Please let me know your thoughts and correct me if I am wrong .
Please let me know about "Early delta Initialization" option .
Kind regards.
hari

Hi,
You got some wrong information.
Info pack - just loads data from setup tables to PSA only.
Setup tables - need to fill by manual by using related t codes.
Assuming as your using LO Data source.
In this case source system lock is mandatory. other wise you need to go with early delta init option.
Early delta init - its useful to load data into bw without down time at source.
Means at same time it set delta pointer and will load into as your settings(init with or without).
if source system not able lock as per client needs then better to go with early delta init options.
Thanks

Performing SPAU in Production System

Dear Team,
We are in the process of upgrading our Production system from EHP3 to EHP7.
We upgraded our Quality system with SPDD and SPAU transport requests from Development system and it finished successfully.
But after upgrading our Kernel in Production system and before performing the EHP7 upgrade, we applied two SAP notes in Production system, these notes were transported from our temporary development(un-upgraded) system(parallel landscape).
While performing the EHP upgrade in Production system, SUM has prompted us the below message
“Decide about Incomplete Modification Transport”
CAUTION: The program has found the transport "MEDK906662"(our SPAU transport) for SPAU but it does not contain all objects which need adjustment.
When we checked the log file it show that two objects are missing in the SPAU transport.We suspect these are the SAP Notes which we applied after kernel upgrade and are missing in SPAU transport request.
Please let me know how we can correct this issue in Production system. I know that SPAU will appear in Production system, but will the system allow me to re-apply/reset the SAP note in SPAU as this system will be un-modifiable.
Regards
Imran

SE06.
System Change. Global setting "modifiable". Componenents "modifiable". Namespaces "modifiable".
Client setting-> select client -> Automatic recording of changes, changes to repository and cross-client customising allowed, protection level 0.
If that doesn't work, give yourself SAPALL and try again.
If that doesn't work, contact SAP because something is messed up. I've successfully applied notes in P systems during upgrade. Including ones that modify SAP_APPL.

SRM 5.5 upgrade to SRM 7.0 with MDM

Hi,
Pl consider the following scenario and give your views.
Our client has SRM 5.5 running with SRM MDM 2.0 in their landscape. Now they wish to upgrade to SRM 7.0 without upgrading MDM.(We are upgrading through the parallel landscape).
So during the upgrade phase, we wish to connect SRM 5.5 and SRM 7.0 both to their existing MDM system for testing purpose. Is this possible?
PS : Parallel landscape is existing DEV environment will be copied and then upgrade the copied environment. We plan to copy only SRM Server and want to continue using the existing MDM, PI, Portal and TREX setup.
Regards

Hi,
No issue for testing purpose in test landscape. It is not production usage and production system.
Regards,
Masa

Help needed in SRM upgrade to SRM server 5.0

Experts,
My client is on EBP 2.0 and going for an upgrade to SRM Server 5.0 and working on classic scenario and keeping the backend as 4.6C for this phase of the project. Please share any experiences on how to go about the upgrade, any questionaries, methodologies also I would like to know the major differences between EBP 2.0 and SRM 5.0.
Thanks in Advance,
Surya

HI Surya
Pls go through following sites
http://service.sap.com/instguides (install and upgrade guides)
http://service.sap.com/ibc-srm (config guides - upto SRM 4.0)
http://service.sap.com/srm (general info)
The installation guides and Config guides will give you perfect steps to follow for installation and configuration.
regards,
Nimish Sheth

Pictures not appearing in after upgrade to SRM-MDM Catalog 3.0 SP7 Patch4

Hello,
Due to some issues in Advanced search we performed the service pack upgrade from SRM-MDM Catalog 3.0 SP5 (with MDM 7.1.03.72) to SRM-MDM Catalog 3.0 SP7 Patch4 ( MDM 7.1.04.146). With this new SP, the Pictures are not appearing anymore under the Hyperlink section anwhere in Catalog browser( Compare, Context view, Item details). With earlier SP pictures were appearing perfectly.
We have done like this:( refer earlier thread - Re: SRM MDM Catalog 3.0 Image display) thanks Sudhanshu, Jitesh and Mandeep for suggesting that solution!
Using the hyperlink field
type : rendered
MIME type : image type i.e. .jpg
URL : web URL
We had gone for this option because we dont want to store impages in MDM, and this worked perfoectly until new SP upgrade.
Any clues?
Thanks
Pravin

Hi Bala,
Nothing appears under the Hyperlink section in Catalog browser, though a valid link exists in Data Manager under Hyperlink as type-Rendered, MIME type as JPG and a valid URL.
I have searched Service Market place for this fix of this issue and found that SAP has improved the technology ( from Object Cache to Blob Cache) to display pictures/hyperlinks from SRM-MDM Catalog 3.0 SP06 and MDM 7.1SP04 onwards. We were on SRM-MDM Catalog 3.0 SP05 and MDM 7.1 SP03 before Dev upgrade.
Here are the notes for reference of others who get into same issue.
Note 1450593 - Implementation of BlobCache
This note states "MDM7.1 SP04 offers new image caching functionality called Blob Cache. The old functionality of Object Cache is replaced with the Blocb Cache mechanism in Catalog 3.0 SP06 P1"
Note 1505796 - Images not showing in SRM-MDM catalog (error in BlobCache)
This note talks about the issue in MDM API with Blob Cache. The Fix has been provided in SRM-MDM Catalog SP08 Patch 01.
But upgrade is not something that happens on the drop of a hat, we dont want to do another upgrade, I would like to know if there is a workaround.
Thanks
Pravin

Q & A for blueprint upgrade to SRM server 5.0

All,
As we are going for upgrade from EBP 2.0 to SRM 5.0 and we have go for blue printing. If any body is having Questionare contains technical and general business questions in this scenario please post such a questions from Q&A db. The client is working on classic scenario. If anyone went for such an upgrade, please provide me some inputs in this regard.
Thank you,
Manyam

HI manyam
following post may be usefuls
G/L account field to be disabled for SC screen
Help needed in SRM upgrade to SRM server 5.0
Hope this provides valuable information.
Regards,
Nimish Sheth
Do reward points for helpful answers.

BADI's in classic scenario after upgrading to SRM 07

Hello,
We are using the classic scenario, just finished upgrading the SRM 4.0 (server 5) to SRM 07.
We are using ECC 6.0.
We used the BADI's:
BBP_CREAT_PO_BACK
BBP_CREAT_RQ_BACK
I have understood that in SRM 7.0 the BADI's that I have to use are:
BBP_CREAT_BE_PO_NEW
BBP_CREAT_BE_RQ_NEW
Do I have to work with the new BADI's or can I stay with the old one?
Thank's
Yaron

Hello,
As far as I know, once you activate new badis, old ones will not be called anymore.
So, if you do not activate them, old badis will still be called.
Just remember that these badis are valid when follow on document is created via RFC in ECC.
If you have activated ESOA (creating POs in ECC via XML), PO badi is not valid anymore.
Regards,
Ricardo

Upgrade to SRM 7.0 Additional fields on 'SOS' of SC

Hello All,
We have Upgrading the SRM system to 7.0. and we ahve one requirement to add few fields on Source Of Supplier' of shopping cart also we need to transfer this data from SRm to ECC system.
I did following changes till now,
Added new fields in following path of SPRO:
1. Under Configure control fields --> Define customer fields on Item level --> Append for Customer Fields on Shopping Cart Item
2. Under Configure control fields --> Define customer fields on Item level --> Append for Customer Cross-Document Item Database Fields
3. Under Configure field control --> Configure control for Fields on Item Level --> Default Metadata for Fields in Items that do not (yet) Exist --> Added new fields for OBj Type BUS2121 (SC) and BUS2201 (PO)
Changes in Webdynpro:
Webdynpro: /SAPSRM/WDC_DODC_SC_I_SOS
View: V_DODC_SC_I_VENDOR
1. Created new enhancement
2. New fields added under context SUP--> ITEM_BASIC_DATA where as type for each field refered to structure /SAPSRM/S_CLL_WD_SC_I_BD
3. Added fields in Layout
4. bind these layout fields to new context elements
Problem:
I'm able to view these fields on SRm 'SOS' screen, when I enter vallues in these fields and click on any other Tab values are not retained and get refreshed. That is all values are set to BLANK value.
Is there any step which I'm missing?
I have searched lot of forums for this, and followed above steps but no sucess.
Please help me to resolve this ASAP.
Thanks in advance.
Regards,
Yogesh

Hello Devi Prasad,
Thanks for reply!
I checked the given method in debug mode.
This method is getting called before assiging supplier. I can see that all custom fields are available in the internal table at the time of debug.
Now the process is, when I enter any supplier between range 000-999 and click on asisgn supplier button, my custom fields will appear on the SOS tab. Now when I enter any value in these fields and click on any other Tab or Order the shopping cart all custom fields value get cleared and does not store values in it.
My requirement is to hold these values in custom fields till I order the shopiing cart and after Order these values should be stored in the database.
Regards,
Yogesh

Custom fields in webdynpro SRM 7.0 while upgrade from SRM 5.0

Hi Experts,
We are upgrading from SRM 5.0 to 7.0. We created 2 custom fields using configure field control in Meta data handling (SPRO) and enabled them for visibility. When we tried to see these two custom fields, they didnt appear in the web dynpro component.
Web dynpro details are below.
Webdynpro: /SAPSRM/WDC_UI_DO_ACC
Window : IV_L_FPC_CA_DETAILS
view : V_DO_ACCOUNT_DETAIL
Field : zzXXXX
We have to manipulate the data of those fields.
Since we couldn't see those fields, unable access the data. Could you pls suggest what was the solution you found for your issue.
Thanks
Dhivya

Hi,
Please check the Meta configuration on which set key you configured.
you have to configure the fields as show in the below link for accounting.You have to use set key as 31 for accounting.
http://wiki.sdn.sap.com/wiki/display/SRM/CustomerAccountFieldsatDefaultsettingsonShoppingCart
Regards
Devi prasad

Replacing development system with copy of production system during upgrade

Hello Guru,
We are planning to replace our development ECC 5.0 system with a copy of production system, and to perform upgrade to ECC 6.0.
SAP upgrade guide stating that:
"If you have modified SAP objects, make sure that you keep your development sysetem. Do not copy your production system to your development system for test purpose."
If we are planning to "Reset to original" for majority of SAP's objects during SPAU, are there other reasons we need to consider the impact of replacing development system with a copy of production system?
Thanks in advance!

Thanks for your response.
When we first implemented SAP system 3 and half years ago, the consultants and the developers were using the development system like a sandbox system, they tried out features or developed programs for learning purpose.
Hence, the development system and production system are very different.
There are many repair transport requests that will never transport into production.
Also, we developed client strategy (different client numbers for each system u2013 Dev, QA, Prod) during the initial implementation.
We were told by the upgrade consultant, it is standard that the development system replaced by a copy of production system during upgrade. The client number in development system will be the same as the production system after upgrade. If I want to avoid confusion for the developer & testing users, I would have to create a new client using the previous development client number, and then perform client copy.
As I review the SAP upgrade guide, I saw the statement about not to replace development system with production system, I would like to know the reasons behind SAP's statement.
By the way, we will replace our QA system with a copy of production system during the upgrade.

SRM Upgrade from SRM 4.0

Does anyone have any good incite on upgrading from SRM 4.0 to SRM 5.0 possibly(6.0)? We are preparing to upgrade to ECC 6.0 and I want to know for:
1 - Is an SRM upgrade absolutely required if we are currently on 4.0?
2 - What are the possible benefits/pitfalls of the upgrade in both SRM 5.0 and 6.0?
Your wisdom is greatly appreciated!
Points will be rightfully rewarded!
Charles

Hi,
See the foll links:
SRM 6.0 update
https://websmp101.sap-ag.de/~sapidb/011000358700006330942006D
Since SRM 6.0 is quite new, and will be officially released after some time, you need to read the release notes in order to find the exact differences in terms of enhancements from the above link.
Refer to this OSS Note as well.
Note 995220 - SRM 6.0 SP Stack 00 (12/2006): Release Information Note
You can check next link:
https://websmp110.sap-ag.de/srm
Re: Additional advantages of having SRM in EBP 5.0 compared to EBP 2.0
In EBP 5.0, you have more flexibility in case of the WF's.e.g. in the SC Approval WF's ,you can have the n-step dynamic header level as well as the Item level approval Workflow in addition to the Standard 1 step,2 step and no approval Workflows
BR,
Disha.
Pls reward points for helpful answers.

Dependencies for an upgrade from SRM 4.0 to SRM 7.0

We have a Client situation - upgrade from SRM 4.0 to SRM 7.0 - they have SAP EP 6.2 and 4.7E backend system.
Now, the questions are -
1. Is it mandatory to upgrade to SAP EP 7.01 (Netweaver 2004s) or will SRM 7.0 work with SAP EP 6.2?
2. It appears SRM 7.0 will work with SAP 4.7E, however, will self-service procurement, sourcing cockpit functionality work okay and integrate with SAP 4.7E without any issues?
An early response is highly appreciated.
SNR

Hi SNR
For your first question please refer to the following link as well as the SRM 7.0 release notes:
https://wiki.sdn.sap.com/wiki/display/SRM/SRMRelatedComponentsperSP+Stack
If you check the EP 6.2 is no longer supported by SRM 5 releases onwards
Based on this information, the SRM 7.0 should not work with EP 6.2
For your Second Question:
It seems to be no restrictions in use Backend 4.7E. You can define it in the SPRO as backend destination / sys type(BBP_BACKEND_DEST table SYS_TYPE = R/3_4.70)
As additional information please kindly refer to the SRM 7.0 Instalation Guides. It can be found in the Service Marketplace
service.sap.com/srm-inst
-> SRM 7.0
There you will find a lot information about installation / upgrade from prior SRM releases
I hope this information helps!
Alvaro

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

Early Delta Initialization option in Production system

Hi Experts,
I have seen some threads related to Early Delta initialization in this forum. I have a question regarding this option.
To minimize the downtime/block users in the R/3 production system during set up tables fillup I would like to use the Early delta option. Please give your suggestions on the following procedure:
For Sales Orders, billing and Deliveries
1. Initialize Early delta in the BI system.
2. Go and fill setup tables
3. Do a full load to BI
4. Run delta job in R/3 (LBWE)
5. Run delta job in BI Info package
Do we miss any documents in this process for e.g. during set up tables fill up changes to existing documents or newly created sales orders.
I feel we won't miss. All changes will be reflected in Delta queue. And even newly created orders also will be coming to delta queue.
Please let me know if I am wrong.
Thank you.

Need Clarification on this thread,
According to my understanding, during the filling of set up table if a user does any posting, then the data available in BW will be incorrect.
am i right?
In your sequence the 4th step
4. Run delta job in R/3 (LBWE), this means you are using queued or unseriallized v3 update.
Early delta iniliazation essentially of no advantage because, as conventional initialization procedures, you can readmit document
postings after successfully filling the setup tables.
can anybody clear my doubt. is it possible during setup table filling user can post a document.
I know the documents will be collected in the queue. But the data loaded to bw will be incorrect right?
Regards,
Anand.
Edited by: araj123 on May 26, 2010 11:41 AM

Upgrade to SRM 5.0- Downtime on production system

Similar Messages

Maybe you are looking for