Project Structure Saving

Dear all;
i have a problem when saving projects specially in CJ20N. the entire structure is expanded (WBS's, Networks, Activities, Copmponents,... etc.). and all the data is read before the saving process takes place.
So for large customers' projects that might exceed 10,000 objects, this cause a huge problem when editing the structure.
can anyone find a reason why the structure is expanded while saving???
thx everyone;

Dear All;
thx a lot for trying to help.
there is something i want to clarify here.
my problem is not how big the structure is, i can handle that.
the problem is:
whne i save the project in CJ20N, the system expands the entire structure of the project (WBS's, networks, activities and components) even if i didn't work on them.
this expansion when saving didn't happen before it just used to save the project on whatever tree form it was.
the question is why does it expand structure when save. and how can i control this i.e. a transaction where i say don't expand when saving!!!!

Similar Messages

  • Issue with project structure...

    Hi all,
    Our projects are created from sales order through assembly processing. All wbs are of first level..the user By mistake manually made changes to the structure by dragging the wbs and dropping it under another wbs in the project thus making it a subordinate wbs I.e second level wbs. Now during the running of the result analysis  for the first level wbs the system is giving an error to delete the ra data of the second level wbs before proceeding with the first level wbs and now the user has realized that project structure is changed. Can we go ahead and delete the ra data of the lower wbs and change the project structure back at this point? What implications will changing the structure have at this point?

    Hi
    Besides above suggestion, you can reorganize your structure by executing "Derive structure" in CJ20N.
    Go to menu bar Project > Check/Derive Structure.
    Note that this is possible before saving changes to system. in you case, when WBS element was dragged and placed under another WBS element, level of WBS also got changed.
    These kind of issues are user induced and avoidance is very difficult. But we can still control implementing User Status. Try this option which will default at initial level and stays there till the closing of project.
    You can select the object  "Change Structure"  and option - Forbidden.
    Thanks,
    Sudhakar
    Message was edited by: Sudhakar Pappu

  • Substitution of Profit center across project structure.

    Dear All,
    Requirement: Need to substitute profit center entered at Project definition level (at all times) to all project elements (WBS elements, N/W header and Activities). Also I need to validate this complete structure for the profit center inconsistency.
    Problem: I have created Substitution rules, which will substitute across all the project objects (only when a new project is created). But if you change the profit center afterwards, it will change only at WBS elements level, however profit center at N/W and Activities will be substituted only when you make some changes to them. To avoid this I have created a validation, which will check across the complete structure.
    Now after changing the profit center using CNMASS for all the objects, even though in physical you can find the new value at N/W header, however while saving it will validate and finds only the oldvalue and hence throws an error.
    Can anyone throw some light on this?
    With regards,
    Harisha

    Hi Martina,
    My problem in detail:
    I am creating a new project structure XXXX (having WBS elements, N/W and Activities) with initial profit center as AA. 1st time while saving the project, profit center AA will be substituted to all objects (I have maintained substitution rules at all objects)
    Now again I will reopen the same project XXXX and I will change the profit center of project XXXX to BB (in the project definition level). With this due to automatic substitution only the profit center at WBS elements will be changed to BB. But not at N/W header and Activities (till you make some changes to N/W or Activity the profit center will be AA only, afterwards if you make any changes to N/W and Activities profitcenter will changes to BB). To avoid this difference I have created a validation rule, which will check the inconsistency of profit center all along the structure.
    Now I am using mass change functionality to change the profit center in onego at all the objects. After making the masschange the profit center at all objects will become BB (but still not saved), however while saving the system validates the profit center and found still N/W and Activities having AA only (in database), so it wont allow us to save.
    If you require further information please ask me again.
    With regards,
    Harisha

  • I have two versions of Pr, one is the latest 2014 and when trying to open a Pr2014 session, I get an error message saying the project was saved in a newer version and cannot be opened. Help

    I have two versions of Pr, one is the latest 2014 and when trying to open a Pr2014 session, I get an error message saying the project was saved in a newer version and cannot be opened. Could there be an issue with an older Pr application on the computer? Please help!

    You need to be very careful which project you open in which version.
    For 2014 make sure its on 2014.1 build 81.

  • How to restrict the user to change the project structure but not the documents?

    Hi,
    I have created one project assigning different users in Solution manger. I want to risitrict some of the users to change the project structure but simultaneously allwoing the project documents to be created, edited or deleted using solar01 under Project documentation tab. For that I have followed the steps provided in the follwoing link.
    http://wiki.scn.sap.com/wiki/display/SM/Howto+Restrict+Changes+to+Project+Nodes+to+Assigned+Team+Members
    I am able to restrict the users to change the project structure, but I am not able to allow access to the project documents. It gives me the message "You are not authorised to change the project". This fulfills my one of the requirements. But, Is there any way  to restrict the user to change the project structure but not the documents?. Any help will be apperitiated.
    Thanks,
    Rutvik Uapdhyay. 

    Hi Rutvik,
    Basically there are 2 different authorization role ...you should look for and customize as per requirement in Z* namespace.
    role  - SAP_SOLAR01_ALL
    this take care of objects in Solar01 like tab access etc
    role -SAP_SOL_KW_ALL
    this takes care of entire documentation within solman
    hope this helps
    Regards
    Prakhar

  • Project Structure in SAP R/3 Replication Issues

    Hi All,
    I have some of the Issues while creating the Project Structure in cProjects.
    1) The Project Structure getting generated in SAP R/3 is only mappped with WBS elements, why not Networks and Network Activies.
    e.g
    *cProjects                     SAP Project Systems*
    Project Definition -
    > Project definition
    Phase----
    > WBS Element
    Task----
    >WBS Element
    Mirrored Task----
    >WBS Element
    Sub Task----
    >WBS Element
    Checklist----
    >WBS Element
    Checklist item----
    >WBS Element
    Is this the standard feature or whether we can create the Network and Network Activites for Tasks and Checklist??
    2) The Numbering of the Phase, Tasks, Sub tasks, hecklist etc... all are of some 24 digit numerals, Can we automate the numbering like, the WBS element at level 1 should copy the project definition number and some extension...
    3) the Project generated in SAP Project Systems i.e the WBS Elements has status "MDLK" Master data locked.... Why is this set. Is it standard? Can we eliminate this?
    Hoping for answers from you all.
    Thanks & Regards,
    Stephen

    Hi Stephen,
    1) The Project Structure getting generated in SAP R/3 is only mappped with WBS elements, why not Networks and Network Activies.
    e.g
    *cProjects SAP Project Systems*
    Project Definition -
    > Project definition
    Phase----
    > WBS Element
    Task----
    >WBS Element
    Mirrored Task----
    >WBS Element
    Sub Task----
    >WBS Element
    Checklist----
    >WBS Element
    Checklist item----
    >WBS Element
    Is this the standard feature or whether we can create the Network and Network Activites for Tasks and Checklist??
    >>>> I think, you use cProject 4.0, as in cProject 3.1 it is possible to get object be replicated as PS activity. 
    Reason: The prupose of the replication is the costs-integration.
    2) The Numbering of the Phase, Tasks, Sub tasks, hecklist etc... all are of some 24 digit numerals, Can we automate the numbering like, the WBS element at level 1 should copy the project definition number and some extension...
    >>> You can implement a Badi to apply your own logic. There is a Note to give you instruction how to do it. If you fails to find it, please let me know. I will search it.
    3) the Project generated in SAP Project Systems i.e the WBS Elements has status "MDLK" Master data locked.... Why is this set. Is it standard? Can we eliminate this?
    >>> As the WBS is automatically created via integration. Use this status to prevent the user change it by mistaken. To behonest, I do not this logic, but it is standard behaviour.
    Kind regards,
    Zhenbo

  • A perticular Project automatically saving in the local Object

    Hi,
    I have an issue regarding ther local Object .. I have different projects need to save in Transport Requests. I observed a perticular project while saving it is generating a transport request number but saving in local object.
    Can you please give me more suggessions to solve this problem ...
    Thanks in advance ..
    Shashi,Samal

    Hi Shashi,
    If it is getting assigned to a TR then it can't be local object.
    Can you give some more details. Also which system, version you are on.
    Regards,
    Atish

  • The project was saved in a newer version of Premiere Pro and cannot be opened in this version

    I edited a project on CC on one computer and saved it on my external. My friend took the same project to edit it on her computer under her own name and licence. Both of us recently upgraded to CC. But the same project that worked a few hours back on Premiere Pro CC, does not work now also on Premiere Pro CC and I received a message saying: The project was saved in a newer version of premiere pro and cannot be opened in this version." Can you please help us.?
    Message was edited by: Kevin Monahan
    Reason: Your title was too long.

    Hi alexxxkid,
    You should be able to import the xml into an earlier version.
    Backward compatibility has never been there with Premiere and it is always recommended not to update in the middle of a project.
    As far as the crash is concerned, please tell me more about it so that i can help you to the best of my knowledge.
    Thanks,
    Rameez

  • Upload Project Structure or Roadmap from MS Project to solution manager

    I have a project ready in MS Project .
    I want to make a roadmap out of it.
    How is that possible? Do I have to manually edit roadmap structure?
    OR Is it possible to upload Project Structure or Roadmap from MS Project to solution manager?

    Hi Hussain,
    Can you please check [this|Creating new Roadmaps; thread for general overview on custom Roadmaps.
    In answer to your specific question, it's not possible to create a Roadmap straight out of MS Project, in standard SolMan.
    Best regards,
    Srini
    Edited by: Srinivasan Radhakrishnan on Jun 5, 2008 1:06 PM

  • CJ20N - project structure and data import

    Hello dear SAP specialists,
    Does anybody ever created a ABAP program to import project structure and populate it with data?
    I'm trying to start with something or get a working program to import some projects with data.
    Actually the program should use BAPI_PROJECT_MAINTAIN to create WBS and GUI_UPLOAD to read a text (cvs) file (LSMW can not be used:)
    Sincerely,
    Me

    Hi,
    Exactly!
    See you have so many tables in that BAPI, now all the data you have in your flat file you have to map to these tables.
    Below is a code...similarly you'll have to do
    TYPE-POOLS: truxs.
    *                           T Y P E S
    TYPES: BEGIN OF t_master_data,
              MATERIAL                      Type  MATNR ,
              IND_SECTOR                    Type  MBRSH ,
              MATL_TYPE                     Type  MTART ,
              PLANT                         Type  WERKS ,
              STGE_LOC                      Type  LGORT_D ,
              MATL_DESC                     Type  MAKTX ,
              BASE_UOM                      Type  MEINS ,
              MATL_GROUP                    Type  MATKL ,
              DIVISION                      Type  SPART ,
              ITEM_CAT                      Type  MTPOS_MARA  ,
              GROSS_WT                      Type  BRGEW ,
              UNIT_OF_WT                    Type  GEWEI ,
              NET_WEIGHT                    Type  NTGEW ,
              VOLUME                        Type  VOLUM ,
              SIZE_DIM                      Type  GROES ,
              BASIC_MATL                    Type  WRKST ,
              DOCUMENT                      Type  DZEINR  ,
              DOC_VERS                      Type  DZEIVR  ,
              PO_UNIT                       Type  BSTME ,
              PUR_GROUP                     Type  EKGRP ,
              AUTO_P_ORD                    Type  KAUTB ,
              "BATCH_MGMT Type  XCHPF ,
              PUR_VALKEY                    Type  EKWSL ,
              "GR_PR_TIME Type  WEBAZ ,
              COMM_CODE                     Type  STAWN ,
              COUNTRYORI                    Type  HERKL ,
              MRP_TYPE                      Type  DISMM ,
              REORDER_PT                    Type  MINBE ,
              MRP_CTRLER                    Type  DISPO ,
              LOTSIZEKEY                    Type  DISLS ,
              MINLOTSIZE                    Type  BSTMI ,
              MAXLOTSIZE                    Type  BSTMA ,
              FIXED_LOT                     Type  BSTFE ,
              MAX_STOCK                     Type  MABST ,
              ROUND_VAL                     Type  BSTRF ,
              PROC_TYPE                     Type  BESKZ ,
              SPPROCTYPE                    Type  SOBSL ,
              ISS_ST_LOC                    Type  LGPRO ,
              SLOC_EXPRC                    Type  LGFSB ,
              PLND_DELRY                    Type  PLIFZ ,
              GR_PR_TIME                    Type  WEBAZ ,
              SM_KEY                        Type  FHORI ,
              SAFETY_STK                    Type  EISBE ,
              PLNG_PLANT                    Type  PRWRK ,
              AVAILCHECK                    Type  MTVFP ,
              DEP_REQ_ID                    Type  SBDKZ ,
              ISSUE_UNIT                    Type  AUSME ,
              STGE_BIN                      Type  LGPBE ,
              BATCH_MGMT                    Type  XCHPF ,
              STGEPERIOD                    Type  MAXLZ ,
              STGE_PD_UN                    Type  LZEIH ,
              MINREMLIFE                    Type  MHDRZ ,
              SHELF_LIFE                    Type  MHDHB ,
              PERIOD_IND_EXPIRATION_DATE    Type  DATTP ,
              ROUND_UP_RULE_EXPIRATION_DATE Type  RDMHD ,
              STOR_PCT                      Type  MHDLP ,
              QM_AUTHGRP                    Type  QMATAUTH  ,
              QM_PROCMNT                    Type  QMPUR ,
              CTRL_KEY                      Type  SSQSS ,
    *           Type  ART ,
    *           Type  AKTIV ,
              VAL_CAT                       Type  BWTTY_D ,
              VAL_CLASS                     Type  BKLAS ,
              PRICE_CTRL                    Type  VPRSV ,
    * NEW ADDITION
              STD_PRICE                     Type  STPRS,
              PRICE_UNIT                    Type  PEINH ,
              MOVING_PR                     Type  VERPR ,
              QTY_STRUCT                    Type  CK_EKALREL  ,
              ORIG_GROUP                    Type  HRKFT ,
              ORIG_MAT                      Type  HKMAT ,
              VARIANCE_KEY                  Type  AWSLS ,
              PROFIT_CTR                    Type  PRCTR ,
              LANGU                         Type SPRAS,
           END OF t_master_data.
    *                  I N T E R N A L   T A B L E S
    DATA:
    *     Internal table of type t_master_data
          ist_master_data TYPE TABLE OF t_master_data,
    *     Internal table of type BAPIMATHEAD
          ist_headdata    TYPE TABLE OF BAPIMATHEAD,
    *     Internal table of type BAPI_MAKT
          ist_mat_desc    TYPE TABLE OF BAPI_MAKT,
    *     Internal table of type BAPI_MAKT
          ist_uom         TYPE TABLE OF BAPI_MARM,
    *     Internal table of type BAPI_MAKTX
          ist_uom_x       TYPE TABLE OF BAPI_MARMX.
    *                   G L O B A L   V A R I A B L E S
    DATA:
          it_num     TYPE num10,
    *     Global variable of type truxs_t_text_data
          it_raw     TYPE truxs_t_text_data.
    *                       W O R K   A R E A S
    DATA:
    *     Work area of type t_master_data
          wa_master_data                TYPE t_master_data,
    *     Work area of type bapimathead
          wa_bapimathead                TYPE BAPIMATHEAD,
    *     Work area of type bapi_mara
          wa_client_data                TYPE BAPI_MARA,
    *     Work area of type bapi_marax
          wa_client_data_x              TYPE  BAPI_MARAX,
    *     Work area of type bapi_marc
          wa_plant_data                 TYPE BAPI_MARC,
    *     Work area of type bapi_marcx
          wa_plant_data_x               TYPE BAPI_MARCX,
    *     Work area of type bapi_mard
          wa_storage_location_data      TYPE BAPI_MARD,
    *     Work area of type bapi_mardx
          wa_storage_location_data_x    TYPE BAPI_MARDX,
    *     Work area of type bapi_mbew
          wa_valuation_data             TYPE BAPI_MBEW,
    *     Work area of type bapi_mbewx
          wa_valuation_data_x           TYPE BAPI_MBEWX,
    *     Work area of type bapi_mard
          wa_mat_desc                   TYPE BAPI_MAKT,
    *     Work area of type bapi_marm
          wa_uom                        TYPE BAPI_MARM,
    *     Work area of type bapi_marmx
          wa_uom_x                      TYPE BAPI_MARMX,
    *     Work area of type mbapi_mpgd
          wa_planning_data              TYPE BAPI_MPGD,
    *     Work area of type mbapi_mpgdx
          wa_planning_data_x            TYPE BAPI_MPGDX,
    *     Work area of type mbapi_mpgd
          wa_return                     TYPE BAPIRET2.
    *                          P A R A M E T E R S
    PARAMETERS:
    *     Parameter of type rlgrap-filename
          p_file TYPE  rlgrap-filename.
    *               A T   S E L E C T I O N   S C R E E N
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
      CALL FUNCTION 'F4_FILENAME'
        EXPORTING
          field_name = 'P_FILE'
        IMPORTING
          file_name  = p_file.
    *                S T A R T - O F - S E L E C T I O N.
    START-OF-SELECTION.
    * To upload data from flat file
      CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
        EXPORTING
          i_line_header        = 'X'
          i_tab_raw_data       = it_raw       " WORK TABLE
          i_filename           = p_file
        TABLES
          i_tab_converted_data = ist_master_data[]  "ACTUAL DATA
        EXCEPTIONS
          conversion_failed    = 1
          OTHERS               = 2.
      IF sy-subrc = 0.
        LOOP AT ist_master_data INTO wa_master_data.
          it_num = wa_master_data-PROFIT_CTR.
          wa_master_data-PROFIT_CTR = it_num.
          MOVE-CORRESPONDING wa_master_data to wa_bapimathead.
          MOVE-CORRESPONDING wa_master_data to wa_client_data.
          wa_client_data_x-MATL_GROUP = 'X'.
          wa_client_data_x-BASE_UOM = 'X'.
          wa_client_data_x-PO_UNIT = 'X'.
          wa_client_data_x-DOCUMENT = 'X'.
          wa_client_data_x-SIZE_DIM = 'X'.
          wa_client_data_x-BASIC_MATL = 'X'.
          wa_client_data_x-PUR_VALKEY = 'X'.
          wa_client_data_x-NET_WEIGHT = 'X'.
          wa_client_data_x-UNIT_OF_WT = 'X'.
          wa_client_data_x-DIVISION = 'X'.
          wa_client_data_x-BATCH_MGMT = 'X'.
          wa_client_data_x-QM_PROCMNT = 'X'.
          wa_client_data_x-MINREMLIFE = 'X'.
          wa_client_data_x-SHELF_LIFE = 'X'.
          wa_client_data_x-STOR_PCT = 'X'.
          wa_client_data_x-ROUND_UP_RULE_EXPIRATION_DATE = 'X'.
          wa_client_data_x-PERIOD_IND_EXPIRATION_DATE = 'X'.
          wa_client_data_x-ITEM_CAT = 'X'.
          MOVE-CORRESPONDING wa_master_data to wa_plant_data.
          wa_plant_data_x-PLANT  = wa_master_data-plant.
          wa_plant_data_x-PUR_GROUP = 'X'.
          wa_plant_data_x-ISSUE_UNIT = 'X'.
          wa_plant_data_x-MRP_TYPE = 'X'.
          wa_plant_data_x-MRP_CTRLER = 'X'.
          wa_plant_data_x-PLND_DELRY = 'X'.
          wa_plant_data_x-GR_PR_TIME = 'X'.
          wa_plant_data_x-LOTSIZEKEY = 'X'.
          wa_plant_data_x-PROC_TYPE = 'X'.
          wa_plant_data_x-SPPROCTYPE = 'X'.
          wa_plant_data_x-SAFETY_STK = 'X'.
          wa_plant_data_x-MINLOTSIZE = 'X'.
          wa_plant_data_x-MAXLOTSIZE = 'X'.
          wa_plant_data_x-FIXED_LOT = 'X'.
          wa_plant_data_x-ROUND_VAL = 'X'.
          wa_plant_data_x-MAX_STOCK = 'X'.
          wa_plant_data_x-DEP_REQ_ID = 'X'.
          wa_plant_data_x-SM_KEY = 'X'.
          wa_plant_data_x-STGEPERIOD = 'X'.
          wa_plant_data_x-STGE_PD_UN = 'X'.
          wa_plant_data_x-CTRL_KEY = 'X'.
          wa_plant_data_x-BATCH_MGMT = 'X'.
          wa_plant_data_x-AVAILCHECK = 'X'.
          wa_plant_data_x-AUTO_P_ORD = 'X'.
          wa_plant_data_x-COMM_CODE = 'X'.
          wa_plant_data_x-COUNTRYORI = 'X'.
          wa_plant_data_x-PROFIT_CTR = 'X'.
          wa_plant_data_x-ISS_ST_LOC = 'X'.
          wa_plant_data_x-VARIANCE_KEY = 'X'.
          wa_plant_data_x-SLOC_EXPRC = 'X'.
          wa_plant_data_x-QM_AUTHGRP = 'X'.
          MOVE-CORRESPONDING wa_master_data to wa_planning_data.
          wa_planning_data_x-PLANT = wa_master_data-plant.
          wa_planning_data_x-PLNG_PLANT = 'X'.
          MOVE-CORRESPONDING wa_master_data to wa_storage_location_data.
          wa_storage_location_data_X-PLANT = wa_master_data-plant.
          wa_storage_location_data_X-STGE_LOC = wa_master_data-stge_loc.
          wa_storage_location_data_X-STGE_BIN = 'X'.
          MOVE-CORRESPONDING wa_master_data to wa_valuation_data.
          wa_valuation_data-VAL_AREA = '1000'.
          wa_valuation_data_X-VAL_AREA = '1000'.
          wa_valuation_data_X-PRICE_CTRL = 'X'.
          wa_valuation_data_X-MOVING_PR  = 'X'.
          wa_valuation_data_X-PRICE_UNIT = 'X'.
          wa_valuation_data_X-STD_PRICE = 'X'.
          wa_valuation_data_X-VAL_CLASS = 'X'.
          wa_valuation_data_X-ORIG_GROUP = 'X'.
          wa_valuation_data_X-QTY_STRUCT = 'X'.
          wa_valuation_data_X-ORIG_MAT = 'X'.
          MOVE-CORRESPONDING wa_master_data to wa_mat_desc.
          APPEND wa_mat_desc to ist_mat_desc.
          IF wa_master_data-PRICE_CTRL = 'S' AND wa_master_data-STD_PRICE IS INITIAL.
            WRITE:/ 'Standard Price not maintained for material ',wa_master_data-MATERIAL.
          ELSE.
            CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
              EXPORTING
                HEADDATA             = wa_bapimathead
                CLIENTDATA           = wa_client_data
                CLIENTDATAX          = wa_client_data_x
                PLANTDATA            = wa_plant_data
                PLANTDATAX           = wa_plant_data_X
                PLANNINGDATA         = wa_planning_data
                PLANNINGDATAX        = wa_planning_data_x
                STORAGELOCATIONDATA  = wa_storage_location_data
                STORAGELOCATIONDATAX = wa_storage_location_data_x
                VALUATIONDATA        = wa_valuation_data
                VALUATIONDATAX       = wa_valuation_data_x
              IMPORTING
                RETURN               = wa_return
              TABLES
                MATERIALDESCRIPTION  = ist_mat_desc.
            Write:/ wa_return-message.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
            Clear: wa_bapimathead
             ,wa_client_data
             ,wa_client_data_x
             ,wa_plant_data
            ,wa_plant_data_X
            ,wa_planning_data
             ,wa_planning_data_x
            ,wa_storage_location_data
             ,wa_storage_location_data_x
             ,wa_valuation_data
           ,wa_valuation_data_x.
          ENDIF.
          REFRESH ist_mat_desc.
        ENDLOOP.
      ELSE.
        Write:/ text-001.
      ENDIF.
    In the above code note how i have taken the same names for the fields in internal table as they are in the BAPI so that the mapping of data becomes easier, since i use MOVE CORRESPONDING.
    Regards,
    Shraddha
    Edited by: shraddha85 on Jan 31, 2011 9:49 AM

  • Project structure built dynamically?

    Hey,
    This is something I frequently wonder about when taking over
    someone elses work. I've got an existing structure for a project -
    a bunch of classes all in different folders matching their class
    definitions. What would be nice is if Flash behaved like Visual
    Studio and kept it's project structure up to date like solutions
    can be kept in VS. Since it doesn't I have to go through typing in
    folder names all over the place and adding files at the end of
    every path.
    So does anyone know if there is something that will help me
    create a project from a directory?

    Hi Hiren,
    Please check this BAPI.
    BAPI_PROJECTDEF_CREATE - Create Project Definition                                              
    BAPI_PROJECTDEF_EXISTENCECHECK - Check whether a project definition exists                                
    BAPI_PROJECTDEF_GETDETAIL - Read detailed information for the project definition                     
    BAPI_PROJECTDEF_GETLIST - Returns a container of project definitions                               
    BAPI_PROJECTDEF_UPDATE - Change Project Definition                                              
    Hope this will help.
    Regards,
    Ferry Lianto 
    Please reward points if helpful.

  • How to create a project structure with the Business Bluprint transaction S

    Hi
    How to create a project structure and add the required scenarios for your SAP system to your project structure with the Business Bluprint transaction SOLAR01.
    Also how to add your SAP system configuration structures to your project structure with the configuration transaction SOLAR02
    Thanks,

    Dear fr
    Have u already created a project?
    select the same in solar01 and click the structure tab
    On the left side select business scenarios and on the right side select the structure tab
    Press F4 here and check the Busines process repository is selected
    Nw you hav all the standard business process
    For non-standard just type there name and press save button.
    Add the relevant one's
    Once added here in solar01 reflected in solar02 automatically with relevant data for standard business process.
    you hav to add manually for non stand scean you have added.
    Hope it clarifies.
    Pls assign pts.

  • Managing Org  units and Master Data in project structure

    How are Org units and Master data managed at the project structure? What would be the appropriate place holders for them in the structure. Should we manage it at the top of the project structure or within the  business scenarios/processes. On what basis should we decide this? How would this impact in case of a global template rollout?
    Please share your experiences regarding this.
    Thanks.
    Mike

    any talented  guy do this way.
    i think  that ur working  in E2E project work
    before  singoff ur business process u should give to ur users  master data templets..they collect for  masterdatas in before realization phase...that time  u should know  how many specifications is there and  in spections how  many in quantitative and how many qualitative u will indentify. if any query let me  back.
    Edited by: Lakshmiananda prasad on Oct 6, 2009 11:48 AM

  • TOC not updating when project is saved

    The Table of Contents is not saving when project is saved. To see saved changes, I have to close and reopen.

    Hi there
    Just to be clear, this *IS* RoboHelp HTML, no?
    In RoboHelp HTML, there is no dynamic link between the TOC items and Topic Names. Sure, if you rename the File Name in a topic so the HTML file name changes, it will automatically update the TOC so that the link isn't broken. But the TOC elements are stored in a separate file completely. So I'm really confused as to what you are seeing or expect to see. Once you have a topic in the TOC, the TOC node may represent the Topic Title. Perhaps:
    How to confgure the gizmo.
    But if you later change that Topic Title to read:
    How to configure the widget
    The TOC will not change automagickally. You will have to either re-run the wizard to create a new TOC or you will need to manually edit the TOC node so it is now correct.
    Cheers... Rick
    Helpful and Handy Links
    RoboHelp Wish Form/Bug Reporting Form
    Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
    Adobe Certified RoboHelp HTML Training
    SorcerStone Blog
    RoboHelp eBooks

  • I just updated to the latest aperture, i have projects previously saved on a drive (in the old version) that now won't load... how do i update them?

    Hi,
    i just updated to the latest aperture, i have projects previously saved on a drive (in the old version) that now won't load... how do i update them?

    But, unless I missed something, you are doing the repair with Aperture 3.5 so if 3.5 can't open an earlier library before doing the upgrade then unless I'm missing something the library will be upgraded before the repair is run, no?
    OT:
    You got me there, Frank - I wondered about the same thing, but Aperture is behaving differently, when upgrading a library, depending on if you are launching into the First Aid Tools or not.
    I repeated my experiments, to explore this difference:
    I restored an Aperture 3.4.3 library and launched the First Aid Tools:
    Apertur went directly into First Aid Mode without first asking to upgrade.
    Then "Repair" asked to be allowed to upgrade the library as you predicted.
    During the upgrade "Aperture"showed "Rebuilding", not "Repairing" or "upgrading". 
    Second experiment: When I only double-click the 3.4.3 library instead of repairing, the upgrade alert is very different:
    It takes a shorter time and does not show "rebuilding".
    I am quite certain, that Aperture will use a different upgrade prodecure, when launched into the First Aid panel for repairing or rebuilding.

Maybe you are looking for