RE : Production system Issue on ME38

Hello guys,
We have very critical issue on ME38 that is scheduling agreement.
One SA has a bunch of line items and that line item has a bunch of schedule line. We didn't use MRP and confirmation.
The problem is even though we did GR successfully at MIGO but GR quantity in SA is not updated, Since GR done successfuly, stock looks good but GR quantity in SA is not updated. Some of item line is updated correctly but the others is not updated correctly.
I don't know what the problem is.
Please help me. It happened production system.
Thanks and regards.
Seol.

Hi,
Definitely this will not occur in SAP
Please check the dates in the schedules line and go the SA and the history. What ever material document no is created it will definitely appear in the history
G.Ganesh Kumar

Similar Messages

  • Production system issues

    1)how to change logical business date to update extracted data to b/w staging area,
    2) what are dead locks
    3)what is reconciliation

    1)how to change logical business date to update extracted data to b/w staging area,
    If you are talking about extraction date, you can set calday in update rules, then you get Calday in Cube/ODS.
    Pls: give clarity on this.
    2) what are dead locks
    At a time more then one task will perform on a single object , you get dead locks.
    Eg: you are loaded data to ODS and data is activating at the same time one more request is updateing data to ODS then at that time there is chance to get deadlocks
    3)what is reconciliation
    Checking the data between Source system and BW system.
    Eg: you loaded sale data to BW, then you need to check the same data is there in ECC or not?. (for this you need Functiona consulatnts help)
    Thanks
    Reddy

  • Issue with java on production system help!

    We just started getting this error when we have a portlet showing over twenty listings and a user selects the next but to view more of the list. We just wen't live this morning what could be wrong? Help
    java.lang.ArrayIndexOutOfBoundsException
    at javax.servlet.ServletInputStream.readLine(ServletInputStream.java, Compiled Code)
    at oracle.webdb.page.PageBuilder.getMetaData(PageBuilder.java, Compiled Code)
    at oracle.webdb.page.PageBuilder.process(PageBuilder.java, Compiled Code)
    at oracle.webdb.page.ParallelServlet.doGet(ParallelServlet.java, Compiled Code)
    at oracle.webdb.page.ParallelServlet.doPost(ParallelServlet.java, Compiled Code)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java, Compiled Code)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java, Compiled Code)
    at org.apache.jserv.JServConnection.processRequest(JServConnection.java, Compiled Code)
    at org.apache.jserv.JServConnection.run(JServConnection.java, Compiled Code)
    at java.lang.Thread.run(Thread.java, Compiled Code)
    James
    null

    This seems like a pretty serious issue. We have a production system up where we cannot limit PORTAL MADE REPORTS to a certain number a page. Users CANNOT click a NEXT button. We have found no way to eliminate the NEXT button on a Calendar.
    We need a workaround before Feb 9.

  • Issue whilel transporting from production system to quality system

    Hi All,
        I am facing issue in process chain when I transport it from production system to quality system. Process chain is related to deleting PSA logs. When transported to quality system object_type and object_name fields in display variant becomes blank. In production system it is showing 8ZXXX_CA, it should become 8ZXXX_HA in quality system.
       Thanks for your help.
    Regards,
    Shankar

    Hi,
        sorry it was frm dev system to quality system, not prod to quality.
    Regards,
    Shankar

  • Resolution required for an issue found in Coherence Command pattern in a production system

    We have a Trade and position processing system. Command pattern is used as it's core mechanism to distribute and execute these Trade and position commands acros the Coherence Cluster. So far the design pattern has worked very well for us.
    However, a scenario was encountered in our productions system, which disallowed to execute commands on a command node.
    Attached is a document which contains a complete detailed analysis of the cause. The end conclusion was that currently command pattern is not able to manage the context state correctly, when there are cluster failures.

    Hi Sandeep,
    If you've not done so already, please raise an issue in the issue tracking system for the project: https://java.net/projects/cohinc/
    Alternatively, raise a Coherence Service Request (SR) and it will be forwarded to us with the appropriate information.
    -- Brian
    Brian Oliver | Architect | Oracle Coherence

  • Same logical system name for two productive systems - BW, PI issues

    Dear all,
    we have a productive system which serves two companies (different company codes). This system is connected both to BW and PI for both companies.
    There is a requirement that these two companies must use their own system, so the whole landscape (dev,qa,prd) will be copied to different systems (different server with different system id).
    As a result of the above procedure we wll have two different productive systems, as required, but we wll have the same logical system name for the two productive systems, which must be both connect to bw and PI.
    However as far as I know:
    - we cannot connect systems with same logical system name to BW,PI
    - we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
    How can we overcome the problem?
    Please advice.

    > However as far as I know:
    > - we cannot connect systems with same logical system name to BW,PI
    > - we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
    Right.
    > How can we overcome the problem?
    Since you split up systems (or plan to) I highly recommend booking an SLO service (http://service.sap.com/slo). Those people have to the tools and the knowlege to help you. I would not do this on my own.
    Markus

  • Info package issue in Production system?

    Hi experts,
    I would like to know about the scenerio of info packages in production system.
    1) When the objects are transported to production system,
    Do we use the same info packages in the prod system,which are used to schedule the load in development system.
    2) Do we create new infopackages everytime for the data load in production system?. Please let me know about this.
    3) In my case when I schedule the infopackage which are transported to prod system are asking for request number. Is it normal?. I mean everytime we schedule, will it ask for request number in prod system.?
    Please let me know the normal procedure as to how to load the data in prod system(Standard Procedure Which is followed by all developer's to load the data)
    With regards,
    Dubbu

    1) When the objects are transported to production system,
    Do we use the same info packages in the prod system,which are used to schedule the load in development system.
    Ans : The choice is yours.In our system we create infopackages directly in production.Its just flexibility for us.
    2) Do we create new infopackages everytime for the data load in production system?. Please let me know about this.
    Ans : Infopackages are reusuable but if they are used in process chains its better to create new ones as it will affect the associated process chain.
    3) In my case when I schedule the infopackage which are transported to prod system are asking for request number. Is it normal?. I mean everytime we schedule, will it ask for request number in prod system.?
    Ans : Yes its normal to ask request number but in development system.

  • SAP Product issue in 'Product System' tcode SMSY

    In the process to create the new 'Product system' for SAP Product 'SAP ERP 6.0', system is not accepting any installation number (because of grey mode) but If i choose the SAP Product ' SAP Netweaver', i can assign Installation number for ECC server.
    When i'm selecting Product 'SAP ERP 6.0' for new product system, i'm getting the Product version 'SAP ERP 6.0 01' .
    as per our license policy, we have to use 'SAP ERP 6.0' as the SAP Product .
    any idea about to fix it or if i'm missing something?
    We are using SAP EHP1 for SAP Solution Manager 7.0 and SAP ECC 6.0 for ECC server landscape.
    Thanks
    Amar

    using the following link (reply from Miguel section), i'm able to fix this problem
    Product Version SAP ERP 6.0 Missing from solman 7.0
    Thanks

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

  • Error while transporting ADDRESS to production system

    Hi all,
    We are in the process of a new rollout and we have created new plants and company codes. the same have been transported to quality and pre-production systems without any issues. however when we transport the same to Production, we face an error
    The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
    The object
      R3TR TDAT ADDRESS_4.6*
    has not yet been imported into client 100 without error.
    the objects are getting transported with same address number as in development which in production points to a different address.
    as far as i know the system should generate a new address number and assign it to the object during transport.
    Any suggestion wud be great

    the log is
       Post-import methods for change/transport request: MEDK909182
          on the application server: ITMISAPGW2
       Post-import method AFTER_IMP_CUST_ADDRESS started for ADDRESS_4.6 T, date and time: 20090714144548
       Post-processing taking place in client 100
       The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
       The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
       The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
       Post-import method AFTER_IMP_CUST_ADDRESS completed for ADDRESS_4.6 T, date and time: 20090714144548
       Post-import methods of change/transport request MEDK909182 completed
            Start of subsequent processing ... 20090714144547
            End of subsequent processing... 20090714144548
       Execute reports for change/transport request: MEDK909182
          on the application server: ITMISAPGW2
       Reports for change/transport request MEDK909182 have been executed
            Start of................ 20090714144548
            End of.................. 20090714144548
       Execution of programs after import (XPRA)
       End date and time : 20090714144548
       Ended with return code:  ===> 8 <===
    regards,
    Tarun
    Edited by: Tarun Bahal on Jul 16, 2009 9:41 PM

  • Transformation pointing to Quality Client in Production System Repeatedly

    Hi,
    I need to understand one issue which is explained in detail below step by step.
    1. I created one Customized Data Source(Full Load) and replicated in BW.
    2. Also created Info Objects, DSO, Info Package, Transformation, DTP.
    3. While transporting this modelling to Production(first time), i unknowingly/mistakenly missed capturing the datasource in Transport Request.Sequence of transport was -
    Data Source
    Info Area
    Info Object Catalogue
    Info Object
    DSO
    Cube & MP
    Data Source
    Transformation
    Info Package & DTP
         Now, the moment TR for transformation was transported it threw an error - "Data Source does not exist in Quality client". Then I transported the Data Source TR and after that re-transported the transformation TR production and this error was removed.
    But, there were 2 transformations in production - 1) Pointing to Production, 2) Pointing to quality.
    4. I request the basis team to delete the second transformation(pointing to quality) from BW production system.
    5. After that we captured Data Source and transformation in same TR and transport was successful.
    6. Now, after few days we transported a change to production for same object and the system again threw the same error mentioned in point no.3 above and created two transformations again.
    How to resolve this issue permanently and I also want to know the reason of this type of system behavior.

    Mohammed,
    I did that also - please read my step no.4.
    We are able to delete the transformation which was referring to quality client and then captured D.S & transformation in a single TR and transport as successful.
    Now, after few days I did one change in the same transformation and transported to production.
    System Behavior:
    Error - " No source exist (i.e.,system referred to quality in production)".
    Also again transformation was visible in production which was referring to quality client(which we already deleted with the help of BASIS).
    Now since again the transformation needs to be deleted from production, our basis team is telling us to they cannot delete objects every time in production.Thus,
    1. Is there any option to solve this issue permanently?
    2. Also is it necessary to transport data source along with the transformation which is directly linked to data source?
    Please Note: We have Dev+Quality as one client and Production.

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

  • Support message and change requests only for production system

    Hi guys,
    I would like to connect the solman helpesk with CHARM ( CHARM is still running ).
    In CHARM I have to create a CR only for production system. ( don't know why - but works as designed).
    In SAP helpdesk I can create support messages for every kind of system type but if I want to connect both (HD and CR) , the source system (ibase component) of the issue will copied to the CR and runs in error because of the rule (only p-system) of CHARM.
    Of course I can change the ibase to production system manually in SDCR but it seems a very error-prone method.
    Now my question: is it possible to change the ibase component due to the creation of CR by copy rule or something like this?
    Kind regards
    Rayko

    Hi Rayko,
    We do not have this option.
    Once in ChaRM, we assume that the changes will always correct an issue in the PROD system.
    I would recommend to open the tickets directly with the PROD system IBase, once the issue is also happening there.
    Best Regards,
    Fernando

  • Delete COPA value fields in a productive system

    Does anyone have practical experience with deleting COPA value fields in a productive system?
    The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
    An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
    I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
    Cheers, Peter

    To delete characteristics or value fields, you should perform the following       
    activities:                                                                               
    1. Delete the corresponding characteristics and value fields from      
    Customizing in all clients (this includes forms, reports, planning     
    layouts, and so forth). To locate characteristics and value fields, use
    the appropriate where-used list in the Customizing Monitor. You can    
    access it by choosing Tools -> Analysis -> Check Customizing Settings  
    (TA KECM).                                                             
    You can jump directly from the where-used list to the relevant         
    Customizing transaction and then delete the appropriate field there.   
    2. Switch to the screen for maintaining the data structure of an       
    operating concern (Maintain operating concern).                                                                               
    3. If you need to effect other changes to the datastucture for the     
    operating concern before making any deletions, effect those changes and
    save the data structure.                                                                               
    4. In order to be able to select the fields of the data structure,     
    choose Extras -> Characteristics (or Value fields) -> Unlock.                                                                               
    5. Select the characteristics and value fields to be deleted and remove
    them from the data structure with the "Reset fields" function.                                                                               
    6. Reactivate the operating concern. The system starts by checking
    whether the operating concern contains any data and whether the fields   
    to be deleted are still being used in any Customizing settings.                                                                               
    7. If none of the fields are still in use, the system then starts the    
    re-activation. If the operating concern does not contain any data or     
    does not require the database system to be converted, the tables are     
    activated. You are then able to activate the environment for the         
    operating concern. In this case, the following activities no longer      
    apply.                                                                   
    If the operating concern already contains data, a system message tells   
    you that the database needs to be converted. If you proceed, an          
    activation log appears (at the top of the list).                                                                               
    8. Analyze the activation log. If it only contains error messages        
    telling you to convert the tables, proceed with the next activity.       
    You must otherwise remove the cause of the errors before the tables can  
    be converted. In this case, you should answer "No" to the next prompt,   
    which asks whether the conversion transaction should start.                                                                               
    9. If you still only receive error messages telling you to convert the   
    tables, choose "Back" and start the conversion.                                                                               
    10. Plan a job for the conversion. A list of the tables to be converted  
    is shown for this. If the tables only contain a small amount of data     
    (less than 10 000 records), then all the tables can be converted in one  
    job. In that case, you can select all the tables.                        
    For larger tables, conversion should take place in several jobs.                  
    However, you should ensure that table CE4xxxx (where xxxx = operating             
    concern) is the last table to be converted.                                       
    Warning. No other changes can be made to the operating concern during             
    the conversion.                                                                   
    A copy of the table is generated during the conversion. The database              
    system should have sufficient memory available for this copy.                     
    To schedule conversion as a job, use the "Schedule selections" function.          
    You can display the current status of the conversion by selecting the             
    "Refresh" icon. Tables disappear from the list once they have been                
    converted sucessfully. If a conversion is taking a while, it is also              
    possible to leave the transaction. You can then continue the conversion           
    using DB requests -> Mass processing in one of the following ways:                
    With the job overview. You access this by choosing System -> Services ->          
    Jobs.                                                                             
    Using the database utility transaction. You access this by choosing               
    Utilities -> Database Utility in the ABAP Dictionary menu.                        
    You can use the status function to call up the status of the operating            
    concern during operating concern maintenance. You need to activate all            
    tables after conversion.                                                                               
    11. To analyze errors that have occurred during the conversion, you can           
    use the database utility transaction by choosing Extras -> Logs. The log          
    has the same name as the conversion job: TBATG-date. You can also                 
    restart the conversion with this transaction.                                     
    For more information on the database utility, choose Help -> Application          
    help while still in the above transaction.                                                                               
    12. Once you have activated all the tables in the operating concern,    
    generate the operating concern environment from within operating concern
    maintenance.                                                            
    You can then use the operating concern again.                           
    Please, refer to the IMG documentation under Controlling ->             
    Profitability Analysis -> Structures -> Define operating concern        
    -> Maintain operating concern, for further details.                     
    Hope it helps

  • SOAP Receiver Channel 2 nodes inactive in Production system

    Hi All,
    We are facing an issue with the SOAP receiver channels in production system. There are 4 nodes which can be seen in the communication channel monitoring and out of which 2 have the status as inactive and the short log says "inactive or never used".
    But the same nodes are active on the sender SOAP channel and all other channels.We have also checked the Status of the SOAP service that is also set to active.
    Now when the server (App server5 in our case) is switched off, which has the 2 active nodes, the messages are not processed since the nodes on the other server are inactive.
    Request you to please help us out in finding out why the nodes are in inactive status only for SOAP receiver channels. Do we need to change any settings at the adapter engine level.
    Thank you.
    Regards,
    Sarvesh Desai
    Edited by: Sarvesh  Nispat Desai on Aug 25, 2010 5:25 PM

    There is an error in reporting the status of SOAP channels. This error has already been fixed by SAP and is available as a fix in higher releases (PI 7.10 and above, latest SPs) .
    The status "inactive or never used" is shown in channel monitoring at the following two times:
    1. After creating a new SOAP channel (sender/receiver) till this channel processes any new message.
    2. After the PI system is restarted, all the SOAP channels show this status, though they are ready to handle any incoming/outgoing messages. The channels continue to display this status till they process any new message.
    In both these situations, the SOAP Channel can handle/process messages successfully. So, kindly ignore this channel status ("inactive or never used") reporting error in channel monitoring. This will not at all hamper the normal functioning of the SOAP channels.
    Hope this answers your query.

Maybe you are looking for