Infosource invisible in production system

Hello,
We are facing a unique problem that we are not able to find the Info source for a ODS and one Infocube in our Production system. In Quality system it was working fine and we could see these Infosources. But on transporting the complete devlopment to Production system , we could not locate the required Infosources.
As a matter of fact,these Infosources was available in the data flow for the Cube,
and we could go to the infosource by double clicking it in the dataflow. But the same was not visible in the Infosource tab in AWB in production system.
We tried various Options like:
1 RSA1 -> Infosource -> from MENU settings -> display generated objects -> and check the radio button show generated objects. Still the infosource was not visible.
Can anyone please provide some inputs to it.
Thanks,
Vipul

Hi Anil,
Yes, you are right; my Application component had not been transported to Production System.
My Infoareas are lying in unassigned nodes and so the info-objects.
But i dont able to understand why my application componet is not been transported to Production system. When it succesfully transported to Quality system where all things are working fine.
I have transported the same request to production system as well. Can you provide some insight to it.
And to other replies i can say that i cant replicate and activate Data Sources in Production system. I have already done these steps in Development system.
Thanks and regards.
Vipul

Similar Messages

  • Infosource invisible in Productive system (APO BW)

    Hello
    I've created a new setup where i'm uploading from a flat file to an infocube. It works fine in the T and Q system.
    However after transport to the P system i can only see the infocube in RSA1, i cannot see the infosource so i can't create an infopackage for loading data. What's strange is that if i select "show data flow" on my infocube i can see the entire chain fine, and i can also doubleclick my infosource and see the structures and transfer rules etc.
    Everything looks fine and everything is active but i cannot see the infosource in the menu and i cannot find it with the search function either.
    Very strange i think, anyone know what might be wrong?
    Regards
    Simon Pedersen

    Dear Simon,
    1. Try executing Transaction RSA6. Open the hierarchy (CtrlshiftF11) and search for the new Data source.
    2. In RSA1, source System> APO Logical system> Right click and select Replicate data source.
    3. Now check if the Data source exist in the system.
    I assume, you have followed the below steps while transporting the changes to production.
    1. You have transported Datasource first.
    2. Then replicated the Datasource in Destination system... (as described in the above step 2)
    3. Then transported child objects like Transfer rules, Communication structure, Infopackage...
    Hope this helps..
    Thanks for your points..
    Cheers
    Vignesh M:-)

  • Hierarchy loading Error in Production system

    Hi All,
    I am loading Hierarchy file, the file is there in application server(AL11), in external tab i gave same path. but when i try to load it is showing below Error message.
    Invalid entry, hierarchy 0XMK4PVWO05BM4GP5KVEFQ9L4 does not exist.
    Diagnosis
    Hierarchy 0XMK4PVWO05BM4GP5KVEFQ9L4 does not exist.
    Procedure
    If the underlying InfoObject supports hierarchies create the hierarchy and try again.
    If hierarchies are not supported, select another InfoSource or change the definition of the InfoObject.
    That means Hierarchy file problem (OR) In Info package I selected Hierarchy selection problem?
    Kidnly help on this issue.
    Cheers,
    Srikanth.
    Edited by: srikanth on Apr 21, 2009 11:49 AM

    Is this only happening in your production system?  Have you tried loading the hierarchy file to your development or acceptance system?
    I've seen this error occur when the authorizations are not set up for loading hierarchies (i.e. maybe they can only be loaded via process chains under the remote ID used for process chains, and not using your own ID).  That's why I was suggesting you try to load the same file to your dev and acc systems and see if you get the same error.  Sometimes this error is thrown for other reasons and does not really have to do with the file being loaded or the hierarchy missing.
    Also, if you're loading from the App Server, double-check that you have the Application Server radio button selected on the tab where you select the file path.
    Good luck!

  • Delting Objects from production system

    Hello All,
    I need to delete some of the Infoobjects,ODS and Infocubes from my Production system.
    for e.g:
    We have Inserted infoobject ZXX as data target,so it is available under infoprovider.
    For this,we have update rules ZYYY.
    In the Infoprovider tab: I right click on the Infoobject ZXX and selected the "Remove Infoobject as data target option".So update rules and the infoobjects were removed from the Infoprovider tab.
    Also I deleted the infosource ZYYY.
    While deleting the Infoobject ZXX from the Infoobject tab,it says "the update rules ZYYY still exists and hence cannot delete the data"
    Please let me know,how can i delelt the Infoobject and the update rules.
    Any help will be appreciated.

    Hi,
    Make sure that you are having prober authorizations to delete the objects. If you have, try to log on again. Also Check for Data flow upward objects from this object.
    Edited by: P. Saravana Kumar on Apr 1, 2009 6:01 PM

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

  • 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

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

  • License for testing and production systems

    Hi Experts
    Can any one help me out on implementing license in my B1 System.
    According to our contract we have licensed following user types:
    User Type
    Licensed
    AddOn Access License    25
    Professional User                5
    Software Development Kit - Development Version 20
    We have Test/development system in one hardware and Production system on different hardware. Please advice me how to request/allocate license for my test/development system and production system.
    We tried creating a Test System in SAP Market place and requested license for test system. While requesting license for production system, it is found that the license is exceeded. In other words, developent system license also counted.
    Please advice me on the best practices of B1 license implementation.
    Thanks and regards
    Ajith G

    Hi,
    Our customer wants to Keep the production data secure. Developers and consultants should not have the access to it.
    Then you have only two options:
    1.Either you should maintain a standalone b1 server for the developers and consultants to test their solutions and scenarios.
    2.Otherwise you can create users in sql studio for accessing only the test database.
    So that as per your requirement
    All configurations and sample data will be kept in a test environment where developers and consultants can do their work.Once everything is correct Admin will do the transfer to production.
    Note:New users can be created in the sql studio under Databases-><Company Db>->Security->Users, Rt.click new user

  • Fetch data from a table present in production system

    Hello Gurus,
    I want to get data from a table which is present on production system. And i cannot create RFC. Can anybody tell me any other way of getting the data?
    Thanks in advance!!
    Regards,
    Kumail

    Hi,
    if it's just a one time requirement to get the data from the table into an excel sheet e.g. for some error analysis or for making a development decision, why bothering with development? Just run se11 or se16 display the whole content and save it as excel sheet via the menu. This would be the fastest solution in my opinion.
    If you do not have the permissions to see the table in production ask a admin or super user. Creating a program to dump data from the system you are not really allowed to see usually brings you in a lot of trouble :o).
    Kind Regards
    Roman

  • Replicate data from one client to another in a production system

    Hello,
    I have two client in production system. Whenever a equipment is created in one client it should be replicated in another client and whenever a equipment is changed in one client the changes should be replicated to another client.
    Data should be immediatly replicated to the another client.
    Can basis do some setting so that the two client will always have the same data for equipments.
    or i have to get the data from one system and send it to another system through idoc and update that data in another system. This will take a lot of time.
    or is there any easy way

    Hi Sachin,
    You need custom program to achieve this requirement. Either you can use ALE+IDoc or direct BAPI function module call.
    This should happen within seconds if designed properly.
    Regards,
    Avinash

  • Error message while transporting SapScript to productive system

    Hi,
    I have tried to transport an order sapscript form (modified Medruck) into the productive system. But I got errors in transaction stms.
    The error message is displayed like this:
    <b>R3TRFORMZMEDRUCKN</b> was repaired in this system
    Message no. <b>TW 104</b>
    <b>Diagnosis</b>
    Object R3TRFORMZMEDRUCKN is in repair status. Therefore, it cannot be imported.
    <b>System Response</b>
    The object is not imported.
    <b>Procedure</b>
    If you still want to import the object, release the relevant repair andrepeat the import.
    Does anybody know something about that problem?
    Cheers

    Hi,
    maybe somebody has already create your form in the productive system. Now you would like to create something already created.
    Maybe, you have to check in the TADIR table (key R3TR / FORM / name of the form) if the form already exist. What is the system source for the form. (in the PROD)
    And finaly, you can go to the SE03, select the first line and execute (to find object R3TR FORM ..) in all the request order. That will show you who has play with this form, and if a request was lost between DEV & PROD.  (in the DEV)
    Rgd
    Frédric
    Message was edited by: Frédéric Girod

Maybe you are looking for


HashFlare