Obsolete transports cleanup

Hello Experts,
I hope my question is not in completely wrong forum but I could not find more suitable one.
Our SAP environment consists of three databases production, test (QA) and development. Over the time there are quite some old transports that were never transported to test or production. These transports can be tests, changes that were late solved by other transports, abandoned developments etc. I would like somehow to get rid off these obsolete transports and to synchronize the workbench and datadictionary among production, test and development environments. Analyzing all objects in all these transports and reverse the changes done would be an enormous work.
I was told that the only "easy" solution would be copying the workbench from production to test and development and to delete all the obsolete transport but with the disadvantage of loosing the version history of all the programs.
Is there any workable solution for this problem?
Regards
Jiri

>
Jiri Medved wrote:
>
> I was told that the only "easy" solution would be copying the workbench from production to test and development and to delete all the obsolete transport but with the disadvantage of loosing the version history of all the programs.
>
This is the optimal solution.
Plus - you need not lose the versions. You can extract the version database before the copy and re-import it after the copy. It works phantastically - I have been using this trick in March 2010 and am absolutely satisfied. [Note 130906|https://service.sap.com/sap/support/notes/130906] describes exactly what you have to do.

Similar Messages

Several old/obsolete transports in the queue - how to get rid of them.

We are looking at an upgrade from ECC5 to ECC6 in the near future. As part of that, i'm looking to "clean up" outstanding or unneeded objects in the system.
In this case there are several old (a couple years +/-) transport requests in the queue for our production system. None of these ever made it all the way through, or issues were discovered in QA so the object was modified and put in a new transport, which did make it into Production. Leaving these unneeded transports sitting in the queue.
1) will these be an issue for the upgrade
2) how do I go about cleaning them out of the queue? Or should I? Or can I?
I'm open to suggestions on how to manage these old transports.
(Now we will move up an incorrect transport followed immediately with the corrected transport, thereby removing an unwanted transport. Unfortunately this was always done in the early days.)
Thanks for your suggestions
Laurie McGinley

You are talking about transport buffer for your prod.
This has no link to your upgrade process.
During the upgrade, it will look for open transports that were not released.( it 'll not look for the transports added to the queue)
For cleanup, you can try the option from tp command.
http://help.sap.com/saphelp_sm32/helpdata/EN/3d/ad5b744ebc11d182bf0000e829fbfe/content.htm

SMON cleanup process taking longer time (cleaning temporary extents)

Os info:     Solaris 5.8
Oracle info:     9.2.0.8
Message:
We are in the process of testing our upgrade from 9.2.0.8 to 11.2.0.3. As a part of this, we have cloned our production database and started cleaning up of unused objects on the new instance.
Dropped an Audit Table (27g table size & 11g index size) from SYSTEM tablespace as a part of 11g upgrade tasks. As you know SYSTEM tablespace is under Dictionary managed tablespace and drop table ran for about 2 weeks.
We are unable to bring this database gracefully, as SMON is still cleaning the temporary extents. This cleanup seems to be very slow and will take about 40+ days.
Created SR regarding this issue, to speed up the SMON clean up process.. but no luck.
At this moment we are looking for a solution to
1#Is there a way to speed up the SMON cleanup process (temporary extents)?
OR
2# Is there a way to bypass the cleanup of this temporary segment and bring the database gracefully?
No Luck from Oracle Support...
Googled it but no luck.
Just want to check with the folks over here and see if there is any solution for this issue.
Thanks in advance for your time and efforts on this forum. Appreciate your assistance!
Thanks,
Raghu Yella.

Just passing by.
>
If the data is not needed, drop the index, truncate the table and then drop the table (as rp0428 noted above)
>
Srini and rp0428, what do you guys know that I don't? A "drop table" (which is what the OP indicated was run) should drop any data (effectively the same thing as a truncate) and all associated indexes. Does the truncate offer some performance benefit in this case?
And I'm still trying to wrap my head around a 40 day drop. The statement, "started cleaning up of unused objects" scares me if there is more backup tables in this bloated SYSTEM tablespace. If that is the case (and maybe regardless), I wonder if it would just be better to create a fresh "clean" database and then with transportable tablespaces reattach all the DATA tablespaces to this new database. Fresh start.

Releasing transport request has an error during the 'export' step.

Hello Everyone,
My environment is ERP 6.0 EHP6, AIX 6.3, Oracle 11g.
We have a transport request that was created in our development system by deleting some obsolete roles. When we try to release the transport request to our q/a system it terminates with errors in the export step.
The errors are.
   End of export R3TRTABUUSR10
   no E071K or E071K_STR entries found for R3TRTABUUSR11
   Start export R3TRTABUUSR12 ...
   no E071K or E071K_STR entries found for R3TRTABUUSR13
Of course we cannot create a new transport request because the roles were deleted.
Can someone please explain to me what could have cause this type of error and possibly how to resolve it?
Regards,
Ron

Hi Ron,
As per your log, no E071K or E071K_STR entries found forR3TRTABUUSR11
no E071K or E071K_STR entries found for R3TRTABUUSR1
Looks like there is no entry found for E071K or E071K_STR in table USR11 and USR13.
Please check those table and make sure the above entries are there, if not that could be the issues.
Also, please check if these tables (USR10, USR11, USR12 USR13) are active in SE14.
Thanks
Adil

Data Load Issue "Request is in obsolete version of DataSource"

Hello,
I am getting a very strange data load issue in production, I am able to load the data upto PSA, but when I am running the DTP to load the data into 0EMPLOYEE ( Master data Object) getting bellow msg
Request REQU_1IGEUD6M8EZH8V65JTENZGQHD not extracted; request is in obsolete version of DataSource
The request REQU_1IGEUD6M8EZH8V65JTENZGQHD was loaded into the PSA table when the DataSource had a different structure to the current one. Incompatible changes have been made to the DataSource since then and the request cannot be extracted with the DTP anymore.
I have taken the follwoing action
1. Replicated the data source
2. Deleted all request from PSA
2. Activated the data source using (RSDS_DATASOURCE_ACTIVATE_ALL)
3. Re transported the datasource , transformation, DTP
Still getting the same issue
If you have any idea please reply asap.
Samit

Hi
Generate your datasource in R/3 then replicate and activate the transfer rules.
Regards,
Chandu.

WSUS Best practice for cleanup order?

Hi All,
I have a Win 2012 WSUS install that initially grew large and the Server Cleanup Wizard would fail when running all of the available options together. I believe I have worked out the best order to run the cleanup options from a GUI:
Expired updates & Superseded updates
Unused updates and update revisions
Unneeded update files
Additionally to this I routinely decline 'superseded updates' and 'superseded updates that also supersede an update'. Note I wasn't running the 'Computers not contacting the server' option as I currently only have 30 machines connected. So now I have a healthy
running system.
I'm now looking at having a large influx of connected devices and as such will start using the 'Computers not contacting the server' option. I am looking to leverage Powershell to automate the cleanup action and schedule it to occur before
the next synchronisation. Powershell offers an extra option (CompressUpdates) to compact the database.
I'm not sure if this did run or not when using the GUI Server Cleanup Wizard and if so under what guise?
So I am thinking the logical order would now be:
Get-WsusServer | Invoke-WsusServerCleanup -CleanupObsoleteComputers
Get-WsusServer | Invoke-WsusServerCleanup -DeclineSupersededUpdates -DeclineExpiredUpdates
Get-WsusServer | Invoke-WsusServerCleanup -CleanupObsoleteUpdates
Get-WsusServer | Invoke-WsusServerCleanup -CleanupUnneededContentFiles
Get-WsusServer | Invoke-WsusServerCleanup -CompressUpdatese:
This way it gets rid of any clients it doesn't need to track anymore -> declines updates that it can -> deletes obsolete updates -> removes physical files -> compresses the newly cut down database.
Would you agree or is there a difference of opinion out there? Please give reasoning.
FYI - My WSUS is servicing XP/7/8/2012 clients just in case that makes any difference.
I did search regarding this but nothing answered in regards to using Powershell options. There was a training video link that Lawrence Garvin posted but it no longer works, not sure if that may have contained the answers.
Kind Regards

I did search regarding this but nothing answered in regards to using Powershell options.
PowerShell is a relatively new capability for launching these cleanup tasks, but functionally no different than doing it via the API or using the UI.
There was a training video link that Lawrence Garvin posted but it no longer works, not sure if that may have contained the answers.
It might have. If you can provide the link, I'll see what I can do to get some replacement content online somewhere. My guess is that it's a link to an old webcast. I have the videos of those webcasts, and I'm working on getting clearance to re-do the slides
and repost the revised videos. Also, I'm presenting on WSUS at SpiceWorld Austin next month, and I'll be covering server maintenance in that session.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.
Thanks for the reply.
I just figured PowerShell running the commands instead of UI would lessen the pocessor usage; my UI is run from another Hyper-v client on the same host server as we are still running XP on our PCs (not happy about it).
Here is tutorial video by Lawrence which may help you for management:https://www.eminentware.com/cs2008/media/10/default.aspx
The specific videos of interest in this scenario are at:
https://www.eminentware.com/cs2008/media/p/216.aspx
and
https://www.eminentware.com/cs2008/media/p/784.aspx
If only I wasn't in Australia I'd come say g'day in Austin ;)
Cheers.

Problem in transports!! Please help

Hello BW Gurus,
I am havinga major problem with transports.The Client had separate HR box as the source system for HR Objects.
Since the HR box is obsolete, we assigned SAP R3 as the new source system to infosources and activated them.
I created a transport by collecting at the transfer rule level. The transport is failing saying it cant fing the SAP source system.
Post-import methods for change/transport request: BWDK960528
Follow-up action RS_AFTER_IMPORT for IOBJ L started at 20060203130629
Start of the after-import method for object type R3TR APCO (Activation Mode)
Start of the after-import method for object type R3TR IOBJ (Activation Mode)
Characteristic 0LANGU: Lower case makes selection of char. values difficult
Start of the after-import method for object type R3TR ISFS (Activation Mode)
Source system SAPTDV210 does not exist
No mapping defined for source system XXXHRP210
RFC connection to source system XXXHRP210 is damaged ==> no Metadata upload
Source system SAPTDV210 does not exist
Start of the after-import method for object type R3TR ISMP (Activation Mode)
Source system SAPTDV210 does not exist
No mapping defined for source system XXXHRP210
Source system SAPTDV210 does not exist
Start of the after-import method for object type R3TR ISTS (Activation Mode)
There is no DataSource with these attributes
Reference to transfer structure 0ACTIONREAS_TEXT_BA not available. No activation possible.
There is no DataSource with these attributes
Reference to transfer structure 0ACTIONTYPE_TEXT_BA not available. No activation possible.

hi Simmi,
seems several errors
1. first you have to do source system mapping in your TARGET system (or you have to do correction since you change to new source system), from the log, i assume SAPTDV210 is the new SAP assigned (in bw dev/source), and e.g your target is SAPTQA999 then in SAPTQA999 do rsa1->tools->source system mapping, and fill up SAPTDV210 in 'orgsrc..'(first column) and SAPTQA999 in 'trgsrc..'(last column?) and save.
2. XXXHRP210 ? if this system still exist, right click this source system and 'restore'.
3. 0ACTIONREAS and 0ACTIONTYPE datasource doesn't exist in target system, in target system have you replicate from r/3 ?
if problem not solve in one go, would help if you specify bw dev name and target name, also r/3 new and old.
hope this helps.

BP Transport Acknowledgement problem...

Hi,
In, XI3.0 stack 11, Business process have two SEND STEPs one for PO and another one for GI and the required condition is GI idoc should get posted only after posting PO idoc.
As of now I have put transport acknowledgement in the first send step so that once all PO idocs are sent to r/3 then only the second SEND step will post the GI idocs.
But transport acknowledgement works only if I keep refreshing the sxmb_moni. If I drop a file and not opening the sxmb_moni for say one hour or one day the second SEND step is not getting processed. Only if I click refresh or open the sxmb_moni again, it is processing the next send step and post the GI idoc.
Could any one help me to resolve the strange behaviour of transport acknowledgement? Is sxmb_moni something to do with getting any acknowledgement? What is happening in the background while refeshing the sxmb_moni?
thanks,
sasikumar

When copying systems, you should never copy one system alone, but always CRM and ECC at the same time. Since both are closely coupled and both contain tables, in which it is described which kunnr is mapped to which CRM GUID, it is without alot of effort and deep middleware knowledge not possible to reactivate the data exchange properly. But even then you have to make sure that in both systems either the same partner numbers do not already exist or clear one system from all existing partners. Some of these mapping tables are i.e. CRMM_BUT_CUSTNO and CRMM_BUT_CONTNO, which contain the mapping information that is now obsolete. Usually these tables should be the same in CRM and ECC (and the data also), but in your case this is not true unfortunately. Even an initial download does not help as this is looking at these tables.
Alternatively if you make a customizing client copy of the CRM this new client can be connected to the ECC much easier as you do not have to remove data from the client. However, of course you still need to make an initial DNL.
Hope this helps, Kai

ABAP commands are obsolete.

Hi all,
Currently my firm is doing the 4.6C to ECC6 upgrade, there's a few programs having obsolete errors and I'm tasked to correcting the coding of this certain program. Here is the coding and the errors i encounter:
report YPU0014 line-size 360
               line-count 65
               no standard page heading.
selection-screen begin of block b1 with frame title text-010.
select-options: s_banfn for eban-banfn,                "PR No
                s_badat for eban-badat,                "PR Create Date
                s_ekgrp for eban-ekgrp,                "PR Purch Group
                s_frgkz for eban-frgkz,                "PR Rel Ind
                s_werks for eban-werks,                "PR Plant
                s_matnr for eban-matnr,                "PR Material
                s_lgort for eban-lgort.                "PR Stor Loc
selection-screen end of block b1.
selection-screen begin of block b2 with frame title text-020.
parameters:     prs01 radiobutton group prst default 'X',
                prs02 radiobutton group prst,
                prs03 radiobutton group prst.
selection-screen end of block b2.
selection-screen begin of block b3 with frame title text-030.
parameters:     pos01 radiobutton group post default 'X',
                pos02 radiobutton group post,
                pos03 radiobutton group post.
selection-screen end of block b3.
* INTERNAL TABLES
data: begin of ITAB occurs 0,   *(error: Tables with headers are no longer supported in the OO context.)*
            BANFN LIKE EBAN-BANFN,            "PR No
            BADAT LIKE EBAN-BADAT,            "PR Date
            MATNR LIKE EBAN-MATNR,            "Material No
            TXZ01 LIKE EBAN-TXZ01,            "Short Text
            LFDAT LIKE EBAN-LFDAT,            "Delv Date
            MENGE LIKE EBAN-MENGE,            "Requested Qty
            MEINS LIKE EBAN-MEINS,            "Unit of Measure
            PREIS LIKE EBAN-PREIS,            "Price Unit
            WAERS LIKE EBAN-WAERS,            "Currency
            AFNAM LIKE EBAN-AFNAM,            "Requistioner
            BNFPO LIKE EBAN-BNFPO,            "Item No
            BEDAT LIKE EBAN-BEDAT,            "PO Date
            BSART LIKE EBAN-BSART,            "Doc Type
            BSMNG LIKE EBAN-BSMNG,            "Ordered Qty
            MEIN2 LIKE EBAN-MEINS,            "PR UOM
            EBELN LIKE EBAN-EBELN,            "PO No
            EBELP LIKE EBAN-EBELP,            "PO Item No
            EKGRP LIKE EBAN-EKGRP,            "Purch Group
            EKORG LIKE EBAN-EKORG,            "Purch Org
            EMLIF LIKE EBAN-EMLIF,            "Vendor
            FRGDT LIKE EBAN-FRGDT,            "Release Date
            FRGGR LIKE EBAN-FRGGR,            "Release Grp
            FRGKZ LIKE EBAN-FRGKZ,            "Release Ind
            FRGZU LIKE EBAN-FRGZU,            "Release Stat
            INFNR LIKE EBAN-INFNR,            "Info Rec
            KNTTP LIKE EBAN-KNTTP,            "Acct Assgn Cat
            LGORT LIKE EBAN-LGORT,            "Storage Loc
            LOEKZ LIKE EBAN-LOEKZ,            "Deld Indicator
            GSFRG LIKE EBAN-GSFRG,            "Overall PR Rel
            STATU LIKE EBAN-STATU,            "Processing Stat
            WAER2 LIKE EBAN-WAERS,            "Currency
            WEBAZ LIKE EBAN-WEBAZ,            "GR Process Time in Days
            WERKS LIKE EBAN-WERKS,            "Plant
       end of ITAB.
data: prfnd(1) type c,
      pofnd(1) type c.
*top-of-page
top-of-page.
format color col_heading.
     write: /1 sy-repid, 150 'Allied Technologies (S) Pte Ltd',
            314 'Date:',
            320 sy-datum.
     write: /1 sy-uname,
            160 'PR Listing',
            314 'Time:',
            320 sy-uzeit.
     write: 330 'Page:', sy-pagno.
     uline.
     write : /1 'PR No', 11 'PR Date', 22 'Material', 42 'Short Text',
             65 'Deld Date', 84 'Qty Reqd', 95 'UOM', 103 'Price Unit',
             115 'Curr', 120 'Requisitioner', 134 'Itm No',
             141 'PO Date', 152 'DocType', 161 'Ord Qty', 175 'UOM',
             180 'PO No', 192 'Itm No', 200 'PurGrp',
             208 'PurOrg', 216 'Vendor', 228 'Rel Date',
             239 'RelGrp', 246 'RelInd', 254 'RelStat',
             263 'Info Record', 278 'AA Cat', 285 'Str Loc',
             295 'Deleted', 304 'Overall Rel', 316 'Procd Stat',
             328 'Curr', 334 'GR Time', 344 'Plant'.
uline.
skip.
end-of-selection.
perform get_data.
perform output_data.
*      Form get_data
form get_data.
clear itab.
select * from eban where banfn in s_banfn and   *(error: SELECT without an INTO clause is not supported in the OO context. Use "SELECT... INTO wa".)*
                           badat in s_badat and
                           frgkz in s_frgkz and
                           werks in s_werks and
                           matnr in s_matnr and
                           lgort in s_lgort and
                           ekgrp in s_ekgrp.
      move 'N' to prfnd.
    if prs01 = 'X' and eban-loekz = 'X'.
      move 'Y' to prfnd.
      perform get_porecord.
    endif.
    if prs02 = 'X' and eban-loekz ne 'X'.
       move 'Y' to prfnd.
       perform get_porecord.
    endif.
    if prs03 = 'X'.
       move 'Y' to prfnd.
       perform get_porecord.
    endif.
    if prfnd = 'Y' and pofnd = 'Y'.
        move-corresponding eban to itab.
        select single * from ekko where ebeln = eban-ebeln.    *(error: SELECT without an INTO clause is not supported in the OO context. Use "SELECT... INTO wa".)*
          if sy-subrc = 0.
            move ekko-lifnr to itab-emlif.
          endif.
        append itab.    *(error: An explicit work area is necessary in the OO context. Use " APPEND wa TO ITAB [SORTED BY])*
        clear itab.
    endif.
endselect.
endform.
form get_porecord.
      move 'N' to pofnd.
      if pos01 = 'X' and eban-statu ne 'B'.
         move 'Y' to pofnd.
      endif.
      if pos02 = 'X' and eban-statu = 'B'.
         move 'Y' to pofnd.
      endif.
      if pos03 = 'X'.
         move 'Y' to pofnd.
      endif.
endform.
* Output selected records to screen
form output_data.
sort itab by banfn badat matnr.
loop at itab.               *(error: At "LOOP AT ITAB", one of the additions "INTO", "ASSIGNING", or "TRANSPORTING NO FIELDS" is required. )*
    write: /1(10) itab-banfn, 11(10) itab-badat, 22(18) itab-matnr,
           42(20) itab-txz01, 65(10) itab-lfdat,
           78(15) itab-menge decimals 2,
           95(3) itab-meins, 100(14) itab-preis, 115(3) itab-waers,
          120(12) itab-afnam, 134(5) itab-bnfpo, 141(10) itab-bedat,
          152(4) itab-bsart, 158(15) itab-bsmng decimals 2,
          175(3) itab-mein2, 180(10) itab-ebeln, 192(5) itab-ebelp,
          200(3) itab-ekgrp, 208(4) itab-ekorg, 216(10) itab-emlif,
          228(10) itab-frgdt,
          240(2) itab-frggr, 248(1) itab-frgkz, 256(8) itab-frgzu,
          266(10) itab-infnr, 280(1) itab-knttp, 287(4) itab-lgort,
          298(1) itab-loekz, 308(1) itab-gsfrg, 320(1) itab-statu,
          329(5) itab-waers, 335(3) itab-webaz, 345(4) itab-werks.
endloop.
skip 1.
write: /25.
May i know how do i recode the areas with the errors?
Thank you for all the help i could get.

From this message ("error: Tables with headers are no longer supported in the OO context."), I'm thinking you are pasting this code inside a Class method. Do not.
But if you intend to make this as an individual report, it should work. Should it still show the same errors as "error: At "LOOP AT ITAB", one of the additions "INTO", "ASSIGNING", or "TRANSPORTING NO FIELDS" is required.", please add the TABLES statement at the top of your code.
(to show:)
report YPU0014 line-size 360 line-count 65 no standard page heading.
TABLES:
    itab
selection-screen begin of block b1 with frame title text-010.
Or better yet, see these changes
OLD
       data: begin of ITAB occurs 0,   *(error: Tables with headers are no longer supported in the OO context.)*
            BANFN LIKE EBAN-BANFN,            "PR No
            BADAT LIKE EBAN-BADAT,            "PR Date
            MATNR LIKE EBAN-MATNR,            "Material No
       end of ITAB.
NEW
       TYPES:
           begin of STAB,
            BANFN LIKE EBAN-BANFN,            "PR No
            BADAT LIKE EBAN-BADAT,            "PR Date
            MATNR LIKE EBAN-MATNR,            "Material No
          end of ITAB
       DATA:
         itab TYPE TABLE OF stab
As for the SELECT statements
OLD
    select * from eban where banfn in s_banfn and...
    " *(error: SELECT without an INTO clause is not supported in the OO context. Use "SELECT... INTO wa".)*
NEW
    DATA: wa_eban TYPE eban.
    select * from eban INTO wa_eban where banfn in s_banfn and...
    " and replace all uses of "eban" inside the select loop with wa_eban
   if prs01 = 'X' and wa_eban-loekz = 'X'.
    " DO THE SIMILAR THING WITH THE OTHER SELECT STATEMENTS
As for itab
OLD
loop at itab.
*(error: At "LOOP AT ITAB", one of the additions "INTO", "ASSIGNING", or "TRANSPORTING NO FIELDS" is required. )*
NEW
DATA: wa_tab LIKE LINE OF itab.
LOOP AT itab INTO wa_tab.
    " replace all occurences of tab with wa_tab inside the loop
   write: /1(10) wa_tab-banfn, 11(10) wa_tab-badat,...
ENDLOOP.
would really make me smile today
Edited by: Thomas Zloch on Jul 13, 2010 11:45 AM

REG: Obsolete statements in SLIN ecc 5.0

Hi all,
When i am executing the ABAP EPC for obsolete statements.(with Also display Hidden Messages)
I get the 2 Obsolete statements and as following :
      Program: ZXXXXX     Row:    652
The current ABAP command is obsolete and problematic, especially so in ABAP
Objects
An explicit work area is necessary in the OO context. Use "APPEND wa TO S_WERKS
[SORTED BY]".
(The message can be hidden with "#EC *)
Program: ZXXXXX     Row:   2558
The current ABAP command is obsolete and problematic, especially so in ABAP
Objects
At "LOOP AT itab", one of the additions "INTO", "ASSIGNING", or "TRANSPORTING NO
FIELDS" is required. in the OO context.
(The message can be hidden with "#EC *)
Though i put the "#EC after above variable still i can see it in the SLIN overview.
Pls help me to hide these Obsolete statements.
Thanks and Regards
Srikanth.P

Lest you find yourself labelled as "out of date" or "obsolete", perhaps you could spend a little time to bring your coding practices up to the state of the product. A LOT of things used in ABAP within my 12 years are now obsolete. For instance, the "Official ABAP Programming Guidelines" by SAP Press, written by Drs. Thummel and Keller, describes FORM....ENDFORM and REFRESH as obsolete.
In current versions, we loop at ...assgining <Field-symbol> or into structure....
We do read table into structure or assigning <field-symbol> or (where possible) transporting no fields.
We don't have tables with header rows, since those can't be used in OO.
We don't use REFRESH, we use CLEAR tabname[].
In OO, we use the SoC, software layering concepts, with GUI, Application and Persistence level Class definitions and implementations.
We used class-based exception handling where possible to avoid abends which are, of course, detrimental to our users' experiences.
etc.

Transporting of z objects form Older version(4.6c) to newer version(ecc6.0)

Hi All,
Now i am involving in Technical Upgradation from 4.6C to ECC60.I want to know some information regarding transportation of Z objects in older version to newer version(ECC6.0).Please help me in this regard.
like tables,dataelements,domains,reports,scripts,smartforms,userexists,Variants,report layouts(all are z objects),text elements.In the above list which will be transported automatically and regarding which abapers have to takencare i mean to say which will be not transported automatically...
and tell me obsolete keywords information..which will be obsoleted in ECC6.0...
thanks in advance
awaitinf for reply..
Points will be Rewarded for helpfull Answeres
Thanks & Regards
Samit

Hi Julio,
you can find the answer in the SAP note
Note 552711 - FAQ: Client copy
point 4.
So the answer is : NO
Kind regards
Imre Takácsi-Nagy
Senior Support Consultant II.
SAP Global Support Center Austria
Netweaver WEB Application Server ABAP / JAVA

How to Transport Standard Tetxts?

Hi Experts,
Pls. clarify me simple doubts that,
1) How to Transport the Standard Texts, which r cretaed in SO10?
2) Wht is customising tbl?
thanq.

Hi
For Standard Text problem..
You can use program : RSTXTRAN
Navigation -> goto SE38 -> enter RSTXTRAN -> execute ->
Name of correction -
text key -object - TEXT
text key- name - enter standard text name
Text id - ST
Text key language - EN
execute now -> select text here -> enter -> now click on push button trsfr texts to corr -> you will get pop up window( request)
==================================
About Customizing Tables..
Definition
The Customizing data in a customer client is not overwritten by a language import or an upgrade. Data is only imported into client 000.
This is because Customizing data is the responsibility of the customer and cannot be overwritten by data from SAP. This also applies, without restrictions, to translations.
However, customers may occasionally want to update their sample data and default settings with the latest translations from SAP.
Use the report RSREFILL and a reference language to update translations in a customer client.
For more information about this program, see the documentation on RSREFILL and Note 48047.
Note that the link between the translation environment and the Change and Transport System enables you to create translations for texts in one system, record them in transport requests, and then distribute them to other systems in your system landscape. As of Release 4.6C, the old SMLT function for supplying Customizing data with the SAP standard translation (normally only imported into client 000) is obsolete.
To translate Customizing data, proceed as follows:
   1. Use Transaction SMLT to import the language packages you need. This imports the SAP data into client 000 according to the specifications in the Notes mentioned above.
   2. Create the Customizing data in the customer client.
   3. Use the report RSREFILL to synchronize as many of the translations as possible with client 000. Read the documentation on RSREFILL before doing this.
   4. Use Transaction SE63 to translate any other Customizing texts. Record your translation work in transport requests and then use the Change and Transport System to distribute them in the system landscape.
<b>Rewards points if it is useful</b>
Thanks & Regards
ilesh 24x7

Inconsistant transport requests after local client copy

Dear experts,
our IT department just made a local client copy with profile SAP_ALL, by which all the transport requests had been copied, too, including quite a lot of workbench and customizing orders in status changeable. I'm supposed to do some basic setup and cleanup in the new client, but I'm confronted with problems like objects being locked in orders/requests that cannot be changed in the new client, as they belong to the original source client.
How can I get rid of those inconsistencies? I'd preferred the new client without transports and without locked objects. Is it really necessary that I clean up this mess manually? Would it have been better to clean this up before the client copy? Or could we just do the client copy with another profile in order to avoid those problems?
Thanks for your appreciated help
Andreas

Hello,
Transports are NEVER part of a client copy.
In fact all the data of your transports is stored in tables that are client independent (E07* tables).
This means that you can view (not edit) always all transports from all clients in a specific system.
When you want to edit or release a transport the source client is important (in which client was the transport originally created).
This is stored in table E070C for all transports and can not be overruled.
So I recommend that you don't clean anything related to transports after a client copy because this will also impact the other clients !
Success.
Wim

Problem releasing workbench transports

We had created a number of changelists in our workbench and are trying to release these to transport them into out test system. When we release the transports which are created without issue in the development workbench we get the following message:
Preparation for export
Transport request   : CRDK903862
System              : CRD
tp path             : tp
Version and release: 372.04.57 700
Execution of the export pre-processing methods for request CRDK903862
Start: Execution of object-specific export pre-processing methods
Changelist C647D7C9CCE64307AFC4F46272840107 is not complete in this system
Request CRDK903862 is modifiable after error during release
Preparation for export
End date and time : 20090925164345
Ended with return code: ===> 8 <===
The Transport Agent Service is already activated.
Has anyone any idea what the problem could be
Thanks in advance

Hi,
You need to first check which TranportOrder ID was not getting released on the server .
Then fire the below query to find the changelists associated with that TransportOrder in the ARS database-
select * from changelist where state <>0 and transportorderid ='<Name of that Transport Order ID>'
Then follow these steps -
1. Stop the Transport Agent in Source repository.
2. Cleanup the blobs from WBTRCL, WBTRBLOB, WBTRBSEG tables
   in ars repository for the changelists, which were associated with
that specific transport order.
DELETE FROM WBTRCL WHERE CLID = <cHANGELIST ID> (GIVE WITHOUT 0X)
DELETE FROM WBTRBSEG WHERE CLID = <cHANGELIST ID> (GIVE WITHOUT 0X)
DELETE FROM WBTRBSEG WHERE CLID = <cHANGELIST ID> (GIVE WITHOUT 0X)
3. Use the transaction SMOBDELCL to remove details of this
   changelist from the CRM server. This transaction
   would require you to enter the id of the changelist.
   The id should be entered without 0x.
4. Create a new change request in the CRM server and add these
changelists to the change request.
5. Steps 1-5 of Note 568624 can be followed for this but NOT steps
   6 and 7.DO NOT release the change request. There is no need to modify
   the TransportOrderId field in changelist table in ARS repository to
   reflect the new change request id.The field is there for
   documentation purpose only.
6. Update the state of the changelist in ARS repository to 1 so that
   Transport Agent can pickup the changelist and send it to server as
   soon as it is started.
Eg:
UPDATE CHANGELIST SET STATE = 1 WHERE CHANGELISTID = <0XChangelistID>
(GIVE WITH 0X)
7. Start the Transport Agent on both Source repository.
Also, you need to make sure that whenever you release a changelist from Mobile Application Studio then
you should not chose this transport Order(which was not getting released earlier) while choosing the transport
Order.

Transport management in EP??

Hello All,
I need to preapre one document for the Transport strategy for SAP EP 7.0.Can anyone plaese send me any link or document.We are having the stand alone java for EP 7.0.I need to know how the changes take place in EP?

Hi,
Transport of Portal Object :-
http://help.sap.com/saphelp_nw04/helpdata/en/1c/f785f15141324c98c5fc71e467d788/frameset.htm
Transporting KM
ice protocols :- How to Export KM Contents by ICE protocol using Offline Channel
KM Transports: Part V
SAP Notes :-
u2022 696084 EP 6.0: How to create SDA files for EPA or PAR files (sapmake_util.zip file)
u2022 788265 EP6.0 How To transport a Portal Desktop
u2022 1003674 Enhancement for non-ABAP systems in CTS
u2022 972495 NW 7.10 Portal Export: references to GPAL objects
u2022 937074 EP6.0 NW04: cleanup interval for transport process reports
u2022 588913 Central note for Import and Export for EP 6.0
u2022 679516 Central Note for the Transport Package Editor
u2022 725797 EP6.0 NW04: Export of PAR files within EPA packages
u2022 914382 PCD deployment fails due to locked objects
u2022 827768 Comparison between Migration and Transport
u2022 690310 EP 6.0: logging and tracing for transport
u2022 618161 EP6.0 Export/Import: avoid overwriting of system objects
u2022 737448 EP6: Import does not update cached objects
u2022 991599 EP: Cluster synchronization for imported PCD objects fails
u2022 906120 Import error when trying to import NWu201904s package in NWu201904
Thanks and Regards,
Jigar Oza

Obsolete transports cleanup

Similar Messages

Maybe you are looking for