Re:Solution Manager

what is solution manager?

Hi,
SAP Solution Manager is a centralized, robust solution management toolset that facilitates technical support for distributed systems -- with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. It combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. As part of SAP NetWeaver, SAP Solution Manager is included in the annual maintenance fee for SAP solutions.
SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
SAP Solution Manager features and functions include:
mySAP Business Suite implementation -- SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
Global rollout -- The toolset eases process standardization and harmonization across organizations and locations by providing proven methodologies and all necessary functionality. You can more easily implement standardized settings at local sites, because configuration settings needn't be re-entered into local components.
Synchronization of custom settings -- With SAP Solution Manager, you can maintain consistency as you customize your heterogeneous IT environment. It enables safer administration of customization, less error-prone replication of custom settings, and simpler consistency checks. SAP Solution Manager reduces manual synchronization efforts by automatically distributing custom settings to various systems simultaneously, and by centrally managing all requests to synchronize settings.
Testing -- SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
IT and application support -- The support desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
Solution monitoring -- SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
Service-level management and reporting -- SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
Service processing -- SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
follow the links,
My weblog for Testing via solman
/people/community.user/blog/2006/12/07/organize-and-perform-testing-using-solution-manager
Also the foll links:-
http://service.sap.com/rkt-solman
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce0b74e3-0601-0010-29a0-f2a6af98ef06
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5348ada6-0301-0010-f38f-a5076178843e
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5d29d690-0201-0010-2f9f-a0f957dee385
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce89c290-0201-0010-5985-dd64605111fd
https://forums.sdn.sap.com/click.jspa?searchID=4444970&messageID=1050611
http://help.sap.com/content/documentation/solutionmanager/index.htm
SAP Solution Manager Ready [original link is broken]
Please reward points.

Similar Messages

  • Create a Support Message in Production system showing up in Solution Manage

    Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
    I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
    Thanks
    Paul

    Hi Paul
    The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
    Make sure your RFC's are trusted and that you have SAP ALL during config.
    I hope this will help:
    Setup Service Desk
    Steps to follow while configuring support desk.
    1) Implement the note 903587 .
    2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
    3) Check all the objects in the table BCOS_CUST using transaction SM30.
    Appl : OSS_MSG
    + :W
    DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
    + :CUST 620
    + :1.0.
    *4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
    4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
    4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
    4.3) Activation of the following components has to be done by replicating the previous steps
    3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
    3.2) SOLMAN40_SDESK_ACTIONLOG_001
    3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
    3.4) SOLMAN40_SDESK_TEXTTYPES_001
    *Depends upon the number of inactive BC set objects that we have after the upgrade.
    4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
    5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
    Number ranges for ABA notifications
    5.1) create an internal and external number range using transaction DNO_NOTIF.
    5.2) assign number range intervals to groups internal and external.
    5.3) SLF1 is the internal number range group
    5.4) SLF2 and SLF3 is the external number range interval
    5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
    5.51) Go to transaction DNO_CUST01
    5.52) From the GOTO menu select the menu item DETAILS
    5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
    The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
    Number ranges for Support Desk notification
    5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
    5.6) Then assign both the external and internal numbering
    5.61) Go to SPRO and then to SAP Solution Manager
    5.62) Then select General Settings and then select Transaction types
    5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
    5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
    5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
    6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
    6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
    6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
    7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
    8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
    8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
    8.2) Select the item Service Desk and then to general settings.
    8.3) Execute the category u2018Define Transaction Typesu2019.
    8.4) Select the transaction type as SLFN
    8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
    9) Activate the partner/ Organization
    9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
    9.2)Find the entries starting with HRALX
    HRALX-HRAC WITH VALUE 'X'.
    HRALX-OBPON WITH VALUE 'ON'.
    HRALX-PBPON u2018ONu2019.
    HRALX-MSGRE u2013 u20180u2019.
    9.3) If entries are not found create it.
    10) Generate Business partner screens
    10.1) Go to transaction BUSP.
    10.2) Execute the report with the following parameters
    CLIENT - Client in which business partners should be created (solution manager client)
    APPLICATION OBJECT-
    SCREEN - *
    Generate all/ selected screens - All screens.
    delete sub screen containers -
    11) implement SAP note 450640.
    11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
    11.2) Execute it with test mode box unchecked.
    If a new relationship is to be created then steps 12 and 13 has to be followed
    12) To create a relationship category
    12.1) Go to transaction BUBA
    12.2) Select the entry CRMH00: Undefined relationship
    12.3) click on copy
    12.4) Rename CRMH00 to ZCRMH00.
    12.5) CREATE A RELATIONSHIP CATEGORY.
    IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
    ' FROM BP2 : IS A PART OF ATTUNE
    13) Add the relationship category to the support team partner function
    13.1)Use SPRO
    IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
    -> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
    13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
    13.3) In the field relation ship category, Select the newly created relationship category and save.
    14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
    15) Create a new access sequence for the support team determination
    15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
    SAP Solution Manager -> Configuration ->
    -> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
    ->Define Access Sequence
    15.2) Click on New Entries
    15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
    15.4) Create an new Individual Access with the following value:
    u2022 Batch Seq: 10
    u2022 Dialog Seq : 10
    u2022 Source : Business Partner Relationship.
    u2022 Detail on the source:
    u2022 Partner Function : Reported By (CRM)
    u2022 Mapping/restrictions
    u2022 Flag Mapping/definition for partner being Searched
    u2022 Partner Function in Source: Support Team (CRM).
    Save it.
    This Access Sequence will give us the Partner which has the relationship assigned
    to the Support Team in the Reported By partner data.
    16) Adapt the partner determination schema/Function
    16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
    SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
    -> Partner Determination Procedure -> Define Partner Determination Procedure.
    16.2) The two options to adapt partner determination schema are
    16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
    16.22) select the line starting with SLFN0001 or the newly created procedure.
    16.23) Double Click on Partner Function in Procedure.
    16.24) Select the Partner Function "Support Team", and click Details.
    16.25) in the detail view only change the Partner Determination/access Sequence to
    the one we've just created. Save your entry.
    17) Create a root organizational model.
    17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
    17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
    17.3) enter the organizational unit, the description and save it.
    18) Create the support team organization
    18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
    19) Create the business Partners.
    19. 1) Key users- End user (Business Partner General) ,Address should be specified.
    19.2) go to the transaction BP.
    19.3) create a new Person, Select the role: Business Partner (Gen).
    For Identification of the key user
    19.31) click on the identification tab
    19.32) enter a line in the identification number formatted as follows
    IDTYPE : CRM001.
    Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
    eg: USER NAME : USER1.
    CLIENT : 100.
    SID : ER1.
    INSTALL NUMBER : 123456789.
    IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
    20) Message Processors- Support Team members .
    20.1) they should be created first as the users in the corresponding client of the solution manager.
    20.2) As business partners they will have the role 'EMPLOYEE'.
    20.3) Go to transaction BP .
    20.4) Create New Person with the role employee.
    20.5) In the Identification tab you should enter the user name in the employee data/User Name.
    eg: username: proc1
    enter proc1 in the field User name.
    21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
    22) Assign the business partners (Message Processors) to the previously created support team.
    22.1) Go to transaction PPOMA_CRM.
    22.2) Select the support team 1.
    22.3) Click on create
    22.4) select position
    22.5) call it 'MPROC_T1/Message Processors for team 1
    22.6) Replicate it for the other support teams.
    22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
    choose owner/Business Partner find and select the business partner
    22.8) Validate and Save it.
    22.9) If the assignment of business partner is not possible then implement the note 1008656
    Or 997009
    23) Create the iBase component
    23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
    23.2) or use the transaction IB51 to create the installed base.
    23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
    24)Assign Business Partners to iBase Components
    IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
    -> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
    *--optional--
    If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
    Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
    Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
    Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
    now to assign the partner Function "System Administrator".
    25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
    26)Define the transaction variant for the message processors
    Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
    Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
    27) Go to transaction PFCG
    27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
    27.2) Give a description Message Processor role and save it.
    27.3) Go to the menu tab and choose add report
    27.4) select the report type : ABAP Report
    27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
    27.6) Enter the previously created variant.
    27.7) flag the skip initial screen box.
    27.8) flag the SAPGUI for windows.
    27.9) Create a new transaction with tcode starting with Y or Z.
    27.10)Display this transaction and check the values at the bottom of the screen
    in the subscreen Default Values, you should have the following parameters:
    u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
    u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
    u2022 D_SREPOVARI-NOSELSCRN = X
    And also all the user should have the correct role.

  • Define Service Desk Destination in the Solution Manager System (Dump creen)

    hi,
    in SPRO when i click on Define Service Desk Destination in the Solution Manager System
    i got dump screen with the error below 
    any help?
    Runtime Errors         SAPSQL_EMPTY_TABNAME
    Except.                CX_SY_DYNAMIC_OSQL_SYNTAX
    Date and Time          13.07.2008 14:05:57
    Short text
        A dynamically specified FROM clause has an unexpected format.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLSHI2" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not
         caught in
        procedure "STREE_READ_NODE_GENER" "(FUNCTION)", nor was it propagated by a
         RAISING clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        The running ABAP program attempted to execute an Open SQL statement in
        which a FROM clause was specified dynamically in the field "TABLE_NAME". In
         this
        FROM clause, either a table name after a join operator is missing, or an
         alias name after the key name "AS". The field "TABLE_NAME" could be empty as
        well.
    regards

    Hi,
    I am facing the same problem. What is SP15 ?
    Is there any SAP Note that can be applied to correct this ?
    Thanks.

  • Implementing the Enterprise Support in Solution Manager

    Hi Experts,
    Can anybody tell me what are the pre requisites to implement Enterprise support in solution manager?
    Also let me know what are steps involved in implementing the enterprise support.
    Thanks in Advance
    Hari

    Hello Hari,
    In order to implement Enterprise Support your organization should registered as a Value Added Reseller(VAR) with SAP. You can get all the required documentation under https://websmp104.sap-ag.de/solutionmanager --> Information for VARs, ASPs and AHPs which is in the left hand side of the page. However, you need to have a S-user ID of the VAR.
    The following are the steps need to perform in implementing the Enterprise Support firmly known as Service Desk for VARs.
    1. SAP Solution Manager basic settings (IMG)
      a) Initial Configuration Part I
      b) Maintain Profile Parameters
      c) Maintain Logical Systems
      d) Maintain SAP Customer Numbers
      e) Initial Configuration Part II
         1) Activate BC Set
             a) Activate Service Desk BC Set
             b) Activate Issue Monitoring BC set
             c) Set-up Maintainance optimizer
             d) Change online Documentation Settings
             e) Activate Solution Manager Services
             f) Activate integration with change request Managemnt
             g) Define service desk connection in Solution Manager
       2)Get components for SAP Service Market place
            a) Get SAP Components
       3) Get Service Desk Screen Profile
           a)generate Business Partener Screen
       4)Copy By price list
           a)activate Service Desk BC Set
           b)Activate Issue Monitoring BC set
           c)Set-up Maintainance optimizer
          f) Business Add-In for RFC Connections with several SAP customers
          g) Business Add-In for RFC Connection of Several SAP Cust. no.
          h) Set-Up SAP Support Connection for Customers
          i) Assign S-user for SAP Support Portal functionality
          j) Schedule Background Jobs
          k) Set-Up System Landscape
          l) Create Key Users
          m) Create Message Processor
    2. Multiple SAP Customer Numbers
          a) Business Add-In for RFC Connections with several SAP customer numbers
          b) Set-Up SAP Support Connection for Customers
    3. Data transfer from SAP
          a) Data Transfer from SAP
    4. Create u201COrganizationu201D Business Partner
    5. Service Provider function (IMG)
          a) Business Add-In for RFC Connections with several SAP customer numbers
          b) Business Add-In for Text Authorization Check
          c) Activate BC Set for Service Provider
          d) Activate Text Types
          e) Adjust Service Desk Roles for Service Provider Menu
    6. Service Provider: Value-Added Reseller (VAR)
          a) Business Add-In to Process Actions (Post-Processing Framework)
         b) Activate BC Sets for Configuration
         c) Create Hierarchy and Product Category
         d) Set-Up Subcategories
         e) Create Business Partner as Person Automatically
         f) Set-Up Automatic Confirmation of Messages
        g) Maintain Business Partner Call Times
        h) Set-Up Incident Management Work Center
    7. Work Center (Web UI)
        a) Activate Solution Manager Services
        b) Assign Work Center Roles to Users
    Hope it helps.
    Regards,
    Satish.

  • Install Solution Manager in RedHat Enterprise 6 with Oracle 11

    Hello ,
    In the marketplace-PAM,  RedHat Enterprise 6 is not listed as approved for EHP1 Solution Manager 7.0 64 bit (unicode) with Oracle.
    Does anyone have any information on this subject?
    Has anyone installed the Solution Manager 7.0/Oracle with RedHat Enterprise 6?
    tks

    Yes, you are correct. Apart from PAM, following Note confirms this. RHEL 6 is not supported yet for Oracle, is in planning stage.
    Note 1565179 - SAP software and Oracle Linux
    Thanks

  • System landcape in large enterprise with solution manager

    Dear Guru,
    Do you have any ideas of how to set up Solution Manager in a big national enterprise?  Let's suppose
    a big company has a headquarter and serveral branches.
    Every branch has its ERP, BW, etc,  do you think it is better to set up respective Solution Manager system
    for each branch or just create a powerful one centrally in the headquarter. Of course the latter means
    less management but more authorization seperation related actions.
    Is there any recommendation for this situation? Your opinion and insight is highly appreciated.
    Thanks
    Ray

    Dear Gugu,
    I know Solution Manager support some scenarios for multiple customer .e.g VAR in service desk.
    But is it possible for hide solution or project infomation, especially content of respective business blueprint
    to different customers?
    I mean we want to use one single Solution Manager for multiple customers, but customers do not want their
    owned document and business process information shared with other customers.
    e.g.  one customer log on to SOLMAN, then he could view project or solution information of other customer,
    furthermore, he could also build up his business blueprint referring to other customer's  business blueprint.
    Is it possible to segregate this infomation?
    Thanks a lot.
    Ray

  • Logical systems while implementing charm in solution manager

    Hello Everybody,
    I just wanted to know how many logical systems we need while implementing charm in solution manager 7.0. I have 3 clients in development , 3 clients in Quality and 1 client in production.
    Thank you,
    vikram.

    Hi Vikram,
    Yes, i1n ChaRM we always work with logical systems, I mean clients.
    The standard is:
    DEV -> QAS -> PRD
    However, you can also use:
    - Minimum
    DEV -> PRD
    - Target groups
    DEV -> QAS -> PRD
             - > TST
    DEV -> QA1 -> QA2 -> PRD
    DEV -> QA1 -> PR1
             -> QA2 -> PR2
    There are a lot of combination possible.
    BR
    Fernando

  • XI 3.0 and BW 3.5 system type/logical component in Solution Manager

    We are in the process of performing an upgrade for ERP 2004, XI 3.0 and BW 3.5. Initially this is being done in the sandpits. All systems are configured and connected our Solution Manager to download the packages.
    We are unable to determine what type of system the XI 3.0 and BW 3.5 should be configured under. For example, previously we had an issue where ERP was configured as ECC 5.0 rather than ERP 2004. This was causing an issue in MOPZ where the upgrade option wasn't visible in a maintenance transaction. The same issue is now happening for XI and BW.
    Please advise on the system type (logical component to use) for XI 3.0 and BW 3.5 in Solution Manager as SAP have made it very confusing. Currently both are under type Netweaver 04.
    Regards,
    -Rohan

    Hi
    I believe that SAP hasn't upgrade option for BW 3.5, Check link:
    https://service.sap.com/solman-mopz
    Upgrade
    a "straight" upgrade for SAP Business Suite (upgrade from SAP ERP 2004 to SAP ERP 6.0, for example) is not supported by Maintenance Optimizer
    Upgrade with an Installation of an Enhancement Package is supported for SAP ERP, SAP SCM, SAP SRM and SAP CRM
    Regards
    William Neira

  • Using HR data in R/3 to create business partners in Solution Manager

    Is it OK for me to setup Solution Manager to automatically download HR data from R/3 to create the Business Partners (employee role) in Solution Manager?
    We have setup SAP CRM 4.0 to automatically download the HR data and create Business Partners (employee role) in CRM.  Since Solution Manager has the CRM component in it, I assume we can do it as well in Solution Manager.
    Regards,
    Mel Calucin
    Bentley Systems

    We did it, i don't see the problem...

  • SAP GUI 7.10 - Issue reading files from Solution Manager

    Hi everyone,
    We have just installed SAP GUI 7.10 on our PC and have tried to open documents from Solution Manager.
    On both Display and Change mode we are getting "The document cannot be displayed" (SOLAR_DOC021)
    Can you suggest anything regarding the source of the problem? Any quick resolution?
    Thank you
    Corinne

    Found it myself. Tricky indeed.
    http://service.sap.com/patches
    - Search for Support Packages and Patches
    - Enter Search Term "SAP GUI"
    - Select SAP GUI FOR WINDOWS
    - Select SAP GUI FOR WINDOWS 7.10 CORE
    - Select SAP GUI FOR WINDOWS 7.10 CORE, on the next page also
    - Select Win 32
    - Arrive at avail. downloads
    Regards,
    Nathan

  • DDIC Password fails in middle of Solution Manager Installation

    I'm performing a new install of Solution Manager 7.0 (4.0) on HPUX IA64 11.23. This is a brand new Landscape. The installation has halted at phase 29/47 "Check DDIC password", and reports the error:
      Test login to SAP System SMA failed.
      SOLUTION: Make sure that the system is started, that the user DDIC exists and that the password of user DDIC is correct.
    From the SAPGUI 7.10., I was unable to login as DDIC or SAP. I used the master passwords given in the install. I also tried the default passwords as mention in another thread password '19920706' for DDIC and '06071992' for SAP.
    I was able to login with SAP* password PASS after adding login/no_automatic_user_sapstar=0
    to the default profile and restarting SAP, but was unable to change the DDIC password because change and transport system not configured. 
    How do I get past this point in the installation process?

    This problem is now resolved. The problems of:
    1) The "Check DDIC password" phase of sapinst of SM 7.0 was failing with DB-Error 0.
    Fix: Install latest kernel patch. Problem was fixed with NW 7.0 kernel patch 133. I installed kernel patch 159. The kernel patch had to be installed via the old method of using SAPCAR to untar the files, backup kernel dir, shutdown sap, and copy files over to kernel dir. See note 19466.
    2) The Warning messages
    WARNING => IcmJ2EEScheduleFunc: Cannot
    access "/sap/public/icman" -
    please check node in TA sicf [icxxman_mt.c 2206]
    was resolved by TA SICF by SERVICE HOST -> active
    to activate the complete default_host subtree.

  • Question for installing Solution Manager & ECC 5.0

    Any idea for installing Solution Manager 3.2 on Windows server 2003 with Oracle9i problem when install Database Instance. Installation failed when the intallation progress went to Oracle Post-Load Action.
    The message from startsap log file is
    "running C:\usr\sap\T01\SYS\exe\run/sapstart.exe name=T01 nr=03 SAPDIAHOST=saptest02 -Wait
    start service SAP01_03 on machine
    saptest02
    OpenService of SAPT01_03 failed. Error#: 1060
    CreateNamedPipe for
    saptest02\pipe\SAP01_03 Failed, Extended Error #2
    start service SAP01_03 on machine
    saptest02
    OpenService of SAPT01_03 failed. Error#: 1060
    C:\usr\sap\T01\SYS\exe\run/sapstart.exe=>sapparam(1c): No Profile Used."
    Another question is about installing the Oracle database software: should we choose Create Databse or not when install Oracle Server Software only?
    Is my installation process as following correct?
    ->SELECT A PRODUCT TO INSTALL:
      Oracle9i Database 9.2.0.1.0
    ->WHAT TPYE OF INSTALLATION DO YOU WANT:
      Enterprise Edition
    ->SELECT A DATABASE SUITED TO YOUR NEEDS:
      Software only
    After end of installation
    install Oracle9i Client 9.2.0.1.0->Administrator
    Thanks a lot

    Hi Shusen, I´m trying to do the same think (Install ECC IDES with Oracle 9i in one computer for educational propose), can you help me with this:
    1.I made the same Oracle install process because when I tried with sapserver.cmd nothing happened, for that reason i made:
    SELECT A PRODUCT TO INSTALL:
    Oracle9i Database 9.2.0.1.0
    ->WHAT TPYE OF INSTALLATION DO YOU WANT:
    Enterprise Edition
    ->SELECT A DATABASE SUITED TO YOUR NEEDS:
    Software only
    After end of installation
    I did not install client, is this correct?
    2.After install this, I run the sapins.exe but  show me this error: INSTALL FIRST SAP J2EE ENGINE, I download the JAVA SDK from JAVA page (java_ee_sdk-5-windows) but did not fix the problem: Do you know what file is this? Or, where is it in the DVD installation?
    Thanks in advance if you or somebody can help me and excuse me if the answers are obviously, but I´m not a system engineer I´m only try to install IDES for learn SAP WM.
    Thanks.

  • Solution Manager on Linux x86_64 installation problem

    I try to install Solution Manager 4.0 on Linux X86_64 platform. Unfortunately i receive error "the JDK installed in directory /usr/lib/java does not support the 64 bit data model". And there is no J2SDK for Suse linux x86_64 (or at least i can't find it. Please help!!!

    OK. I solved the problem by using IBM Java. Also there is an SUSE version of SUN Java 1.4.2 for 64 bit systems.

  • Unable to create tickt in service desk - Solution manage.

    Hello,
    I have implemented service desk ( Solution manager) and It is working fine for most of the system but i am getting error while creating a ticket in service desk for one system.
    Due to some RFC connection problem i have regenerated the RFC ( trusted , Read and TMW) from Solman to Satellite system.
    and now I am not bale to create ticket for that system.
    Error message :
    The URL http://cismp.cargotec.com:8014/sap/bc/bsp/sap/dswpnotifcreate/msg_new.do was not called due to an error.
    Note
    The following error text was processed in the system SMP : Error SYSTEM_CORE_DUMPED occured. P1=11
    The error occurred on the application server cismp_SMP_14 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
    Method: DO_HANDLE_EVENT of program CL_DSMOP_BSP_NOTI_CTRL========CP
    Method: DISPATCH_INPUT of program CL_BSP_CONTROLLER2============CP
    Method: DO_REQUEST of program CL_DSMOP_BSP_NOTI_CTRL========CP
    Method: DO_REQUEST of program CL_BSP_CTRL_ADAPTER===========CP
    Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_BSP===============CP
    Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
    Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
    Module: %_HTTP_START of program SAPMHTTP
    Can any body guide me what should be done to resolve the issue.

    Hi Prakhar,
    As i mentioned workcenter is working fine for all other systems. and user have all roles same as in other  systems.
    BP is created and we are trying to create ticket from Solman itself  so there is no point to maintain bCOS_CUST table.
    but still we are not able to create ticket only for one system.
    Error Message :
    Error when processing your request
    What has happened?
    The URL http://cismp.cargotec.com:8014/sap/bc/bsp/sap/dswpnotifcreate/msg_new.do was not called due to an error.
    Note
    The following error text was processed in the system SMP : Error SYSTEM_CORE_DUMPED occured. P1=11
    The error occurred on the application server cismp_SMP_14 and in the work process 1 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
    Method: DO_HANDLE_EVENT of program CL_DSMOP_BSP_NOTI_CTRL========CP
    Method: DISPATCH_INPUT of program CL_BSP_CONTROLLER2============CP
    Method: DO_REQUEST of program CL_DSMOP_BSP_NOTI_CTRL========CP
    Method: DO_REQUEST of program CL_BSP_CTRL_ADAPTER===========CP
    Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_BSP===============CP
    Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
    Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
    Module: %_HTTP_START of program SAPMHTTP
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SMP in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server cismp_SMP_14 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server cismp_SMP_14 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 011 -u: XABHYABH -l: E -s: SMP -i: cismp_SMP_14 -w: 1 -d: 20091006 -t: 141511 -v: RABAX_STATE -e: SYSTEM_CORE_DUMPED
    Regards,
    Bhavesh

  • Setting up EarlyWatch in Solution manager

    Hi Guys
      I am trying to configure Early Watch in solution manager(System Id u2013SOL , Installation No - 0020306432) for an satellite system (System Id -DEV u2013Installation No : 0020181089).
    I have followed all the configuration steps listed below :
    1.     Configuration RFCs to market place SAPOSS and to satellite Systems and RFC Back to solution manager. All RFC like SAPOSS and Back has been tested from SDCCN (Solution manager and satellite system)
    2.     Configured  SDCCN in solution manager and in satellite system except u201CGenerate Includes for Service data control centeru201D in SPRO of solution manager as this process is getting time out and not letting us to generate all the includes
    3.     Activated Service data Control center locally and assign solution manager as u2018Master system for allu2019.
    4.     Activated SDCCN in satellite system(DEV) ,Created Earlywatch Service in Solution manager for DEV system  and also created/Started u2018Refresh Sessionu2019 in SDCCN of DEV(Satellite system)
    5.     This successfully shows me Early watch link in u2018Waitingu2019 Status in solution manager.
    6.     I click on u2018Start Service Processingu2019 to Schedule/Run u201CSM:EXEC SERVICESu201D background job .
    Problem :  Background job u201CSM:EXEC SERVICESu201D get cancelled after some time and throws a Dump which is pasted below.
    Dump shows that an include u2018/1CAGTF/IF_LOGFUNC_000393u2019  is missing which should have been generated while activating the includes for SDCCN in SPRO of solution manager.
    I found includes from u2018/1CAGTF/IF_LOGFUNC_000001u2019 to  u2018/1CAGTF/IF_LOGFUNC_000353u2019 in the system as it seems that not all include have been generated  . 
    *Could you please help me to provide some SAP note so that I would be able to generate all the includes .  *
    DUMP
    Runtime Errors         SYNTAX_ERROR
    Date and Time          24.05.2008 00:01:02
    Short text
    Syntax error in program "RDSVASAEW_ROOT_____________073 ".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "RDSVASAEW_ROOT_____________073
    " in include "RDSVASAEW_ROOT_____________073 " in
    line 96:
    "INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "RDSVASAEW_ROOT_____________073
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    The following syntax error was found in the program
    RDSVASAEW_ROOT_____________073 :
    "INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "mslsol"
    Network address...... "192.168.193.154"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 10
    Shortdump setting.... "full"
    Database server... "MSLSOL"
    Database type..... "ORACLE"
    Database name..... "SOL"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Aug 29 2006 00:18:21"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.2.0) "
    Patch level. 75
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 8176
    EM...... 29266272
    Heap.... 0
    Page.... 24576
    MM Used. 24845128
    MM Free. 236264
    User and Transaction
    Client.............. 600
    User................ "BASISA"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLDSVAS_PROC"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "SAPLDSVAS_PROC" - in "EXECUTE".
    The main program was "RDSMOPBACK_AUTOSESSIONS ".
    In the source code you have the termination point in line 2146
    of the (Include) program "LDSVAS_PROCCD0".
    The program "SAPLDSVAS_PROC" was started as a background job.
    Job Name....... "SM:EXEC SERVICES"
    Job Initiator.. "BASISA"
    Job Number..... 00384300
    Source Code Extract
    Line
    SourceCde
    2116
    ls_stdparameter-versnr           = po_ctnode->versnr.
    2117
    ls_stdparameter-grp              = po_ctnode->grp.
    2118
    ls_stdparameter-id               = po_ctnode->id.
    2119
    ls_stdparameter-reference_versnr = po_ctnode->reference_versnr.
    2120
    ls_stdparameter-reference_grp    = po_ctnode->reference_grp.
    2121
    ls_stdparameter-reference_id     = po_ctnode->reference_id.
    2122
    else.
    2123
    ls_stdparameter-grp              = pf_grp.
    2124
    ls_stdparameter-versnr           = pf_versnr.
    2125
    ls_stdparameter-reference_grp    = pf_grp.
    2126
    ls_stdparameter-reference_versnr = pf_versnr.
    2127
    endif.
    2128
    2129
      Formroutinen aufrufen
    2130
    loop at    actseq
    2131
    into  ls_actrel
    2132
    where exec_time = pf_exec_time.
    2133
    check ls_actrel-exec_time ne gf_exec_time_event
    2134
    or ( ls_actrel-exec_time = gf_exec_time_event and
    2135
    ls_actrel-event     = pf_event               ).
    2136
    call function 'DSVAS_CDMNT_FORM_NAME'
    2137
    exporting
    2138
    pf_container_type = 'A'
    2139
    pf_form_number    = ls_actrel-action
    2140
    importing
    2141
    pf_form_name      = lf_form_name.
    2142
    perform (lf_form_name)
    2143
    in program (program)
    2144
    using ls_stdparameter
    2145
    if found.
    >>>>>
    endloop.
    2147
    endmethod.                    "execute
    2148
    2149
    Collect_Known_Events
    2150
    method collect_known_events.
    2151
    data: ls_actseq type line of ltype_action_sequence_table,
    2152
    lf_event  type dsvasactseq-event.
    2153
    2154
    loop at actseq into ls_actseq
    2155
    where ( exec_time = gf_exec_time_event and
    2156
    event     ne space                 )
    2157
    or   exec_time = gf_exec_time_1
    2158
    or   exec_time = gf_exec_time_2
    2159
    or   exec_time = gf_exec_time_3
    2160
    or   exec_time = gf_exec_time_modus_close.
    2161
    if ls_actseq-exec_time = gf_exec_time_event.
    2162
    read table pt_events with table key table_line = ls_actseq-event
    2163
    transporting no fields.
    2164
    if sy-subrc ne 0.
    2165
    insert ls_actseq-event into table pt_events.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    1
    SY-TABIX
    1
    SY-DBCNT
    0
    SY-FDPOS
    30
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    DSWP: Execute rule set
    SY-MSGTY
    E
    SY-MSGID
    FL
    SY-MSGNO
    046
    SY-MSGV1
    DSVAS_TOOLS_PACKAGE_GET
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080524
    SY-UZEIT
    000049
    SY-XPROG
    SAPCNVE
    SY-XFORM
    CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    11 FORM         SAPLDSVAS_PROC                      LDSVAS_PROCCD0                       2146
    EXECUTE
    10 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCD0                       2142
    LCL_ACTION_SEQUENCE=>EXECUTE
    9 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1741
    LCL_CHECK_TREENODE=>EXECUTE
    8 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1792
    LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
    7 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCCTI                       1806
    LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
    6 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       2025
    LCL_SESSION=>EXECUTE
    5 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       1582
    LCL_SESSION=>CONTEXT_INSTANCES_CREATE
    4 METHOD       SAPLDSVAS_PROC                      LDSVAS_PROCSEI                       1995
    LCL_SESSION=>EXECUTE
    3 FUNCTION     SAPLDSVAS_PROC                      LDSVAS_PROCU02                        303
    DSVAS_PROC_SESSION_OPEN
    2 METHOD       CL_DSMOP_SOLUTION=============CP    CL_DSMOP_SOLUTION=============CM01P   184
    CL_DSMOP_SOLUTION=>START_PERIODIC_SERVICES
    1 EVENT        RDSMOPBACK_AUTOSESSIONS             RDSMOPBACK_AUTOSESSIONS                72
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.      11 Ty.          FORM
    Name  EXECUTE
    PF_EXEC_TIME
    I
    4
    9
    0
    0
    PF_EVENT
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    PO_CTNODE
    |
    | 2000D000 |
    | E0001C00 |
    | PF_GRP |
    |  |
    | 22222222222222222222 |
    | 00000000000000000000 |
    | 00000000000000000000 |
    | 00000000000000000000 |
    | PF_VERSNR |
    | 00000 |
    | 33333 |
    | 00000 |
    | 00000 |
    | 00000 |
    | <%_L02E>-EXEC_TIME |
    | ??? |
    | ?????? |
    | ?????? |
    | <%_L02F> |
    | I |
    | 4 |
    | 9 |
    | 0 |
    | 0 |
    | LS_ACTREL-EXEC_TIME |
    | I |
    | 4 |
    | 9 |
    | 0 |
    | 0 |
    | GF_EXEC_TIME_EVENT |
    | E |
    | 4 |
    | 5 |
    | 0 |
    | 0 |
    | SYST-REPID |
    | SAPLDSVAS_PROC |
    | 5454455455554422222222222222222222222222 |
    | 310C43613F02F300000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | LS_ACTREL-EVENT |
    |  |
    | 2222222222222222222222222222222222222222 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | SY-SAPRL+0(4) |
    | 70 |
    | 33 |
    | 70 |
    | 00 |
    | 00 |
    | LS_ACTREL-ACTION |
    | 108 |
    | 333 |
    | 108 |
    | 000 |
    | 000 |
    | LF_FORM_NAME |
    | ACTION_108 |
    | 44544453332222222222222222222222 |
    | 1349FEF1080000000000000000000000 |
    | 00000000000000000000000000000000 |
    | 00000000000000000000000000000000 |
    | ME->PROGRAM |
    | RDSVASAEW_ROOT_____________073 |
    | 5455454455544555555555555553332222222222 |
    | 243613157F2FF4FFFFFFFFFFFFF0730000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | %_DUMMY$$ |
    |  |
    | 2222 |
    | 0000 |
    | 0000 |
    | 0000 |
    | LS_STDPARAMETER |
    | EA6000000000255###ESESSION                                           00047EA_ROOT |
    | 4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222 |
    | 516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | No.      10 Ty.          METHOD |
    | Name  LCL_ACTION_SEQUENCE=>EXECUTE |
    | PF_EXEC_TIME |
    | I |
    | 4 |
    | 9 |
    | 0 |
    | 0 |
    | PF_EVENT |
    |  |
    | 2222222222222222222222222222222222222222 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | PO_CTNODE |
    |
    2000D000
    E0001C00
    PF_GRP
    22222222222222222222
    00000000000000000000
    00000000000000000000
    00000000000000000000
    PF_VERSNR
    00000
    33333
    00000
    00000
    00000
    <%_L02E>-EXEC_TIME
    <%_L02F>
    I
    4
    9
    0
    0
    LS_ACTREL-EXEC_TIME
    I
    4
    9
    0
    0
    LS_ACTREL-EVENT
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    LS_ACTREL-ACTION
    108
    333
    108
    000
    000
    LF_FORM_NAME
    ACTION_108
    44544453332222222222222222222222
    1349FEF1080000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
    ME->PROGRAM
    RDSVASAEW_ROOT_____________073
    5455454455544555555555555553332222222222
    243613157F2FF4FFFFFFFFFFFFF0730000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    LS_STDPARAMETER
    EA6000000000255###ESESSION                                           00047EA_ROOT
    4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222
    516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.       9 Ty.          METHOD
    Name  LCL_CHECK_TREENODE=>EXECUTE
    PF_EXEC_TIME
    I
    4
    9
    0
    0
    PF_EVENT
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    GF_EXEC_TIME_ATTRIBUTES
    a
    6
    1
    0
    0
    RSJOBINFO
    00000000000000                                  ##
    2222222222222222222222222222222233333333333333222222222222222222222222222222222200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ME
    |
    | 2000D000 |
    | E0001C00 |
    | GT_OPEN_SESSIONS |
    | Table IT_3668[1x44] |
    | FUNCTION-POOL=DSVAS_PROCDATA=GT_OPEN_SESSIONS |
    | Table reference: 1911 |
    | TABH+  0(20) = 807E0D3E000000000000000077070000540E0000 |
    | TABH+ 20(20) = 010000002C000000FFFFFFFF0417010010040000 |
    | TABH+ 40( 8) = 10000000A4318001 |
    | store        = 0x807E0D3E |
    | ext1         = 0x00000000 |
    | shmId        = 0     (0x00000000) |
    | id           = 1911  (0x77070000) |
    | label        = 3668  (0x540E0000) |
    | fill         = 1     (0x01000000) |
    | leng         = 44    (0x2C000000) |
    | loop         = -1    (0xFFFFFFFF) |
    | xtyp         = TYPE#000007 |
    | occu         = 16    (0x10000000) |
    | access       = 4     (ItAccessHashed) |
    | idxKind      = 0     (ItIndexNone) |
    | uniKind      = 1     (ItUnique) |
    | keyKind      = 3     (user defined) |
    | cmpMode      = 8     (cmpManyEq) |
    | occu0        = 1 |
    | groupCntl    = 0 |
    | rfc          = 0 |
    | unShareable  = 0 |
    | mightBeShared = 0 |
    | sharedWithShmTab = 0 |
    | isShmLockId  = 0 |
    | gcKind       = 0 |
    | isUsed       = 1 |
    | isCtfyAble   = 1 |
    | >>>>> Shareable Table Header Data <<<<< |
    | tabi         = 0xC0AB0D3E |
    | pgHook       = 0x00000000 |
    | idxPtr       = 0x78F10D3E |
    | shmTabhSet   = 0x00000000 |
    | id           = 2504  (0xC8090000) |
    | refCount     = 0     (0x00000000) |
    | tstRefCount  = 0     (0x00000000) |
    | lineAdmin    = 16    (0x10000000) |
    | lineAlloc    = 16    (0x10000000) |
    | shmVersId    = 0     (0x00000000) |
    | shmRefCount  = 1     (0x01000000) |
    | >>>>> 1st level extension part <<<<< |
    | regHook      = Not allocated |
    | collHook     = Not allocated |
    | ext2         = Not allocated |
    | >>>>> 2nd level extension part <<<<< |
    | tabhBack     = Not allocated |
    | delta_head   = Not allocated |
    | pb_func      = Not allocated |
    | pb_handle    = Not allocated |
    | GF_EXEC_TIME_BEFORE_REPORT_GEN |
    | R |
    | 5 |
    | 2 |
    | 0 |
    | 0 |
    | GF_EXEC_TIME_INIT |
    | I |
    | 4 |
    | 9 |
    | 0 |
    | 0 |
    | ME->INITIALIZED |
    |  |
    | 2 |
    | 0 |
    | 0 |
    | 0 |
    | GF_EXEC_TIME_AFTER |
    | A |
    | 4 |
    | 1 |
    | 0 |
    | 0 |
    | ME->ACTSEQ |
    |
    2000D000
    C0003C00
    SCREEN
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ME->HAS_TABLES
    X
    5
    8
    0
    0
    SYST
    ##########################A###P##############################################T###ÿ##### u####
    0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
    1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
    0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
    00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
    SY-REPID
    SAPLDSVAS_PROC
    5454455455554422222222222222222222222222
    310C43613F02F300000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ME->CHECK_TABLES
    |
    | 2000D000 |
    | 3000CC00 |
    | No.       8 Ty.          METHOD |
    | Name  LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
    | PF_EXEC_TIME |
    | I |
    | 4 |
    | 9 |
    | 0 |
    | 0 |
    | PF_EVENT |
    |  |
    | 2222222222222222222222222222222222222222 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | PF_CON |
    | SESSION |
    | 5455444222 |
    | 35339FE000 |
    | 0000000000 |
    | 0000000000 |
    | PF_INS |
    |  |
    | 2222222222222222222222222222222222222222 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | ME->DYNAMIC |
    | X |
    | 5 |
    | 8 |
    | 0 |
    | 0 |
    | ME |
    |
    2000D000
    E0001C00
    GF_SESSION_DEF_TYPE_MORE_DEV
    L
    4
    C
    0
    0
    ME->ACTIVE
    X
    5
    8
    0
    0
    GF_SESSION_DEF_TYPE_VERSION
    V
    5
    6
    0
    0
    ME->CON
    SESSION
    5455444222
    35339FE000
    0000000000
    0000000000
    ME->INS
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ME->CHILD_CONDSEQ
    F0000000
    F0000000
    GF_CONTEXT_SESSION
    SESSION
    5455444222
    35339FE000
    0000000000
    0000000000
    ME->CHILDREN
    Table[initial]
    LO_TNODE
    |
    | F0000000 |
    | F0000000 |
    | %_ARCHIVE |
    |  |
    | 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | No.       7 Ty.          METHOD |
    | Name  LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
    | PF_EXEC_TIME |
    | I |
    | 4 |
    | 9 |
    | 0 |
    | 0 |
    | PF_EVENT |
    |  |
    | 2222222222222222222222222222222222222222 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | PF_CON |
    | SESSION |
    | 5455444222 |
    | 35339FE000 |
    | 0000000000 |
    | 0000000000 |
    | PF_INS |
    |  |
    | 2222222222222222222222222222222222222222 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | ME |
    |
    2000D000
    F0000C00
    ME->CHILD_CONDSEQ
    |
    | F0000000 |
    | F0000000 |
    | ME->CHILDREN |
    | Table IT_3674[26x8] |
    | DATA=CHILDREN
    Table reference: 1919
    TABH+  0(20) = 68550D3E00000000000000007F0700005A0E0000
    TABH+ 20(20) = 1A00000008000000800100000417010030080000
    TABH+ 40( 8) = 10000000C1288001
    store        = 0x68550D3E
    ext1         = 0x00000000
    shmId        = 0     (0x00000000)
    id           = 1919  (0x7F070000)
    label        = 3674  (0x5A0E0000)
    fill         = 26    (0x1A000000)
    leng         = 8     (0x08000000)
    loop         = 384   (0x80010000)
    xtyp         = TYPE#000029
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 4     (cmpSingleEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xB0B10D3E
    pgHook       = 0xF0882E3E
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 2508  (0xCC090000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 48    (0x30000000)
    lineAlloc    = 48    (0x30000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    LO_TNODE
    |
    | 2000D000 |
    | E0001C00 |
    | LO_CTNODE |
    |
    2000D000
    E0001C00
    %_SPACE
    2
    0
    0
    0
    No.       6 Ty.          METHOD
    Name  LCL_SESSION=>EXECUTE
    PF_EXEC_TIME
    I
    4
    9
    0
    0
    PF_EVENT
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    PF_CON
    SESSION
    5455444222
    35339FE000
    0000000000
    0000000000
    PF_INS
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ME->ACTSEQ
    |
    | F0000000 |
    | F0000000 |
    | ME->GLOBAL_CHECK_GRP |
    | EA_ROOT |
    | 44554452222222222222 |
    | 51F2FF40000000000000 |
    | 00000000000000000000 |
    | 00000000000000000000 |
    | ME->GLOBAL_VERSNR |
    | 00047 |
    | 33333 |
    | 00047 |
    | 00000 |
    | 00000 |
    | ME->CHECK_TREE |
    |
    2000D000
    F0000C00
    GF_EXEC_TIME_MODUS_CLOSE
    W
    5
    7
    0
    0
    ME->RAISED_EVENTS
    Table[initial]
    GF_EXEC_TIME_LOGICAL_COMPLETE
    L
    4
    C
    0
    0
    No.       5 Ty.          METHOD
    Name  LCL_SESSION=>CONTEXT_INSTANCES_CREATE
    LT_ZOMBIES
    Table[initial]
    LS_CTREL-TREENODE
    F0000000
    F0000000
    LO_ZOMBIE
    |
    | F0000000 |
    | F0000000 |
    | LT_NEW_CONINS |
    | Table IT_3670[1x100] |
    | FUNCTION-POOL=DSVAS_PROCCLASS=LCL_SESSIONMETHOD=CONTEXT_INSTANCES_CREATEDATA=LT_NEW_CONINS |
    | Table reference: 1920 |
    | TABH+  0(20) = 90C50D3E30F3DE3D0000000080070000560E0000 |
    | TABH+ 20(20) = 0100000064000000080100000417010060140000 |
    | TABH+ 40( 8) = 01000000C1248401 |
    | store        = 0x90C50D3E |
    | ext1         = 0x30F3DE3D |
    | shmId        = 0     (0x00000000) |
    | id           = 1920  (0x80070000) |
    | label        = 3670  (0x560E0000) |
    | fill         = 1     (0x01000000) |
    | leng         = 100   (0x64000000) |
    | loop         = 264   (0x08010000) |
    | xtyp         = TYPE#000094 |
    | occu         = 1     (0x01000000) |
    | access       = 1     (ItAccessStandard) |
    | idxKind      = 0     (ItIndexNone) |
    | uniKind      = 2     (ItUniqueNon) |
    | keyKind      = 1     (default) |
    | cmpMode      = 2     (cmpSingleMcmpR) |
    | occu0        = 1 |
    | groupCntl    = 0 |
    | rfc          = 0 |
    | unShareable  = 0 |
    | mightBeShared = 1 |
    | sharedWithShmTab = 0 |
    | isShmLockId  = 0 |
    | gcKind       = 0 |
    | isUsed       = 1 |
    | isCtfyAble   = 1 |
    | >>>>> Shareable Table Header Data <<<<< |
    | tabi         = 0x08AB0D3E |
    | pgHook       = 0x00000000 |
    | idxPtr       = 0x00000000 |
    | shmTabhSet   = 0x00000000 |
    | id           = 2505  (0xC9090000) |
    | refCount     = 0     (0x00000000) |
    | tstRefCount  = 0     (0x00000000) |
    | lineAdmin    = 1     (0x01000000) |
    | lineAlloc    = 1     (0x01000000) |
    | shmVersId    = 0     (0x00000000) |
    | shmRefCount  = 1     (0x01000000) |
    | >>>>> 1st level extension part <<<<< |
    | regHook      = 0xB0F0BE3D |
    | collHook     = 0x00000000 |
    | ext2         = 0x00000000 |
    | >>>>> 2nd level extension part <<<<< |
    | tabhBack     = Not allocated |
    | delta_head   = Not allocated |
    | pb_func      = Not allocated |
    | pb_handle    = Not allocated |
    | <LFS_CONINS> |
    | SESSION |
    | 54554442222222222222222222222222222222222222222222 |
    | 35339FE0000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | ME |
    |
    90006000
    4000B000
    <LFS_CONINS>-CON
    SESSION
    5455444222
    35339FE000
    0000000000
    0000000000
    <LFS_CONINS>-INS
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SY
    ##########################A###P##############################################T###ÿ##### u####
    0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
    1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
    0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
    00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
    GF_EXEC_TIME_BEFORE
    B
    4
    2
    0
    0
    No.       4 Ty.          METHOD
    Name  LCL_SESSION=>EXECUTE
    PF_EXEC_TIME
    I
    4
    9
    0
    0
    PF_EVENT
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    PF_CON
    2222222222
    0000000000
    0000000000
    0000000000
    PF_INS
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ME->ACTSEQ
    |
    | F0000000 |
    | F0000000 |
    | ME |
    |
    90006000
    4000B000
    ME->LOGICAL_COMPLETE
    2
    0
    0
    0
    GF_EXEC_TIME_COMPLETE
    C
    4
    3
    0
    0
    ME->COMPLETE
    2
    0
    0
    0
    SY-XFORM
    CONVERSION_EXIT
    444545544454545222222222222222
    3FE65239FEF5894000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    No.       3 Ty.          FUNCTION
    Name  DSVAS_PROC_SESSION_OPEN
    PF_HANDLE_TO_USE
    0
    0000
    0000
    PF_MAX_TREE
    2
    0
    0
    0
    PF_MODE
    C
    4
    3
    0
    0
    PS_SESSION_NUMBER
    EA6000000000255
    443333333333333
    516000000000255
    000000000000000
    000000000000000
    PF_HANDLE
    1
    0000
    1000
    PF_HIDE_TREE
    2
    0
    0
    0
    PF_MODE_USED
    2
    0
    0
    0
    PF_NEXT_CHECK_GRP
    22222222222222222222
    00000000000000000000
    00000000000000000000
    00000000000000000000
    PF_NEXT_CHECK_ID
    00000
    33333
    00000
    00000
    00000
    PF_NEXT_CON
    2222222222
    0000000000
    0000000000
    0000000000
    PF_NEXT_INS
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    PT_ERRORS
    Table[initial]
    PT_FRONTEND_TREE[]
    Table[initial]
    PF_LANGUAGE
    E
    4
    5
    0
    0
    <%_TABLE_DSVASSESSADMIN>
    LF_BUNDLE_VERSNR
    00038
    33333
    00038
    00000
    00000
    DSVASRESULTSGEN-CLUSTR
    0
    00
    00
    PS_SESSION_NUMBER-SESSNO
    6000000000255
    3333333333333
    6000000000255
    0000000000000
    0000000000000
    LS_OPEN_SESSIONS-SESSION
    |
    | 90006000 |
    | 4000B000 |
    | LO_SESSION |
    |
    90006000
    4000B000
    LS_OPEN_SESSIONS
    EA6000000000255C####k#
    4433333333333334009060
    51600000000025531040B0
    0000000000000000000000
    0000000000000000000000
    SY-XPROG
    SAPCNVE
    5454454222222222222222222222222222222222
    3103E65000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    LS_SESSDEFGEN-MULTI_USER

    Please replace the Service Definitions in your SAP Solution Manager
    system as described in SAP Note 727998.
    As of SAP Solution Manager 7.0 (= 4.0) Support Package Stack 15 (which
    includes ST-PI 700_2005_1 SP06) you can trigger the required steps
    within transaction SDCCN:
    Menu Utilities -> Maintain Service Definitions ->
    Select 'Delete and Replace Service Definitions -> Confirm this
    selection-> Confirm that you want to delete the definitions -> Confirm
    that a new task 'Service Definition Refresh' was created
    Take a note of the task id -> Review the log for this task id when it
    is completed. You should not see any errors for either the update
    of a Service Definitions table or the generation of any re-import
    include.
    Reschedule SM:EXEC SERVICES and the reported dump will no longer
    occur.

  • Problem with BI activation in Solution Manager

    Hello SAP experts.
    I have problem with BI Content Activation in Solution Manager solman_workcenter - test management - settings - Bi reporting
    The customizing in client 010 is ok. I have BW client 001. RFC connections
    are ok. After activation of BW content in workcenter only new job in sm37
    has been planned but the button Status Report has not appeared. I installed
    newest add-on SAPK-70405INBICONT.
    Detailed description:
    After customizing in:
    SPRO-Basic Data-BW Setup
    and
    SPRO-Scenario-Specific Settings - Test Management - BW-based Reporting.
    The Activation of BW content in transaction solman_workcenter - Test
    Management - Settings - BI Reporting Settings the message appears:
    "Test Workbench Reporting - BI Content not active", after pressing save:"Settings of Test Workbench Reporting saved"
    and
    "Activation of BI Content for Test Workbench Reporting started".
    In test evaluation the button Status report doesnt show. After repeated
    activation appears the same message as in beginning: Test Workbench
    Reporting - BI Content not active.
    Thank you

    Hi Marian,
    Could you please provide me with details on how to setup test workbench reporting. I have a BW system external to Solution Manager. I have setup the RFC conncections and all is okay. I have also setup the source system in BW and installed the web templates. However, when activating the content via solman_workcenter - test management - settings, I get the following error:
    Content Activation Log
    Log for Setup ID 20100819135323
    20100819 135323[ERROR ]: Current Status: ERROR
    20100819 135323[INFO ]: Job CCMS_BI_SETUP successfully scheduled
    20100819 135323[ERROR ]: Incorrect system setting: standard transport is active
    20100819 135323[ERROR ]: Change system settings or set user parameters RSOISCONTENTSYSTEM and RSOSTANDARDCTOACTIVE
    20100819 135323[ERROR ]: Prerequisites check failed
    20100819 135323[ERROR ]: Jobname/count: CCMS_BI_SETUP 13532300
    I am sure there is something wrong in my setup but I cannot figure out what it is. A step by step help on how to do it will be greatly appreciated.
    Regards,
    Rue.

Maybe you are looking for

  • ACS 5.3, EAP-TLS Machine Authentication with Active Directory

    I have ACS 5.3. I am testing EAP-TLS Machine Authentication using Active Directory as an external Identity Store. II was testing and everything was going fine until I did some failure testing. My problem: I deleted my computer account out of Active D

  • Users custom stamps dissapear in Acrobat 7.0 Professional

    Hello, For some reason our users custom stamps are dissapearing in Adobe Acrobat 7.0 Professional when they close Acrobat, reopen it, and attemp to use the stamp(s) they had previously created. I am not sure if we can upgrade Acrobat because the user

  • Email issues with "extended PDFs" for readers...

    I have a Form that will be sent to among 3 employees by email... 2 of the 3 employees only have adobe reader on their desktops...this is why the form was saved in the "extended format" the issue I have is when employee 1 emails the Form to employees

  • How to use Start Routine for this requirement

    Hello, I am having data in 2 ods and should load that data into cube, but there isn't any common object in both the ods's. I need to analyze based on these ods objects. so I thought of pulling some objects into 1ods which are used for analysis and ad

  • Lightroom 5 Exif "File Number"

    I would like to rename my images to below format: Foldername_DSCFileNumber_Year-Day-Month so example name would be: Test_DCS2342352_2012-12-12 Unfortunatelly lightroom cannot read the file number from EXIF. Is there any way to do it without using any