TDMS 3.0 for ERP 6.0: step by step procedure for TDSH6 Shell creation

Dear All,
I need to perform shell creation. I have never done this and need help with step by step instructions.
I need to refresh my my development system with a TDMS shell creation from production client in production system.
I am familiar with TDTIM and performed many TDTIM copies. I have gone throught the master and operational guides for TDMS also.
I would try to list down my understanding so far after reading the guides.
Please correct me if I am wrong ang also suggest correct steps.
1. All my three systems (central, sender and receiver) are ready from installation point of with with authorizations and latest SPs.
2. I log into Central/Control system and start a new package "ERP Shell creation package for AP Release higher 4.6 "
3. AS I have never executed this option I do not know what are the stps inside it.
But I assume I should be asked for the source client details from which shell needs to be creates. (000 or pruduction client)
What type of shell : slave or master?
4. During the shell creation from sender system client, is there a downtime for sender system.
5. Once the shell creation is done an export dump will created.
6. I perform all the preprocessing steps of a homogenous system copy on the receiver systems.
7. Stop receiver system, start sapinst database instance installation with homogenous system copy with R3load option.
8. Provide the export dump location to sapinst.
9. After database instance is installed, perform system copy specific post processing steps.
10. Afte the system is ready it has only one client 000 now available in development system and i need to create a new cleint from 000 which will act as my new development cleint.
I request all you experts to please provide your comments at the earliest as activity would be starting from 5th of this month.
Regards,
Prateek.

Hi,
Let me answer your questions.
Some queries
1. Is there a downtime for Production system (sender system).
SAP recommends that nothing much should be going on during the export of the Sender(PRoduction) system, but so far i have never encountered an issue doing the export in online mode.
2. Shell creation works on both Production and 000 client or only Production client,
Be carefull!!! - A Shellcreation is a normal Homogenous Systemcopy using R3load. You will create a 'new' system with the DDIC and clientindependent customization of the Sender system. ALL former data of the target system will be deleted.
You mention that you will refresh a development system that way. Please be aware of the implications that a development refresh contains. That said. After the refresh you will have the 000 client and parts (users ... authorizations of sonder) of the other clients on the new system.
3. when I import the the dump using sapinst, how many clients are available in receiver systems.
See above. All client configuration will be available, but nearly no data will be in these clients except 000. A manual part of the Shellcreation is to clean up the target system (delete the clients that are not needed) This is a fast process.
4. Soem where in the guide it is mentioned that downtime depends on the type of shell I create.
Kindly suggest should I create a master shell or slave.
Hm. The master shell is just a concept that you create a complete new system and put that system into your transport landscape without filling it with data. You can then use that system as the source for a normal (database dependent) systemcopy without impacting your prod system. The result is a very small copy that can be repeated very often without an impact to prod/QA...
Downtime is as described in point1 not required
5. Once I execute this activity of shell creation for lets say receiver system A, then can I use the same export dump for second receiver system B.
Yes
6. Lastly please suggest the activity execution time as customer has provided us 2 days to execute this activity.
This depends on your knowledge of homogenuous systemcopies and the preparation + some items like size of stxl and other tables that will be exported/imported. If you are very familiar with the systemcopy process using R3Load 2 days are feasable.
I have seen shellcreations done within 1-2 days but also much longer ones!
As a prerequisite i would always recommedn to have the latest R3* + migmon exe available on sender + target.
I hope i have clarified some of your items.
Best Regards
Joerg

Similar Messages

Error in installation EHP5 for ERP 6.0

Dear Friends
During the installation EHP5 for ERP 6.0
in preprocessing step
İ saw this error
How can i solve this problem
CURRENTPHASE MAIN_INIT/SHDINST_CHK1
...started at 20110726222215
Using phase log file 'SHDINST_CHK1.LOG'.
Error message set: 'Messageserver "sapmsSHDKLT" is not an entry in services'
...begin dialogue at 20110726222215
best Regars

Hi,
Which is you OS.?
Depending on that your would need to add the entry
sapmsSHDKLT 36<shadow instance number>
to the file ..\WINDOWS\system32\drivers\etc or /etc/services
Regards,
Srikishan

Step by Step procedure for Integration of B0 with BI 7.0, Portal

Hi,
My key concerns include integration with SAP Portal, which I did not find in instalaltion guide.
Please advice on step by by Procedure for BO with BI 7.0 starting with the right version of BO to be installed.
1. Which version compatible with BI 7.0 SP 12, LATER TO BE UPGRADED TO sp 16
2. Source of data will be BI and reports will be using BO.
3. What are components to be installed
4. Prerequisites for Integration with BI AND SAP Portal.
5.Steps for Integration with BI 7.0
6. Steps for Integration with SAP Portal- Where to get the sample iviews. What to do for connction between Portal and BO - this i didnt find in installation guide
Thanks,
Harish

HI,
here the items:
SAP Side:
- all machines have to be in the same domain
- BI has to trust the portal
- BI has to accept SSO tickets
- EP has to generate SSO tickets
BusinessObjects:
- SAP Authentication has to be configured
- BI system should be configured has default system in the options of the SAP authentication
- authentication.default parameter in the web.xml for InfoView has to be set to secSAPR3
- BusinessObjects has to be in the same domain
EP side:
- in the system landscape configure the Crystal Enterprise Server Properties for your BI system
- import the portal iview template that is part of the SAP Integration Kit
- create a new iView
Ingo

Release procedure for Purchase orders

Hello SAP Gurus,
Can anyone explain in steps the release procedure for purchase orders and also can any one explain how it differs from Puchase requisition release procedure.
Thanks
NDS

Hi
Release procedure for Purchase orders here is process flow.
Go to spro>img>materials management>purchassing>Release procedure for Purchase orders
1. Create characterstics -Intially you will create characterstics based on which you would like to release a purchase order.
Charactrestics are like plant, purchase order value,purchase group etc.. Assign characterstics to release class 032.
2. Create Release group say 01 and create release codes like pm(project manager), gm(general manager) etcc..
3. Create a Release starategy say s1 and assign release group to it 01 and release class 032 and department to whom this release stategy applies say MM. define the order of release say first pm followed by gm etc..
4. under classfication define value limits for release of purchase order.
5. define release indicators
6. simulate the release
7. assign if there is any workflow.
hope it helps.

Cash sales using Pricing procedure for account determination cash settl

Hi all ,
we are customizing for cash sales , we have defined all steps as per "cash account determination" in basic functions.but , system is posting again to customer account, i.e account receivable account.
if we assing "EVV" accounting key in the field "Account key for cash allocation" of billing type ( bv-cash sales),and assigning GL account for account key "EVV" in VKOA, it is working fine.
if we want to post cash account using cash account determination pricing procedure i.e by assining pricing procedure in billing document type, it is not working. Is there any additional cusotmizing has to be done in addition to steps involved in "cash account determination of basic functions?
can any one help on this?
regs,
ramesh

Hi,
thanq for your reply.
we have used same document types mentioned by you. for the same only cash account determination given.
if we remove revenue account determination procedure, system will not post accounting document, system will give message, this billing is not relevant for accounting.
our aim is to post sale account, but instead of accounts receivables, it has to post to cash clearing account.
so, we have assigned revenue account determination procedure ( for sales posting) and cash account determination procedure ( for cash clearing posting).
you may be right, some where i missed some thing, which is not tracked by me. If you can give steps, at least I can check, same thing was customized or not.
regs,
ramesh

Pricing procedure for order with reference from order

Dear Friends,
If I create a sales order with reference to another sales order of different type, the pricing procedure is copied too.
But I would to use another pricing procedure for second document
I found the oss note 14136 but this is for reference from invoce
I tried to create new data transfer routine for orders in copy from 51, but does not work
Can you help me??
thanks
best regards
GdA

> If I create a sales order with reference to another sales order of different type, the pricing procedure is copied too. But I would to use another pricing procedure for second document,
Based on my understanding of query.
You are looking for a different pricing procedure in second doc.
For instance, the PricProc for SalesDoc1 is ZPR001 and the PricProc for SalesDoc2 is ZPR002, in addition to that, you want SalesDoc1 to become reference doc for SalesDoc2.
For this, ZPR002 & ZPR001 should have common base price condition type and rest pricing can change.
And for maintaining different Pricing Procedure with similar combination of sales area for SalesDoc1 & SalesDoc2, maintain different document pricing procedure for both docs and maintain Pricing procedure accordingly..
Thanks & Regards
J Prakash

Requirment class & Procedure for each schedule line category

Hi all,
In requirment class we have a switch on/off indicator for avai check and TOR.In define procedure for schedule line category also we have the same.
If I dont want the system to carry out availabilty check, I can switch off the indicator in requirment class or at schedule line category.
My question is why we have these indicators in 2 places.
It is written we can fine tune these settings at Define procedure for schedule line category settings
Could anyone explain in details with Business scenarious
Thanks in advance
Mano

Hi,
1. Availability check at Requirements Class level -
The requirements class contains all control features for planning such as relevance for
planning, requirements planning strategy and requirements consumption strategy.
In addition, it is specified at a global level whether an availability check is to take place for
the material in the sales and distribution documents on the basis of the ATP quantity
(ATP = available to promise) and whether requirements are to be passed on.
2. Availability check at Schedule line category level -
A finer degree of control can be obtained for sales documents using the schedule line category.
Replenishment lead time is only included in the check performed on the basis of the
ATP quantity.
You can control with the schedule line category whether an availability check and
transfer of requirements should be carried out in the sales documents.
Note -
1. At the global requirements class level, the availability check can only be switched on in combination with the transfer of requirements. At schedule line level, the settings are proposed from the requirements class.
2. If the availability check is switched on at requirements class level, it can be switched off at schedule line level. However, you cannot switch on the availability check at schedule line level, if it is switched off at requirements class level. You can make this setting at schedule line level. But the system ignores it and the setting for the requirements class applies.
3. Also, at schedule line level when the availability check is switched on, the transfer of requirements can be switched off. For example, this makes sense for inquiries or sales information.
4. The settings specific to schedule lines for performing an availability check are only relevant for sales documents. In the shipping documents, the settings from the requirements class and the delivery item category are used. As with the schedule line category, the availability check can be switched off as required in the delivery item category.
regards
bhaskar

Post Installation Steps for ERP add-on Inventory Manager 4.0

Hi,
I need to confirm what are the post-installation activities we must to perfom for ERP Add-on (Inventory Manager 4.0), besides de BC Activation. I did not find any information regarding the post installation steps for the ERP Add-on of Inventory Manager 4.0 (the installation guide for IM 4.0 on service marketplace does not remark the steps only explain the theorical part of the installation)... And we need to confirm if the steps are the same of Inventory Manager 3.2 Add-on or we must do an additional step?
Best Regards,
MC
Stephen Streeter Manju Venkatesha

Yeah...of course...
I forgot to specify it.
I install the first ERP 2005 SR2 on Oracle 10.2.0.2 and the other have to be installed on the same version of DB.
All installation are not MCOD.
This mean every installation has its own DB with different SID for every installation.
And of course I have at least doubled the space required by installer. Taken from sap notes the required space for ERP 2005 SR2 is about 90 GB.
The total space of mount point is about 500 GB....
Thanks
Dan

What is the "BW shell creation package for BW system" in TDMS?

I see for lower version of SAP systems such as 4.6 and BW(e.g.3.0, etc), there is a "shell creation package " for those
types of systems.
Could you explain what is that for?
Thanks!

1) where to find the info about the copy sequence such as: first shell creation, then initial package or whatever, then ...?
> TDMS solution operation guide will be helpful, the same is available at SAP service market place. In short the sequence is -
first shell (only if the repository is not in sync) then initial package (ex. TDTIM) and then refresh packages (as an when needed)
2) for HR we do not have shell creation, what we have is "initial package for master data and customizing" , the next step is "ERP initial package for HCM personel dev. PA & PD". Why we do not have shell creation here?
> For HR as only few objects are transfered the need of a full shell system does not arise. only the object to be transfered are synced.
3) Will TDMS replace system copy for ERP, BW, CRM completely?
> Shell will not replace them but we may say that it will supplement it. When you need a complete copy means repository along with application data then you need to go for system copy but if you only need repository to be copied from source to destination then shell is helpful. Also it should be noted that Shell is an TDMS package whereas System copy is a SAP standard tool.
I hope the above response is helpful.
Regards,
Pankaj

Step by step procedure for Upgrade to ECC6.0

Hi,
I gained a lot from this forum . Can someone please mail me at
[email protected]
step by step procedure for upgrade .
Will award full points for helpful documents..
With regards,
Mrinal

SAP defined a roadmap for upgrade.
1) Project Preparation
Analyze the actual situation
Define the objectives
Create the project plan
Carry out organizational preparation for example identify the project team
2)Upgrade Blueprint
The system and components affected
The mapped business processes
The requirements regarding business data
3)Upgrade Realization -- In this phase the solution described in the design phase is implemented in a test environment. This creates a pilot system landscape, in which the processes and all their interfaces can be mapped individually and tested on the functional basis.
4)Final Preparation for Cutover -- Testing, Training, Minimizing upgrade risks, Detailed upgrade planning
5)Production Cutover and Support
The production solution upgrade
Startup of the solutions in the new release
Post processing activities
Solving typical problems during the initial operation phase.
SAP expects at least 2 to 3 months for Upgrade and that again depends on project scope and complexity and various other factors.
STEPS IN TECHNICAL UPGRADE
     Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
     Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
     After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
     Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
     Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
The main Category of Objects that needs to be Upgraded is
     Includes
     Function Groups / Function Modules
     Programs / Reports
     OSS Notes
     SAP Repository Objects
     SAP Data Dictionary Objects
     Domains, Data Elements
     Tables, Structures and Views
     Module Pools, Sub Routine pools
     BDC Programs
     Print Programs
     SAP Scripts, Screens
     User Exits
Also refer to the links -
http://service.sap.com
http://solutionbrowser.erp.sap.fmpmedia.com/
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
Hope this helps you.

Open ERP transaction within CRM 2007 using wizard for transaction launcher

Hello everybody,
I am trying to launch a SAP ERP transaction within SAP CRM 2007 using the transaction launcher wizard.
First I maintained all necessary setting for the RFC connections (in ERP and CRM) using for example transaction SM59 and BD87, e.g. the master data replication is working fine. Second I created a business object type based on the SAP Standard business object TSTC and set the u201CExecuteu201D method to u201CSynchronousu201D in SAP ERP.
Afterwards I created the URL for our ITS server and started the transaction launcher in CRM. During the step u201CFurther technical detailsu201D I selected as transaction type u201CBOR transactionu201D and chose our logical system (ERP) and added our newly created BOR object type as well as the method u201CExecuteu201D. If I now press the u201CNextu201D button the error message u201CAn RFC destination could not be specified for the logical system XYu201D is shown.
Any help is highly appreciated.
Thanks lot and kind regards,
Franziska

Hi,
The error you get is because the client you have mentioned for logical system mapping and the client in which you created the BOR object are not same.
Remember, for sucessfull transaction Launcher Configurations,
1) The client in which WEB UI Runs
2) The Logical System mapping and client mentioned in ITS url
3) The client is which you created the BOR object.
4) The client on which you are configuring transaction launcher wizard
ALL SHOULD BE THE SAME CLIENT, unless you are using the OWNLOGSYS concept for logical system mapping.
For example,
If my WEB UI is on client 200 of development system,
then i must create TSTC based BOR in client 200 , Map logical system for client 200 and configure trnsaction launcher in client 200.
In this approach, you cant transport the developments to other system and client ( like Quality and production system) , hence its advicible to create a logical system with name OWNLOGSYS. The name of logical system must be kept OWNLOGSYS in all the systems and clients so that then you can transport yout transaction launcher developments and the error you get now will not come. It its not possible to maintain the logical system with this name in all the system , then you will have to do as i mentioned in points 1 to 4.
Hope this helps.
Thanks & Regards,
Suchita

Profiles for ERP Sales Order

Dear experts,
I'm trying to configure our CRM 2007 system (upgraded from CRM 4.0) in order to call ERP Sales Order functions from the the new CRM WebClient UI. The ERP background system is ECC 5.0.
Issue Description:
In standard, we should have 2 default profiles for ERP Sales Orders: DEFAULT and SALESPRO but I can't see them. I think those entries will allow us to call some ERP Sales Order functions from CRM. When I try to recreate them manually, a short dump occurs.
Steps for reconstruction:
1. CRM > Interaction Center WebClient > Business Transaction > ERP Sales Order > Define Profiles for ERP Sales Order
2. Select SALESPRO and double-click on Assign Document Types to ERP profiles in the left menu
3. Select New Entries and select SALESPRO for the ERP Sales Order Profile
4. Select a Document Type using the F4 search. Short dump occurs and can be analysed in the ECC system (SLS_LORD_GET_VALUES_AUART)
Do you have any idea why this short dump occurs?
Thanks in advance
Stephanie

Hi,
see ERP Sales Transaction in CRM 2007 for details.
They say that you can connect only a ECC6.0 to CRM, not any older versions.
Unfortunately I cannot check this statement.
Regards,
Claudia

Procedure for Standby Database for SAP ERP 6.0

Hello All,
We are using SAP ERP 6.0 with Oracle 10g with AIX 5.3.
We are planning to setup a standby database for our SAP ERP 6.0 production system as part of remote DR site using Oracle Data Guard.
I was under the assumption that i can first install an erp 6.0 (ABAP) system using homogeneous system copy from my erp 6.0 (ABAP) production system and then start configuring oracle dataguard.
But the System Copy Guide "System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 ABAP" has mentioned that "You cannot create standby systems with a system copy".
Please suggest the best practise or the procedure for creating standby database for SAP ERP 6.0 system. Iam not looking at the steps for creating a pure oracle 10g standby database, but with SAP instances as well.
Thanks in advance.
CVS

Hi,
Please refer the below mentioned link for configuring data guard.
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm
Below mentioned are the sequence of stpes, which needs to be followed for setting up data guard.
3.1 Configuring the Primary Database
3.1.1 Enable archiving and define a local archiving destination
3.1.2 Create a password file
3.1.3 Configuring the Oracle networking files
3.1.4 Set initialization parameters on the primary database
3.1.5 Take Offline/Online backup of the primary database
3.1.6 Create a control file for the standby database
3.1.7 Prepare initialization parameter file for the standby database and start the primary database with the changed pfile.
3.1.8 Copy all files from the primary host to the standby host
3.2 Configuring the Standby Database
3.2.1 Configuring the Oracle networking files
3.2.2 Create a INIT parameter file for the standby database
3.2.3 Copy the standby controlfile to the appropriate location
3.2.4 Create Oracle Password File
3.2.5 Start the physical standby database
3.2.6 Initiate log apply services
Regards,
Ranjith

TDMS for BI - shell creation and SMIGR_CREATE_DDL

If a homogeneous system copy of a BI system is done, it's necessary to run the job SMIGR_CREATE_DDL because depending on what database is used, special SQL scripts for tables must be used (concerning primary keys).
How does that integrate into a shell creation? Is the shell creation process aware of those scripts? I mean, it's theoretically possible that the SQL scripts has a table that is excluded from being transferred?
Markus

Markus and Pankaj:
I have created a SHELL (BW) using Markus' way as listed below.
Because Markus did not mention that SMIGR_CREATE_DDL should be run at the beginning, so I did not run it.
So how to determine in the created shell what is missing?
We do have partitioned tables and bitmap indexes.
Thanks!
Here is the way provided by Markus:
I basically do shell creation as follows:
- install the latest system copy tools (R3load, R3ldctl, R3szchk, libdb<database>slib.dll)
- create an installation directory and give full permissions to <sid>adm and SAPService<SID>
- create a directory for export location and give full permissions to <sid>adm and SAPService<SID>
- open a cmd.exe as <SID>adm, step to the installation directory and execute "R3ldctl -l R3ldctl.log -p ." (note the "dot" which means actual directory)
- in parallel start the client export of client 000 in source system using SCC8 (profile SAP_ALL) and note the file names you get in the last dialog window
- when R3ldctl is finished give permissions to SAPService<SID> for all files in the installation directory
- proceed with TDMS
- when you are at the point to start the system copy start sapinst, choose system copy and select start migration monitor manually (VERY important!)
- sapinst will run R3ldctl, R3szchk and then prompts you to start migration monitor
- step to your normal installation directory (c:\program files\sapinst_instdir....), open export_monitor_cmd.properties and adapt the file. The import thing is, that you need to point to YOUR DDL<DB>.TPL file you create in step 4 (in my list here)
- start export_monitor.cmd and export the system
- proceed with TDMS to adapt the database sizes (DBSIZE.XML)
Import:
- if you have an already installed system uninstall it
- start sapinst normally, choose system copy and point to the export you created
- install the system normally (as a new installation)
- if you want to make sure the import works as the export choose "start migration monitor manually"
- if sapinst stops and requests you to start migration monitor copy the kernel from source system to target system
- configure import_monitor_cmd.properties and start migmon
- logon in client 000, start transaction STMS and create a domain (basically only a transport profile will be created)
- start program BTCTRNS1 (this will suspend all jobs from the source system but not delete them)
- copy the files from the client copy to TRANSDIR/cofiles and TRANSDIR/data and import them to client 000 (either use STMS or use command line tp)
- adapt profile parameters (RZ10)
- run SGEN
- invalidate connections in SM59 that point to other production systems
- finished
- to re-enable all the jobs run BTCTRNS2, however, I'd do this only if you're sure you have invalidated RFCs and or sending jobs (e. g. from SCOT)

TDMS Step-BY-Step Guide (HCM)

Hello experts,
could anyone please let me know where I can find a Step-By-Step Guide for
implementing the HCM-Scenario for TDMS?
Would be great if it could be more detailed than the operation and master guide.
Many many Thanks.
Regards Marco

Hi Marco,
There is no step by step guide for TDMS HCM, but you have a common guide for all TDMS Scenarios.
You can access the master and operations guide in the service market place.
You can follow the TDMS Master Guide for TDMS HCM information ( genrally the platform is same, but some of the activities differ). For specific activities in HCM, you can refer to the documentation for each activity. ( By selecting the activity in the process tree and selecting 'Activity Documentation' button on the toolbar. It displays a details information for each activity.
If you have any specific questions, do not hesitate to post them here.
Regards,
Prasanth

TDMS 3.0 for ERP 6.0: step by step procedure for TDSH6 Shell creation

Similar Messages

Maybe you are looking for