SAP QM Inspecton set up details

can anyone ell me
in MM01 QM VIEW---Inspection Set up --- Details , there are various options for Check or Uncheck
how these are relates to each other ,WHICH OPTIONS TO BE CHECK ?
e.g.   RELATION BETWEEN   insp. with task list & sampling procedure
what is exactly DMR
how we use it

SACC001 wrote:
can anyone ell me
>
> in MM01 QM VIEW---Inspection Set up --- Details , there are various options for Check or Uncheck
> how these are relates to each other ,WHICH OPTIONS TO BE CHECK ?
>
> e.g.   RELATION BETWEEN   insp. with task list & sampling procedure
>
> what is exactly DMR
> how we use it
If you assign any inspection type in material master --> QM view then releavent checkbox and field with default set-up will appear over there. You can set default selection for inspection type @ SPRO --> QM --> quality inspection --> Define Default Values for Inspection Type. These predefine value you can change at QM view --> inspection type for each material.
If necessary you can check/uncheck each field/box value as per your business requirement. You can go through following link to understand each field/ check box importanse.
[http://help.sap.com/saphelp_erp60_sp/helpdata/en/61/2db434d6e3681ae10000009b38f83b/frameset.htm]
If you are selection "inspection with task list/ specification" then you don't need to enter "sampling procedure" here because this value drive from inspection plan or material sepcification. More information given in above link.
DMR is dynamiv modification rule and which is nothing but skkipping rule.  More info you can here.
[http://help.sap.com/saphelp_erp60_sp/helpdata/en/3c/929d11db7d11d283cb0000e829fdb3/frameset.htm]
Hope this helps.

Similar Messages

  • How to set Assignment details in RSBBS

    Hi Experts,
    RRI is used in dev.I want to know how to set assignment details.What's the meanning of
    Type ,selection type and required entry? pls be more specific.Thank you.
    Best regards,
    Gavin

    <b>Look at</b> ...explained wid examples
    http://help.sap.com/saphelp_nw04/helpdata/en/a2/9b548d979de04180d15b5a55aa94aa/frameset.htm
    Post back for any further questions ...

  • How to create the Sap script & Layout Set (wants sample code)

    Hi All ,
    Can you please provide me the step by step procedure
    to create the Sap script & Layout Set .(please provide sample
    code/links /docs for layout & print program).
    Regards
    Rahul

    hi,
    go through the following links  what i found to create sap script.
    http://www.thespot4sap.com/Articles/SAPscript_Introduction.asp
    http://abapliveinfo.blogspot.com/2008/01/free-sapscript-made-easy-46-book.html
    http://www.thespot4sap.com/articles/SAPscript_example_code.asp
    http://idocs.de/www3/cookbooks/sapscript/sapscript_1/docu.htm
    http://idocguru.com/www5/cookbooks/sapscript/sapscript_1/example.htm
    www.geocities.com/wardaguilar25/sapscript-tutorial.html
    http://logosworld.de/www3/cookbooks/sapscript/sapscript_8/docu.htm
    how to create a  scripts?give steps?
    https://forums.sdn.sap.com/click.jspa?searchID=1811669&messageID=2969311
    https://forums.sdn.sap.com/click.jspa?searchID=1811669&messageID=2902391
    https://forums.sdn.sap.com/click.jspa?searchID=1811669&messageID=3205653
    https://forums.sdn.sap.com/click.jspa?searchID=1811669&messageID=3111402
    http://www.sap-img.com/sapscripts.htm
    http://sappoint.com/abap/
    http://www.henrikfrank.dk/abapexamples/SapScript/sapscript.htm
    http://help.sap.com/saphelp_crm40/helpdata/en/16/c832857cc111d686e0000086568e5f/content.htm
    http://www.sap-basis-abap.com/sapabap01.htm
    http://www.sap-img.com/sapscripts.htm
    http://searchsap.techtarget.com/tip/1,289483,sid21_gci943419,00.html
    http://sap.ittoolbox.com/topics/t.asp?t=303&p=452&h2=452&h1=303
    http://www.sapgenie.com/phpBB2/viewtopic.php?t=14007&sid=09eec5147a0dbeee1b5edd21af8ebc6a
    Other Links

  • Do you trust the SAP standard rule set ?

    Hello all,
    I have the impression that, too often, the SAP standard ruleset has been taken for granted : upload, generate and use. Here is a post as to why not to do so. Hopefuly, this will generate a interesting discussion.
    As I have previously stated in other threads, you should be very careful accepting the SAP standard rule set without reviewing it first. Before accepting it, you should ensure that your specific SAP environment has been reflected in the functions. The 2 following questions deal with this topic :
    1. what is your SAP release  ? ---> 46C is different than ECC 6.0 in terms of permissions to be included in the function permission tab. With every SAP release, new authorization objects are linked to SAP standard tcodes. Subsequently some AUTHORITY-CHECK statements have been adapted in the ABAP behind the transaction code. So, other authorizations need to provided from an implementation point of view (PFCG). And thus, from an audit perspective (GRC-CC), other settings are due when filtering users' access rights in search for who can do what in SAP.
    2. what are your customizing settings and master data settings ? --> depending on these answers you will have to (de)activate certain permissions in your functions. Eg. are authorization groups for posting periods, business areas, material types, ... being used ? If this is not required in the SAP system and if activated in SAP GRC function, then you filter down your results too hard, thereby leaving certain users out of the audit report while in reality they can actually execute the corresponding SAP functionality --> risk for false negatives !
    Do not forget that the SAP standard ruleset is only an import of SU24 settings of - probably - a Walldorf system. That's the reason SAP states that the delivered rule set is a starting point. 
    So, the best practice is :
    a. collect SAP specific settings per connector in a separate 'questionnaire' document, preferably structured in a database
    b. reflect these answers per function per connector per action per permission by correctly (de)activating the corresponding permissions for all affected functions
    You can imagine that this is a time-consuming process due to the amount of work and the slow interaction with the Java web-based GRC GUI. Therefore, it is a quite cumbersome and at times error-prone activity ...... That is, in case you would decide to implement your questionnaire answers manually. There are of course software providers on the market that can develop and maintain your functions in an off-line application and generate your rule set so that you can upload it directly in SAP GRC. In this example such software providers are particularly interesting, because your questionnaire answers are structurally stored and reflected in the functions. Any change now or in the future can be mass-reflected in all (hundreds / thousands of) corresponding permissions in the functions. Time-saving and consistent !
    Is this questionnaire really necessary ? Can't I just activate all permissions in every function ? Certainly not, because that would - and here is the main problem - filter too much users out of your audit results because the filter is too stringent. This practice would lead too false negatives, something that auditors do not like.
    Can't I just update all my functions based on my particular SU24 settings ? (by the way, if you don't know what SU24 settings are, than ask your role administrator. He/she should know. ) Yes, if you think they are on target, yes you can by deleting all VIRSA_CC_FUNCPRM entries from the Rules.txt export of the SAP standard rule set, re-upload, go for every function into change mode so that the new permissions are imported based on your SU24 settings. Also, very cumbersome and with the absolute condition that you SU24 are maintained excellent.
    Why is that so important ? Imagine F_BKPF_GSB the auth object to check on auth groups on business areas within accounting documents. Most role administrator will leave this object on Check/Maintain in the SU24 settings. This means that the object will be imported in the role when - for example - FB01 has been added in the menu.  But the role administrator inactivates the object in the role. Still no problem, because user doesn't need it, since auth groups on business areas are not being used. However, having this SU24 will result in an activated F_BKPF_GSB permission in your GRC function. So, SAP GRC will filter down on those users who have F_BKPF_GSB, which will lead to false negatives.
    Haven't you noticed that SAP has deactivated quite a lot of permissions, including F_BKPF_GSB ? Now, you see why. But they go too far at times and even incorrect. Example : go ahead and look deeper into function AP02. There, you will see for FB01 that two permissions have been activated. F_BKPF_BEK and F_BKPF_KOA.  The very basic authorizations needed to be able to post FI document are F_BKPF_BUK and F_BKPF_KOA.  That's F_BKPF_BUK .... not F_BKPF_BEK. They have made a mistake here. F_BKPF_BEK is an optional  auth object (as with F_BKPF_GSB) to check on vendor account auth groups.
    Again, the message is : be very critical when looking at the SAP standard rule set. So, test thoroughly. And if your not sure, leave the job to a specialized firm.
    Success !
    Sam

    Sam and everyone,
    Sam brings up some good points on the delivered ruleset.  Please keep in mind; however, that SAP has always stated that the delivered ruleset is a starting point.  This is brought up in sap note 986996     Best Practice for SAP CC Rules and Risks.  I completely agree with him that no company should just use the supplied rules without doing a full evaluation of their risk and control environment.
    I'll try to address each area that Sam brings up:
    1.  Regarding the issue with differences of auth objects between versions, the SAP delivered rulset is not meant to be version specific.  We therefore provide rules with the lowest common denominator when it comes to auth object settings.
    The rules were created on a 4.6c system, with the exception of transactions that only exist in higher versions.
    The underlying assumption is that we want to ensure the rules do not have any false negatives.  This means that we purposely activate the fewest auth objects required in order to execute the transaction.
    If new or different auth object settings come into play in the higher releases and you feel this results in false positives (conflicts that show that don't really exist), then you can adjust the rules to add these auth objects to the rules.
    Again, our assumption is that the delivered ruleset should err on the side of showing too many conflicts which can be further filtered by the customer, versus excluding users that should be reported.
    2.  For the customizing settings, as per above, we strive to deliver rules that are base level rules that are applicable for everyone.  This is why we deliver only the core auth objects in our rules and not all.  A example is ME21N. 
    If you look at SU24 in an ECC6 system, ME21N has 4 auth objects set as check/maintain.  However, in the rules we only enable one of the object, M_BEST_BSA.  This is to prevent false negatives.
    3.  Sam is absolutely right that the delivered auth object settings for FB01 have a mistake.  The correct auth object should be F_BKPF_BUK and not F_BKPF_BEK.  This was a manual error on my part.  I've added this to a listing to correct in future versions of the rules.
    4.  Since late 2006, 4 updates have been made to the rules to correct known issues as well as expand the ruleset as needed.  See the sap notes below as well as posting Compliance Calibrator - Q2 2008 Rule Update from July 22.
    1083611 Compliance Calibrator Rule Update Q3 2007
    1061380 Compliance Calibrator Rule Update Q2 2006
    1035070 Compliance Calibrator Rule Update Q1 2007
    1173980 Risk Analysis and Remediation Rule Update Q2 2008
    5.  SAP is constantly working to improve our rulesets as we know there are areas where the rules can be improved.  See my earlier post called Request for participants for an Access Control Rule mini-council from January 28, 2008.  A rule mini-council is in place and I welcome anyone who is interested in joining to contact me at the information provided in that post.
    6.  Finally, the document on the BPX location below has a good overview of how companies should review the rules and customize them to their control and risk environment:
    https://www.sdn.sap.com/irj/sdn/bpx-grc                                                                               
    Under Key Topics - Access Control; choose document below:
        o  GRC Access Control - Access Risk Management Guide   (PDF 268 KB) 
    The access risk management guide helps you set up and implement risk    
    identification and remediation with GRC Access Control.

  • Please Help, Data Set Master/Detail with mySQL DB

    Hi...
    I installed the Data Set Master/Detail Sample (states and
    citys autopopulate) getting values from a XML file...
    when a user adds a listing in my site, it works great.. i use
    the XML file values for the states/citys and then everything is
    stored in a DB... BUT i need to do this..
    when he comes back to edit his listing, i want the Data Set
    Master/Detail to show hes values (from de DB) with the option to
    edit them, not the first XML file values.
    Thanks

    Thank you kinblas!!!!!
    I saw another post with the solution!!!
    Here it is
    http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=602&threadid =1308016&highlight_key=y&keyword1=SetDefaultState
    Thanks again!

  • SAP GUI timeout setting

    Hi,
    How is the SAP GUI timeout setting done?
    Thank you.

    Hi Lammie,
    Strange. If that's happening, then definitely there should be some user-specific settings somewhere. Or maybe it has something to do with the profiles in RZ10. I don't know if it's possible but maybe the profiles can be associated with users and in your case, different ones are associated to your user and your colleagues's users.
    Best regards,
    Akshat

  • Worked on the SAP-Script layout sets in MM modules.

    sir,
    Like to know How would  Worked on the SAP-Script layout sets in MM modules.

    Hi,
    First of all what are we trying to achieve?
    I understand that changes where made to standard SAP SAPscript RVINVOICE01 and you where asked to make further changes.
    In SAP configuration you need to see what is the driver program for your SAPscript and what is the SAPscript name (transaction VOK2->Output->Processing Programs->Billing Documents) or via table TNAPR.
    This will allow you to see what is the driver program for your SAPscripr (this is the program that prepares data to be formatted by your SAPscript layour set).
    Once data is derived by an ABAP program, a sapscript is called from driver ABAP to print this data.
    You may need to make changes to driver ABAP (in case changes to data are required) or to SAPscript if changes to layout and window positioning are requested.
    Try not to modify standard SAP programs (copy to Z versions)...
    Hope it is of some help...
    Michael

  • Work on the SAP-Script layout sets in SD modules

    Hi,
         How to Work on the SAP-Script layout sets in SD modules. The documents modified were RVINVOICE01 as per the client’s requirements.

    Hi,
    First of all what are we trying to achieve?
    I understand that changes where made to standard SAP SAPscript RVINVOICE01 and you where asked to make further changes.
    In SAP configuration you need to see what is the driver program for your SAPscript and what is the SAPscript name (transaction VOK2->Output->Processing Programs->Billing Documents) or via table TNAPR.
    This will allow you to see what is the driver program for your SAPscripr (this is the program that prepares data to be formatted by your SAPscript layour set).
    Once data is derived by an ABAP program, a sapscript is called from driver ABAP to print this data.
    You may need to make changes to driver ABAP (in case changes to data are required) or to SAPscript if changes to layout and window positioning are requested.
    Try not to modify standard SAP programs (copy to Z versions)...
    Hope it is of some help...
    Michael

  • SAP language parameter setting

    Dears:
    The parameter zcsa/installed_languages which is in RZ10, control the sap language parameter setting, but i am not very understand how to set the value, i find some set the value to 123EM, i don't know that the 123 meaning here. And some just set it to DE2, D is for Germany, and E is for English, so what is 2 for? Do you know the standard value setting for this parameter?

    The language environment that comes with the standard SAP installation includes German and English. To use SAP with other languages, you must perform a language import or supplement (use transaction SMLT). Changes in the language environment usually require changes in the codepage setup, which requires changes in some database tables and in the profile files.
    Most language administration can be done with transactions SMLT and SP12, and reports RSCP0001, RSCP0004, RSCP0017, and RSCP0020.
    The codepage environment is summarized in the report RSCP0001. Running the report will generate a screen with codepage parameters drawn from different places. A proper codepage setup usually requires that all codepage parameters are the same. This table show the output of the RSCP0001 report, and where its data is drawn from:  Report output Source 
    1.  Table TCPDB   
    Code page for transparent data in the database  Entry in TCPDB table 
    Code page for non-transparent data in the
    database (for example, pools and clusters)  Entry in TCP0C table (can change from online report above) 
    2.  System profile parameters   
    Code page for transparent data in the database  install/codepage/db/transp = 8300 
    Code page for non-transparent data in the
    database (for example, pools and clusters)  install/codepage/db/non_transp = 8300 
    Code pages used by this application server  install/codepage/appl_server = 8300 
    Code pages used by SAPTEMU  saptemu/Codepage = 8300 
    For example, changes in the instance profile, for Traditional Chinese, might look like:
    Change Installed languages to include M (Traditional Chinese)
    zcsa/installed_languages = DEM
    Change to desired language for logon screen
    zcsa/system_language = E
    Add the following parameters for Chinese Character Set
    install/codepage/appl_server = 8300
    install/codepage/db/transp = 8300
    install/codepage/db/non_transp = 8300
    saptemu/Codepage = 8300
    abap/locale_ctype = Chinese(Taiwan)_Taiwan.950
    install/collate/active = 0
    abap/locale_all/needed = 0
    rscp/TCP0B = TCP0D
    abap/set_text_env_at_new_mode =1
    abap/import_char_conversion = 0

  • Disabling SAP* user and setting up Super Administration

    hi guys
    How to Disabling SAP* user and setting up Super Administration. Set up user groups, user permissions
    regards
    kamal

    Hi,
    Pls search on SDN , before u post.
    check this wiki link.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/ep/to%252breset%252badministrator%252bpassword%252bthrough%252bconfig%252btool
    Thanks

  • SAP BEX Analyzer Set values for variables

    Please help us out in sorting out this problem,
    We are automating BEx Analyzer for a Testing Project with Quick Test Professional (QTP) a functional automation tool uses VB script.
    Problem:
    There are 5 steps in automation
    Invoke BEx Application
    Log in to BEx server
    Run Query
    Set values for Variables for Query
    Display Report
    We are able to do 1,2,3 steps using BEx API functions and running BEx macros but we struck up with 4th step,
    1. Invoke BEx Application
    ‘Launch Excel
    Dim app
    Set app = createobject("Excel.Application")
    ‘Make it visible
    app.Visible = true
    ‘Attach add-in to Excel file
    app.Run ("'C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.xla'!SetStart")
    2. Log in to BEx server
    Login to Bex server
    Function logonToBW(app)
    Dim myConnection
    Dim logonToBW2
    On Error Resume Next
    logonToBW2 = True
    ' Create logon to system with following user and system details
    Set myConnection = app.Run ("'C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.xla'! SAPBEXgetConnection")
    With myConnection
    .client = "600"
    .User = "USERNAME"
    .Password = "Welcom123"
    .Language = "en"
    .systemnumber = "00"
    .System = "BWDCLNT600"
    .systemid = "BWD"
    .ApplicationServer = "156.158.7.161"
    .SAProuter = ""
    .Logon 0, true
         If .IsConnected = 0 Then
               .Logon 0, False
    If .IsConnected <> 1 Then
    MsgBox "Automatic logon failed. Please enter your username and password in the next screen ..."
    Exit Function
    End If
    End If
    End With
    ' Run connection query to see if connected
    app.Run ("'C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.xla'!SAPBEXinitConnection")
    logonToBW2 = True
    End Function
    3. Run a Query
    app.Run "'C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.xla'! runQuery", "ZZCCA3_M01_Q0003"
    Till here the script is running fine then the “Select values for Variables” window is displayed.
    This is where exactly we struck up; in this window we need to select values.
    Name of the Fields
         Field Name     Technical name of characteristic     Variable Name     Value
    1     Company Code                     0COMP_CODE     ZM_COMPCODE     1000
    2     Cost Center Hierarchy          0COSTCENTER     ZS_CCTRN     1000MDON
    3     Cost Center Node     0COSTCENTER     ZS_CCTRN     1000COP
    4     Cost Element          0COSTELEMENT     ZS_COELN     1000GDON_6999
    5     Fiscal Year     0FISCYEAR     0P_FYEAR     2007
    To select values for variables, we are trying below code but its giving an error,
    app.Run  "'C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.xla'!SAPBEXSetFilterValue", “1000”, "0COMP_CODE"
    app.Run  "'C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.xla'!SAPBEXSetFilterValue", “1000MDON”, " 0COSTCENTER "
    app.Run  "'C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.xla'!SAPBEXSetFilterValue", “1000COP”,  "0COSTCENTER"
    app.Run  "'C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.xla'!SAPBEXSetFilterValue", “1000GDON_6999”,  "0COSTELEMENT "
    app.Run  "'C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.xla'!SAPBEXSetFilterValue", “2007”,  " 0FISCYEAR"
    Any help highly appreciated, thanks in advance.

    Hi Reinhard,
    Pleas look at this:
    Passing a range to SAPBEX.XLA!SAPBEXSetFilterValue
    Best regards,
    Eugene

  • /usr/sap/trans/actlog - Increase log detail

    Hi everyone,
    I'm after away of logging when objects are added to deleted from a modifiable change request (eg I want to see the object details, who, and date/time.  I'm aware that when you create a new transport request/task that a log is created in /usr/sap/trans/actlog, however I was wondering if there was away to increase the detail level of what is written to the log file, or if someone knows of another way of tracking this information.
    Cheers
    Shaun

    Operating system level files in the transport process:
    The SAP C program TP, requires a special file structure for the transport process. The file system is operating system dependent. TP uses a transport directory or file system, which is called /usr/sap/trans.
    The /usr/sap/trans file system is generally NFS mounted form the development system to other systems unless a system is defined as a single system in the CTS pipeline. All the sub directories should have <SID>adm as the owner and sapsys as the group; and proper read, write and execute access should be given to owner and the group. The TP imports are always performed by <SID>adm.
    The following are the subdirectories in /usr/sap/trans:
    /data
    /cofiles
    /bin
    /log
    /actlog
    /buffer
    /sapnames
    /tmp
    /usr/sap/trans/data: holds the data of transport objects after they are released . This subdirectory contains files named R9<5 digits >. containing the exported objects. The example of a data file is R904073.DEV. The extension DEV means the data file was released from the DEV or development system.
    /usr/sap/trans/cofiles: The cofiles directory holds the command files for all change requests. This subdirectory contains command files named K9<5 digits>.. They contain, for example, import steps to be performed. files are like a command or control files used to import the data files. The common directory for CTS system is /usr/sap/trans. After a change request is released from the source system , the data is exported immediately to the file system of the operating system. The SAP transport utility TP uses the cofile to transport a data file. The example of a file in cofiles directory is K904073.DEV.
    /usr/sap/trans/bin: holds the most important file TPPARAM in the CTS system. TPPARAM file has all the information about the CTS systems in the CTS pipeline. TPPARAM file is the parameter file for the transport program TP and it is the common file for all the systems in the CTS pipeline. As you know already that /usr/sap/trans should be NFS mounted to all the systems in a CTS pipeline, TP program has access to the TPPARAM file from all the systems. The following is an example of typical TPPARAM file for five SAP systems in the CTS pipeline:
    #@(#) TPPARAM.sap 20.6 SAP 95/03/28
    # Template of TPPARAM for UNIX #
    # First we specify global values for some parameters, #
    # later the system specific incarnation of special parameters #
    # global Parameters #
    transdir = /usr/sap/trans/
    dbname = $(system)
    alllog = ALOG$(syear)$(yweek)
    syslog = SLOG$(syear)$(yweek).$(system)
    # System spezific Parameters #
    # Beispiel T11 #
    DEV/dbname = DEV
    DEV/dbhost = sap9f
    DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
    QAS/dbname = QAS
    QAS/dbhost = sap8f
    QAS/r3transpath = /usr/sap/QAS/SYS/exe/run/R3trans
    TRN/dbname = TRN
    TRN/dbhost = sap17
    TRN/r3transpath = /usr/sap/TRN/SYS/exe/run/R3trans
    PRE/dbname = PRE
    PRE/dbhost = sap19f
    PRE/r3transpath = /usr/sap/PRE/SYS/exe/run/R3trans
    PRD/dbname = PRD
    PRD/dbhost = sap18f
    PRD/r3transpath = /usr/sap/PRD/SYS/exe/run/R3trans
    /usr/sap/trans/log: holds the entire log files, trace files and statistics for the CTS system. This subdirectory contains all log files, such as ULOGs, ALOGs, SLOGs, log files named 9<5 digits>. for each executed step, and log files named . for steps that are collectively executed, for example, step N (structure conversion) and step P (move nametabs). When the user goes to SE09 (workbench organizer) or SE10 (customizing organizer) transaction and opens the log for a transport, the log file for that transport will be read from /usr/sap/trans/log directory. Each change request should have a log file. Examples of log files are DEVG904073.QAS, DEVI904073.QAS and DEVV904073.QAS. The name of a log file consists of the names of the change request, the executed step, and the system in which the step was executed:
    <source system><action><6 digits>.<target system>
    Now we can analyze the above example DEVG904073. QAS. The <source system> = DEV, <action> = G or report and screen generation, <6 digits> = 904073 (these six digits numbers are exactly the same number as the six digits of the transport) and the <target system> = QAS
    Possible values for <action> are:
    A: Dictionary activation
    D: Import of application-defined objects
    E: R3trans export
    G: Report and screen generation
    H: R3trans dictionary import
    I: R3trans main import
    L: R3trans import of the command files
    M: Activation of the enqueue modules
    P: Test import
    R: Execution of reports after put (XPRA)
    T: R3trans import of table entries
    V: Set version flag
    X: Export of application-defined objects.
    /usr/sap/trans/actlog: This subdirectory contains files named Z<6 digits> recording each action on a request or task, for example, creation, release, or change of ownership. The example of an action file is DEVZ902690.DEV. The following are the contents of the file:
    1 ETK220 “==================================================” “=================
    =============================
    1 ETK191 “04/30/1998″ Action log for request/task: “DEVK902690″
    1 ETK220 “==================================================” “=================
    =============================
    1 ETK185 “04/30/1998 18:02:32″ “MOHASX01″ has reincluded the request/task
    4 EPU120 Time… “18:02:32″ Run time… “00:00:00″
    1 ETK193 “04/30/1998 18:02:33″ “MOHASX01″ owner, linked by “MOHASX01″ to “DEVK902691″
    4 EPU120 Time… “18:02:33″ Run time… “00:00:00″
    1 ETK190 “05/04/1998 11:02:40″ “MOHASX01″ has locked and released the request/task
    1 ETK194 “05/04/1998 11:02:40″ **************** End of log *******************
    4 EPU120 Time… “11:02:40″ Run time… “00:00:09″
    ~
    ~”DEVZ902690.DEV” 10 lines, 783 characters
    /usr/sap/trans/buffer: This subdirectory contains an import buffer for each SAP System named after the SID. When a change request is released, the import buffer of the target systems is updated. Contains control information on which requests are to be imported into which systems and in what order the imports must occur. The /usr/sap/trans/buffer will have a directory for each system in the CTS pipeline. For example the buffer file for DEV system is /usr/sap/trans/buffer/DEV.
    /usr/sap/trans/sapnames: holds information pertaining to transport requests for each system user. This subdirectory contains files named after the user's logon name. A file is created for each SAP System user, who performs transport actions, and updated when the user releases a request. There are files for each user who released change requests from the system.
    /usr/sap/trans/tmp: holds information about temporary data and log files. While the transport is occurring the Basis administrator can find a file that is related to the transport in the tmp directory; that file shows the exact status if the transport (What objects are being imported at that time).
    Important SAP delivery class and table types and tables in the CTS process:
    Delivery class
    The delivery class defines who (i.e. the SAP system itself or the customer) is responsible for maintaining the table contents. In addition the delivery class controls how the table behaves in a client copy and an upgrade. For example when you select a SAP defined profiles to perform a client copy, certain tables are selected according to their delivery class. DD02L table can show what delevery class a table belongs to.
    The following delivery classes exist:
    A: Application table.
    C: Customizing table, maintenance by customer only.
    L: Table for storing temporary data.
    G: Customizing table, entries protected against overwriting.
    E: Control table.
    S: System table, maintenance only by SAP.
    W: System table, contents can be transported via own TR objects.
    Table type
    The table type defines whether a physical table exists for the logical table description defined in the ABAP/4 Dictionary and how the table is stored on the database.
    The following are different table types in SAP:
    Transparent Tables
    There is a physical table on the database for each transparent table. The names of the physical table and the logical table definition in the ABAP/4 Dictionary are same. For every transparent table in SAP, there is a table in database. The business and application data are stored in transparent tables.
    Structure
    No data records exist on the database for a structure. Structures are used for the interface definition between programs or between screens and programs.
    Append Structure
    An Append structure defines a subset of fields which belong to another table or structure but which are treated as a separate object in the correction management. Append structures are used to support modifications.
    The following table types are used for internal purposes, for example to store control data or for continuous texts:
    Pooled table
    Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated-pooled tables are stored.
    Cluster table
    Cluster tables contain continuous text, for example documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least part of the keys must agree. Several cluster tables are stored in one corresponding table on the database.
    Tables in CTS process:
    TRBAT and TRJOB:
    TRJOB and TRBAT are the major tables in the CTS process. After TP program has sent the event to the r3 system, RDDIMPDP checks table TRBAT in the target system to find out if there is an action to be performed. Mass activation, distribution, or table conversions are the examples of actions. If there is action to be performed, RDDIMPDP starts the appropriate program in the background task. RDDIMPDP then reschedules itself.
    By checking table TRJOB, RDDIMPDP automatically recognizes if a previous step was aborted, and restarts this step. For each transport request , TP program inserts an entry into table TRBAT. If the return code 9999 in this table then the step is waiting to be performed. Return code 8888 indicates that the step is active and currently being processed. A return code of 12 or less indicates that the step is finished. In addition, TP inserts a header entry to let the RDDIMPDP program know to start processing. The column return code will therefore contain a B for begin. When RDDIMPDP is started, it sets the header entry to R(un), and starts the required program. When all the necessary actions are performed for all the transport requests, the column return code contains all the return codes received, and the column TIMESTAMP contains the finishing time. The header entry is set to F(inished). TP monitors the entries in TRBAT and TRJOB tables. When the header entry in TRBAT is set to finished. The entry in TRJOB is deleted.
    Transport Tables SE06
    TDEVC – Development classes
    TASYS – Details of the delivery. Systems in the group that should automatically receive requests, have to be specified in table TASYS.
    TSYST – The transport layers will be assigned to the integration systems. ( Define all systems)
    TWSYS – Consolidation routes ( define consolidation path)
    DEVL – Transport layers are defined here
    In “Configuring the CTS system” section, We will learn more about the transport tables in SE06 transaction
    Programs in the CTS process:
    In the CTS table section we learned about the RDDIMPDP program. RDDIMPDP program needs to be scheduled in all the clients in an instance. It is recommended to schedule the RDDIMPDP as event driven.
    RDDPUTPP and RDDNEWPP programs can be used to schedule RDDIMPDP program in the background.
    The ABAP/4 programs that RDDIMPDP starts are determined by the transport step to be executed that is entered in the function field of table TRBAT.
    Function Job Name Description of transport Steps
    J RDDMASGL Activation of ABAP/4 dictionary objects
    M RDDMASGL Activation of match codes and lock objects
    S RDDDISOL Analysis of database objects to be converted
    N RDDGENOL Conversion of database objects
    Y RDDGENOL Conversion of matchcode tables
    X RDDDICOL Export of AD0 objects
    D RDDDIC1L Import of AD0 objects
    E RDDVERSE Version management update during export
    V RDDVERSL Version management update during import
    R RDDEXECL Execution of programs for post – import processing
    G RDDDIC3L Generation of ABAP/4 programs and screens
    Version Management:
    One of the important features of Workbench Organizer is Version Management. This feature works for all the development objects. Using the version management feature the users can compare and retrieve previous versions of objects.
    Version management provides for comparisons, restore of previous versions, documentation of changes and assistance in the adjustment of data after upgrading to a new release. With the release of a change request, version maintenance is automatically recorded for each object. If an object in the system has been changed N times, it will have N delta versions and one active version. To display version management, for ABAPs use transaction SE38 and for tables, domains and data elements use SE11. The path to follow is Utilities -> Display version. Using version management the users can view existing version for previously created ABAP code, make changes to the code, compare code versions and restore original version of the code. Now the users will be restore previous versions without cut and paste steps of the past.
    TP and R3trans program:
    The basis administrator uses TP program to transport SAP objects from one system to another. TP is a C program delivered by SAP that runs independently of the R/3 system. TP program uses the appropriate files located in a common transport directory /usr/sap/trans. TP starts C programs, ABAP/4 programs and special operating system commands to its job. R3trans is one of the most important utility program called by TP. Before using the TP program, the basis administrator needs to make sure that the CTS system is setup properly and the right version of TP is running in the system. The TP program is located in the run time directory /usr/sap/<SID>/SYS/exe/run directory. It is automatically copied in the install process. A global parameter file TPPARAM that contains the databases of the different target systems and other information for the transport process controls TP. The global parameter file determines which R3trans is used for each system. If the parameter r3transpath is not defined properly then no export and import can be done. The basis administrator should make sure that the default value “r3transpath” is properly defined. Later in this chapter we will learn more about TP and R3trans; also we are going to see how they are used.
    Configuring the TPPARAM file:
    Each time TP is started, it must know the location of the global parameter file. As we have seen before TPPARAM file should be in directory /usr/sap/trans/bin. The parameters in TPPARAM can either global (valid for each and every system in the cts pipeline) or local to one system. Th parameters are either operating system dependant (these parameters preceded by a keyword corresponding to the specific operating system) or database dependant (contain a keyword corresponding to a specific database system).
    The global parameter file provides variables that can be used for defining parameters. The variables can be defined in format: $(xyz). The brackets can be substituted with the “\”-character if required.
    The following pre-defined variables are available for the global parameter file:
    $(cpu1): The CPU name can be sun or as4 for example. In heterogeneous networks this variable is very important.
    $(cpu2): Acronym for the name of the operating system. The example for this variable can be
    hp-ux, or sunos . This is an operating system specific variable.
    $(dname): Used for the day of the week (SUN,MON,….).
    $(mday): Used for the day of the current month (01-31).
    $(mname): Used for the name of the month (JAN…DEC).
    $(mon): Used for the Month (01-12).
    $(system): R/3 System name.
    $(wday): Day of the week (00-06, Sunday=00, Monday=01, Tuesday=02 and so on).
    $(yday): Day of the current year (001-366). Using the number any day of the year can be chosen.
    $(year): Year (Example:1998 or 1999).
    $(syear): Short form of the year (two positions).
    $(yweek): Calendar week (00-53). The first week begins with the first Sunday of the year.
    For the database connection:
    The transport environment also needs parameters to connect to the R/3 System database. As we know already the every instance in the R/3 CTS pipeline has its own database, therefore specific parameters should be defined for each database system. From dbtype parameter of RSPARAM file, TP program identifies the database system.
    The two parameters “dbname” and “dbhost” are required for ORACLE databases.
    DBHOST: is the name of the computer on which the database processes execute. TCP/IP name of the host if NT is being used.
    DBNAME: is the name of the database instance.
    As of Release 3.0E, two new parameters have been introduced.
    DBLOGICALNAME: The default value is $(system). The logical name that was used to install the database.
    DBCONFPATH: The default value is $(transdir).
    The parameters “dbname” and “dbhost” are also used for INFORMIX databases in an installation:
    DBHOST: Same as Oracle.
    DBNAME: Name of the database instance, uppercase and lowercase are distinguished here.
    INFORMIXDIR : “/informix/<SAPSID>” is the default value. Defines the directory namewhere the database software can be found.
    INFORMIXSQLHOSTS: “$(informixdir)/etc/sqlhosts[.tli|.soc]“is default value under Unix. The name of the SQLhosts file with its complete path is defined with this parameter.
    INFORMIX_SERVER: “$(dbhost)$(dbname)shm” is the default value. The name of the database server may be specified for a local connect.
    INFORMIX_SERVERALIAS: “$(dbhost)$(dbname)tcp”is the default vlue. The name of the database server can be specified for a remote connect.
    For Microsoft SQL Server database the two parameters “dbname” and “dbhost” are also required. DBHOST: The TCP/IP name of the host on which the database is running.
    DBNAME: The database instance name.
    For DB2 in AS/400 only “dbhost” is required.
    DBHOST: System name of the host on which the database is running.
    If the”OptiConnect” is used, the following line should be specified:
    OPTICONNECT 1
    For DB2/ AIX
    The two parameters “dbname” and “dbhost” are required
    DBHOST: The host on which the database processes are running. It is the TCP/IP name of the host for Windows NT (As we have seen in the earlier examples).
    DBNAME: Database instance name.
    The DB2 for AIX Client Application Enabler Software must also be installed on the host on which tp is running.
    ALLLOG: “ALOG” $(syear) $(yweek)”is the default value. This variable can be used in TPPARAM file to specify the name of a file in which tp stores information about every transport step carried out for a change request anywhere in the transport process. The file always resides in the log directory.
    SYSLOG: “SLOG $(syear) $(yweek).$(system)” is the default value. This variable can be used to name a file in which tp stores information about the progress of import actions in a certain R/3 System. The file does not store information for any particular change request. The file always resides in the log directory.
    tp_VERSION: Zero is the default value. If this parameter is set to not equal to zero, a lower version of tp may not work with this TPPARAM file. If the default value (zero) is set, the parameter has no affect.
    STOPONERROR: (Numeric value) The default value is 9. When STOPONERROR is set to zero, tp is never stopped in the middle of an “import” or “put” call. When STOPONERROR is set to a value greater than zero, tp stops as soon as a change request generates a return code that is equal to or greater than this value (The numeric value of the STOPONERROR parameter is stored in the variable BADRC). Change requests, which still have to be processed for the current step, are first completed. A “SYNCMARK” in the buffer of the R/3 System involved, sets a limit here. tp divides the value of this parameter between two internal variables. STOPONERROR itself is treated as a boolean variable that determines whether tp should be stopped, if the return code is too high.
    REPEATONERROR (Numeric value too): The default value is 9. The REPEATONERROR parameter is similar to STOPONERROR. The difference is, REPEATONERROR specifies the return code up to which a change request is considered to be successfully processed. Return codes less than REPEATONERROR are accepted as “in Order”. Change requests that were not processed successfully stay in the buffer.
    NEW_SAPNAMES: Default value is “FALSE”. A file is created for each user of the R/3 System group in the “sapnames” subdirectory of the transport directory. Except some of the operating system,the name of the user is the name of the file. It is very important to remember hat the special characters or length of the file name could cause problems. If all the R/3 Systems in the transport group have at least Release level 3.0.; TP program is efficient to handle this problem. The user names are modified to create file names that are valid in all operating systems and the real user names are stored in a corresponding file.
    Though we have seen so many parameters, for the minimum configuration the following two parameters are very important.
    TRANSDIR: specifies the name of the common transport directory. The following is a typical example from TPPARAM of Unix as we have seen before.
    transdir = /usr/sap/trans/
    DBHOST: contains the name of the database host. In Windows NT environment, this is the TCP/IP host name. The following is an example in Unix:
    DEV/dbname = DEV
    DEV/dbhost = sap9f
    DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
    For TP, to control ‘Start and Stop’ command files and database in R/3 the following important parameters are specified in TPPARAM:
    Parameters for the tp Function “PUT”: LOCK_EU (boolean) default value is “TRUE”. Though from version 3.1 onward the tp put command is used seldom in cts process still it is important to know how this parameter works. When “tp put” is used, it changes the system change option . If the parameter is set to “FALSE” nothing gets changed. If the parameter is set to “TRUE”, the system change option is set to “Objects cannot be changed” at the beginning of the call, and gets changed back to its previous value at the end of the call. The “tp put” command will give the exact status of the locking mechanism.
    LOCKUSER (used as boolean value): Default value is “TRUE”. This parameter is about the user login while tp put call is executed. If this parameter is set to “FALSE”, no locking mechanism for the users takes affect. If this parameter is defined as “TRUE” then a character is set in the database level; so only DDIC and SAP* can log on to the system. Users that have already logged on are not affected (this is a reason for activating the parameters STARTSAP and STOPSAP). The charactertor is removed at the end of the call, and all the users can log on to the SAP R/3 System again.
    STARTSAP: Default value is ” “.or “PROMPT” for Windows NT . This parameter is used by TP to start an R/3 System. It is not necessary for the clients to make tp start and stop R/3 system..
    STOPSAP: Default value is ” “or “PROMPT” for Windows NT. TP uses this parameter to stop an R/3 System.
    STARTDB: Default value is ” “. TP uses the value of this parameter to start the database of an R/3 System.
    The parameter is not active under Windows NT.
    STOPDB: Default value is ” “. TP uses the value of this parameter to stop the database of an R/3 System.
    This parameter is not active under Windows NT.
    The above parameters in UNIX can be used as following:
    STARTSAP = startsap R3
    STOPSAP = stopsap R3
    STARTDB = startsap db
    STOPDB = stopsap db
    In Windows NT:
    STARTSAP = \\$(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\startsap.exe
    R3 <SID> <HOST NAME> <START PROFILE>
    STOPSAP = \\$(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\stopsap.exe
    R3 <SID> <HOST NAME> <INSTANCE> <PROFILE PATH + Instance profile>
    The parameters STARTDB and STOPDB are not active under Windows NT.
    Parameters for the tp function “CLEAROLD”
    DATALIFETIME (Numeric): Default value is “200″. When the data file has reached a minimum age, it is moved to the subdirectory old data with tp check. tp clearold all. The life span of the data files in the data sub directory can be set in days with this all, parameter.
    OLDDATALIFETIME (Numeric): Default value is “365″. When a file located in the olddata subdirectory is no longer needed for further actions of the transport system and has reached a minimum age, it is removed with tp check.all, tp clearold all. The minimum age in days can be set with this parameter.
    COFILELIFETIME (Numeric): Default value is “365″. This parameter is used just like DATALIFETIME parameter.
    LOGLIFETIME (Numeric): Default value is “200″. This parameter applies to the life span of the log files. When the log files in log subdirectory is no longer needed for the transport system and has reached a minimum age, it is deleted with the calls tp check.all, tp clearold all. The minimum age in days can be defined with this parameter.
    The Three Key Utilities of the CTS system (TP, R3trans and R3chop):
    TP: Earlier in this chapter we have seen the objectives of TP. The TP transport control program is a utility program that helps the user to transport objects from one system to another. TP program is the front-end for the utility R3trans. TP stands for “Transports and Puts”. To make the TP work successfully the CTS system needs to be correctly configured. The following steps are very important for TP to run properly.
    The transport directory /usr/sap/trans must be installed and NFS mounted to all the systems in the CTS pipe line.
    RDDIMPDP program must be running (event driven is recommended) in each client. RDDIMPDP can be scheduled in the background by executing RDDNEWPP or RDDPUTPP. Use the tp checkimpdp <sap sid> command in /usr/sap/trans/bin directory as <sid>adm user to check RDDIMPDP program.
    Use the tp connect <sap sid> command in /usr/sap/trans/bin directory to see whether the tp program is connecting to the database successfully or not. To run TP command the user has to logon as <sid>adm in source or target system.
    The R/3 Systems in the CTS pipeline must have different names.
    The Global CTS Parameter File TPPARAM must be correctly configured.
    The source system (for the export) and target system ( for the import) must have at least two background work processes. TP always schedules the C class job, so if all the background jobs are defined as A class job then there will be problems in transport steps.
    Important Tips :.It is always better to have the up to date TP version installed in your system. A user can ftp a current version of TP from SAPSERV4 of SAP. Though R3trans and other utility programs can be used to do the transport, it is recommended to use TP whenever possible for the following reasons..
    The exports and imports are done separately using TP program. For example: when a transport is released from the system, the objects are exported from the source database to the operating system and then the import phase starts to transport those objects to the target system.
    TP takes care of the order of the objects. The order, that was followed to export the objects; the same order will be followed to import them to the target database.
    The TP command processes all change requests or transports in the SAP system buffer that have not yet been imported successfully. All the import steps are executed automatically after TP calls R3trans program to execute the following necessary steps:
    Dictionary Import: ABAP/4 dictionary objects will be imported in this step.
    Dictionary Activation: Name tabs or runtime descriptions will be written inactively. The R/3 system keeps running until the activation phase is complete. The enqueue modules are the exceptions in the running phase. After the activation of new dictionary structure the new actions are decided to get the runtime objects to the target system.
    Structure conversion: If necessary the table structure is changed in this phase.
    Move Nametabs: The new ABAP/4 Dictionary runtime objects which were inactive up to now are moved into the active runtime environment in this process. The database structures are adjusted accordingly. From the first step to the Main import step inconsistencies can occur to the R/3 system. After the main import phase all the inconsistency ca be solved.
    Main import with R3trans: All the data are imported completely and the system comes to a consistent state.
    Activation of enqueue-objects: The enqueue-objects cannot be activated in the same way as the objects of the ABAP/4 Dictionary, so they have to be activated after the main import in this step. They are then used directly in the running system.
    Structure Conversion of match codes, Import application defined objects, versioning and execution of user defined activities are some of the steps after activation of enqueue-objects. The next step is generation of ABAP/4 programs and screens, where all the programs and screens associated with the change request are generated. When all the import steps are completed successfully, the transport request is removed from the import buffer.
    It is recommended by SAP to schedule regular periods for imports into the target system (e.g. daily, weekly or monthly). Shorter periods between imports are not advisable. The transport to production should not be done in the off hours when the users are not working
    TP can be started with different parameters. The “tp help” command can help user to generate a short description about the use of the command.
    The following are the some important commands of TP:
    For export:
    tp export <change request>: The complete objects in the request from the source system will be transported. This command also used by SAP System when it releases a request.
    tp r3e <change request>: R3trans export of one transport request.
    tp sde <change request>: Application defined objects in one transport request can be exported.
    tp tst <change request> <SAP system >: The test import for transport request can be done using this command.
    tp createinfo <change request>: This command creates a information file that is automatically done during the export.
    tp verse <request>: This command creates version creates versions of the objects in the specified request.
    To Check the transport buffer, global parameter file and change requests:
    tp showbuffer <sid>: Shows all the change requests ready to be imported to the target system.
    tp count <sid>: Using this command users can find out the number of requests in the buffer waiting for import.
    tp go <sid>: This command shows the environment variables needed for the connection to the database of the <sid> or target system.
    tp showparams <sid>: All the values of modifiable tp parameters in the global parameter file. The default value is shown for parameters that have not been set explicitly.
    To import the change requests or transports:
    tp addtobuffer <request>.<sid>: If a change request is not in the buffer then this command is used to add it to the buffer, before the import step starts.
    tp import all <sid>: This command imports all the change requests from the buffer to the target system.
    tp put <sid>: The objective of this command is same as “tp import all <sid>”, but this command locks the system. This command also starts and stops the SAP system, if the parameters startsap and stopsap parameters are not set to ” “.
    tp import <change request> <sid>: To import a single request from the source system to target system.
    tp r3h <change request>| all <sid>: Using this command user can import the dictionary structures of one transport or all the transport from the buffer.
    tp act <change request>|all <sid>: This command activates all the dictionary objects in the change request.
    tp r3i <change request> | all <sid>: This command imports everything but dictionary structures of one.
    tp sdi <change request>|all <sid>: Import application-defined objects.
    tp gen <change request>|all <sid>: Screen and reports are generated using this command.
    tp mvntabs <sid>: All inactive nametabs will be activated with this command.
    tp mea <change request>|all <sid>: This command will activate the enqueue modules in the change request.
    When you call this command, note the resulting changes to the import sequence.
    Additional tp utility options:
    tp check <sid>|all (data|cofiles|log|sapnames|verbose): User uses this command to find all the files in the transport directory that are not waiting for imports and they have exceeded the minimum time specified using the COFILELIFETIME, LOGFILELIFETIME, OLDDATALIFETIME and DATALIFETIME parameters of TPPARAM file.
    tp delfrombuffer <request>.<sid>: This command removes a single change request from the buffer. In case of TMS, the request will be deleted from the import queue.
    tp setstopmark <sid>: A flag is set to the list of requests ready for import into the target system. When the user uses the command tp import all <sapsid> and tp put <sapsid>, the requests in front of this mark are only processed. After all the requests in front of the mark have been imported successfully, the mark is deleted.
    tp delstopmark <sid>: This command deletes the stop mark from the buffer if it exists.
    tp cleanbuffer <sapsid>: Removes all the change requests from the buffer that are ready for the import into the target system.
    tp locksys <sid>: This command locks the system for all the users except SAP* and DDIC. The users that have already logged on are not affected by the call.
    tp unlocksys <sid>: This command unlocks the system for all the users.
    tp lock_eu <sid>: This command sets the system change option to “system can not be changed” tmporarily.
    tp unlock_eu <sid>: This command unlocks the system for all the changes.
    tp backupall <sid>: This command starts a complete backup using R3trans command. It uses /usr/sap/trans/backup directory for the backup.
    tp backup delta <sid>: Uses R3trans for a delta backup into /usr/sap/trans/backup directory.
    tp sapstart <sid>: To start the R/3 system.
    tp stopsap <sid>: To stop the R/3 system.
    tp dbstart <sid>: To start the database.
    tp dbstop <sid>: To stop the database.
    Unconditional modes for TP: Unconditional modes are used with the TP program and these modes are intended for the special actions needed in the transport steps. Using unconditional mode user can manipulate the rules defined by the workbench organizer. The unconditional mode should be used when needed, otherwise it might create problems for the R/3 system database. Unconditional mode is used after the letter “U” in the TP command. Unconditional mode can be a digit between 0 to 9 and each has a meaning to it. The following is a example of a import having unconditional mode.
    tp import devk903456 qas client100 U12468
    0: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location.
    1: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again.
    2: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals.
    3: When used with tp import, it overwrites the system-dependant objects.
    5: During the import to the consolidation system it permits the source systems other than the integration system.
    6: When used in import phase, it helps to overwrite objects in unconfirmed repairs.
    8: During import phase it ignores the limitations caused by the table classification.
    9: During import it ignores that the system is locked for this kind of transport.
    R3trans: TP uses R3trans program to transport data from one system to another in the CTS pipeline. efficient basis administrator can use R3trans directly to export and import data from and into any SAP systems. Using this utility transport between different database and operating system can e done without any problems. Different versions of R3trans are fully compatible with each other and can be used for export and import. The basis administrator has to be careful using R3trans for different release levels of R/3 software; logical inconsistency might occur if the up to date R3trans is not used for the current version of R/3 system.
    The syntax for using the control file is following:
    R3trans [<options>] <control file> (several options used at the same time; at least one option must be there)
    For example: R3trans –u 1 –w test.log test
    In the above example a unconditional mode is used, a log file “test.log” file is used to get the log result and a control file “test”, where the instructions are given for the R3trans to follow. The user needs to logon as <sid>adm to execute R3trans.
    The following options are available for the R3trans program:
    R3trans -d : This command is used to check the database connection .
    R3trans -u <int>: Unconditional mode can be used as we have seen in the above example.
    R3trans -v : This is used for verbose mode. It writes additional details to the log file
    R3trans -i <file>: This command directly imports data from data file without a control file.
    R3trans -l <file>: This provides output of a table of contents to the log file.
    R3trans -n : This option provides a brief information about new features of R3trans.
    R3trans –t: This option is used for the test mode. All modifications in the database are rolled back.
    R3trans -c <f1> [<f2>]: This command is used for conversion. The <f1> file will be copied to <f2> file after executing a character set conversion to the local character set.
    Important tips: Do not confuse the backup taken using R3trans with database backup. The backups taken using R3trans are logical backups of objects. In case something happens to the SAP system these backups can not be used for recovery. R3trans backups can be only used to restore a copy of a particular object that has been damaged or lost by the user.
    R3trans -w <file>: As we have seen in the above example this option can be used to write to a log file. If no file is mentioned then trans.log is default directory for the log.
    R3trans also can be used for the database backup.
    R3trans –ba: This command is used for a complete backup. we will see in the next paragraph how to use
    the control file for the backup.
    R3trans –bd: This command is used for a delta backup if the user does not want a complete backup.
    R3trans –bi: This option

  • Proper method to fire off some code to create a default set of detail data.

    Greetings, fellow nerds. First, I'd like to thank the folks that have helped me out in the past. I don't always return back to the topic to give kudos, and sometimes I even figure out my problem before anyone says anything. And I try to find reference to my problem by doing a search on it beforehand. Which often works.
    Anyways...
    I've got a mater/detail form that I set up using the wizard. Every time a new master record is created, I'm gonna want to set up 62 generic rows of detail records to be associated with it. The detail section defaults to an 'add row' button, which may actually be used, and even the delete function. But, I don't want the user to have to enter 62 rows.
    I've created a table of the generic rows, and have written the sql to populate the details table, using the bind variable that is the id of the master table/row.
    If the user is looking at the master table 'report', and clicks create, it fires off the add process for the master table. No details. Filling in the various master fields, and clicking create, a master record is created, and the page stays there with no re-direct back to the 'report'. And the options are now 'apply changes', and 'cancel'. Cancel takes you back to the 'report', with no details created. At the same time, the details become available for this new master record. But again, with the option to add a single detail row.
    At what point should I fire off the code that will generate the 62 rows of template detail records? Do I just add a button beside the 'add row' button, that will fire off the code, and return them to what they are looking at, with the 62 rows staring back at them to edit? Do I hook it to the 'create' button on the master portion of the page? If so, I'd want it to fire after all of the validations for the master data, and the master record was in fact inserted.
    I'd like to do this the 'correct' way.
    Thanks in advance,
    Clayton

    I can't say anything about a correct way of doing this. Your descriptions doesn't
    point to any critical issues if doing it this or another way. What I can say is that
    this looks like a perfect case for utilizing collections.
    Denes Kubicek

  • Help needed in XML Bursting to set printer details

    Hi,
    In xml bursting to set the printer details, we need to Specify the printer attribute as a URI such as:"ipp://myprintserver:631/printers/printername"
    Here I am getting printername dynamically from report. But I am
    not understanding "ipp://myprintserver:631/printers". Here What I have to give?
    Please help me in this.
    Thanks in advance.

    Which environment are you trying this in ? In Enterprise server, bursting is defined by a SQL query which can be run against the table that you want. So you can even populate the printer name from your query. So the URI, ipp://myprintserver:631/printers/printername" is the syntax. In your case you have to create this string in your SQL query by concatenating the parts "ipp://" + printername + ":631/". If there is a name to the printer in the printserver, then that too can be concatenated.
    In case this is in EBS , the same has to be done in the control file.

  • E-commerce 5.0 for SAP ERP 6.0 ehp3: detailed description of product

    Hello community,
    I have installed and customized B2C shop (version 5.0) for SAP ERP 6.0 (NO TREX, NO IPC).
    At first i maintained my shop with english language and after i checked out that all work properly i decided to localize it for russian language.
    I created new shop for russian language and faced the following problem: list of products in my shop displays correctly but when i want to check detailed description of product (click on product in list) i see something like this &#1053 &#1086 &#1091 &#1090 &#1073 &#1091 &#1082  instead of description on russian.
    Can somebody help me to sort out this issue?
    Thanks in advance.
    BR,
    Dzmitry

    HI,
    I  can obtain detailed description of product on russian after i installed SAP E-commerce for SAP ERP version 7.0 instead of version 5.0.
    Br,
    Dzmitry

Maybe you are looking for

  • Why is the repeat button close to the shuffle on the 5th generation iPod touch?

    I'm asking because on the previous generations it was different how you could repeat and shuffle songs. Why did Apple change it?

  • Intel VT in the Bios of Satellite P200-13F disabled?

    Hi, I just bought a toshiba Satellite P200-13F and now I am finding out that the Vitrualization cannot be switched on in the BIOS. Can anyone tell me if Toshiba is planning to release a BIOS with this feature supported? I want to use the machine for

  • Problem using "xsl:include"

    I am trying to include one xsl file in another. When I do this, I get the error: "oracle.xml.parser.v2xslexception: xsl-1002: Error while processing xsl file (no protocol tabledef.xsl" - where tabledef.xsl is the name of the xsl file I am trying to i

  • Multiple HTTP Proxies

    Hi, we have a WebLogic Workshop (8.1.5) / Integration (8.5) project which makes heavy usage of WebService controls. We need to make the WebService calls via different HTTP proxies. Is it possible to use either a) an automatic proxy configuration file

  • Creating release order from contract

    Hello I tried to create a relase order from contract. But it gave me the message "Partner XXXX is not authorized to release from the contract" In the customization of the contract type WK1 I have maintained the setting as A for the field check partne