FM RH_INSERT_INFTY lock by CL_HR_ALEOX_BADI in production system

Hi Gurus,
I am using FM RH_INSERT_INFTY in a Z.. Report in order to massive charge the organizational structure. But it's taking so long, and when I see in SM50 is performing in report "CL_HR_ALEOX_BADI==============CP" in production system.
Does anybody knows if something has to be set up before execute the class CL_HR_ALEOX_BADI.
Any help is very useful.
Thanks in advance,
Regards

This is my entry in SM50.
Regards

Similar Messages

  • Lock on Portion and MRU in Production System

    Can anyone explain why is there a lock on MRU and Portion in the production system but not in development? Can it be removed?

    Hi Kunal,
    The lock will appear in production system only as the standard logic checks for production client before showing up the lock.
    ============================
    CHECK g_clnt_prod = 'P'.
    ============================
    Lock Icon on Portion:
    Following two FMs are used to determine whether the locked icon is to be displayed or not
    ISU_DB_EVER_FIND_CONT_FOR_PORT,
    ISU_DB_TE422_FIND_MRU_FOR_PORT
    Simply put forward, if portion is being used  for an ISU contract(EVER) or is associated with any MRU(TE422) lock icon will be displayed.
    Lock Icon on MRU
    It check in table EANLH(Install.Time Slice) with the following condition bis >= sy-datum AND ableinh = te422-termschl.If record is found, then the lock icon is displayed.
    Simply put forward, if MRU is being used up in any ISU installation as on system date, the MRU lock will be displayed.
    About, removing the icons, it checks for business function  ISU_UTIL_1 to be active for the system. If not, the lock is not displayed in production environment .
    I hope, this clarifies you doubt.
    Thanks,
    Ritesh

  • RFC users locked after system copy in production system

    Hi,
    BW_User,MDBTC(RFC users) system users were locked in our BI Production system at the same time system copy activity was running in the Quality system(production to quality) so as per our colleagues concern after system copy they started Quality system with out changing background work-process 0 so some jobs were triggered which were copied from production system.
    Is there any cause to lock RFC users in production system for system copy? If there is any other reason where we can check logs
    Thanks
    Jalandhar Reddy

    Hi,
    Well maybe i am wrong to analyze your problem .
    Anyway I faced this issue to in our system before and we found that one background job was running  in a system that has basically  prompting an RFC connection to another system. In the t.code SM59 and there was wrong password was put in.We just reset the password and it was worked fine.
    You can try for this..
    Regards
    Bhuban
    RKFL

  • Translations in production system.

    Dear experts,
    We're currently reviewing all modified objects in an upgrade project to ECC 6.0 and we are seing that there are lots of objects directly translated in the production system. If we reset to original this objects in the development system we will loose all this translations.
    My question is if it is possible to lock translations in our production system. As far I know I can use SM01 to lock translation transactions like SE63, and also a properly authorization schema will he helpful here. But this is not the case, some of our developers are SAP_ALL/SAP_NEW. So they can override this mechanisms.
    Is there any way to disable SE63 or just work with translations like ABAP code ?
    Regards,
    Joan B. Altadil

    why are you giving SAP_ALL to developers in production env???/

  • Best practice to reduce downtime  for fulllaod in Production system

    Hi Guys ,
    we have  options like "Initialize without data transfer  ", Initialization with data transfer"
    To reduce downtime of production system for load setup tables , first I will trigger info package for  Initialization without data transfer so that pointer will be set on table , from that point onwards any record added as delta record , I will trigger Info package for Delta , to get delta records in BW , once delta successful, I will trigger info package for  the repair full request to  get all historical data into setup tables , so that downtime of production system will be reduced.
    Please let me know your thoughts and correct me if I am wrong .
    Please let me know about "Early delta Initialization" option .
    Kind regards.
    hari

    Hi,
    You got some wrong information.
    Info pack - just loads data from setup tables to PSA only.
    Setup tables - need to fill by manual by using related t codes.
    Assuming as your using LO Data source.
    In this case source system lock is mandatory. other wise you need to go with early delta init option.
    Early delta init - its useful to load data into bw without down time at source.
    Means at same time it set delta pointer and will load into as your settings(init with or without).
    if source system not able lock as per client needs then better to go with early delta init options.
    Thanks

  • Activate BI Business Content in production system

    Hi experts
    I have a doubt, someone activated business content in production system, what are the consecuences in the future?
    Are there any procedure to follow to activate business content from developement system and then to transport to QAS and PRS?
    Edited by: José Jaramillo Padrón on Dec 15, 2008 11:32 PM

    Hi
    what are the consecuences in the future?
    Yes Its not advisable to activate the Business Content in Production server, because all the final Reporting Data will be fetched for the users from the same Production server and we should keep the system ready and available for all the time for the data loading and reporting.
    If you are engaging the the system in activating the BC (hope you know that BC activation takes time and while activating it will lock all the dependent objects involved in it)
    Are there any procedure to follow to activate business content from developement system and then to transport to QAS and PRS?
    BC should be activated from Dev then Transport it to Quality testing activities user acceptance then transport finally to PRS.
    Hope you know the steps for activating BC or else http://help.sap.com/saphelp_bw31/helpdata/en/80/1a66d5e07211d2acb80000e829fbfe/frameset.htm
    Hope it helps

  • Error in Importing standard SAP DCs to Production system

    Hi All
    I am trying to do a transport from QA to Production system. 3 of the standard components
    sap.com_GP-CORE
    sap.com_CAF-MF
    sap.com_CAF
    are not getting imported  to Prod. It gives an error
    caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'cedeploy' could not be connected to the specified host 'bhbc1ce01.ent.bhicorp.com'and port '50004'.:The user 'cedeploy' could not be connected to the specified host 'bhbc1ce01.ent.bhicorp.com'and port '50004'.
    com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'cedeploy' could not be connected to the specified host 'bhbc1ce01.ent.bhicorp.com'and port '50004'.
    The user is not locked. I managed to import the rest of the components to Prod with the same user ID.
    Only thing i am able to notice is that, the Owner for these 3 components are "jointadm"  and the rest of the other components had owner as "Make".
    Please give me your suggestion.
    regards
    Deepu

    HI,
    Under the runtime systems tab in CMS lanscape configurator,
    check  the username and password details given for thr production runtime system .
    also once save the configuration.
    Regards,
    Satya.

  • Background Job Running long time in Production system ???

    Hi guys,
    I have custom report which runs normally in 20 minutes.  i am executing this report every day.  but when i execute the same report yesterday it took 5 hours.
    i did the performance trace ....the sql statements are in acceptable range only. i don't see any major time consumption. 
    since it's in production system  we can't debug the active job....
    can u guys, throw light on this issue.
    Note : there are many posts related to this already in the forum, but not helps to resolve my issue.
    Regards
    Girish

    Giri,
    You can use STAD (or older one SE30) to have a trace of the program if you have that access and will be a great help in finding the problem.
    If you can't due to some reason, then next time job runs for long (while in ACTIVE state), check SM50 regularly to see that the is process hanging on a table fetch, check that any of the DB table is not getting frequent locks in SM12.
    Also, you should check that if your job does any table update, is there any new index created in prod system for that table.
    If you can't find anything, then take the necessary access in Prod from basis temporarily and debug the job to find exact issue.
    Regards,
    Diwakar

  • Solman 7.1 LVSM Product system has no technical system assigned

    Hi All,
    As reference of blog #sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification  work in SOLMAN7.1SAPNetworkWeblogs%2528SAPNetworkWeblogs%2529
    I have created product instance from LSVM and now I have problem to add "product system" for Enterprise portal (using NW 7.3)  to the landscape, as its throw me an error "Product system has no technical system assigned".
    From the display help its mentioned:
    *Diagnosis*
    Product system is not assigned a technical system in the system landscape of the Solution Manager.
    *System Response*
    Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your product systems are incorrectly assigned, many important functions are not available to you, or are only available on a restricted basis.
    *Procedure*
    Assign one or more technical systems to your product system . SAP recommends that you use the corresponding wizard of the Landscape Verification Tool. To start the wizard, choose the button Change Technical System Assignments next to the message. The user interface of the wizard contains detailed information about its usage.
    I'm not sure with sentence of Assign one or more technical systems to your product system and which wizard are this referring to ?
    I have also checked from the wiki:
    http://wiki.sdn.sap.com/wiki/display/SMSETUP/MaintenanceofProductintheSystemLandscape#MaintenanceofProductintheSystemLandscape-EnterprisePortal
    And its only supported for NW 7.0 not 7.3.
    Is there anyone had this issues ?
    It's feels like I'm the only one stuck in this.
    Thanks in advanced.
    Raff

    Hi Sunny,
    Many thanks for your reply.
    I have followed the guide you mentioned, now I can see 2 EPD Error from LVSM.
    1. Product system EPD has no technical system assigned (new)
    2. Technical system EPD is not assigned to a product system
    For number 1. if I clicked on Change Technical System Assignments I can see EPD there, but when I want to add the EPD by clicking > I've got this error message " Newly linked technical system EPD has already been locked by user" I've tried to remove the lock from sm12 but nothing happen.
    For number 2. if I clicked on Change Product System Assignments, there is an error messages "Technical system EPD was updated in parallel session"
    I believe the number 1. coming because I create it from SMSY, but the number 2. is still there in the first place.
    Cheers,
    Raff

  • 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.

  • Not able to change the data of test data containers in production system

    Dear All,
    We have created eCATT scripts in Development SolMan System and moved the transports to Production SolMan System.  Customer wants to change the data at Test data containers and run the scripts in production system but we are not able to edit the data. 
    May be the reason is SCC4 transaction code has set the below option.
    Changes and transports for client-specific Objects
    u2022 No changes allowed
    Customer doesnu2019t want to change the above option and wanted to change the test data containers to give different datau2019s and run the eCATT scripts.
    Could you please let me know the solution for this?
    Your help is really appreciated.
    Thanks,
    Mahendra

    eCatt has the feature where you don't need to transport the scripts or test configuration to our target system. We can keep all our scripts and test data in Solman and run this script any other system in your landscape using the System data container and target system.
    Maintain the production as one of the target system in System container in Solman and point that system while running the script. Change the test data in Solman to run this script.
    Let me know if you need more information
    thanks
    Venkat

  • Error while extracting the data in R/3 production system,

    Hi Team,
    We got the following error while extracting the data in R/3 production system,
    Error 7 When Sending an IDoc R3 3
    No Storage space available for extending the inter 44 R3 299
    No storage space available for extending the inter R3 299
    Error in Source System RSM 340
    Please guide us to fix the issue

    It´s very difficult to help you without knowing
    - what is going to be transferred
    - where you get this error
    - system configuration
    - actual memory usage
    - operating system
    - database and configuration etc. etc.etc. etc.
    I suggest you open an OSS call and let the support have a look on your system. It´s much easier if one has system access to find out the cause for that problem.
    Markus

  • Activating Update Rules in BW Production Systems? How

    Hi all...
    How do we activate Update rules in Production systems?
    As we dont have the activate button high lighted in update rules.
    Urgent.
    Thansk in Advance.

    Hi,
    Since the production system is not chnagable you will will not get the activate button. you can only see the updaterules in display mode.
    You should activate the update rule in the Dev environment and capture the same in a transportable request and transport the same to Production environment.
    If it is very urgent and the transport from Dev would take time. You can as the basis to open the productyion client from tcode scc4, once the procuction client is open you will be able to activate the update rules in production system itself.
    assign points if useful
    regards
    Venkata Devaraj

  • Unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

    unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

    Hi,
    For SU01 role removal, you do not need S_USER_AGR with 02, and as you mentioned both authorizations available in production, if so trace should not show you the S_USER_AGR with 02 with RC=04.
    I would recommend to do role comparison for the user performing the activity. and then check if you have the S_USER_AGR with 02 in user buffer SU56.
    But ideally it should not ask you S_USER_AGR for 02 through SU01, so please take help of abaper to debug it.
    Also put trace in non-prd to see if S_USER_AGR is getting checked with 02 for removal through SU01.
    BR,
    Mangesh

  • Process Order tables and Production System Performance

    Hi All,
    What are the different tables of Process order? Also how do i know which table affects the system performance of Production system and to what extent if Change Logging is made active ?
    The issue is in our clients place we would like to set the Change Logging ( Records changes made for any transaction )  for Process orders and we would like to know to which tables change logging should be made active so that Production system performance is not affected.
    Please help me regarding this.
    Thanks in Advance,
    Neetha Avani.

    All the changes done in any transaction are saved in CDPOS table.
    when there is any report developed based on this table then the performance will be very slow.
    Tables used for process orders are
    AFKO            Order header data PP orders
    AFPO            Order item
    AFRU            Order Confirmations
    AFRUHR        Order Confirmations for HR
    AFRV             Confirmation pool
    AFVC             Operation within an order
    Hope the above helps.

Maybe you are looking for