Transport Type and Status

Hi All,
I was checking transport type and status in E070 table. By pressing F1 I saw there can be 3 types of transport K,C and T. But in my production system table I found another 2 types R and F,and in transport status I saw R and D.
It will be helpful if anyone explain me these transport types and status.
Thanks in advance..
Moderator message: please press F4 as well, will give you all possible values.
Locked by: Thomas Zloch on Jun 22, 2011 9:21 AM

you need to create 2 status schemes.
Goto SPRO > SAP Solution Manager Implementation Guide > SAP Solution Manager > Advanced Configuration > Scenario-Specific Settings > Implementation > Document Management > Status for Documents > Define Document Status Schemes
Do these steps for a blueprint schema and config schema
1. Click yes to the Cross-Client popup
2. Click the New Entries button
3. Name you status Schema
4. Click Save
5. Highlight the new schema
6. Click the status value folder on the left
7. Click the New Entries button
8. Add you values in the order you wish, initial status, min, max, ect..
9. Click save
Go to SOLAR_PROJECT_ADMIN
Open your project
Click the Project Standards tab
Click the Documentation Types tab
Click the Project Template button (bottom right)
Find you documentation types for Blueprint and Configuration in the right hand box
Go to the last column for those documentation types (you'll need to scroll)
Select the newly created schema
Click the save button
regards,
Jason

Similar Messages

  • What is means "Transport Type" "Number of Failures" "Last Failure Time" "Last Success Time" "Last Failure Status"

    when i running repladmin /showrepl    it show status
    Showrepl_COLUMNS
    Destination DC Site
    Destination DC
    Naming Context         is
    means  ?
    Source DC Site
    Source DC
    Transport Type         is
    means  ?
    Number of Failures     is
    means  ?
    Last Failure Time   
    Last Success Time   
    Last Failure Status    is
    means  ?
    Please explain to me .  Thnak you

    Naming Context: NamingContext refers to the directory partitions that Active Directory comprises. Naming contexts include the three Read/Write naming contexts — domain, schema, and configuration — and the optional Read-only naming contexts
    that are present on domain controllers that are global catalog servers. A naming context can also be an application directory partition. A naming context is specified as a distinguished name, which indicates its hierarchical relationship to the forest root
    domain (for example, DC=MyDomain,DC=Microsoft,DC=Com). 
    Source: http://technet.microsoft.com/en-us/library/cc757782(v=ws.10).aspx
    Transport Type: See Transport Type section in this Microsoft article: http://technet.microsoft.com/en-us/library/cc755994(v=ws.10).aspx
    As for the Number of Failures and the Last Failure Status
    they are used to identify how many failures occurred since the last successful replication and the the status of the replication (If
    Last Failure Status is equal to 0 then the replication is done successfully). Details here: http://support.microsoft.com/kb/2498185/en-us
    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Get Active Directory User Last Logon
    Create an Active Directory test domain similar to the production one
    Management of test accounts in an Active Directory production domain - Part I
    Management of test accounts in an Active Directory production domain - Part II
    Management of test accounts in an Active Directory production domain - Part III
    Reset Active Directory user password

  • VF11 wrongly created with RV Doc type and with not clear status.

    Hi All
    Issue: There are 2 billing documents which were created(VF01) in March are canceled (VF11) in May. Cancel document is saved with a message (No automatic clearing of billing document XXXXXXXXX) and message diagnosis saying that u201CThe Automatic clearing of billing document and reversal is not possible. This may be, for example, because the line item update is deactivatedu201D
      In the SD document flow cancel billing document is created and it's posted to accounting with Document type RV(which is not configured in the billing  types) and it is in not clear status.
    2 Sales order types are ZNRC(No Rebate u2013 Credit)    second is ZCR (CM Req With Refer).
    Order Type  : ZNRC , Billing type :ZG2, Cancel billing type :Z5, Accounting document in billing type for ZG2: is DG and accounting document in cancel billing type Z5 is :(_) blank.
    Order type:  ZCR Billing type :G2, Cancel billing type :S2, Accounting document in billing type for G2: is DG and accounting document in cancel billing type S2 is :(_) blank.                                                
          FI document type Not maintained in the cancel billing type configuration because this should be determine by reversal document type DA which is maintained in DG document type from FI side. It will be triggered in VF11)
    The above configuration is working with the order created VA01,billing VF01 and cancelling VF11 done in same period. If the order and billing done in old period and canceling(VF11) done in current period than FI document creating with RV document type and with not clear status in the document flow.
    I reviewed similar issues with SAP Note and with below explanation:
              "There are 2 procedures that are possible when Vf11 is posted.
              Old Procedure - An FI "Reversal" document was created that was not connected with the orignal.
              New Procedure - A Real FI reversal was carried out with clearing."
    In this case, our system is following with new procedure except above mentioned orders created in previous period and and canceled in current period.
      My Questions are: How the RV document is getting triggered here? why the cancel document (Reversal FI Doc) is not clearing?
         Appreciate your answers or suggestions.
    Thanks in advance,
    Sunil
    Edited by: Sunil kumar Matta on Jun 9, 2011 3:40 PM

    Thank you Ivano.
      I referred SAP note 1259505 and 339928. But initially we thought of none of the symptoms mentioned in the SAP note are matching with our issue. Then we contacted SAP online support and they suggested checking one SAP note (Mentioned above).
      Our system is following new cancellation procedure, but itu2019s failing only for some few documents.
      Finally we identified several reasons for the issue. One is profitability segment in the billing document and cancelled document is different due to some changes in segment assignments. Another one is consolidation- consolidation document does not exist in the billing document list but it is getting created in Canceled document (VF11).(Consolidation postings are switched off some time back and now itu2019s on)
      After some discussions it is decided to include accounting document type (Reversal) in cancel billing types to avoid default RV document type in canceled billing document accounting document. And non-cleared documents need to be created manually in F-32.
      Thread is closed.
    Sunil

  • Person type and assignment status for terminated employee

    Hi,
    When I terminate an employee, is it possible to default the field "type" on "Person type and assignment status for terminated employee" section into another value? Its default values is: "Ex-Employee released".
    Thank you.

    Navigate to Work Structures -> Status and query for all rows with system status Terminated Assignment. select your required assignment status as Default. Untick the other default.

  • Authorisation combined with document type, activity and status

    I want to create a role for a user who is only allowed to create and change document type ZDI  in status IW .
    Which object authorization can provided this check ?
    The object authorization C_DRAW_TCD  control only the activity (create/modify) and the document type (ZDI).
    The object authorization C_DRAW_STA control only  the document type (ZDI) and the status of the document (IW).
    But I need the combination of the both authorization. Does a possibility exist in standard to do it without create a client new authorisation?
    Thanks in advance for your help.
    Amande

    Thanks for your response.
    But it doesn't works as I want.
    The object authorisation C_DRAW_TCS  is checked before the save but not after save with the changed values.
    for example :
    the user has the following authorizations in the modification role:
      C_DRAW_TCS  activity 02 document type ZDI  document status IW 
      C_DRAW_TCD document type ZDI  activity 02
      C_DRAW_STA document type ZDI status IW
    The user has also the autorisation C_DRAW_STA document type ZDI status FI  in the display role
    With this configuration the user can modify the document ZDI in status IW and change the status into FI . I don't want that the user can change the status into FI. Does exist a possibility to avoid this?
    Of course, after storing this change of the status , the user can't access to the document ZDI with status FI.
    SAP doesn't check the authorization C_DRAW_TCS  activity 02 document type ZDI  document status FI  after status change.
    Thanks in advance
    Amande

  • IDOC error 639 IDoc & and determined transport type & do not match

    Hello,
    can you help me with this issue?
    An idoc is stuck beacuase of this error:
    IDoc & and determined transport type & do not match
    Message no. IHC_IDOC639
    What does it mean? how can I fix thiss issue in order to re-process the idoc?
    Thank You

    Hi,
    is SAPNET note 784881 implemented? If no, implement it and try again.
    BR Christian

  • Transport classes and programs to another server

    Except for transport routing and charm copy function, do we have other ways to do so?
    for example copy or so forth.
    best regards,
    Blake Le

    Hi Blake
    SAP R/3 Correction and Transport System
    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 . 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. These 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. 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: holds action log files. The example of an action file is DEVZ902690.DEV. The following are the contents of the file:
    1 ETK220 u201C==================================================u201D u201C=================
    =============================
    1 ETK191 u201C04/30/1998u2033 Action log for request/task: u201CDEVK902690u2033
    1 ETK220 u201C==================================================u201D u201C=================
    =============================
    1 ETK185 u201C04/30/1998 18:02:32u2033 u201CMOHASX01u2033 has reincluded the request/task
    4 EPU120 Timeu2026 u201C18:02:32u2033 Run timeu2026 u201C00:00:00u2033
    1 ETK193 u201C04/30/1998 18:02:33u2033 u201CMOHASX01u2033 owner, linked by u201CMOHASX01u2033 to u201CDEVK902691u2033
    4 EPU120 Timeu2026 u201C18:02:33u2033 Run timeu2026 u201C00:00:00u2033
    1 ETK190 u201C05/04/1998 11:02:40u2033 u201CMOHASX01u2033 has locked and released the request/task
    1 ETK194 u201C05/04/1998 11:02:40u2033 **************** End of log *******************
    4 EPU120 Timeu2026 u201C11:02:40u2033 Run timeu2026 u201C00:00:09u2033
    ~
    ~u201DDEVZ902690.DEVu201D 10 lines, 783 characters
    /usr/sap/trans/buffer: transport buffer of the target systems; 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. 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 u201CConfiguring the CTS systemu201D 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 u201Cr3transpathu201D 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 u201C\u201D-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,u2026.).
    $(mday): Used for the day of the current month (01-31).
    $(mname): Used for the name of the month (JANu2026DEC).
    $(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 u201Cdbnameu201D and u201Cdbhostu201D 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 u201Cdbnameu201D and u201Cdbhostu201D 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 : u201C/informix/<SAPSID>u201D is the default value. Defines the directory namewhere the database software can be found.
    INFORMIXSQLHOSTS: u201C$(informixdir)/etc/sqlhosts[.tli|.soc]u201Cis default value under Unix. The name of the SQLhosts file with its complete path is defined with this parameter.
    INFORMIX_SERVER: u201C$(dbhost)$(dbname)shmu201D is the default value. The name of the database server may be specified for a local connect.
    INFORMIX_SERVERALIAS: u201C$(dbhost)$(dbname)tcpu201Dis the default vlue. The name of the database server can be specified for a remote connect.
    For Microsoft SQL Server database the two parameters u201Cdbnameu201D and u201Cdbhostu201D 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 u201Cdbhostu201D is required.
    DBHOST: System name of the host on which the database is running.
    If theu201DOptiConnectu201D is used, the following line should be specified:
    OPTICONNECT 1
    For DB2/ AIX
    The two parameters u201Cdbnameu201D and u201Cdbhostu201D 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: u201CALOGu201D $(syear) $(yweek)u201Dis 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: u201CSLOG $(syear) $(yweek).$(system)u201D 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 u201Cimportu201D or u201Cputu201D 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 u201CSYNCMARKu201D 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 u201Cin Orderu201D. Change requests that were not processed successfully stay in the buffer.
    NEW_SAPNAMES: Default value is u201CFALSEu201D. A file is created for each user of the R/3 System group in the u201Csapnamesu201D 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 u2018Start and Stopu2019 command files and database in R/3 the following important parameters are specified in TPPARAM:
    Parameters for the tp Function u201CPUTu201D: LOCK_EU (boolean) default value is u201CTRUEu201D. 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 u201Ctp putu201D is used, it changes the system change option . If the parameter is set to u201CFALSEu201D nothing gets changed. If the parameter is set to u201CTRUEu201D, the system change option is set to u201CObjects cannot be changedu201D at the beginning of the call, and gets changed back to its previous value at the end of the call. The u201Ctp putu201D command will give the exact status of the locking mechanism.
    LOCKUSER (used as boolean value): Default value is u201CTRUEu201D. This parameter is about the user login while tp put call is executed. If this parameter is set to u201CFALSEu201D, no locking mechanism for the users takes affect. If this parameter is defined as u201CTRUEu201D 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 u201D u201C.or u201CPROMPTu201D 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 u201D u201Cor u201CPROMPTu201D for Windows NT. TP uses this parameter to stop an R/3 System.
    STARTDB: Default value is u201D u201C. 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 u201D u201C. 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 u201CCLEAROLDu201D
    DATALIFETIME (Numeric): Default value is u201C200u2033. 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 u201C365u2033. 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 u201C365u2033. This parameter is used just like DATALIFETIME parameter.
    LOGLIFETIME (Numeric): Default value is u201C200u2033. 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 u201CTransports and Putsu201D. 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 u201Ctp helpu201D 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 u201Ctp import all <sid>u201D, 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 u201D u201C.
    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 u201Csystem can not be changedu201D 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 u201CUu201D 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 u2013u 1 u2013w test.log test
    In the above example a unconditional mode is used, a log file u201Ctest.logu201D file is used to get the log result and a control file u201Ctestu201D, 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 u2013t: 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 u2013ba: 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 u2013bd: This command is used for a delta backup if the user does not want a complete backup.
    R3trans u2013bi: This option will display backup information.
    The following are some of the examples of control files:
    We have already learned how to use a command for the logical backup of the objects in the database. To get a complete backup the following example control file can be used.
    backup all
    file = /usr/sap/trans/backall
    The option u201Cfile = u2026u201D is the name of the directory into which the data files are to be written. If you are taking a complete backup of DEV system then the backup file is going to look like u201CDEV.A000.bcku201D the next complete
    Reward if useful
    Regards
    divya

  • IDOC Types and their equivalent messages in EDIFACT and ANSI X12

    Hi all, since I only have a list of messages in EDIFACT and ANSI X12 for release 4.6 B, I need to update the list from 6.0 version, but I don't have online support system to get it (OSS), it's note 104606 in OSS.
    Can somebody give me a link to the full new updated list? Will surely give points with your helpful answers
    Regards,

    Hi,
    Please check these perhaps they may help.
    Mapping ANSI X12 to SAP Message Type and IDoc Type:
    204 Motor carrier shipment information
    The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
    214 Transportation carrier shipment status message
    The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
    304 Shipping instructions
    The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
    810 Invoice or billing document (also 880), EDI - Inbound INVOIC posting configuration
    The logical message is INVOIC, the IDoc type INVOIC01.
    812 Credit and debit advice
    The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
    820 Payment order and credit advice
    For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
    For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
    823 Lockbox
    The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
    830 Delivery schedule (LAB)
    The logical message is DELINS (from the EDI standard ODETTE) or DELFOR, the IDoc type is DELFOR01.
    832 Price catalog (also 879, 888, 889)
    The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
    834 Benefit enrollment and maintenance
    The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
    840 Request
    The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
    843 Quotation
    The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04. Outbound processing is supported.
    850 Purchase order or order (also 875)
    The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
    852 Stock and sale data
    The logical message is PROACT, the IDoc type PROACT01.
    855 Ordering or order response (also 865)
    The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
    856 Transport and shipping notification (ASN - Advanced Ship Notification)
    For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
    For delivery in the SAP application, the logical message is DESADV, the IDoc types are DESADV01 (expires) or DELVRY01 and DELVRY02.
    860 Ordering or order modification (also 876)
    The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
    861 Credit advice (ERS - Evaluated Receipt Settlement)
    The logical message is GSVERF, the IDoc type GSVERF01.
    862 delivery schedule (FAB)
    The logical message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDoc type is DELFOR01.
    864 Text message
    The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
    940 Shipping order and stock order
    The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
    945 Shipping confirmation and stock confirmation
    The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
    997 Functional Acknowledgment
    This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
    "22" Shipping OK, acknowledgment has yet to come
    "16" Functional Acknowledgment positive
    "17" Functional Acknowledgment negative
    The status values "14" and "15" are available for the Interchange Acknowledgment accordingly.
    Regards,
    Ferry Lianto

  • Message types and idoc types

    hi,
         i need the list of message types and idoc types for edi.
          can any one of u pls send it.

    Hi,
    Check the OSS notes 104606.
    The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
    204 Motor carrier shipment information
               The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
    214 Transportation carrier shipment status message
               The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
    304 Shipping instructions
               The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
    810 Invoice or billing document (also 880)
               The logical message is INVOIC, the IDoc type INVOIC01.
    812 Credit and debit advice
               The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
    820 Payment order and credit advice
               For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
               For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
    823 Lockbox
               The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
    830 Delivery schedule (LAB)
               The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
    832 Price catalog (also 879, 888, 889)
               The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
    834 Benefit enrollment and maintenance
               The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
    840 Request
               The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
    843 Quotation
               The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
    850 Purchase order or order (also 875)
               The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
    852 Stock and sale data
               The logical message is PROACT, the IDoc type PROACT01.
    855 Order confirmation (also 865)
               The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
    856 Transport and shipping notification (ASN - Advanced Ship Notification)
               For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
               For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
    860 Ordering modification (also 876)
               The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
    861 Credit advice (ERS - Evaluated Receipt Settlement)
               The logical message is GSVERF, the IDoc type GSVERF01.
    862 Delivery schedule (FAB)
               The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
    864 Text message
               The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
    940 Shipping order and stock order
               The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
    945 Shipping confirmation and stock confirmation
               The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
    997 Functional acknowledgment
               This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
               "22" Shipping OK, acknowledgment has yet to come
               "16" Functional acknowledgment positive
               "17" Functional acknowledgment negative
               The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
    Cheers
    VJ

  • What is difference between transport protocol and message protocol

    what is difference between transport protocol and message protocol
    please give definition and small explanation

    Hi,
    Transport protocol gives information about outside of message details, kind of system, security details.
    A transport protocol is a network protocol that has the capability of transferring some payload from one node to another, thus providing some level of transparency from the underlying network.
    Transport protocols are used as a mechanism to move payloads around a network. Typically, a payload will have a transport binding associated with it. For example, SOAP (acting as a payload) has a predetermined binding for HTTP (a transport protocol).
    Some common transport protocols include: HTTP, HTTP-R, SMTP and BEEP.
    Message protocol gives you an idea of message type XI payload
    http://help.sap.com/saphelp_nw04/helpdata/en/b6/0b733cb7d61952e10000000a11405a/content.htm

  • The type and the length of the members of the structures

    I am making the BC-XAL program.
    Reading `XAL_Interface_Documentation_11.pdf', now I succeeded in "Reading All Saved Monitor Sets" and "Reading All Monitors of a Monitor Set". but I can't find the type and the length of the member of the Structure BAPITNDEXT, so I cannot get the Monitoring Tree of a Monitor.
    where can I get any documents or information ?

    This is how it looks in my 46c system.
    MTSYSID         SYSYSID         CHAR      8     0R/3 System, name of R/3 System                                 
    MTMCNAME        ALMCNAME        CHAR     40     0Alert: name of monitoring context                              
    MTNUMRANGE      ALTIDNUMRG      CHAR      3     0Alert: monitoring type number range (perm., temp, ...)         
    MTUID           ALTIDUID        CHAR     10     0ALert: Unique Identifier for  Monitoring Types (used in TID)   
    MTCLASS         ALTIDMTCL       CHAR      3     0Alert: monitoring type class (perf., single msg.,...)          
    MTINDEX         ALTIDINDEX      CHAR     10     0Alert: internal handle for TID                                 
    EXTINDEX        ALTIDINDEX      CHAR     10     0Alert: internal handle for TID                                 
    ALTREENUM       ALTREENUM       INT4     10     0Alert: MT Tree info: Number of tree                            
    ALIDXINTRE      ALIDXINTRE      INT4     10     0Alert: Tree Info: Index of MT in Tree                          
    ALLEVINTRE      ALLEVINTRE      INT4     10     0Alert: Tree Info: Level of MTE in Tree                         
    ALPARINTRE      ALPARINTRE      INT4     10     0Alert: Tree Info: Index of Parent of MT in Tree                
    OBJECTNAME      ALMOBJECT       CHAR     40     0Alert: Name of Monitoring Object                               
    MTNAMESHRT      ALMTNAMESH      CHAR     40     0Alert: Short Name of Monitoring Type                           
    CUSGRPNAME      ALCUSGROUP      CHAR     40     0Alert: Customization: Name of Customization Group              
    DELIVERSTA      ALDELIVSTA      INT4     10     0Alert: MT Val: Delivery Status                                 
    HIGHALVAL       ALVALUE         INT4     10     0Alert: alert value (1 = green, 2 = yellow, ....)               
    HIGHALSEV       ALSEVERITY      INT4     10     0Alert: severity (alerts, monitoring type custom..)             
    ALSYSID         SYSYSID         CHAR      8     0R/3 System, name of R/3 System                                 
    MSEGNAME        ALMSEGNAME      CHAR     40     0Alert: name of monitoring segment                              
    ALUNIQNUM       ALAIDUID        CHAR     10     0Alert: Unique Identifier to be used in AID (char10)            
    ALINDEX         ALINDEX         CHAR     10     0Alert: internal handle                                         
    ALERTDATE       ALDATE          DATS      8     0Alert: date                                                    
    ALERTTIME       ALTIME          TIMS      6     0Alert: Time value in timeformat                                
    DUMMYALIGN      ALDUMMYC2       CHAR      2     0Alert: Dummy field. Purpose: Alignment of date/time 16 byte    
    LASTVALDAT      ALDATE          DATS      8     0Alert: date                                                    
    LASTVALTIM      ALTIME          TIMS      6     0Alert: Time value in timeformat                                
    LASTVALDUM      ALDUMMYC2       CHAR      2     0Alert: Dummy field. Purpose: Alignment of date/time 16 byte    
    ACTUALVAL       ALVALUE         INT4     10     0Alert: alert value (1 = green, 2 = yellow, ....)               
    ACTUALSEV       ALSEVERITY      INT4     10     0Alert: severity (alerts, monitoring type custom..)             
    VALSYSID        SYSYSID         CHAR      8     0R/3 System, name of R/3 System                                 
    VMSEGNAME     ALMSEGNAME     CHAR     40     0     Alert: name of monitoring segment                                  
    VALUNIQNUM     ALAIDUID     CHAR     10     0     Alert: Unique Identifier to be used in AID (char10)                                  
    VALINDEX     ALINDEX     CHAR     10     0     Alert: internal handle                                  
    VALERTDATE     ALDATE     DATS     8     0     Alert: date                                  
    VALERTTIME     ALTIME     TIMS     6     0     Alert: Time value in timeformat                                  
    VALERTDUM     ALDUMMYC2     CHAR     2     0     Alert: Dummy field. Purpose: Alignment of date/time 16 byte                                  
    COUNTOFACT     ALCNTACTAL     INT4     10     0     Alert: MT Val: Count of active Alerts                                  
    COUNTSUM     ALCNTSUMAL     INT4     10     0     Alert: MT Val: Sum of Alerts in MT                                  
    VISUSERLEV     ALVISILEVL     INT4     10     0     Alert: MTE type dev cust: Visible on user level (op,exp,dev)                                  
    TDSTATUS     ALTDSTATUS     INT4     10     0
         Alert: MT: Type Def Status
    Welcome to SDN.
    Regards,
    Rich Heilman

  • Errors While Transporting Transformations and DTPs

    Hi Experts,
    Iu2019m trying to transport transformations and DTPs from DEV to QA and am getting the following error messages.  Does anyone know whatu2019s happening and how I can fix this?
    Thanks,
    Janice
    The following are excepts from the log of the transport organizer with further SAP supplied information on the error messages.
    Transformations:
    Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode) 
    Activation of Objects with Type Transformation                                                  
    Checking Objects with Type Transformation                                                       
    Checking Transformation 06C3WE26JQY0VSZPNMOZFKD0W416PRU4                                        
    No rule exists                                                                               
    Target RSDS 0ACCOUNT_TEXT QA1CLNT400 is not allowed                                             
    Target RSDS 0ACCOUNT_TEXT QA1CLNT400 is not allowed
    Message no. RSTRAN802
    No rule exists
    Message no. RSTRAN514
    DTPs:
    Start of the after-import method RS_DTPA_AFTER_IMPORT for object type(s) DTPA (Activation Mode)
    Conversion of T version from DTP DTP_4FG5GXT9OLNN3YM3QFMW9V3W5 to M version...                 
    Conversion of T version from DTP DTP_4FK894515QD0O9UM4JSJPIB91 to M version...                 
    Activation of Objects with Type Data Transfer Process                                          
    Saving Objects with Type Data Transfer Process                                                 
    Saving Data Transfer Process DTP_4FKN7KAKCOLQ3ROIB7U7DV13A                                     
    Transformation 06C3WE26JQY0VSZPNMOZFKD0W416PRU4 is inactive (cannot be executed)               
    Error saving Data Transfer Process DTP_4FKN7KAKCOLQ3ROIB7U7DV13A                               
    Transformation 06C3WE26JQY0VSZPNMOZFKD0W416PRU4 is inactive (cannot be executed)
    Message no. RSTRAN715
    Diagnosis
    The transformation 06C3WE26JQY0VSZPNMOZFKD0W416PRU4 is inactive (not executable).
    This can be caused, for example, by a change made to the source object or target object of the transformation.
    The transformation connects the source  to the target .
    Procedure
    The transformation must be reactivated.
    Error saving Data Transfer Process DTP_4FKN7KAKCOLQ3ROIB7U7DV13A
    Message no. RSO843

    Thanks so much everyone for your suggestions.  Iu2019ve tried them all and hereu2019s what I now have:
    Anil u2013 Active datasources were included in the original transport.  I tried retransporting and got the same error messages.
    Voodi u2013 0ACCOUNT_TEXT was resident in the Q system as a 3x datasource.  I replicated it as a 70 datasource in D and this is what was transported to Q.  It is a 7.0 datasource in Q.  I got the same error messages when I tried transporting just the transformations.
    Jayaram - 0ACCOUNT is active in the Q system and is currently being used in transformations other than the one Iu2019m trying to import.
    Godhuli u2013 I not only re-replicated the datasource in D, I reactivated the transformations and DTPs and resaved the InfoPackages.  I tried retransporting with a new transport request and it failed with the same error messages.
    Is there anything else anyone can think of?
    Thanks,
    Janice

  • Error While Transporting Transformation and DTP

    I am trying to transport Transformation and DTP.But its giving following error.
    <b>Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)   
    InfoObject xxxx has a characteristic routine, but no rule                                  
    InfoObject xxxx has a characteristic routine, but no rule                                   
    InfoObject xxx has a characteristic routine, but no rule                                      
    InfoObject xxx has a characteristic routine, but no rule                                   
    No rule exists                                                                               
    Transformation  : Rule 1 could not be imported                                                    
    Transformation  : Rule 2 could not be imported                                                    
    Transformation  : Rule 8 could not be imported                                                    
    Transformation  : Rule 9 could not be imported                                                    
    Transformation  : Rule 60 could not be imported                                                   
    Transformation  : Rule 109 could not be imported                                                  
    Transformation  : Rule 128 could not be imported                                                                               
    Start of the after-import method RS_DTPA_AFTER_IMPORT for object type(s) DTPA (Activation Mode)   
    Conversion of T version from DTP xxxx to M version...                    
    An exception has occurred                                                                               
    </b>
    Any help.Thanks

    Hello,
    Do you have any routines in the transformation you are trying to transport. Looks like its missing some routines that needs to be transported.
    Hope that helps.

  • Assignment of Step type and CR step for MDG_S

    Hi
    This is in continuaton for thread MDG_S workflow.
    I original issue which is for MDGS when I assigned WS543000005 to CR type and sumitted CR goes no where,
    As as per SWEL it  shows No Reciver Found enen though GET_AGENT table is maintained.
    In another system I found that WS531000044 is assigned ti CR Type Then I tested it and found that CR creates Work Items also upto final processing.
    as per below
    Before CR Submission : CR status is 02: Changes to be executed
    After CR Submission : CR status is 01:To be considered and Approved
    After CR Reviewer approves : CR status is 09: Dependant Data to be processed /Approved
    After Purchase reviewer Finalize processing :CR status is 09: Dependant Data to be processed /Approved
    After Finainace reviewer Finalixe processing :CR status is 09: Dependant Data to be processed /Approved
    Now I can not see CR any where even though CR step 04 and 04 assigned to my user ID
    I have some questions as Description in Define Change Request Steps is not Mataching with description in GET_AGENT desesion table.
    Also it is observed that step 80 is not assigned to WS531000044 in IMG node Define Change Request Steps but it can be seen in GET_AGENT decesion table and step no 06 and 07 does not appears in GET_AGENT decesion table ( In edit mode).
    Can you explain from where assignment of  CR steps to CR type in desion table are taken ino accout ?
    Why description is not matched for steps under IMG and in decesion table?
    Can you explain me releationship between CR step and step type,CR Status and where they \maintained in IMG and how proceeses modelling is diffenent t for determination of Next CR step in case of WS531000044 ?

    Please keep in mind that "hard-wired" workflow templates are just that: hard-wired. This means that a specific workflow template (for example WS53100044) will always have the same number of steps, each step will always have the same type and number, agents will always be assigned in the same way, and those can't be altered by configurations. To understand each workflow template's behavior, you can either open that template in transaction PFTC or SWDD, or alternatively, read the exact behavior in SAP Help documentation. You basically need to google the workflow template number and you should be able to find the description of each template's behavior (by the way, the number you type has an extra zero so if you can't find a match on Google, you will know why ).
    Now, the assignment of CR steps to CR type is done in the workflow template itself and NOT in the decision table. See the first screenshot:
    The step number above "should" correspond to what is in the configuration table (for readability and consistency of documentation purposes). However, if for some reason, it does not, the hard-coded value is the value that will actually be considered. So, in technical terms, the assignment of step numbers in MDGIMG has no influence on how the workflow template will behave. Again, the main purpose is for the corresponding description in the step number configuration table to show on the CR window.
    The other thing is the step type. A step type purpose is mainly to indicate what set of buttons will show at the top of the CR window. The fact that step types are represented by numbers confuse a lot of people with step numbers. I would have personally preferred if step types were a 2-char field so that a clear distinction can be made between step types and step numbers. In any case, buttons on the CR correspond to actions and you can see in MDGIMG that you can assign step types to actions. SAP delivers a pre-defined set of step types and associated actions. Those must NOT be altered because they could break the standard workflow templates. However, you can create your own custom step types and link them with as many actions (standard or custom actions) as you like. But again, you can't assign those custom step types to hard-wired workflow templates. You can only use them in your custom workflow templates or in the rule-based workflow.
    Now, the question is how does the hard-wired workflow know what step type to use. The answer is easy: you can either find that in the SAP Help documentation or in the workflow template definition in transaction SWDD. For the above screenshot, the step type is 2. You can find that if you double-click the task ID TS75707980 (or display it using transaction PFTC) and look in the "Cntainer" tab. In this case, this task will ALWAYS have type 2. Other tasks are assigned different step types or are more dynamic in the sense that they expect the step type to be passed from the main workflow template calling them. For example TS53200002 will always have type 7, TS60808005 will always have type 5, and TS60807954 accepts the step type dynamically. This last one is the one used in the rule-based workflow (hence it has to read the step type configured in the decision table).
    I hope this answers you question. You definitely need some level of workflow design/build knowledge in order to be able to completely understand all of this. Hopefully, this gives you a good starting point.

  • How to use the selection profile and status profile for production order?

    Hi expert,
       I want to know how to use the selection profile and status profile for production order. what's the usage for these two selection profile and status profile ?
      Please help me.
      thanks in advance.
      george.shi

    Hi George,
    There are are two types of statuses.One is system status and second one is user status.These statuses will tell us current situation of an order.
    We can't change system statuses.But we can create our own statuses through status profile.With this profile we can control user statuses.
    In this status profile,
    1.We define the sequence in which user statuses can be activated,
    2.We define initial statuses
    3. Allow or prohibit certain business transactions.
    Selection profiles are used to select the objects (say production orders) with different status combinations.We assign status profiles to selection profiles in BS42 T-Code.
    Regards,
    Raja.
    Edited by: Rajarao on Oct 30, 2008 6:21 AM
    Edited by: Rajarao on Oct 30, 2008 6:22 AM

Maybe you are looking for

  • Ethernet LAN not working after upgrading to windows 8.1

    After upgrading from Windows 8 to 8.1, my Ethernet LAN is no longer working. Wireless LAN connectivity is OK. I have run the HP Support Assistant and downloaded the drivers for 8.1. Hovever, I do not see a 8.1 driver listed for the Ethernet LAN.

  • Can I create a PDF with embedded Postscript Type 1 fonts when ordering?

    I have Adobe Acrobat Professional version and can set up a Postscript file to be distilled with the proper settings for print. I often do this for professional printers. Are there settings available for book orders, and if so, can I send my own PDF t

  • IPhone SDK running on phone

    I can run an app in the simulator, but when I set the Target to the phone it gives me an error "Error: not device found". This despite the fact that the phone shows up in the Organizer window with a green light, so it obviously found the phone. Has a

  • Error 0xc00007b occurs when opening Photoshop CS6?

    Trying to re-install after Windows 7 crashed and service centre re-installed the OS.  now CS6 Photoshop doesn't come up cleanly.  it gives error 0xc000007b

  • ActiveX Bridge tutorial

    Hi, Can anyone please point me to a turorial or guide on how to use the ActiveX bridge? I am basically looking for a description on how to incorporate my bean into Microsoft Word, for example. Your help is appreciated. Thanks, Walter.