Pre-activities in source system before export

Hello Experts,
Please share reason why following activities needs to be done before export:-
1) No switching of operating modes takes place while a system is being copied
2) No upgrade-prepare is performed
3) No incremental conversion is in progress
4) No canceled or pending update requests should be in the system.
Thanks
S.BASIS

Hi
Refer below for details;
When operation modes are switched (based on the definition from its time table), the work processes (WP) are redistributed in the active instance.
This means, when WP used as a dialog process (DIA), it can be switched for use as a background process (BGD) or vice-versa, i.e. depends on the WP type defined in Operation mode.
While switching Ops Mode, WP may not be switched immediately instead WP is set to be switched when next possible ( if WP is busy in its current status, with either DIA or BGD) but this switch is more risk and or possible to get into error mode while system (means, WP) is busy with its export or upgrade activity. So SAP advise to deactivate Ops. Mode switch.
Best Regards
Swami

Similar Messages

Activites after source system refresh

Hi all,
we made source system refresh recently.
When iam running INIT I am not able to get the data ,but in rsa3 data it is available
Now I am not able to retrive the data from source system for SD data sources like 2LIS_02_ITM.
Can any one tell me what type of activities i need to do after source system refresh for LO data sources.
Thank
Pruthvi

Hi Pruthvi,
As you mentioned about refresh, it would be a system other than Production system.
Delta Loads:
1. Whenever a refresh happens from the production, the delta pointers are disturbed.
2. You need to re initialize the delta pointer for the DS you mentioned.
3. If it is for the testing purpose of the Delta functionality, you may intialize the delta pointer 1st and then ask for postings of data in the ECC side.
4. Once the postings are done, you would see data in Delta Queue in RSA7 in source system.
5. Now run the Delta InfoPackage so as to fetch this data from the Delta Q of SS to the BW system.
Full Loads
1. If you are expecting a full load (Historical data), you need to first fill the Setup tables (in Background only) in the SS.
2. Once the Setup table fill job is completed in SS, you may execute a Full InfoPackage in order to get this full load.
Let me know if this helps..
-Bhushan.

FM CRM_PRIDOC_READ_OW works in source system but not when executed from BW

Hello All,
I have extended an extractor in the source system by adding additional fields.
One of the FM I've used is CRM_PRIDOC_READ_OW. When I run an extraction test in the source system eveything works and data does populates into the new fields.But when I run the infopackage from the BW side, I get an error message which saids the transaction has been terminated. I've been able to trace and pinpoint the possible cause of the error. When I do not call this FM, the infopackage finishes but I do not get data for the new fields and when I do call this FM, I get the error.
Has anyone experiance this issue before?
Your assistance will be much appreciated. Here is a portion of the code I wrote:
loop at I_TABLE into l_s_ZASCRM_OPPT_I.
    lv_guid = l_s_ZASCRM_OPPT_I-GUID.
    lv_item_guid = l_s_ZASCRM_OPPT_I-ITEM_GUID.
    call function 'CRM_PRIDOC_READ_OW'
      exporting
      iv_header_guid = lv_guid
      importing
      ES_PRIDOC = ls_pridoc.
    loop at ls_pridoc-PRIC_COND into ls_pric_cond.
      if ls_pric_cond-kposn = lv_item_guid.
        case ls_pric_cond-STUNR.
          when '40'.
            l_s_ZASCRM_OPPT_I-zz_gpm_ttl_i = ls_pric_cond-kwert.
          when '55'.
            l_s_ZASCRM_OPPT_I-zz_gpd_ttl_i = ls_pric_cond-kwert.
          when '60'.
            l_s_ZASCRM_OPPT_I-zzfy_sp_i = ls_pric_cond-kwert.
          when '70'.
            l_s_ZASCRM_OPPT_I-zzfy_gpm_i = ls_pric_cond-kwert.
          when '80'.
            l_s_ZASCRM_OPPT_I-zzfy_gpd_i = ls_pric_cond-kwert.
        endcase.
      endif.
    endloop.
    append l_s_ZASCRM_OPPT_I to l_s_ZASCRM_OPPT_Itab.
    clear l_s_ZASCRM_OPPT_I.
endloop
Thanks,
Jeff

Hello Geo!
Thank you for your question. I think we mapped all the systems you show. Always the same error. Concerning your systems my transport log would say:
Source system R3DEV does not exist
We mapped this.
Any ideas? Is there maybe something in customizing to do what could be forgetten? The system is newly connected and there have never been a transport compounded to this source system before.
Best regards,
Peter

BDLS for conversion of logical source system name

Hello All,
I am trying to reassign a new source system NEW1 by replacing old source system OLD1 using BDLS in the source system.
But the NEW source system logical system name already exists as I created it . Can I delete the new source system and then use BDLS?
How do I make sure that the reassignment happens correctly?
And what precautions should be taken to avoid further consequences?
Regards,
NIKEKAB

BDLS does a pretty good job... Never had issues with it when using it... Always execute a test run, look for warnings or errors...
Yes, you can delete the source system before doing BDLS... I assume, since it is new, nothing is connected to it...
You always will have to check RFC connections, datasources replicas, rules, etc, once the conversion is done...
Make sure you take a look at note 886102, it has very good information and make reference to other relevant notes specific for BDLS, like 121163, 369759, etc... Read the notes carefully, follow the steps and you'll be fine...
Once everything is done and in place, you shouldn't have any surprises in the future... It's just normal maintenance...
Good luck...

Downtime for Heterogeneous System Copy Export of Source DB2 LUW

Hello,
What is the downtime required for a heterogeneous system copy export of a source database on AIX with DB2 LUW? Here are the following details of the data itself:
DB size: 120 GB used of 240 GB.
Physical server: IBM Power5 quad-core 1.65GHz virtualized
RAM: 9.5GB

> What is the downtime required for a heterogeneous system copy export of a source database on AIX with DB2 LUW? Here are the following details of the data itself:
I suggest you just "try it out" as a test run. It's quite impossible to give estimates based on database sizes. It's possible to migrate roughly 1 TB/hour with appropriate hardware, mostly your harddisks will be the bottleneck.
There are also a number of other factors like number of R3load processes, table splitting or not, parallel export/import etc.
I highly suggest to run the migration a few times before you do the "live" migration.
Markus

BW Myself source system in ECC 5.0 while Export DataSource!!

Hello BW Experts,
When we do Export DataSource for a DataMart eg:ODS, we have to again select our Myself BW source system and replicate our datasource to see it visible in the infosource tree with our DataMart name starting with 8*.
Plz clarify these Qs:
1. Can we perform "Generate Export dataSource " for customer generated DataMarts and replicate them in Myself BW source (Other than Business Content DataMarts??)??
2. Which is the Myself BW system in the ECC 5.0 version as everything is integrated and used being the source system as T90CLNT800 with the client 800and with a single userID and password.
Note:I could not find my generated Datasource for my customer generated DataMart to replicate the same using T90CLNT800 context menu.
Plz throw some light on this!!
regards,
Sapster...Points will be awarded.

Hi,
You dont need to replicate the datasource after the generate export datasource. You can find your 8* datamart in the infosource by using any of these 2 methods:
1. Goto the top most of the info-source i.e. "Infosources" -> right click -> Insert lost nodes. You should be able to find your datamart.
2. Goto settings (menu) -> Display generated objects -> show generated objects.
Hope this helps.
Bye
Dinesh

Exporting and Importing Portal users from Source system to Target system

Hi All,
I have exported all portal users from source portal in to file Users.txt do i need to convert this file in to some other format so that i can import these users in Target portal.
any links documents
Regards,
Murali

Hi,
If you look in to User.txt
I have role also i have deleted role in User.txt uploded file with rest of the otherdata including group it it able to create users.
so in Nut shell let's say
1. UID-Murali
Role- Manager
Group- HRGroup
user existing in DEV and i want to trnasfer data to PRD
Role:Manger should exist in PRD, and group is not mandatory optional
but the link http://help.sap.com/saphelp_nw70/helpdata/EN/ae/7cdf3dffadd95ee10000000a114084/frameset.htm
says while uploading users role is optional it throws waring but i got error.
i am bit confused.
Now let's sau there are 10 users, 10 roles and 2 groups in source system if i want to export all users,roles,groups to target system what sequnce i have to follow without getting any error , warining is there any restriction on number of users, roles, groups i know file size should be less than 1MB.
Points are on the way.
Regards,
Murali

Re: Pre & Post activities for homogeneous system copy

Dear All,
can any body help with pre & post activities for homogeneous system copy
Thanks in advance
Best regards,
khan

Hi,
Use Oracle Database specific method to perform homogeneous system copy.
Along with this reference official [system copy guide|https://websmp209.sap-ag.de/~sapidb/011000358700000416402008E.PDF], You can also refer this [useful doc|http://www.basisconsultant.com/component/remository/Sytem-Copy-Guides/Homogeneous-System-Copy-using-OnlineandOffline-Backup/] for the same to have all required pre-post activities information with more details.
Regards,
Bhavik G. Shroff

Pre-cautions to be taken before to start development activities

What are the pre-cautions to be taken before to start development activities in development server?
please give me answer
regards
ramanji

You should always wear protection glasses and gloves.

Source system deletion before copy or refresh of Non productive system

Hi
regarding the refresh of non prod BI system. . As part of refresh, we were asked to follow note 886102.
In this Scenario B3 matches to us. While doing the scond step. I have to delete source systems from RSA1 except my self system.
It is taking long time to delete source systems as each object of source system is prompting for request and consuming long time to complete thsi activity.
Please help me with a smarter method to delete the sourcesystems.
Thanks,
Haaris
Edited by: Hari Prasad Bolla on Jul 14, 2010 8:50 PM

Hi:
The primary source of information is the how to paper on this topic:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
YOu are correct, you can refreh the BI system without deleting the source system.
Thanks for any points you assign (after all, I wrote the paper!).
Best Regards -
Ron Silberstein
SAP

RFC connection to source system is damaged , no Metadata uploaded

Hello Friends,
I need your help to understand and rectify why my transport is failing again and again.
RFC connection to source system BT1CLNT200 is damaged ==> no Metadata upload
Environment - Production Support (Dev - Quality - Testing - Production)
Alive scenario - Need to create two InfoObject and incorporate the fields in to data targets and reports.
What we have did?
1st request - We have created new request and captured two Infoobjects in to the request.
2nd Request - We have captured the replicated Datasource along with that the below sequence displayed by default in the same package.
Communication structure
DataSource Replica
Transfer Rules
InfoSource transaction data
Transfer structure
3rd Request - we have captured DSO and Cube only in this request.
4th Request - Captured 2 update rules (ODS) Update Rule (Cube)
The above 3rd request failed in the testing system (successful in Quality System) and ODS is inactive in the Testing system.
Testing system Error Message:
The creation of the export DataSource failed
RFC connection to source system BT1CLNT200 is damaged ==> no Metadata uploa
RFC connection to source system BT1CLNT200 is damaged ==> no Metadata uploa
Error when creating the export DataSource and dependent Objects
Error when activating ODS Object ZEOINV09
Error/warning in dict. activator, detailed log > Detail
Structure change at field level (convert table /BIC/AZEOINV0900)
Table /BIC/AZEOINV0900 could not be activated
Return code..............: 8
Following tables must be converted
DDIC Object TABL /BIC/AZEOINV0900 has not been activated
Error when resetting ODS Object ZEOINV09 to the active version
So we have captured the data mart Datasource and created a new( 5th ) request (transported only 5th request )and transported in the below sequence
Communication structure
Datasource Replica
Transfer Rules
Infosource transaction data
Transfer structure
development to Quality - Successfully
Failed in testing system again.
How to rectify this error, please help us
Thanks,
Nithi.

Hello All,
*Question -1*
I have checked the connections and typed the steps below - what i have seen in the screen.
Steps :
R/3 Connection - I have double clicked on the BT1CLNTXXX and tested the connections.
Connection Type :
Logon - 0KB , 10 KB , 20KB, 30 KB
R/3 connection:
5 msec, 0msec, 1msec,1msec,1msec
Please let me know whether RFC connection is OK or not.
Question - 2
I want to know is there is any option to check before transporting the TR from Developement to Quality - "Preview Check " the sequence , so that we can avoid the Transport failure because of TR sequence.
Regards,
Nithi.

BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

Background:
I am relatively new to BW team and will be going through my 1st source system upgrade.
We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
We are upgrading to the source system to ECC 6.0.
In Development and QA Environments:
we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
We have a opportunity to compare the BW Objects, data flow and data loading from
both source systems.
In Production, however, we will just upgrade over 3 days downtime.
One Question that comes to mind in this regard...
What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
Some of the suggestions that were given to me include following points.
Before Upgrade:
1 Check data, taking pre images of it for testing with post upgrade.
2. Perform proper analysis of Source system related BW objects.
- A complete listing of actively used Datasources,.. etc.
3. Make delta queues empty,
Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
After Upgrade:
1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
(depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
Maintain Control Parameters for Data Transfer
http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
4. Check for Changes to extract structures in LBWE Customizing Cockpit
- OSS Notes 328181, 396647, 380078 and 762951
5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc.
Below is a link for some useful programs in this regard.
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
new/changed datasources,if needed.
8. Check all CMOD enhancements.
If we are using a customer exit with the extractor in the OLTP, see Note 393492.
7. Check for unicode (all custom programs or Function Modules for DataSources)
5. Check all the queues in RSA7, start delta runs and test data consistency.
For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
9. Take back up of data posted during upgrade for contingency planing.
10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
We have similar scenario -
We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
Our strategy in ECC deployment ->
In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
In production we are going to use same system PRXX upgraded from 4.7 to ECC.
Now we are in testing phase of ECC with all interfaces like BI in Dev.
My questions are below ->
How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
Also in new ECC sourcesystem copy we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
Is there any easy way for above scenario ?
Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
I have found some other links which have some pieces of information regarding the topic -
Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0
Re: ECC 6.0 Upgrade
Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
ECC 5.0 to ECC 6.0 upgrade
Thanks
Prasanth

Plug-Ins and Extractors - Related to Upgrade of Source system

Hi,
We are upgrading from R3 to ECC.
Can I say that, if the Plug-in in current R3 system and the new system(post upgrade)(ECC) are same then, the extractors will also remain same ? hence, nothing will be affected in BW ?
For example, if the current system(R3) has the Plug-in as PI 2004.1 and the upgraded ECC also has the same Plug-in PI 2004.1 , Can I say that the extractors will also be the same ?
Regards,
Rekha .

You have to take care of all your deltas are picked into the bw before upgradation.
Some times you may required to replicate the data sources after upgradation.
You may lose the connection between your R3 and you BW.
Please do a souce system check after the upgradation.
You have to take care of all deltas :
As a standard practice we drain the delta queues by running the IP/ chain multiple times.
As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
See SAP Notes 506694 and 658992 for more details.
Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
The SAP BW Service SAPI, which is used for internal and BW to BW data mart extraction, is
upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
upgrade to avoid any possibility of data loss.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895 [original link is broken]
OSS notes 328181 and 762951 as a prerequisites.
http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B

Create source system in BW3.5

Hi all
can anybody tell me the procedure for creating source system in BW3.5 using automatic method at this time i create and assign logical system in both BW and R3 system and create Background users in BW system now my confusions are
1 Is this nessory that i create a diffrent user which is not dialog user in BW or R3 and
2 Thing is this nessorry that no pre created RFC connection present in R3
thx

hi,
i m listing down the steps with brief description, check if you r going that way.
1.you have same background user in BW and R/3 with proper autho.
2.you created new source system in RSA13, selecting first option of automatic creation.
3.you fill in all details correctly in popup window "Create R/3 Source System", that comes up.
4.pressing ok, it will ask you to log in as admin in target system. Before loggin in check client no, it may be diff e.g. 000, then change it to yr system client no.
5.next it will give you RFC destinations screen. goto tab "Logon/Security", give password for the user thr. save the changes.
6.you can check the connection by clicking "Test Connection" and try also "Remote Logon". If your password is correct, then it will log you in the system.
7.now everything is setup, so comeback. It will ask you to replicate/activate datasources from the source sytem. Click "Replicate as Well".
pls mark question answered, if you have no further doubts
Now it is finished.
Hope it helps.
Regards,
Purvang

Source system 8(ODS name) does not exist

Hi experts!
When I transport some Process Chane from DEV to PRD I faced with issue that the source system 8(ODS name) does not exist.
Is anyone faced with same error?
Thx!

Hi.......
Look.......
U cannot Transport it........First Right click on the Infoprovider in PRD >> Export Datasource...........then replicate it from bw myself........
U hav to generate it in Production also.............hav u done this before replication.....?
Regards,
Debjani....

Pre-activities in source system before export

Similar Messages

Maybe you are looking for