Error in confirmation document in CRM

Hi Experts
I am doing the service confirmation as per sap best practices scenario C69 Service Order Management  and
Problem Details
I am doing the service confirmation as per sap best practices document
C69 Service Order Management
When I assign the technician to the Service  confirmation and save the service confirmation.
I am getting this error  when confirming orders with materials.
Error
Errors have occurred while transferring the document into another system.
Refer to the enclosed log to view the error messages.
Transmission log
No customer could be determined for technician with personnel number xxxxx (Notification E CRMSERV_ACC_EXEC 006) Enter a customer for special stock W (Notification E M7 072)
I have created an HR record for  an internal service technician in SAP R/3 6.0 for the Personnel number xxxxx . I have linked this record to CRM 2007 through the BP record.
Pls suggest some hints!!!
Regards,
PP

Hi,
Consignment process is related to confirmation process because we have to tell the system where to pick up the stock(spares )from.
Technician stock is represented by a-
1. Storage location in SAP ERP
2. Technician consignment stock in SAP ERP
3. Customer consignemnt stock in  SAP ERP
You are using the third scenario here
When confirmation is created system,we are telling the system we have used some stock to carry out repair
For the system to be able to determine the correct stock,we maintain customer consignment stock or technical consignment stock.
By maintaining consignment order for customer we are doing nothing but mainatining the stock for that customer
Hope this  clarifies your doubt
BR
Itty

Similar Messages

  • Cannot view SharePoint Online documents through CRM Online Outlook Connector - iframe error

    We are integrating CRM 2013 Online with SharePoint 2013 Online. We have installed the CRM List Component solution. We have also modified the SharePoint master page to permit display of SharePoint content in iframes. We can view SharePoint documents within
    CRM using Internet Explorer after setting the Documents link for an opportunity to point to a document set in SharePoint. However we cannot view documents through the CRM Outlook Connector. We receive the error that "This content cannot be displayed in
    a frame".
    We have tried adding *.sharepoint.com, *.dynamics.com, and *.microsoftonline.com to IE's Trusted Zone with no effect.
    The application launched by the Outlook Connector is called Microsoft.Crm.Application.Outlook.WebFormsHost and it's my understanding that it uses the IE engine to render online content.
    Is there anyway to view SharePoint content embdedded in CRM via an iframe with the Outlook Connector?

    I have the same problem here.
    The integration works fine outside of Outlook, but if, for example, an account is opened within CRM for Outlook the error occurs.
    - No masterpage modification
    - Some security setting in IE 11 (perhaps IE 11 is the problem)
    - Installed the solution in the used site collection
    - Configured CRM settings
    Dirk

  • Problem in transfering the Document from CRM to R/3

    Dear CRM Experts,
               I am working in CRM 2007.
      we connected the CRM 2007 with R/3.
    In CRM we creating the Service order -> Service Confirmation -> Return Order.
    When  we create the Return Order in CRM it Copies the Document and creates the Same Return order in R/3.
    But in our case it is not creating the return order in R3 and  i am getting the Error message
    "An error has occured in the system R22CLNT787 while copying the document
    Message no. CRM_ORDER_MISC 020
    Diagnosis
    Errors have occured while transferring the document into another system. Remove the error messages from the enclosed log.
    Transmission log
    Object link not known in CO (Notification E IAOM 019)"
    Please help me to solve this problem.
    Thanks & Regards,
    Ashok

    We had a similar error in transferring documents in the other direction, from R/3 to CRM.  During the transfer, SAP carried out the following steps:
    1.  Transfer R/3 object to CRM
    2.  Create 1Order Object in CRM
    3.  CRM send BOR object (log sys, GUID, obj type) of 1Order Object to the R/3 object
    4.  R/3 attaches the BOR object under linked objects
    5.  R/3 sends a response with the success/failure of the operation in Step 4.
    6.  CRM receives the message and writes it to a log
    We were missing Step 4.  (We are using Case Modeller in R/3 FSCM Dispute Management, so we had to attach/activate the link between R/3 and CRM in that step).
    Check CRM transaction SMW01 to see your message logs.  Perhaps they will offer more insight.
    Thanks,
    Ben
    We found that we were missing table entries in the

  • Error in Sales Transaction in CRM 4.0 ?

    Hi All,
    We are working on CRM 4.0 i have created a sales transaction in WEB and  transaction will see in CRM and it is getting downloaded to R/3.
    But when I go back to CRM and check Sales Transaction it is showing me error as "An error has occured in the system XYZCLNT100 while copying the document".
    And i have been check in SMQ1&SMW01 ..in both T codes there is no error ..
    How can i figure out this problem ?
    can anyone help me in this regard?
    Thanks in advance.

    Please look into note 490932 for any issues of this nature
    This note gives an insight into possible error causes during the download or upload of sales transactions between CRM and R/3 and helps you correct these errors. This note is relevant for CRM Release3.0.
    It is also relevant for releases higher than 3.0.
    Other terms
    Download, initial, delta, delta download, SALESDOCUMENT, BUS_TRANS_MSG, event 00501014 501014
    Reason and Prerequisites
    The error causes may be included an incorrect configuration or missing system settings. The note only focuses on the sales transaction-specific configuration of the data exchange, but not on the settings for CRM Middleware in general or for other CRM Server applications.
    Solution
    In CRM Release 3.0, the following sales document items are transferred to the R/3 System:
    Sales items
    Customer return items
    Substitute delivery item
    Credit memo request items
    Debit memo request items
    As a leading system for the order entry, CRM only transfers data to the R/3 System if it is relevant for the logistical subsequent processing (delivery, billing). For this reason, requests for quotations and quotations themselves are not transferred to the R/3 back-end system with the standard delivery. With SAP note 455678, you can use a modification solution to also transfer quotations entered in CRM to the R/3 back-end system.
               Restrictions of note 455678:
    If you are using this solution, you cannot create any sales orders with reference to customer quotations in CRM.
    Mixed document processing (partially customer quotation items and partially sales order items) is not supported in the R/3 System and is therefore not possible during the quotation upload. The solution specified here only performs the upload for documents that consist of quotation items only.
    The quotation items must be defined in the Customizing for copying. This solution does not cover scenarios where the order is generated from the quotation as a result of a status change. Therefore, quotations entered in SAP Internet Sales (in particular) cannot be transferred to the R/3 System.
    Only completion rule 'A' ('Completed with one-time reference') is supported in the R/3 System.
    Sales transaction-specific settings for the data exchange
    1. Basic administrative settings for the replication of sales transactions
    a) The BDoc relevant for the distribution of all transaction types is called BUS_TRANSACTION_MESSAGE. In transaction SMOEAC, the relevant R/3 site must be subscribed to the corresponding publication 'All Business Transactions (MESG)' so that sales documents can be distributed to the R/3 back-end system. (To create a subscription, select the 'Subscription' object type in the 'Object type' selection list in transaction SMOEAC and then select the 'Object -> Create' function from the application menu or the corresponding symbol from the application function bar. The Subscription Wizard, which supports you during the creation of a new subscription, is started as a result.)
    b) Check to see whether the current CRM release has been maintained in the R/3 back-end system in the CRMPAROLTP table. This has to be taken into account in particular after an upgrade. You can maintain the CRMPAROLTP table in transaction SM30 in the R/3 back-end system:
                           Parameter name "CRM_RELEASE"
                           Param. value "30A"
    c) Event 00501014 must be activated in the R/3 back-end system so that the delta download of sales transactions from the R/3 back-end system to CRM works. The event must also be active for the upload of sales transactions from CRM to R/3.
    d) The event is activated automatically after a successful initial download. Call transaction R3AC4 ('Object Class Activation') in CRM and check whether the following entries exist:
                           Object class "BUSPROCESSND"
                           RFC destination <R/3 destination>
                           Select your entry and then choose 'Events by Object Class' (branch to the TBE31 table in the R/3 back-end system). The following entries must exist:
                           Event "00501014"
                           Obj. class "BUSPROCESSND"
                           Function "CRS_SALES_COLLECT_DATA"
                           If you do not see these entries, your initial download was not completed successfully.
    e) In transaction BD97 of your CRM system, the R/3 back-end system must have been maintained as the standard BAPI destination. Check the V_TBDLS view to see whether your R/3 back-end system has been defined as a logical system. A termination message in the SAPLCRM_ DISTRIBUTED_LOCKING program when you call a transaction in CRM indicates the missing destination assignment.
    Refer to notes 597812 and 674487. According to note 597812, the cross-system lock is processed using the RFC destination of the CRM middleware (SMOF_ERPSH table). However, the aforementioned entry in transaction BD97 for the Standard BAPI destination is still used to branch via the document flow to the R/3 system.
    f) In Release 3.1I, you can only have one entry for the RFCDEST field (RFC destination) in the CRMRFCPAR R/3 table.
    2. Definition of sales transaction-related Middleware parameters
    a) If you do not want a BOM explosion to occur for document items in CRM during the transfer to the R/3 back-end system, make the following settings in transaction R3AC6:
                           Key "R3A_SALES"
                           name "NOSTRUCTURE"
                           value "X"
                           This would make sense, for example, if you have already carried out a BOM explosion on the mobile client and if you do not want a new BOM explosion in the R/3 back-end system.
                           Make sure that the assigned item numbers in the sales transaction/sales document are set differently for main items and subitems so that no item numbers are assigned twice after the transfer and the BOM explosion in the R/3 System. The item numbers of the main items must be set identically in CRM and R/3. For more information, see note 496906.
                           Example:
                           CRM sales transaction
                           Pos.Nr.   Item No. Product
                           100 MAT1
                           200 MAT2
                           R/3 order
                           Pos.Nr.   Item No. Material
                           100 MAT1
                           101 Subitem1
                           102 Subitem2
                           103 Subitem3
                           104       ...
                           200 MAT2
                           You can maintain the item number assignment for the transaction types (CRM) or for the sales document types (R/3) in the Customizing.
    b) If a document is created in CRM and transferred to the R/3 back-end system, the warning messages of the transferred R/3 back-end document can also be displayed in the CRM document. In this way, you can recognize, for example, in the CRM document whether the transferred R/3 back-end document is incomplete and has to be postprocessed so that it can be further processed logistically. For this purpose, make the following settings in transaction R3AC6:
                           Key "R3A_SALES"
                           name "COLLECT_WARNINGS"
                           value "X"
    c) When you transfer a CRM document to R/3, you have the following control options with regard to pricing:
                           Key "R3A_SALES"
                           name "PRICINGTYPE"
                           value
                                             'B' = new pricing
                                             or
                                             'C' = copy manual pricecomponents,
                                             redetermine others
                                             or
                                             'G' = Copy price components unchanged,
                                             redetermine taxes (this value is
                                             delivered as a default setting)
    3. Definition of the R/3 dummy division in CRM
                  Note that no division exists in CRM in transactions at header level. In the R/3 order, however, the header division is a mandatory field. Thus, the R/3 dummy division must be maintained in CRM Customizing so that it can be determined during the transfer of a document. Otherwise, the order cannot be transferred to the R/3 back-end system.
                  Customizing path: 'Customer Relationship Management -> Master Data -> Organizational Management -> Division Settings -> Define Use of Division and Dummy Division'.
                  The use of several dummy divisions can be programmed in the CRM_DATAEXCH_AFTER_BAPI_FILL BAdI in the CRM_R3_SALESDOCUMENT_UPLOAD function module.
    Hints for the initial download
    Filter settings
    In transaction R3AC1, you set the filters for the initial/delta download of business objects. In the SALESDOCUMENT business object, you can set the filters for the order download from R/3 to CRM. For successful execution of the initial download, you have to set at least the VBAK-ERDAT filter criterion (document entry date) for the SALESDOCUMENT business object. This filter setting is required for the successful completion of order downloads.
    After you have completed these filter settings, you have to transfer these settings to the R/3 System. Select 'Filter sync.(R/3)'.
    Choose your R/3 System as a source site and check whether you are using the VBAK-ERDAT filter criterion:
    Example:
    Table/Structure Field OP Low
    VBAK ERDAT Greater than <Date>, for example, 20020128
    The date must be entered in the same form as it is stored on the database (YYYYMMDD)!
    The following filter criteria are also available:
    VBAK-AUART Sales document type
    VBAK-SPART Division
    VBAK-VBTYP Sales document category
    VBAK-VKORG Sales organization
    VBAK-VTWEG Distribution channel
    We recommend that you also use sales document numbers (VBAK-VBELN) as a further filter criterion. With this criterion, you can carry out an initial download according to sales document number intervals. The advantage of this filter criterion is that if your initial download terminates due to an error, you can restart the download after correcting the error as of the sales document number for which the error occurred. In this way you avoid having to restart a download for sales documents that have already been replicated.
    Example:
    Table/Structure   Field          OP            Low           High
    VBAK             VBELN          zwisch.        0005000000    0005099999
    Enter the field contents in the same way as it is stored on the R/3 database (leading zeros).
    If you want to use this filter criterion, go to transaction SM30 and make the following entry in the SMOFFILFLD table:
    Object name Table/Structure name Field name
    SALESDOCUMENT VBAK VBELN
    Note 497327 deals with possible filter-specific problems during the delta download that can occur due to missing R/3 back-end entries.
    Block size
    In this context, the block size specifies how many documents are selected in a transaction and transferred to CRM as a BDoc. The block size is defined on the system. The default value may have to be set to a lower value if problems occur (for example, memory overflow during the selection in the R/3 System). If the initial download terminates, check the dump log in the R/3 System (transaction ST22). The TIME_OUT or STORAGE_FREE_FAILED runtime errors indicate that the block size is too large. In this case, reduce the block size and restart the download.  In addition, you can clarify with your Basis Administration whether the rdisp/max_wprun_time kernel parameter is large enough (this avoids a TIME_OUT error).
    Basically, you should only download a few documents during the first download to check whether the system settings are correct. In this way, you can identify possible Customizing errors and correct them before the large load.
    Queue processing during the initial download
    In the case of very large transfer data sets, it may make sense to process the initial download in parallel within one object (object-internal parallel initial download) to complete the initial data transfer faster. Note 350176 describes the corresponding procedure.
    Queue processing during the upload/delta download
    Queues in CRM are defined in the SMOFQFIND table (for example, from CRM to CDB or from CRM to R/3).
    For the BUS_TRANS_MSG BDoc type, the default setting of the queue processing is that all orders for a customer are processed in one queue.
    As an alternative, you can set the queue processing in such a way that each order is processed in a separate queue. As a result, an individual order can no longer block the processing of other orders if an upload problem has occurred.
    If you prefer this queue processing, go to transaction SM30 and make the following change in the SMOFQFIND table:
    Select the BUS_TRANS_MSG BDoc type and change the segment field name from QUEUE_NAME to OBJECT_ID.
    In the same way, you can also set the queues for the delta download in the R/3 back-end system in such a way that each order is processed in a separate queue. If you prefer this queue processing, go to transaction SE16 in the R/3 back-end system and make the following change in the CRMQNAMES table:
    Select the entry for the SALESDOCUMENT object and change the BAPIFLD field from SOLD_TO to DOC_NUMBER (with BAPIOFFSET=3 and BAPIFLDLEN=10). Leave the second entry for the SALESDOCUMENT object (with QOBJPART=SAL_ERR) unchanged.
    In transaction SMQR, check to see whether the queues have been registered or check transaction SMQS to see whether the destinations have been registered because otherwise, the queues are not processed automatically, and this can lead to queue overloads.
    Check the queues regularly.
    Composite SAP Note 504090 covers all notes that solve known problems in the transfer as of Support Package 06 (SP06).
    Document cannot be maintained in online mode
    If you cannot maintain a document, this can have various reasons. Basically, a sales document entered in CRM is locked until the R/3 System has confirmed the update of the order successfully.
    If message CRM_ORDER019 "Document will be distributed - changes are not possible" occurs in CRM, check the queues (transaction SMQ1 and SMQ2). To analyze the data exchange from CRM to R/3, refer to note 431345.
    If message CRM_ORDER013 "Transaction &1 is being processed by user &2" occurs in CRM or if message V1042 "Sales document &1 is currently being processed (by user &2)" occurs in R/3, the document is processed in the other system respectively. To avoid inconsistencies, a cross-system lock is set during the processing of a replicated transaction so that the document cannot be processed simultaneously in two systems.
    Other notes
    Only error-free sales documents are distributed to the R/3 System. If, in R/3, you change a sales document that was originally created in CRM, these changes are not transferred to CRM. That is, you should always make the changes in the original CRM document to ensure the consistency of the document data in both systems. Sales documents entered in the R/3 System are transferred to CRM, but they are locked for processing there. Changes to a document created in R/3 are also transferred to CRM.
    In your settings for the data exchange, also make sure that the document number ranges correspond in both systems. For the successful sales document exchange between the systems, the transaction types and item categories have to be created in exactly the same way in both systems. If these objects do not exist in one system, you have to create them manually.
    In transaction CRMM_BUPA_MAP, you can determine into which R/3 customer number the CRM business partner is converted and vice versa. If you do not receive a conversion for the specified business partner here, this indicates that a transfer problem has not occurred in the sales document but during the business partner download.
    Header Data
    Release Status: Released for Customer
    Released on: 02.05.2006  15:04:13
    Priority: Recommendations/additional info
    Category: Consulting
    Primary Component: CRM-BTX-BF-IF R/3 Interface for Business Transactions

  • There was an error opening this document.  The file is damaged and could not be repaired.

    Good Day all
    When busy doing internet banking on www.absa.co.za and I try to print a confirmation, I get the following error message: "C:\Documents and Settings\%user profile%\Local Settings\Temporary Internet Files\Content.IE5\%folder name%\%file name%.pdf
    Could not open file.
    File not found."
    I've managed to locate the actual file that it's looking for, but when I try and open the file using either Adobe or Foxit Reader, I get the following error message: "There was an error opening this document. The file is damaged and could not be repaired."
    I've un-installed Adobe and installed version 9.1 for this particular user. This happened a while ago and then an un-installation and re-installation of Adobe solved the issue. This time, unfortunately, it didn't. I then un-installed Adobe and tried again, UNSUCCESSFULLY. So I loaded Foxit Reader, also without any success.
    If there's anyone out there who could possibly help, please do so... It's extremely urgent.
    Please find the errors attached as well.
    Regards,
    ME

    I contacted the company and they asked me to try using another browser, which I did... and using FireFox worked
    thanks for the help ʇɐb ɹəuəllıʍ
    cheers!

  • SSRS PDF Export. There was an error opening this document. This file is damaged and could not be repaired

    Hello,
    I just experienced this problem, and was able to successfully mitigate.  I wanted to share my experience and Solution. 
    The problem started with the following error after succesfully exporting a PDF Document.  "There was an error opening this document. This file is damaged and could not be repaired."
    This is only applicable if you can still export and open SSRS Reports to other formats. Go to the Log files of the SQL Instance. In my particular case I used the Default MSSQL instance:   C:\ Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting
    Services\LogFiles  
    The Folder will begin with MSRS (SRS is for SQL Reporting Services)
    Sort the files by date modified and check for the most recent log file: ex.  SQLDmpr0000.log  The 0000 will be the incremental amount of errors you have experienced in SRS. Check for the following error:
    "System.DllNotFoundException: Unable to load DLL 'T2Embed': Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"
    Below is a sample from the log. 
    reportrendering!ReportServer_0-1!1b78!02/07/2012-11:56:03:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: , Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException:
    An error occurred during rendering of the report. ---> Microsoft.ReportingServices.OnDemandReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.DllNotFoundException: Unable to load DLL 'T2Embed': Access
    is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
       at Microsoft.ReportingServices.Rendering.ImageRenderer.FontPackage.TTGetEmbeddingType(Win32DCSafeHandle hdc, UInt32& status)
       at Microsoft.ReportingServices.Rendering.ImageRenderer.FontPackage.CheckEmbeddingRights(Win32DCSafeHandle hdc)
       at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFWriter.ProcessFontForFontEmbedding(PDFFont pdfFont, Dictionary`2 embeddedFonts)
       at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFWriter.EndReport()
       at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFRenderer.Render(Report report, NameValueCollection deviceInfo, Hashtable renderProperties, CreateAndRegisterStream
    createAndRegisterStream)
       at Microsoft.ReportingServices.Rendering.ImageRenderer.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo,
    NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
       --- End of inner exception stack trace ---
       at Microsoft.ReportingServices.Rendering.ImageRenderer.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo,
    NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
       at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderFromOdpSnapshot(IRenderingExtension newRenderer, String streamName, ProcessingContext
    pc, RenderingContext rc)
       --- End of inner exception stack trace ---;
    If you notice the error states that T2Embed.dll access is denied. In my case this due to a hotfix installed by Microsoft: 
     MS11-087: Vulnerability in Windows kernel-mode drivers could allow remote code execution: December 13, 2011
    Be advised, in order to fix your problem and render pdf's, a vulnerability shall be created.
     To fix this issue and allow the export to PDF work correctly, you must give the system Read/Execute Permissions, and Built-in\Administrators Full Control. 
    Go to Windows\System32 and find the T2Embed.dll Go to Security and modify the permissions as listed above. Do the same to the T2Embed.dll in the SysWow64 folder.
    Restart Reporting Services and you will be able to export to PDF. 
    Best Wishes! 
    Mariano
    www.lucontech.com 

    I'm not convinced this is the exact cause of the issue.  I will check my log files to see if I find anything like what you described.  However, I get this error when a particular user tries to do a "print preview" from a custom button.  The
    code builds a ReportViewer object, sets the ReportPath, etc.
    The reason I'm not convinced is because we have a separate reports page that has the report viewer embedded into it.  If the user generates the report that way and exports to PDF, Word, etc...the user can generate the file and be on their way.  As
    soon as the user clicks our "Print" button on the page without the ReportViewer embedded, the above mentioned error occurs.  
    UPDATE: Perhaps we have a different problem since my issue is from a custom button.  I found the solution
    here and confirmed the solution with the customer.  It had to do with the code using Response.Flush() instead of Response.End().
    One thing I noticed before I implemented the change: When you would close the PDF, it would ask you to save changes to the PDF.  After implementing Response.End() instead, that prompt went away.  No doubt it has to do with the differences between
    how Response.Flush() and Response.End() handle the stream returned.
    Anyway, posting in case someone has the same issue.

  • Adobe pdf problem; the message comes up:- There was an error opening this document. The file is damaged and could not be repaired.

    Dear all
    I have got  3 mac computers. 2011 13 inch air, 27 inch mac and 2010 pro. latest softwares. all of them have a problem in opening pdf files;esp older files. the error message comes up 'There was an error opening this document. The file is damaged and could not be repaired.'
    I have reinstalled reader, checked software updates etc.
    Any help will be appreciated

    It isn't likely to be a problem with the software. You have two different applications which have no interaction between them, neither of which can open the same group of files on three different systems. It's possible that one application has a problem, but not both or that one system has a problem, but not all three. Typically if there were software corruption, it would not show as a failure to open a specific type of file, but in opening and running the application itself.
    I realise that that doesn't really help you since it doesn't resolve the poblem, but I think you need to start with a known-good pdf, preferably one you can download from an internet source, and see whether that opens. If it does, then it would confirm that the software is working properly.
    For a known-good PDF to download, try one of the manuals from the support site here.

  • Error in invoice posting from CRM to ECC

    Dear Guru's ,
    when we release the billing document from CRM to ECC , system throughs error messages and while we checking the confimation the below  green message is appering .
    --> Object link not known in CO
    Whatever the master data  we maintained in the order and confimation is perfect .Kindly advise why this green error is coming???
    Regards ,
    Pakalapati

    solved by my self

  • "No connectivity with the server" error for one document but not the other, in the same document library

    We have a number of users all of a sudden getting "No connectivity with the server.  The file 'xxx' can't be opened because the server couldn't be contacted." errors trying to open MS Office docs (Word, Excel, etc.) in SharePoint with IE,
    just by clicking the link and selecting the "Read Only" option.  If they select the "Check Out and Edit" option, they can open the document no problem.  One of my customers gets the error on one document but not the other, in
    the same document library!  The older document (a weekly report) was copied and renamed as per standard procedure.  She can read the older document, but not the new one.
    It is definitely a profile issue, as other people have logged onto the machines of the users with problems and do not get the error.  We have also renamed people's c:\user profile folders and the corresponding Profilelist registry entry and the newly
    created profile does not experience the error for these people.  Renaming the profile back restores all their personal settings but the error reappears.  When we copied the old profile's folder structure into the new profile, many of the user settings
    were restored (but not all, like Dreamweaver settings) but the error did not appear.  We think that the system folders files (like AppData) weren't totally copied over so we're going to run another test using xcopy.  We are rebooting between
    logons to make sure all files are unlocked.
    The laptops and computers are mainly 32bit, Win7 Enterprise running IE9 and Office 2010 Professional Plus, but there's a few 64bit machines as well. The SharePoint farm has 1 WFE, 1 App Server running search and CA, and a shared database server running SQL
    2005 SP4.  SharePoint is 64bit MOSS 2007 with the latest CU.
    We've checked the logs on the client as well as on the server and there aren't any helpful entries.  We've also run Process Monitor, also with no helpful entries.  We're planning to run something like Fiddler next.
    It's not everyone, because there are many people are accessing the SharePoint system and the same files.  It is also not a permission thing, as we've tested by giving the users elevated permissions with no changes.  One person experiencing
    the errors is a Site Collection Admin.  That same person ran a test where I coped a simple Excel file into a Document Library which contained a problem file.  They were able to open it Read Only no problems that day, but the next day, the same
    file gave them an error.   In their case, they usually get a "xxx is not checked out" error and only occasionally get the "No connectivity with the server" error.
    We've tried lots of things including:
    Deleting IE cache
    Deleting SharePoint Drafts and webcache folder contents
    Running IE without add-ons
    Upgrading and Downgrading IE
    Uninstalling and re-installing IE
    Reinstalling our SSL certs
    Repairing Office
    Removing and then adding back in the Microsoft Office "Microsoft SharePoint Foundation Support" Office Tool 
    Deleting all HKLM and HKLU Office registry settings
    Toggling IE Compatibility Settings
    Toggling the IE Automatic Logon option
    Toggling the location of checked out files
    Adding the site in the trusted sites list
    Adding the site to the WebClient\Parameters registry locations
    Making sure the WebClient service is started
    Rebooting the machine (lol :)
    This is becoming a serious issue, not just because of the inconvenience for the users having to check out every document they want to read, but we have some files with macros that open up other documents to run which are now failing.  There aren't
    "check out" workarounds for some of those macros.
    We're planning to open a ticket with Microsoft, but I'm throwing it out here first in case someone has run into this before, or may have some suggestions on what to try next.  Thanks!
    -Richard.
    PS  I think this needs to be in the "General" forum instead?

    It took three days of dedicated troubleshooting, but I have found the cause of the errors, and a couple of fixes.  It helped tremendously that my own machine was throwing the error.  I have scheduled a couple of users to work with me to test the
    various fixes, to see which one works best, so the story isn't over yet.
    I had backed up my c:\users profile folder and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList registry key so I could restore my profile after I was done.  I made a copy of the profile folder and was using that for awhile,
    but then made another copy where I had deleted a lot of content out of it so that the copies would go faster.  Since a newly created profile did not have errors, I was trying to copy back as much of the profile as possible to make it easier for our users
    to get back to work.  Instead of blowing away their profile and starting from scratch (which we know worked) I wanted to narrow down what was causing the error and just skip that from the restore.  The concept was to keep as much as the users profile
    in tact (application settings, etc.) not just restoring their desktop and My Documents folders.
    When we first tested a few weeks ago, simply copying the folder contents didn't reproduce the error.  I then tried xcopy, but got the "can't read file" error.  Then I tried robocopy, and ran into the "junction" problem. 
    I went back to xcopy, and found that placing the excludes.txt file in the windows/system32 folder eliminated the error.
    So the process went as follows: 
    Reboot and log into the machine as another user
    Delete the profile and associated registry key
    Reboot and log into the machine as the affected user, creating a new profile, and there is no error
    Reboot and log in as the other user
    xcopy the contents of the skinned-down backed-up profile to the newly created profile
    Reboot and log in as the affected user, and the error occurs
    Repeat the above, but add items in the excludes.txt file to see what, when eliminated, causes the error not to appear in the last step
    I eventually found that skipping the c:\users\<profile folder>\appdata\local\Microsoft\office\14.0 folder allowed the entire profile to be copied over without the error occurring.  That was strange, because we've cleaned out the cache folders
    before which didn't fix the issue. 
    So I went about it the opposite way, and tried to delete the 14.0 folder from the restored profile, and after reboot, the error still occurred.
    What eventually worked was deleting the 14.0 folder and copying over a 14.0 folder from a newly created profile!
    One way to do this was to:
    Reboot and log in as another user
    Rename the c:\users profile folder
    Rename the appropriate [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList] registry key
    Reboot and log in as the affected user, confirm that there is no error
    Reboot and log in as the other user
    Copy the C:\Users\<profile folder>\AppData\Local\microsoft\Office\14.0 folder to the other user's desktop
    Delete new profile folder, and rename the backup to be the production folder
    Delete the C:\Users\<profile folder>\AppData\Local\microsoft\Office\14.0 folder and then paste the 14.0 copy from the desktop
    Reboot and log in as the affected user, confirm that there is no error
    We've tried this on a couple machines and it works.  I had to run Windows Explorer as Administrator to access the other profile's folders.
    We've also successfully copied a 14.0 folder created by one profile on one affected computer over another profile's folder on another computer, eliminating the error, so we're trying that first, as that is fewer steps.
    We may attempt to script this, but the self-help instructions are only 5 lines long:
    Reboot and log into the affected computer with another account
    Go to <link to location of 14.0 folder on network> and copy the 14.0 folder
    Run Windows Explorer as Administrator
    Go to c:\users\<profile folder>\appdata\local\microsoft\office and delete the 14.0 folder, and paste the copied 14.0 folder (trying to overwrite it makes Win7 want to merge the folders)
    Reboot and log into your normal account, and confirm the error is gone
    I'll come back and report after we go into the field with this fix, but after the few tests, I am cautiously optimistic that this is it.

  • To create follow up : Service Confirmation document

    Hi Experts,
    My requirement is to create a Service Confirmation document as a follow up document of an existing service order. Kindly let me know about the procedure and information regarding mandatory fields that i need to pass from Serivce Order to the Service confirmation document.  Also the information about some standard fields that needs to populate while creating the Confirmation document.
    Will definetly rewards points for useful answers !!
    Thanks,
    Sunil

    Hi sunil,
    Configure the following steps in SPRO
    1.Create Ztransaction types(SRVO,SRVC) and Z item catogories(SRVP,SRVM,SVCP,SVCM) by copying std Tx types  and Item catogories
    Path: IMG-> CRM-> Transactions -> Basic Settings ->Define transaction types
    --> Define item catogories
    2.Maintain the copying control for the above transactions as source and target transactions.
    Path: IMG-> CRM-> Transactions -> Basic Settings -> Copying cotrol for Business Transactions -->Define Copying cotrol for transaction types.
    3.Define the Item categories and maintain the copying control
    for copying use the std item categories
    For Service Order
    Service Product Item  SRVP
    Service Material Item  SRVM
    For Service Confirmation
    Service Product Item confirmation SVCP
    Service Material Item Confirmation SVCM
    Path: IMG-> CRM-> Transactions -> Basic Settings -> Copying cotrol for Business Transactions -->Define Copying cotrol for Item catogories
    4.Maintain Item catogory determination when copying
    Maintain as follows( use zcatogory and ztransaction which are created)
    Source catogory; Target Tx type ; Item Cat.By
    SRVP ;                    SRVC   ;               SVCP
    SRVM ;                    SRVC   ;               SVCM
    Path: Path: IMG-> CRM-> Transactions -> Basic Settings -> Copying cotrol for Business Transactions -->Define Item Category determination when copying
    I hope the above will helpful to you.
    Let me know if you have any difficulties.
    Reward points if it is helpful.
    Regards,
    Madhu

  • Bapi-salesorder creation error in  creating document

    hai friends..
      iam doing creation of sales order using bapi .-structures..
      but error in creating doucment ....
    can u send me some example .. abt sales order .creation ..
    once u check my code ...
    DATA: BEGIN OF HEADER OCCURS 0,
           VBELN LIKE BAPIVBELN-VBELN,
           AUART LIKE VBAK-AUART,
           VKORG LIKE VBAK-VKORG,
           VTWEG LIKE VBAK-VTWEG ,
           SPART LIKE VBAK-SPART,
           VKBUR LIKE VBAK-VKBUR,
           KUNNR LIKE BAPIPARNR-PARTN_NUMB ,"vbak-kunnr,
        END OF HEADER.
    DATA: BEGIN OF ITEM OCCURS 0,
           VBELN LIKE BAPIVBELN-VBELN,
           POSNR LIKE BAPISDITM-ITM_NUMBER ,"vbap-posnr,
           MATNR LIKE VBAP-MATNR,
          NETWR LIKE VBAP-NETWR,
           KWMENGE LIKE VBAP-KWMENG,
          WERKS LIKE VBAP-WERKS,
          NETPR LIKE VBAP-NETPR,
       END OF ITEM.
    DATA:  ORDER_HEADER_IN LIKE BAPISDHD1,
           ORDER_HEADER_INX LIKE BAPISDHD1X.
    DATA: ITAB_HEAD likE order_header_in,
          ITAB_HEADX likE ORDER_HEADER_INX.
    DATA: ITAB_ITEM  TYPE STANDARD TABLE OF  BAPISDITM WITH HEADER LINE,
          ITAB_ITEMX TYPE STANDARD TABLE OF  BAPISDITMX WITH HEADER LINE.
    DATA: KUST TYPE STANDARD TABLE OF  BAPIPARNR WITH HEADER LINE,
           RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
    DATA: VNO  LIKE BAPIVBELN-VBELN,
          VCNT LIKE VBAP-POSNR.
    LOOP AT HEADER.
        VCNT = 10.
        CLEAR ITAB_HEAD.
       ORDER_HEADER_IN-REFOBJTYPE = 'OR'.
       ORDER_HEADER_IN-REFOBJKEY = 'OR'.
       ORDER_HEADER_IN-REFDOCTYPE = 'OR'.
       ORDER_HEADER_IN-DOC_TYPE = HEADER-AUART.
        ITAB_HEAD-DOC_TYPE = HEADER-AUART.
        ITAB_HEAD-SALES_ORG = HEADER-VKORG.
        ITAB_HEAD-DISTR_CHAN = HEADER-VTWEG.
        ITAB_HEAD-DIVISION = HEADER-SPART.
        ITAB_HEAD-SALES_OFF = HEADER-VKBUR.
        KUST-PARTN_NUMB = HEADER-KUNNR.
         ITAB_HEADX-DOC_TYPE = 'X'.
         ITAB_HEADX-SALES_ORG = 'X'.
        ITAB_HEADX-DISTR_CHAN = 'X'.
        ITAB_HEADX-DIVISION = 'X'.
        ITAB_HEADX-SALES_OFF = 'X'.
        LOOP AT ITEM WHERE VBELN = HEADER-VBELN.
          REFRESH RETURN.
          ITAB_ITEM-ITM_NUMBER = VCNT.
          ITAB_ITEM-MATERIAL = ITEM-MATNR.
          ITAB_ITEM-NET_WEIGHT = ITEM-KWMENGE.
          APPEND ITAB_ITEM.
          ITAB_ITEMX-ITM_NUMBER = VCNT.
          ITAB_ITEMX-MATERIAL = 'X'.
          ITAB_ITEMX-NET_WEIGHT = 'X'.
          APPEND ITAB_ITEMX.
          VCNT  = VCNT + 10 .
        ENDLOOP.
        CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
          EXPORTING
        SALESDOCUMENTIN               = SALESORDER
            ORDER_HEADER_IN              = ITAB_HEAD
         ORDER_HEADER_INX              = ITAB_HEADX
        SENDER                        =
        BINARY_RELATIONSHIPTYPE       =
        INT_NUMBER_ASSIGNMENT         =
        BEHAVE_WHEN_ERROR             =
        LOGIC_SWITCH                  =
        TESTRUN                       =
        CONVERT                       = ' '
         IMPORTING
           SALESDOCUMENT                 = VNO
          TABLES
           RETURN                        = RETURN
           ORDER_ITEMS_IN                = ITAB_ITEM
           ORDER_ITEMS_INX               = ITAB_ITEMX
            ORDER_PARTNERS                = KUST.
       CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
            EXPORTING
              WAIT          = 'X'.
             IMPORTING
               RETURN        = RETURN.
    LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
    ENDLOOP.
    IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
    ELSE.
    COMMIT WORK AND WAIT.
    ENDIF.
        WRITE: / '   Sales Order NO  IS: ', VNO.
        WRITE: / SPACE.
        CLEAR VNO.
        WRITE SY-ULINE.
      ENDLOOP.
    my HEader  is    123    OR  1000 30 10 SATYA.
    ITem  2  IS     123   10  HAI   15
    once u check it ......

    Hi Satya,
    just check this
    REPORT  Z_STANDARD_SALES_ORDER no standard page heading.
    DATA DECLARATION
    CONSTANTS : C_X VALUE 'X'.
    Structures to hold Sales order header data
    DATA : HEADER LIKE BAPISDHD1," OCCURS 0 WITH HEADER LINE,
           HEADERX LIKE BAPISDHD1X." OCCURS 0 WITH HEADER LINE.
    Internal Tables to hold Sales order ITEM DATA
    DATA : ITEM LIKE BAPISDITM OCCURS 0 WITH HEADER LINE,
           ITEMX LIKE BAPISDITMX OCCURS 0 WITH HEADER LINE.
    Internal Tables to hold Partners ITEM DATA
    DATA : PART LIKE BAPIPARNR OCCURS 0 WITH HEADER LINE.
    Internal Tables to hold Partners SCHEDULE DATA
    DATA: SCHEDULE LIKE BAPISCHDL OCCURS 0 WITH HEADER LINE,
          SCHEDULEX LIKE BAPISCHDLX OCCURS 0 WITH HEADER LINE.
    Internal table to hold messages from BAPI call
    DATA: RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
    DATA  W_MSG(150).
    *DATA: begin of wa_MESSAGE,
         message(150),
         end of wa_message.
    *DATA: itab_msg like table of wa_message with header line.
    Data: Begin of Record occurs 0,
          Control type i,
          DOC_TYPE like HEADER-DOC_TYPE,
          SALES_ORG like HEADER-SALES_ORG,
          DISTR_CHAN like HEADER-SALES_ORG,
          DIVISION like HEADER-DIVISION,
          PURCH_NO_C like HEADER-PURCH_NO_C,
          PARTN_NUMB like PART-PARTN_NUMB ,
          PARTN_ROLE like PART-PARTN_ROLE ,
          ITM_NUMBER like ITEM-ITM_NUMBER,
          MATERIAL like ITEM-MATERIAL,
         TARGET_QTY like item-TARGET_QTY,
          REQ_QTY LIKE BAPISCHDL-REQ_QTY,
          TARGET_QU like item-TARGET_QU,
          PLANT like ITEM-PLANT,
          PMNTTRMS like header-PMNTTRMS,
          End of record.
    data: itab like ALSMEX_TABLINE occurs 0,
          wa like ALSMEX_TABLINE.
    data: SO like BAPIVBELN-VBELN.
    Selection Screen
    selection-screen begin of block b1 with frame title text-001.
    PARAMETERS: P_FILE LIKE RLGRAP-FILENAME OBLIGATORY.
    selection-screen end of block b1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
      PERFORM GET_FILE USING P_FILE.
    Start of Selection
    start-of-selection.
      DATA: xl type string.
      xl = '*.xls'.
      IF not P_FILE CP xl.
        Message 'Wrong input file format' type 'E'.
      ENDIF.
      CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
        EXPORTING
          FILENAME                      = P_FILE
          I_BEGIN_COL                   = 1
          I_BEGIN_ROW                   = 1
          I_END_COL                     = 13
          I_END_ROW                     = 3000
        TABLES
          INTERN                        = itab
    EXCEPTIONS
      INCONSISTENT_PARAMETERS       = 1
      UPLOAD_OLE                    = 2
      OTHERS                        = 3
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    DATA POPULATION
      loop at itab into wa.
        if wa-col = '0001'.
          record-Control = wa-value.
        elseif wa-col = '0002'.
          record-DOC_TYPE = wa-value.
        elseif wa-col = '0003'.
          record-SALES_ORG = wa-value.
        elseif wa-col = '0004'.
          record-DISTR_CHAN = wa-value.
        elseif wa-col = '0005'.
          record-DIVISION = wa-value.
        elseif wa-col = '0006'.
          record-PURCH_NO_C = wa-value.
        elseif wa-col = '0007'.
          record-PARTN_NUMB = wa-value.
        elseif wa-col = '0008'.
          record-PARTN_ROLE = wa-value.
        elseif wa-col = '0009'.
          record-PMNTTRMS = wa-value.
        elseif wa-col = '0010'.
          record-ITM_NUMBER = wa-value.
        elseif wa-col = '0011'.
          record-MATERIAL = wa-value.
        elseif wa-col = '0012'.
          record-REQ_QTY = wa-value.
        elseif wa-col = '0013'.
          record-TARGET_QU = wa-value.
        elseif wa-col = '0014'.
          record-PLANT = wa-value.
        endif.
        AT END OF row.
          APPEND record.
          CLEAR: wa, record.
        ENDAT.
      endloop.
      DATA: tot_lines type i,
            tot_po type i,
            index type i.
      describe table record lines tot_lines.
      read table record index tot_lines.
      tot_po = record-control.
      DO tot_po times.
        index = index + 1.
        clear: HEADER,HEADERX,ITEM[],ITEMX[],RETURN,RETURN[],SCHEDULE[],SCHEDULEX[], PART[],PART.
        refresh: ITEM[],ITEMX[],RETURN[],SCHEDULE[],SCHEDULEX[],PART[] .
    POPULATE HEADER FLAG.
        HEADERX-UPDATEFLAG = c_x.
        HEADERX-doc_type = c_x.
        HEADERX-SALES_ORG = c_x.
        HEADERX-DISTR_CHAN = c_x.
        HEADERX-DIVISION = c_x.
        HEADERX-PURCH_NO_C = c_X.
        HEADERX-PMNTTRMS = c_X.
        loop at record where control = index.
    POPULATE HEADER DATA FOR PO
          HEADER-DOC_TYPE = record-DOC_TYPE.
          HEADER-SALES_ORG = record-SALES_ORG.
          HEADER-DISTR_CHAN = record-DISTR_CHAN.
          HEADER-DIVISION = record-DIVISION.
          HEADER-PURCH_NO_C = record-PURCH_NO_C.
          HEADER-PMNTTRMS = record-PMNTTRMS.
    *POPULATE ITEM DATA.
          ITEM-ITM_NUMBER = record-ITM_NUMBER.
          ITEM-MATERIAL = record-material.
         ITEM-TARGET_QTY = record-TARGET_QTY.
          ITEM-TARGET_QU = record-TARGET_QU.
          ITEM-PLANT  = record-PLANT .
          APPEND ITEM.
    *POPULATE ITEM FLAG TABLE
          ITEMX-ITM_NUMBER = record-ITM_NUMBER.
          ITEMX-UPDATEFLAG = C_X.
         ITEMX-TARGET_QTY = C_X.
          ITEMX-PLANT = C_X .
          ITEMX-MATERIAL = C_X .
          ITEMX-TARGET_QU = C_X .
          APPEND ITEMX.
    *POPULATE SCHEDULE  TABLE
          SCHEDULE-ITM_NUMBER = RECORD-ITM_NUMBER.
          SCHEDULE-REQ_QTY = RECORD-REQ_QTY.
          APPEND SCHEDULE.
    *POPULATE SCHEDULE  TABLE
          SCHEDULEX-ITM_NUMBER = RECORD-ITM_NUMBER.
          SCHEDULEX-REQ_QTY = C_X.
          APPEND SCHEDULEX.
        endloop.
    *POPULATE PARTNER  TABLE
        PART-PARTN_NUMB = record-PARTN_NUMB.
        PART-PARTN_ROLE = record-PARTN_ROLE.
        APPEND PART.
    *BAPI CALL
        CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
              EXPORTING
               ORDER_HEADER_IN               = HEADER
               ORDER_HEADER_INX              = HEADERX
      SENDER                        =
      BINARY_RELATIONSHIPTYPE       =
      INT_NUMBER_ASSIGNMENT         =
      BEHAVE_WHEN_ERROR             =
      LOGIC_SWITCH                  =
      TESTRUN                       =
      CONVERT                       = ' '
              IMPORTING
               SALESDOCUMENT                 = SO
              TABLES
               RETURN                        = RETURN
               ORDER_ITEMS_IN                = ITEM
               ORDER_ITEMS_INX               = ITEMX
               ORDER_PARTNERS                = PART
               ORDER_SCHEDULES_IN            = SCHEDULE
               ORDER_SCHEDULES_INX           = SCHEDULEX
      ORDER_CONDITIONS_IN           =
      ORDER_CONDITIONS_INX          =
      ORDER_CFGS_REF                =
      ORDER_CFGS_INST               =
      ORDER_CFGS_PART_OF            =
      ORDER_CFGS_VALUE              =
      ORDER_CFGS_BLOB               =
      ORDER_CFGS_VK                 =
      ORDER_CFGS_REFINST            =
      ORDER_CCARD                   =
      ORDER_TEXT                    =
      ORDER_KEYS                    =
      EXTENSIONIN                   =
      PARTNERADDRESSES              =
        loop at return where type = 'E' and ID NE 'MEPO' and ID NE 'BAPI'.
          WRITE:/ Return-message.
        endloop.
    *Confirm the document creation by calling database COMMIT
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            WAIT = 'X'.
    *Messages
        loop at return where type = 'S' and number ne '233'.
         WRITE:/ Return-message.
          CALL FUNCTION 'FORMAT_MESSAGE'
            EXPORTING
              ID        = return-ID
              LANG      = SY-LANGU
              NO        = return-NUMBER
            IMPORTING
              MSG       = W_MSG
            EXCEPTIONS
              NOT_FOUND = 1
              OTHERS    = 2.
          WRITE W_MSG.
         itab_msg-message = w_msg.
         append itab_msg.
          clear: W_MSG.
        ENDLOOP.
      enddo.
         -->P_W_FILE  text
    FORM GET_FILE  USING    P_W_FILE.
      CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
        CHANGING
          FILE_NAME     = P_W_FILE
        EXCEPTIONS
          MASK_TOO_LONG = 1
          OTHERS        = 2.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.     "GET_FILE
    Regards,
    Sachin

  • Batch Number on Confirmation Document

    Hi Experts!
    I have a problem with posting an confirmation document in SRM 5.0 (Extended Classic). I try to post Confirmation in SRM in relation to PO for a material that has in ERP indictator batch management checked, but I get the error message: "Enter a batch". The problem is that I don't see such a field in SRM confirmation....
    Please help.
    Regards
    RafaD

    Can it be possible that the standard field is hidden? As I see in screens related to confirmation transaction I see that there is a GS_CFITEM-BE_BATCH field to enter the batch number:
    PACKAGE BBP_CF
    SCREEN 5000 - Item: Basic Data
    FIELD - GS_CFITEM-BE_BATCH
    But when you execute trx for confirmation and you go to Item details and tab Basic Data field "Batch" is not available (in fact not only batch field - screen 5000 has much more fields than It's visible in basic data tab)
    It seems that I need to somehow unhide this field. Do you have any idea what is the best way to achieve that?
    Regards
    RafaD

  • Error when creating document flow for delivery

    Hi,
    I would like to post the GR for Inbound delivery. I receive an error the TO is not confirmed. I have tried to confirm the tranfer order and I receive the "error when creating document flow for delivery . In order to avoid inconsistencies the goods movement posting was cancelled." It seems like the document already exist.
    How can I do to confirm the TO and post the GR.
    Thanks
    Dede

    In Inbound delivery after GR only a TO is created and confirmed.
    So please check the PO history and see a GR is there or not .
    Once a GR is found create a TO and do the confirmation

  • Error while saving Adobrforms: There was a error reading the document(26)

    Hello,
    Am not able to save the pdf form.
    Error : "The document could not be saved.There was a error reading the document(26)."
    Can anyone please tell me why i am getting this error.
    Thanks,
    satheesh

    Hi Satheesh,
    Can you give more details about your scenario..
    Regards,
    Ravi

  • When I attempt to open a PDF file I saved from a website, I get the message "There was an error opening this document. The file is damaged and could not be repaired." Is there any way to correct this problem?

    When I attempt to open a PDF file I saved from a website using Safari, I get the message "There was an error opening this document. The file is damaged and could not be repaired." When I save the same PDF file using FireFox it opens up immediately. Is there any way to correct this problem with Safari?

    Back up all data.
    Triple-click the line of text below to select it, the copy the selected text to the Clipboard (command-C):
    /Library/Internet Plug-ins
    In the Finder, select
    Go ▹ Go to Folder
    from the menu bar, or press the key combination shift-command-G. Paste into the text box that opens (command-V), then press return.
    From the folder that opens, remove any items that have the letters “PDF” in the name. You may be prompted for your login password. Then quit and relaunch Safari, and test.
    The "Silverlight" web plugin distributed by Microsoft can also interfere with PDF display in Safari, so you may need to remove it as well, if it's present.
    If you still have the issue, repeat with this line:
    ~/Library/Internet Plug-ins
    If you don’t like the results of this procedure, restore the items from the backup you made before you started. Relaunch Safari again.

Maybe you are looking for

  • PR not generated when multiple lines added to work order

    Hello Guys, I am facing issues when I tried to add multiple non stock components to generate PR. I have added around 20 non stock components with "N" as item category along with text description only ( Component field was blank). When I save the WO,

  • PROBLEM IN ACTIVATION OF A CLASS WHICH IS COPIED FROM STD CLASS

    Hi All,          I have a problem in activating a class which is copied from the standard class. std class: CL_GUI_FRONTEND_SERVICES The class has got some protected methods and attributes. here i'm getting following error whenever i try to activate

  • [SOLVED] Missing kdelibs 4.10.2 for i686

    ..And after the upgrade everything kde related crashes... just an example systemsettings(5077) SettingsBase::initApplication: "View load error: The plugin 'classic_mode' uses an incompatible KDE library (4.10.2)." systemsettings(5077) SettingsBase::i

  • *** Some incoming/outgoing emails have garbled text it it...

    I sent out an email yesterday and the recipient called me to let me know that the message looked like garbage because there were punctuation marks (question marks, parentheses, etc.) in the body of the email and I didn't put them there. I've also not

  • XDO Delivery_Throwing an error in r12

    Dear Team, We are having an issue in our R12 applications.When we send Separate Remittance Advice we are getting an error like... Loaded email attachment file prefix from DB: Message { Code = IBY_FD_EMAIL_ATT_PRE, Cause = Payment} Preparing for email