PO with Archived status

Hi,
we are having  many POs with status 'Archived'. Any one tell me of what this status is for ? And how to resolve it ?
many POs we have received today with this status and please suggest me.
Thank you very much.
Regards, Sunayana N

Hi,
we have the following situation with "archived status":
-No Archiving has been aktivated.
- For direct material we create a RESERVERTION as follow-on documents in ERP in case stock is available.
- But when saving the SC in SRM the status of follow-on document is archived reservation.
- Mentioned reservation is definitly not available in ERP.
Did you solve the erronous message of the SRM-System in ´this issue?
Thanks
Isam

Similar Messages

  • "The request failed with HTTP status 401: Unauthorized"

    Hi,
    I'm trying to get both RSS feeds and SSRS reports on a web application which is having NTLM authentication without Kerberos. The catch is proxy setting, if I give <proxy autoDetect="false" /> in web.config of my sharepoint web
    application SSRS reports will be rendered in SQL Server Report viewer perfectly (I deploy using BIDS), but RSS viewer webpart will not display my internet feeds. If I give
    <proxy autoDetect="true" /> RSS feeds are displayed properly but SSRS report will throw the following error.
    The request failed with HTTP status 401: Unauthorized.
    Description:
    An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
    Exception Details: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
    Source Error:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
    Stack Trace:
    [WebException: The request failed with HTTP status 401: Unauthorized.]
    System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) +412862
    System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) +300
    Microsoft.SqlServer.ReportingServices2005.Execution.ReportExecutionService.ListRenderingExtensions() +53
    Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.ListRenderingExtensions() +207
    Microsoft.Reporting.WebForms.ServerReport.ListRenderingExtensions() +130
    Microsoft.ReportingServices.SharePoint.UI.WebParts.ActionMenu.OnPreRender(EventArgs e) +180
    System.Web.UI.Control.PreRenderRecursiveInternal() +108
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Control.PreRenderRecursiveInternal() +224
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3394
    I tried to work around this by adding proxy settings with bypass list.
    <system.net>
        <defaultProxy useDefaultCredentials="true">
          <proxy proxyaddress="http://<proxy IP address>:<port>" bypassonlocal="true" usesystemdefault="true" />
          <bypasslist>
      <add address="<my report server>" />
      <add address="http://<report server>:8080/reportserver/" /> 
      <add address="<IP of my report server>" />
          </bypasslist>
        </defaultProxy>
    </system.net>
    This makes RSS feed to work but SSRS throw the above error. I would need some advice from Microsoft on how to fix this.
    Note: My sharepoint site cannot be anonymous. I have just once service account that runs sql server service, report service, sharepoint services etc. This account is local admin on all servers, has highest access on sql box, run SSRS web service and app
    pools, etc.
    I have four servers, 2 WFE in windows load balanced, 1 app server (running Central admin and report service in sharepoint integrated mode), 1 db server hosting all content and config dbs and report server db.
    Regards,
    Manoj
    Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3618

    Hi,
    Thanks to share your post.
    For the issue,
    do you mean that the error happen with the use of NTLM authentication without Kerberos? If yes, the possible cause should be the lacking of Kerberos.
     My suggestion is to implement the Kerberos authentication in your environment. You may check it and test it. For the detailed steps of implementing of the Kerberos:
    http://blogs.msdn.com/b/martinkearn/archive/2007/04/23/configuring-kerberos-for-sharepoint-2007-part-1-base-configuration-for-sharepoint.aspx.
    http://blogs.msdn.com/b/james_world/archive/2007/08/20/essential-guide-to-kerberos-in-sharepoint.aspx.
    Hope this could help you!
    Leo

  • SSRS 2012 - The request failed with HTTP status 401: Unauthorized.

    I have SSRS Reporting Services 2012 load balanced on two servers. 
    Both servers are running Windows Server 2012 R2.
    I have a Web Application that renders reports by utilizing this SSRS Reporting Services 2012. 
    When the application generates a report using load balancing I get error the message, “The request failed with HTTP status 401: Unauthorized.”
    However, using only one reporting server, the application is able to render the report just fine. 
    It seems that when the requests are shared between the servers the problem occurs.
    One solution is to configure Load Balancing with “Source IP” persistence. 
    This seems to work.  I believe this is a “sticky” session. 
    With this Load Balancing configuration, the application can render the report just fine. 
    (However, I have not done complete testing.)
    The problem occurs when calling the service ListChildren(string, bool ) on SSRS. 
    I have been researching online.  I tried modifying the registry on the servers based on online articles (see below.)
    Here are some articles I have looked at.
    http://msdn.microsoft.com/en-us/library/cc281307(v=sql.110).aspx
    http://blogs.msdn.com/b/lukaszp/archive/2008/07/18/reporting-services-http-401-unauthorized-host-headers-require-your-attention.aspx
    http://blogs.msdn.com/b/lukaszp/archive/2008/07/18/reporting-services-http-401-unauthorized-host-headers-require-your-attention.aspx
    Is there a better solution?  Will Load Balancing with “Source IP” persistence be an acceptable solution?  Is there a patch needed for the servers or SSRS?  Please let me know.

    Hi GoGladiator,
    Generally, "The request failed with HTTP status 401: Unauthorized" occurs when
    The service account used to connect to the Report Server is not authorized.
    The Reporting Services is configured to use Kerberos, however, we didn't register Service Principal Name (SPN) for the account the Reporting Services is running under.
    So, to fix this issue, we can refer to the follow steps:
    Make sure the user is able to connect to the Report Server.
    If using Kerberos authentication, please make sure SPN is configured correctly. If using Kerberos authentication, please make sure SPN is configured correctly.
    For more information about Kerberos Authentication and how to register SPN for a report server in Reporting Services, please see the articles below:
    Configure Windows Authentication on the Report Server
    Register a Service Principal Name (SPN) for a Report Server
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • SQL Server Reporting Service 2008 R2 - The request failed with HTTP status 401: Unauthorized.

    I got the error "The request failed with HTTP status 401: Unauthorized." when I call the Reporting Service Web Service.
    The code is very simple:
    // Initialise the reporting service Web Service
    this.RSWebService = new ReportingService2010();
    // Pass windos authentication credentials to Web Service
    this.RSWebService.Credentials = System.Net.CredentialCache.DefaultCredentials;
    // List children
    List<CatalogItem> reports = this.RSWebService.ListChildren(folder, false).ToList();
    The SQL Server is installed on a different machine (say server A) from the Web server (say server B). We are using Windows Server 2003.
    The code work fine for all the scenario below:
    i) Run locally (XP) to call the web service on the sql server
    ii) Provide the Network Credentials with the username, password, and domain when calling the web service
    iii) If the web server and sql server is using same server (i.e. not distributed)
    I'm using windows authentication and impersonation. Any idea?

    Hi Raymond,
    If I understand correctly, the issue only happens in the environment that the web server is different with the SQL Server Reporting Services server. This means the web server is a remote server of the Report Server. Windows Integrated authentication is used
    in this case. When running the web page, the 401 error occurs.
    If so, it is actually a double hop issue. The double-hop problem will usually only be an issue to those of you who write some sort of web-based code (a web application or web service) that uses impersonation.
    To fix the issue, we can configure kerberos authentication for the web application and the SQL Server Reporting Services.
    Below is a great article that has delivered many solutions to fix the issue you met:
    http://odetocode.com/articles/216.aspx
    Additionally, you can read the following article to know more about double-hop:
    http://blogs.technet.com/b/askds/archive/2008/06/13/understanding-kerberos-double-hop.aspx
    http://blogs.msdn.com/b/knowledgecast/archive/2007/01/31/the-double-hop-problem.aspx
    If you have any more questions, please feel free to ask.
    Thanks,
    Jin Chen
    Jin Chen - MSFT
    Thanks Jin. I believe this is the cause of the problem as well.
    I tried to register the SPN but unfortunately it still doesn't work. I'm not sure whether I'm using the correct SPN name.
    I have 3 reporting server instance on the SQL box. So the Web Service URL is like
    http://Server:80/VirtualDirectoryDev,
    http://Server:80/VirtualDirectoryTest  and
    http://Server:80/VirtualDirectoryStaging .
    What's the SPN I need to register?
    I tried
    Setspn -a http/Server:80/VirtualDirectoryDev domain\account
    and
    Setspn -a http/aerver:80 domain\account.
    But both of them are not working :(

  • Storing of HR documents with archive link in DMS?

    hi experts,
    how to store HR documents with archive link in DMS?
    i found somewhere it is possible with tr. code OAWD,OAAD
    is helpful..or is there any other way for storing HR documents
    becz i am not able to do it..
    if any one guide me it will be very helpful to me.
    thx..pts will be awarded be sure..

    hi sam ra,
    SAP ArchiveLink - Scenarios in
    Applications (BC-SRV-ARL)
    SAP ArchiveLink® is one of the SAP Basis cross-application communication interfaces between
    the SAP System and external components. External components may be general desktop
    applications or external storage systems. The integration of SAP ArchiveLink in the various SAP
    applications enables the storage scenarios explained in this cross-application documentation.
    The documentation is structured as follows:
      An Introductory Section  (Seite 10) containing general information about storing using SAP
    ArchiveLink and about the following documentation
      An application-specific section for each SAP application component (for example, FI, SD,
    HR) with the relevant storage scenarios
    For information on related areas, see the following documentation:
      SAP ArchiveLink  (Extern)
      SAP Business Workflow  (Extern)
      Archiving and Deleting Application Data  (Extern)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink - Introduction
    April 2001 9
    SAP ArchiveLink - Introduction
    The following sections contain general information about this scenarios documentation.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink and Application Scenarios
    10 April 2001
    SAP ArchiveLink and Application Scenarios
    SAP ArchiveLink® is one of the integrated interfaces in the SAP Basis System that can be used
    to store all kinds of documents in external content servers.
    SAP ArchiveLink therefore complements the existing range of SAP application software. For a
    detailed description of SAP ArchiveLink, see Introduction to SAP ArchiveLink  (Extern).
    The SAP application components, for example, SD, FI, HR and MM, support storing using SAP
    ArchiveLink by providing various application scenarios. Inbound documents, outbound
    documents, print lists, archive files, desktop files and binary files are supported.
    How the inbound documents are entered in the system and forwarded for processing and storing
    depends on the storage scenario used. For information about the possible Storage Strategies
    (Extern) , see the documentation SAP ArchiveLink  (Extern).
    This documentation describes the storage scenarios that are integrated in the SAP applications,
    for example, how Sales and Distribution (SD) documents can be stored in external storage
    systems using SAP ArchiveLink.
    Archiving in databases using the ADK (Archive Development Kit) is not the same as
    storing using SAP ArchiveLink.
    For informationen about data archiving using the ADK archiving transaction, see the
    documentation Archiving and Deleting Application Data  (Extern).
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink: Overview
    April 2001 11
    SAP ArchiveLink: Overview
    Background
    There is a growing trend nowadays to transfer stored data from paper/microfiche to external
    “content servers” (for example, archives). Companies are obliged by law and/or internal
    standards to keep documents for a certain length of time. Traditionally, paper archives or
    microfilms have been used, but these methods are very expensive, either due to copying costs or
    the large amount of space required by such archives. By contrast, electronic storing methods are
    a much cheaper option and represent an important part of the “paperless office” concept.
    SAP’s R/3 System supports a variety of business processes, which can involve documents both
    in paper form and in electronic form. The documents either serve to trigger all kinds of processing
    steps in FI, SD, HR and so on, or they are documents relating to processes in one of these
    application areas.
    When linked to SAP applications, content servers and the SAP ArchiveLink interface allow
    flexible access to all document searches available in the SAP System and can therefore lead to
    considerable time savings. In addition, a combination of the SAP System and SAP ArchiveLink
    allows users multiple access (parallel and direct) to stored documents from their work center
    without the need for time-consuming searches, which guarantees faster access to documents.
    The subsequent sections of this documentation describe the integration of SAP ArchiveLink in
    the functions of various application components within the SAP System.
    Concept
    SAP ArchiveLink provides the following interfaces:
      User interface
      Application Interface
    This interface consists of function modules, which must be integrated in the SAP
    applications, if SAP ArchiveLink functions are to be used.
    Business objects are linked to stored documents and object methods are available that
    allow storing using SAP ArchiveLink to be integrated flexibly in SAP Business Workflow.
      Interface between SAP and external components and general desktop applications
    External components may be HTTP content servers, for example. General desktop
    applications may be MS Word and MS Excel, for example.
    Positioning SAP ArchiveLink
    SAP ArchiveLink enables
      Incoming documents to be stored in the SAP System
      Information from the SAP System (for example, outgoing documents and print lists) to be
    stored
      Direct access from SAP application components to stored documents
      Integration of external content servers with the SAP System
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink: Overview
    The SAP ArchiveLink-specific Terms  (Extern) “document”, “technical document class”, “document
    type”, “object type” and “synchronous storing” and “asynchronous storing” are explained in the
    SAP ArchiveLink documentation, which also contains information on the Administration Concept
    (Extern) (content servers, links and link tables).
    Technical Basis
    Links from documents to business objects are created by the generation of a link table entry,
    which contains both a unique identification for each business object using the object type and
    object key and a reference to a stored document using the content server ID and a unique key for
    each document stored in this content server. It is therefore possible to create a link between a
    business object and any number of documents using a simple 1:n relationship in a table. No
    entry is required in the application tables in which the business objects are managed. If the link
    table entry for an stored document is deleted, all references in the SAP System to this stored
    document are also deleted. This technique allows the options for accessing stored documents to
    be integrated flexibly into the SAP System.
    Application Interface
    The interface to the SAP applications contains the following functions:
      Linking business objects with stored documents
    This function is used to display, retrieve or store stored documents directly from the
    business object. An example of this is the link between an F1 business object invoice
    and original invoices that have been scanned into the system.
      Linking business objects with stored outgoing documents
    This function is used to store documents generated using SAPscript and link them with
    the relevant business objects. Examples of documents are outbound quotations, order
    confirmations, purchase orders and invoices.
      Storing print lists
    The process for storing print lists is the same as for outgoing documents.
    As of R/3 Release 4.6C, application objects archived in data archiving (ADK) are not
    stored using SAP ArchiveLink, but rather using the Content Management Service
    (Extern) of the SAP Knowledge Provider  (Extern) (KPro).
    Integration Status
    Many applications in the SAP System are linked directly or indirectly with SAP ArchiveLink:
      Direct link
    – FI
    – MM
    – SD
      Indirect link
      Via the DMS (document management system): MM, PP,...
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink: Overview
    April 2001 13
    SAP ArchiveLink is centrally integrated in the DMS and all applications with object
    links to the DMS are therefore linked to SAP ArchiveLink.
      Via MC (Message Control): MM, SD,...
    The integration of SAP ArchiveLink in message control allows outgoing documents to
    be stored.
      Via SAPconnect and the Business Workplace: Faxes
    Inbound faxes can be processed directly in the Business Workplace, stored and
    linked with business objects without having to be printed first.
    Generic Object Services
    For R/3 Release 4.0A, generic object services are provided for four SAP ArchiveLink
    functions via the system menu for all SAP applications.
    From the business objects implemented in the SAP applications, four SAP ArchiveLink functions
    can be executed in all applications and independently of which application is involved:
      You can display the hit list of stored documents
      You can assign stored documents subsequently to a business object.
      You can store documents in dialog
      You can create a bar code for a business object
    These functions are integrated into all SAP applications via object services. There is no need for
    special function modules to be integrated in the applications. For more information, see Generic
    Object Services  (Extern).
    For these functions to work smoothly, object orientation in the SAP application and
    support of object services are important.
    For more information, see Business Context Facilities and Generic Object
    Relationships  (Extern).
    Business Applications
    MM
    The following documents relating to purchasing in MM can be stored:
      Outgoing purchasing documents
      Requests for quotation
      Purchase orders
      Scheduling agreements
      Forecast delivery schedules
      Contracts
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink: Overview
    14 April 2001
      Incoming purchasing documents
      Quotations
      Order confirmations
      Incoming invoices and credit memos
      Incoming delivery notes
      Print lists
    For more information about storing in MM, see SAP ArchiveLink - Storage Scenarios in MM
    (Seite 74).
    SD/WS
    The following are examples of sales documents that can be stored:
      Incoming customer inquiries and customer inquiry changes
      Outgoing customer quotations
      Incoming purchase orders and purchase order changes
      Outgoing order confirmations
    For more information about storing in SD, see SAP ArchiveLink - Storage Scenarios in SD [Seite
    50].
    PA
    The following personnel administration and payroll documents can be stored:
      Incoming HR master data documents
      Incoming recruitment documents
      Incoming travel management documents
    For more information about storing in PA, see SAP ArchiveLink - Storage Scenarios in PA [Seite
    204].
    QM
    The following QM documents can be stored:
      Incoming documents for quality notifications (for example, customer complaints)
      Outgoing documents for quality notifications (for example, letter of complaint to vendor)
      Outgoing quality certificates
    For more information about storing in QM, see SAP ArchiveLink - Storage Scenarios in QM
    (Seite 93).
    The DMS and Applications Connected with the DMS
    In the DMS and in applications that are connected with the DMS (often MM and PP), the
    following documents can be stored:
      Incoming documents
      Originals managed in the DMS (PC files)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink: Overview
    April 2001 15
    For more information about storing in the DMS, see Storing in Document Management (CADMS)
    (Seite 24).
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Customizing
    16 April 2001
    Customizing
    Customizing is divided into three areas:
      General Customizing for SAP ArchiveLink
      Customizing for SAP Business Workflow
      Application-specific Customizing for individual SAP ArchiveLink scenarios
    General Customizing for SAP ArchiveLink
    To make these settings, proceed as follows:
    Use the Implementation Guide (IMG):
    Basis   Basis Services   SAP ArchiveLink
    For further information, see the Customizing  (Extern) section in the documentation SAP
    ArchiveLink.
    Customizing for SAP Business Workflow
    For the storage scenarios that use SAP Business Workflow:
      Storing for Subsequent Entry  (Extern)
      Storing for Subsequent Assignment  (Extern)
      Storing and Entering  (Extern)
      Storing and Assigning  (Extern)
    you must make Workflow Customizing settings.
    For further information, see the section Specific Customizing  (Extern) in the documentation SAP
    ArchiveLink and the IMG (Basis   Basis Services   SAP ArchiveLink).
    Application-Specific Customizing
    In the individual application scenarios, further customizing settings are required. The
    application-specific customizing for each SAP application component is described in the following
    sections of this documentation.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Aim of this Documentation
    April 2001 17
    Aim of this Documentation
    This documentation describes the SAP ArchiveLink scenarios that are delivered as part of the
    standard system by SAP. There is a section for each storage scenario. The documentation
    describes the standard software.
    Each storage scenario description is assigned to one of the “big” application components in the
    SAP System. Storage scenarios in the following application components are currently described:
      BC (Basis)
      CA (Cross-Application Components)
      FI (Financial Accounting)
      SD (Sales and Distribution)
      MM (Materials Management)
      IS-RE (Real Estate Management)
      QM (Quality Management)
      PP (Production Planning and Control)
      PM (Plant Maintenance and Service Management)
      PA (Human Resource Management)
      PY-DE (Payroll Germany)
    The individual storage scenarios are structured as function descriptions and generally contain the
    following sections:
    Section Description
    Use Business background
    (this section is sometimes separate from the pure function description).
    You learn which application scenarios SAP ArchiveLink supports, which
    employees are involved and the advantages and simplifications offered by SAP
    ArchiveLink.
    This information is enough to give you a first overview of the storage scenarios.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Aim of this Documentation
    18 April 2001
    Prerequisites   Technical implementation
    You become familiar with the document types and the corresponding technical
    document classes that form the basis of the scenario. You discover which object
    types and link tables are used.
    This information is particularly useful if you are planning to enhance or change
    the scenario.
      Preparation and Customizing
    The settings that are necessary to adapt the scenario to the specific
    requirements of your corporate structure are described.
    The settings described are scenario-specific and usually complement the SAP
    application component Customizing.
    Activities This section describes the technical and business connection of the scenario to
    the R/3 application and how the corresponding application functions are called.
    This documentation is not intended to replace the SAP ArchiveLink
    documentation and should only be seen as a central reference point for
    documentation relating to the implementation of SAP ArchiveLink in the individual
    SAP applications.
    To find out more about using SAP ArchiveLink and make full use of the functions for
    enhancements and in-house developments, see the SAP ArchiveLink  (Extern)
    documentation.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink - Storage Scenarios (BC)
    April 2001 19
    SAP ArchiveLink - Storage Scenarios (BC)
    Ablegen von Listen mit SAP ArchiveLink  (Extern)
    The following sections describe storage scenarios in R/3 Basis (BC):
      Storing Lists in the Report Tree
      Storing Print Lists
      Storing SAPoffice Documents
    See also:
      General Introduction  (Seite 10) to this scenario documentation
      SAP ArchiveLink  (Extern) documentation
      General Report Selection  (Extern) documentation
      BC - ABAP Programming  (Extern) documentation
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Lists in the Report Tree (BC)
    20 April 2001
    Storing Lists in the Report Tree (BC)
    Use
    This section describes the storing of lists generated by executing reports in report trees. The
    process is not application-specific and is usually possible for any list unless storing is specifically
    prohibited in the program.
    Users can access reports that they require in the hierarchical structure of the report tree easily
    from all applications, via general report selection in the SAP information system.
    The SAP standard report tree contains several standard reports for all applications. To access
    reports from a particular application, you must expand the structure until you reach a list of
    reports on the lowest level. Here you select and execute the required report. You can display the
    result on the screen or print it via the spool system.
    Companies can configure the standard report tree to suit their requirements. For example, you
    can add your own reports or pre-generated lists and even change the entire structure.
    Prerequisites
    Technical Implementation (BC)
    Object type
    SREPOTREE
    Document type
    ABAP
    Link table
    TOA01
    For further information on executing reports and displaying pre-generated lists in report trees,
    see General Report Selection  (Extern).
    Technical Implementation (BC)
    Although storing lists generated in the report tree is similar for all applications, the report tree
    available to you may vary from the SAP standard, since your company can adjust the SAP
    standard report tree to suit its requirements.
    For further information on Customizing the report tree, see the Implementation Guide (IMG).
    Choose
    Tools   Business Engineer   Customizing
    Implementation projects   Display SAP Reference IMG
    and then Basis   Reporting - Report tree.
    Activities
    Storing lists
    When you have executed a report in the report tree, you can save the result list there and store it
    simultaneously.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Lists in the Report Tree (BC)
    April 2001 21
    To save your list and store at the same time:
    1. Choose System   List   Save   Report tree.
    2. Select Store in the dialog box displayed and specify where the list should be stored in the
    report tree. Specify the values for Report tree and Nodes.
    3. Choose Save.
    You have now saved your list in the report tree and the process is complete.
    Displaying information on storing lists
    You can check whether a list has been stored in the report tree:
    To check whether a list has been stored:
    1. Position the cursor on the relevant list.
    2. Choose Utilities   List information.
    The System displays a dialog box. The check boxes indicate whether the list has been
    stored.
    Displaying stored lists
    To display a stored list in the report tree, choose the relevant list by double-clicking.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Business Workplace Documents
    22 April 2001
    Storing Business Workplace Documents
    Use
    Documents stored in the Business Workplace  (Extern) are usually stored in the R/3 database (PC
    documents and binary documents can also be stored in an HTTP content server). To save
    memory space in the database, you can store documents in an external storage system using
    SAP ArchiveLink. The content of the documents that you have stored using SAP ArchiveLink is
    then deleted from the database.
    You can only retrieve Workplace documents stored using SAP ArchiveLink from the
    external storage system, from within the R/3 System. Direct access within the
    storage system is not possible.
    Prerequisites
    Technical Implementation
    Object type
    SOFM
    Link table
    TOA01
    Document class
    BIN
    Document type
    SOAARCHIVE Description: Office data object
    Preparation and Customizing
    To store documents from the Business Workplace, a content server must be maintained for the
    object type SOFM and the object class SOAARCHIVE in Customizing  (Extern) for SAP
    ArchiveLink.
    To perform mass archiving of Workplace documents, you need authorization  (Extern) for
    Workplace administration. This authorization is contained in the role SAP_BPT_USER.
    Activities
    Proceed as described in Mass Archiving  (Extern).
    The procedure for displaying and changing documents stored in the archive is no different for the
    user than the procedure for documents stored in the R/3 database. Calling documents from the
    archive usually takes longer, however.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink - Storage Scenarios (CA)
    April 2001 23
    SAP ArchiveLink - Storage Scenarios (CA)
    The following sections describe the storage scenarios in the R/3 application component CA
    (Cross-Application):
      Document Management System (CA-DMS)
      Data Achiving (CA-ARC)
    See also:
      General Introduction  (Seite 10) to the scenario documentation
      SAP ArchiveLink  (Extern)
      Application Data Archiving  (Extern)
      Document Management System  (Extern)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Optical Archiving in Document Management (CA-DMS)
    24 April 2001
    Optical Archiving in Document Management (CA-DMS)
    eingehende Dokumente  (Seite 30)
    You can use SAP ArchiveLink® to archive documents from the document management system
    (DMS) in optical archiving systems.
    Documents Input when Processed (CA-DMS)  (Seite 30)
    Checking a Document into an Archive (CA-DMS)  (Seite 31)
    Displaying an Archived Document (CA-DMS)  (Seite 32)
    Copying an Archived Document to a Document Info Record (CA-DMS)  (Seite 33)
    Digital Original Application Files (CA-DMS)  (Seite 25)
    Archiving an Original Application File (CA-DMS)  (Seite 26)
    Creating a New Version (CA-DMS)  (Seite 27)
    Changing an Original Application File for an Existing Version (CA-DMS)  (Seite 28)
    Displaying an Archived Original Application File (CA-DMS)  (Seite 29)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Digital Original Application Files (CA-DMS)
    April 2001 25
    Digital Original Application Files (CA-DMS)
    For each document info record, you can maintain and archive two original application files.
    Each original application file can be linked to a maximum of 99 additional files. These are
    archived automatically when you archive the original application file.
    Functions
    You process original application files with the following menu option of the document info record:
    Extras   Originals   File 1(2)
    The following functions for archiving and processing archived original application files are
    available:
      Archiving an Original Application File (CA-DMS)  (Seite 26)
      Creating a New Version (CA-DMS)  (Seite 27)
      Changing an Original Application File for an Existing Version (CA-DMS)  (Seite 28)
      Displaying an Archived Original Application File (CA-DMS)  (Seite 29)
    Notes on archiving original application files
      The system checks the application that is used to process the original application file (for
    example, WinWord 7.0).
    In the IMG for the Document Management System in the activity Define workstation
    applications, you define the archives for the various applications (for example, archive A2
    for the application WinWord 7.0).
      The system does not log the archiving of original application files. However, in the IMG for
    the Document Management System, you can define in the activity Define document types
    that all field changes are to be logged (Indicator: Create change documents).
    If you have archived an original application file with the function Check in archive, you
    can track any changes to the storage data (fields Data carrier and Original) in the change
    documents.
    Notes on processing archived original application files
    You have two options for processing an archived original application file:
      Creating a New Version (CA-DMS)  (Seite 27)
      Changing an Original Application File for an Existing Version (CA-DMS)  (Seite 28)
    See also:
    Figure: Changing an Archived Original Application File  (Extern)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Archiving an Original Application File (CA-DMS)
    26 April 2001
    Archiving an Original Application File (CA-DMS)
    You archive an original application file if you want to save the current processing status for
    documentation purposes.
    See also:
    Figure: Archiving Original Application Files  (Extern)
    To archive an original application file:
    1. Process the document in change mode (Basic data screen).
    2. Choose Extras   Originals   File 1(2)   Check in archive.
    The system saves the original application file to the optical disk defined in Customizing.
    You see a dialog box with the following message:
    Document archived successfully
    3. You can check which archive the document was saved to.
    To do this, display the data carrier and path for the original application data by choosing
    Storage data.
    The data carrier and the path where the original application file was stored before being
    checked in the archive is no longer displayed. The system has overwritten this data with
    the archive data.
    If the document type is defined such that all field changes are logged, you can still
    display the previous storage place (Goto   Display changes).
    4. Save your document info record.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Creating a New Version (CA-DMS)
    April 2001 27
    Creating a New Version (CA-DMS)
    This means that you keep the old version (for example, 00) containing the archived original
    application file and create a new version (for example, 01) directly from the old version. For the
    new version, you then change the original application file.
    To process the archived original application file (new version):
    1. On the Basic data screen, choose Document   New version.
    The system copies the data of the existing version (for example, 00), including the archived
    original application data.
    2. In the new version (for example, 01), the original application file is still archived.
    3. Choose Extras   File 1(2)   Change.
    The system automatically creates a copy of the checked in original application file.
    – Enter the target for the copy. This path identifies the place where the original
    application file for the new version (for example, 01) is stored.
    – If the system accepts your entries, you see a dialog box with the following message:
    Data copied from archive
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Changing an Original Application File for an Existing Version (CA-DMS)
    28 April 2001
    Changing an Original Application File for an Existing
    Version (CA-DMS)
    This means that you change the version whose original application file has been archived. There
    is only one version in this case.
    You can display the processing status that the original application file had in the archive from the
    status log if the following applies:
    When checking the original application file into the archive, you set a status for which the
    Indicator: Audit function is selected. This indicator causes original application files that are
    checked into the SAP database, a vault, or an archive with this status to be stored automatically.
    To change the archived original application file (existing version):
    1. Choose Extras   Originals   File 1(2)   Change.
    The system automatically creates a copy of the archived original application file.
    2. You see a dialog box, where you can enter the target for the copy. As a default value, you
    see the path where the file was stored before being archived.
    – To accept the default value, choose Continue.
    – If you want the file to be copied elsewhere, enter the required data (data carrier,
    path, and file name) in the dialog box. This path identifies the place where the
    original application file for the same version is stored. The system overwrites the
    previous archive data.
    If the system accepts your entries, you see a dialog box with the following message:
    Data copied from archive
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Displaying an Archived Original Application File (CA-DMS)
    April 2001 29
    Displaying an Archived Original Application File (CADMS)
    To display an original application file, you always use the following function, whether the data is
    stored on a server or in an archive:
    Extras   Originals   File 1 (2)   Display.
    The system automatically determines the path in the computer network. If the original application
    file is stored in an archive, you see a dialog box with the following message:
    Data copied from archive
    You can display archived data only from computers that have SAP ArchiveLink
    software installed.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Documents Input when Processed (CA-DMS)
    30 April 2001
    Documents Input when Processed (CA-DMS)
    You process documents input when processed in the Archive menu of the document info record.
    The following functions are available:
    Checking a Document into an Archive (CA-DMS)  (Seite 31)
    Displaying an Archived Document (CA-DMS)  (Seite 32)
    Copying an Archived Document to a Document Info Record (CA-DMS)  (Seite 33)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Checking a Document into an Archive (CA-DMS)
    April 2001 31
    Checking a Document into an Archive (CA-DMS)
    You use this function to check a scanned-in document (image) into an optical archive.
    See also:
    Scenario: Checking a Document into an Archive  (Extern)
    To check a document into an archive:
    1. Two windows are active on your computer screen:
    – a scan window with a scanned-in document
    – a window for the R/3 document management system
    2. In the document management window, choose the function you require (Document 
    Create or Change).
    Enter the required data on the initial screen and choose ENTER. You see the Basic data
    screen.
    3. Choose Archive   Check into archive.
    The system checks whether a status network that supports a status of status type A
    (archived) is defined for the chosen document type.
    Archiving is possible in the following cases:
    – if the status network does not support a status of status type A
    – if the status network supports a status of status type A at the current processing
    stage.
    The system automatically sets the status of status type A and records the status
    change in the status log.
    The system automatically determines the archive that is defined in the IMG
    functionOptical Archive.
    When the data has been archived, you see a dialog box with the following message:
    Document archived successfully
    4. Save your document info record.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Displaying an Archived Document (CA-DMS)
    32 April 2001
    Displaying an Archived Document (CA-DMS)
    You use this function you to display documents that were either scanned in when processed,
    then archived, or copied from the archive from the document info record.
    This function is only active it at least one document has been archived for the chosen
    document info record.
    To display a document from the archive:
    1. Choose menu option Archive   Display from archive.
    2. What you do next depends on the situation:
      If only one archived document exists for the document info record, the system goes
    directly to the display program (viewer) and displays the document.
      If more than one archived documents exist for the document info record, you first
    see a dialog box listing the archived objects with the date on which they were
    archived.
      On the list, select the archived objects you want to display in the viewer.
      Choose the Choose pushbutton.
    The system goes to the first selected object.
    In the viewer, you can switch between the objects you selected by choosing the
    appropriate function (Object + or Object -) from the Goto menu.
    3. To exit the display function for archived objects, close the viewer with Document   Exit.
    You can now continue processing the document info record.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Copying an Archived Document to a Document Info Record (CA-DMS)
    April 2001 33
    Copying an Archived Document to a Document Info
    Record (CA-DMS)
    This function allows you to copy a document that has been archived by another application (for
    example, SAPoffice) to a document info record.
    See also:
    Scenario: Copying an Archived Document to a Document Info Record  (Extern)
    Figure: Copying an Archived Document to a Document Info Record  (Extern)
    To copy a document from an archive:
    1. Two windows are active on your screen:
    – a window showing the document in the display program (viewer) of the archive
    – a window for the R/3 document management system
    2. In the document management window, choose the function you require (Document 
    Create or Change).
    3. Place the cursor on the viewer window again.
    – Choose Edit   Select
    This selects the scanned-in document for processing in the document management
    system.
    4. Place the cursor on the document management window.
    Choose Archive   Copy from archive.
    The system makes the same status checks as described in Checking a Document into
    an Archive (CA-DMS)  (Seite 31).
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink and Application Data Archiving (CA-ARC)
    34 April 2001
    SAP ArchiveLink and Application Data Archiving (CAARC)
    Use
    You can use the Archive Development Kit data archiving transaction and SAP ArchiveLink to
    store archive files in external archives. For more information see: Technical Background (CAARC)
    (Extern).
    Prerequisites
    You must enter the following settings in customizing in order to use the SAP ArchiveLink
    interface to archive application data:
      Platform-independent filename
      Document type
      Automatic transfer of archive files
    Activities
      Checking Storage Status of Archive Files (CA-ARC)  (Seite 38)
      Storing Archive Files Manually (CA-ARC)  (Seite 39)
    See also:
    Setting Platform-independent Filenames for SAP ArchiveLink (CA-ARC)  (Seite 35)
    Setting Archive File Document Type (CA-ARC)  (Seite 36)
    Storing Archive Files Automatically (CA-ARC)  (Seite 37)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Setting Platform-independent Filenames (CA-ARC)
    April 2001 35
    Setting Platform-independent Filenames (CA-ARC)
    1. Call the Archive Management.
    2. Enter the name of the archiving object and press Enter.
    3. Choose the Customizing function.
    4. In archiving object-specific customizing choose Technical Settings.
    5. In the logical filename field enter a filename that refers to the exchange directory of the
    attached SAP ArchiveLink archive system. For example, the logical filename
    ARCHIVE_DATA_FILE_WITH_ARCHIVE_LINK. The system delivers the following standard
    defined filename:
    , if you use this runtime variable in the specification of the
    physical path. For example, the physical path could be:
    ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK. See the FILE transaction
    documentation for further information.
    See also:
      Setting Archive File Document Type (CA-ARC)  (Seite 36)
      Storing Completed Archive Files in the Archive System Automatically (CA-ARC)  (Seite 37)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Setting Archive File Document Type (CA-ARC)
    36 April 2001
    Setting Archive File Document Type (CA-ARC)
    1. Call the Archive Management.
    2. Enter the name of the archiving object and press Enter.
    3. Choose the Customizing function.
    4. Choose Technical Settings in archiving object-specific customizing.
    5. Choose the document type Archive in the group box Archive System Link.
    See also:
      Setting Platform-independent Filenames for SAP ArchiveLink (CA-ARC)  (Seite 35)
      Storing Completed Archive Files in the Archive System Automatically (CA-ARC)  (Seite 37)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Completed Archive Files in the Archive System Automatically (CA-ARC)
    April 2001 37
    Storing Completed Archive Files in the Archive System
    Automatically (CA-ARC)
    1. Call the Archive Management.
    2. Enter the name of the archiving object and press Enter.
    3. Choose the Customizing function.
    4. Choose Technical Settings in archiving object-specific customizing.
    5. Mark the checkbox Exec. automat. in the group box Archive System Link.
    See also:
      Setting Platform-independent Filenames (CA-ARC)  (Seite 35)
      Setting Archive File Document Type (CA-ARC)  (Seite 36)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Determining Whether an Archive File is Stored in the Optical Archive (CA-ARC)
    38 April 2001
    Determining Whether an Archive File is Stored in the
    Optical Archive (CA-ARC)
    1. Call the Archive Management.
    2. Enter the name of the archiving object and press Enter.
    3. Choose the Management function.
    4. Set the cursor on the file whose archive residence you want to know, and double-click.
    The Archive Management: Archiving File Detail popup appears. Read the Storage option
    status text.
    See also:
    Storing Completed Archive Files in the Archive System Manually (CA-ARC)  (Seite 39)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Completed Archive Files in the Archive System Manually (CA-ARC)
    April 2001 39
    Storing Completed Archive Files in the Archive System
    Manually (CA-ARC)
    Only archive files whose data objects have been deleted in the database can be
    stored in an external archive system.
    1. Call the Archive Management.
    2. Enter the name of the archiving object and press Enter.
    3. Choose the Management function.
    4. Set the cursor on the file which you want to store in the external archive system.
    If you want to store all the files in a session, set the cursor on the session number.
    5. Choose the Store function.
    The Archive Management: Store via ArchiveLink popup appears.
    6. Choose the Store Files function.
    The file is passed to the external archive system.
    See also:
    Determining Whether an Archive File is Stored in the External Archive (CA-ARC)  (Seite 38)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink - Storage Scenarios (FI)
    40 April 2001
    SAP ArchiveLink - Storage Scenarios (FI)
    The following sections describe storage scenarios in the Financial Accounting (FI) application
    component.
    See also
      The general introduction  (Seite 10) to this scenario documentation
      SAP ArchiveLink  (Extern)dokumentation
      Financial Accounting documentation
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Print Lists (FI)
    April 2001 41
    Storing Print Lists (FI)
    Use
    In the FI application component, you can use SAP ArchiveLink to transfer the following print
    lists to an external storage system:
      Compact document journal (RFBELJ00)
      Line item journal (RFEPOJ00)
      Open item account balance audit trail (RFKKBU00)
      Accumulated account balance audit trail (RFKLBU10)
    Storage using SAP ArchiveLink has the following advantages:
      Reduced burden on online system
      Safer storage
      Faster, easier access
    Prerequisites
    Technical Realization (FI)
    Following improvements to the print reports, the print lists are now provided with an index when
    they are stored, enabling you to access objects (including sub-objects) at a later date.
    A particular account in the account balance audit trail.
    The system also generates a link to any stored documents that might exist, enabling you to
    display the corresponding stored document from the stored print list.
    For a detailed description of how to store print lists, refer to Print Lists  (Extern) in the SAP
    ArchiveLink documentation.
    There are no plans for enhancements.
    Preparation and Customizing (FI)
    No special Customizing settings are required to be able to store print lists in FI. For
    information on the Customizing settings for SAP ArchiveLink, see Customizing  (Seite 16).
    Special authorizations are not required.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Print Lists (FI)
    42 April 2001
    Activities
    For notes on using these functions (in particular displaying stored print lists) see
    Searching for, Displaying and Printing Print Lists  (Extern) in the SAP ArchiveLink
    documentation.
    To store print lists in the FI application component, proceed as follows:
    1. Run the appropriate program and enter your selection criteria.
    2. On the selection screen, choose Optical archiving and enter the following information in
    the dialog box that is now displayed:
    – Object class: DRAW (document)
    – Object type: D01 (print list)
    – Identification: XXX (three figure alphanumeric code of your choice)
    – Text: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (up to 30 characters
    long).
    3. Now choose Execute in background or Execute + Print.
    To view the stored list, from the R/3 System initial screen, choose
    Office   Business Documents   Find lists. Enter the name of the report program and
    any additional selection criteria. Choose Enter. From the list that is now displayed you
    can select a print list and display its contents.
    When displaying the list, you can also display the incoming and outgoing documents
    (provided these were also stored). You do this via hyperlinks which are recognizable
    as such by being underlined.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Incoming Documents (FI)
    April 2001 43
    Storing Incoming Documents (FI)
    Use
    In the FI application component, you can transfer incoming documents (invoices, credit memos)
    to an external archive system using SAP ArchiveLink. Data can be stored in different ways:
      Store for subsequent entry
      Store and enter, and
      Late storing with bar codes
      Assign, then store
    For detailed information on the ways in which you can store documents, see Storage
    Strategies  (Extern) in the SAP ArchiveLink documentation.
    The procedure Store for entry later with document parking is different to other storage
    methods. Under this procedure, processing is even more automated than it would otherwise be.
    The accounting clerk responsible for parking documents receives an incoming document (an
    invoice for example) via SAP Business Workflow. In the entry transaction to which the invoice
    is subject, the clerk can park this document using the existing incoming document. He or she can
    then send the parked invoice together with the incoming document for further processing
    (approval or additional investigation) to the relevant colleague. This colleague can then complete
    processing and post the invoice.
    Prerequisites
    Technical Realization (FI)
    Object type
    BKPF (financial accounting document)
    Link table
    TOA01
    Document class
    FAX
    Document type
    In the standard system, the following document types are supplied for the R/3 FI application
    component.
    FI document Document type
    Incoming invoice without invoice verification FIIINVOICE
    Incoming credit memos without invoice verification FICREDIT
    Incoming invoice parking FIIINVPREL
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Incoming Documents (FI)
    44 April 2001
    Fast invoice entry FIIPAYMEN2
    Incoming payment FIIPAYMENT
    Enhancements
      You can define your own document types under
    Tools   Business Documents
      Document types   Global document types and
    Tools   Business Documents
      Document types   WFL document types.
      You can define your own transaction links under
    Tools   Business Documents
    Document types   Workflow parameters.
    Further information
    For basic technical information on adding SAP ArchiveLink functions to the R/3 application
    components, refer to the section Incoming Documents  (Extern) in the SAP ArchiveLink
    documentation.
    Preparation and Customizing (FI)
    The basic preliminary settings that you must make in SAP ArchiveLink are described in
    Customizing  (Seite 16)
    You need to make settings in Customizing for Financial Accounting only for the activity Late
    storing with bar codes. For more information, see the documentation for the activities Specify
    Control Parameters for Bar Code Entry and Maintain Document Types for Bar Code Entry
    located in Customizing for Financial Accounting under Financial Accounting Global Settings 
    Document   Document Header.
    Activities
    Scenario: Assignment and Storage in FI
    For information on this procedure, see the following sections of the SAP ArchiveLink
    documentation:
    Scenario: Late Storage with Bar Codes in FI
    For information on this topic, see:
      Process: Late Storing with Bar Codes  (Extern)
      Concept: Storing with Bar Codes  (Extern)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Incoming Documents (FI)
    April 2001 45
    Scenario: Store for Subsequent Entry in FI
    For information on this topic, see:
      Concept: Store for Subsequent Entry  (Extern)
      Process: Store for Subsequent Entry  (Extern)
      Store for Subsequent Entry  (Extern)
    Scenario: Entry and Storage in FI
    For information on this topic, see:
      Concept: Store and Enter  (Extern)
      Process: Store and Enter  (Extern)
      Store and Enter  (Extern)
    Document Processing Functions
    In certain document processing transactions in FI you have direct access to the functions
    available under SAP ArchiveLink. These transactions include:
      Changing documents (FB02)
      Displaying documents (FB03)
      Changing parked documents (FBV2)
      Displaying parked documents (FBV3)
    When carrying out these transactions, you can use the following functions:
      Subsequently assign a stored document from the external content server (see Assign
    Stored Documents Subsequently  (Extern))
      Display the stored document for an FI document from the external content server (see
    Searching for Incoming Documents  (Extern))
    The assignment and display functions might typically be accessed as follows:
    1. From the General Ledger menu, choose Document   Display.
    2. Enter the document number and the company code in which it was posted. Choose
    ENTER.
    The system now displays the R/3 document.
    3. To display the stored document for this R/3 document, choose Environment   Object
    links
    To assign this document to a document already stored, choose Environment   Assign
    original.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Incoming Documents (FI)
    46 April 2001
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Outgoing Documents (FI)
    April 2001 47
    Storing Outgoing Documents (FI)
    Use
    You can store documents transferred from the General Ledger (FI-GL), Accounts Receivable (FIAR)
    and Accounts Payable (FI-AP) application components using SAP ArchiveLink. Documents
    that you created using SAPscript are stored in an external storage system and linked to the
    documents or accounts from which they are derived. You can store the following outgoing
    financial accounting documents:
      Payment advice notes
      Checks
      Correspondence like payment notifications and bank statements
      Dunning notices
    Storage using SAP ArchiveLink takes place using Business Transaction Events, to which end
    SAP supplies sample function modules that you can activate by making the appropriate
    Customizing settings.
    If you already use your own programs (user exits) or Business Transaction Events to
    manage printing, faxing, email or dispatching, check whether you need to replace
    these developments with a function module enhanced to perform these functions.
    IMPORTANT: Ensure that no data is overwritten.
    Prerequisites
    Technical Realization (FI)
    Object type
    BKPF (financial accounting document)
    BUS3007 (customer account)
    BUS3008 (vendor account)
    Link table
    TOA01
    Document class
    PDF
    Document type
    The following document types exist in the standard system:
    FI document Document type Function module
    Payment advice note FIOPAYAVIS FI_OPT_ARCHIVE_PAYMENT_ADVICE
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Outgoing Documents (FI)
    48 April 2001
    Check FIOPAYMENT FI_OPT_ARCHIVE_ PAYMENT
    Correspondence:
    Payment notification
    Bank statement
    FIOPAYCONF
    FIOACCSTAT
    FI_OPT_ARCHIVE_CORRESPONDENCE
    Dunning notice FIODUNNING FI_OPT_ARCHIVE_DUNNING_NOTICE
    If you make changes in Customizing to the object types and document types, you will need to
    adapt the corresponding function modules in each case.
    Enhancements
    There are no restrictions to the way in which sample function modules in the standard system
    can be enhanced. They can also be duplicated for additional document types and object types as
    many times as necessary.
      You can define your own document types in the Basis Implementation Guide under
    Basis Services   SAP ArchiveLink   System Settings   Maintain Document Types.
      To define you our own object types, on the SAP R/3 screen, choose
    Tools   Business Framework   BAPI development   Business Object Builder.
      The sample function module FI_OPT_ARCHIVE_CORRESPONDENCE contains the
    correspondence types SAP01 (payment notificiation) and SAP08 (account statement).
    Additional correspondence types can be added to this function module. You can define
    correspondence types in Customizing for Financial Accounting under the
    Implementation Guide under
    Financial Accounting Global Settings   Correspondence   Define Correspondence
    Types.
    Preparation and Customizing (FI)
    To activate storage for financial accounting documents using SAP ArchiveLink, make the
    following settings in Customizing:
    1. If you want to make changes to the function modules (changing the document type
    defined in the standard system for example) copy the sample function modules to your
    name range. You should then make these changes in the source text.
    For a detailed description of the procedure for copying sample function modules to your
    name range, see the IMG documentation for the activity Use Business Transaction
    Events (located under Financial Accounting Global Settings.)
    2. Define the storage method in the function modules. Enter the setting in source text for
    the parameter c_itcpo-tdarmod. The following settings are possible:
      2 Store only
      3 Print and store
    3. Create a product with which all function modules that you want to activate can be
    summarized at a later date.
    To do this, choose the activity Use Business Transaction Events, located in Customizing
    for Financial Accounting under Financial Accounting Global Settings. On the SAP
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Outgoing Documents (FI)
    April 2001 49
    Business Framework: Business Transaction Events screen, choose Settings   Products
      ... of a customer. Mark this product as active by selecting the Active indicator.
    4. Assign the function modules to processes (Events).
    To do this, choose the activity Use Business Transaction Events, located in Customizing
    for Financial Accounting under Financial Accounting Global Settings. On the Business
    Framework: Business Transaction Events screen, choose Settings   P/S function
    modules   ... of a customer. In the table that is now displayed, enter the names of the
    function modules that you want to activate, together with the Events or products required.
    Enter also the name of the product already created.
    The names of the processes defined in the standard system are as follows:
    Function module Process
    FI_OPT_ARCHIVE_PAYMENT_ADVICE 00002050
    FI_OPT_ARCHIVE_ PAYMENT 00002060
    FI_OPT_ARCHIVE_CORRESPONDENCE 00002310
    FI_OPT_ARCHIVE_DUNNING_NOTICE 00001040
    Activities
    Storing outgoing documents (FI)
    Outgoing documents are stored automatically if you have carried out the above-mentioned
    settings in Customizing.
    Displaying stored documents
    Stored documents can be displayed as follows:
      On the SAP R/3 screen, by choosing Office   Business Documents   Documents 
    Find lists
      From the Accounts Receivable or Accounts Payable menu by choosing Master records
      Display.
    Enter the customer or vendor you wish to display, select one of the indicators under
    Company code data and choose ENTER.
    On the screen that is now displayed, choose System   Display relationships   Stored
    documents.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink - Archiving Scenarios (SD)
    50 April 2001
    SAP ArchiveLink - Archiving Scenarios (SD)
    The following sections describe the archiving scenarios in the R/3 application component SD
    (Sales and Distribution):
      General sales and distribution (SD)
      Sales support (SD-CAS)
    See also
      General Introduction  (Seite 10) to this scenario documentation
      SAP ArchiveLink  (Extern)documentation
      Sales and distribution  (Extern) documentation
      Sales support  (Extern) documentation
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Optical Archiving of Incoming Original Documents (SD)
    April 2001 51
    Optical Archiving of Incoming Original Documents (SD)
    Betriebswirtschaftlicher Hintergrund (SD)  (Seite 52)
    Weitere Voreinstellungen  (Extern)
    Spezial-Customizing  (Extern)
    Ablegen für spätere Erfassung  (Extern)
    Zuordnen und Ablegen  (Extern)
    Spät ablegen mit Barcode  (Extern)
    Ablegen und Erfassen  (Extern)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Business Background (SD)
    52 April 2001
    Business Background (SD)
    The Sales and Distribution application component contains an SAP ArchiveLink function that
    provides sales personnel with a quick and efficient means of optically archiving and processing a
    wide range of incoming documents including inquiries, purchase orders, contracts, and
    complaints. SAP ArchiveLink offers easy online access to these archived documents during the
    planning, processing, and analyzing of business transactions in Sales and Distribution.
    The SAP ArchiveLink interface supports the following archiving scenarios for incoming
    documents in SD:
      Early archiving
      Late archiving
      Late archiving using bar codes
      Simultaneous archiving
    Early Archiving
    In the early archiving scenario, incoming paper documents are archived in the R/3 System before
    an SD document is created.
    In early archiving, the archiving process usually begins in a central mailroom where a designated
    person opens, presorts, prepares, and records (scans) the incoming mail. Once an incoming
    document is scanned and an incoming document type is assigned to it, the system triggers the
    SAP Business Workflow to notify the authorized employee(s) that an incoming document has
    been received and is due to be processed. When the employee accesses the archived
    document, the system automatically calls up the relevant business transaction, such as Create
    sales order, according to the incoming document type. After the employee creates and saves the
    SD document, the system automatically assigns the archived document to it.
    For a detailed description of early archiving, see Early Archiving (SD)  (Seite 54).
    Late Archiving
    In the late archiving scenario, incoming paper documents are archived in the R/3 System and
    assigned to existing Sales and Distribution documents.
    In late archiving, an employee processes an original document directly from paper or carries out
    a sales activity before receiving an original document. At a later point in time, the original
    document is scanned into the system and archived as a facsimile. It is then assigned to the
    existing SD document by:
      The person at the archiving station who scans the original documents
      The person responsible for processing the SD document
    As in the scenario for early archiving, the archiving process usually takes place in a central
    location at the company.
    For a detailed description of late archiving, see Late Archiving (SD)  (Seite 55).
    Late Archiving Using Bar Codes
    Late archiving using bar codes is a special form of late archiving. In this case, however, a bar
    code is attached to the incoming document either in the mail room or at the time of processing.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Business Background (SD)
    April 2001 53
    An SD document is created from the original document whose bar code ID is linked to the SD
    document number. Later, the original document is scanned into the system which recognizes the
    bar code ID and automatically makes the proper assignment to the SD document.
    For a detailed description of late archiving using bar codes, see Late Archiving Using Bar Codes
    (SD)  (Seite 56).
    Simultaneous Archiving
    Simultaneous archiving is a special form of early archiving in which the incoming document is
    scanned into the system, optically archived and, at the same time in another window, the
    corresponding SD document is created or changed. The system does not activate SAP
    Business Workflow in this case; no mail is sent.
    For a detailed description of simultaneous archiving, see Simultaneous Archiving (SD)  (Seite 57).
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Early Archiving (SD)
    54 April 2001
    Early Archiving (SD)
    The following steps describe a typical scenario in which incoming paper documents are archived
    before a Sales and Distribution document is created:
    1. A clerk in the central mail room of a company receives a letter from a customer who wishes
    to buy several products.
    2. The clerk scans the letter into a scanning system.
    The system displays the letter in the scan dialog window.
    3. Using the SAP ArchiveLink interface in the R/3 System, the clerk or another designated
    employee selects the function for early archiving and chooses an appropriate incoming
    document type for the scanned document, for example, the general description “Customer
    response to a sales activity”, SDIACTRESP.
    4. The clerk confirms the assignment of the incoming document type.
    This triggers a workflow in which a mail is sent to the employee who is responsible for
    creating sales documents, in this case Mr. Jones in the Sales department.
    All employees who are to be notified by SAP Business Workflow must first be listed
    in the company’s organizational structure (see Customizing for SAP Business
    Workflow).
    5. Mr. Jones receives the work item in his integrated inbox. When he calls up the work item for
    processing, a dialog box appears in which Mr. Jones can confirm or overwrite th

  • Issue with Archiving printlist

    Hello,
    On one of our Production system, we have an issue for archiving printlist.
    We are using option Print immediatly, Print only on a specific output linked archive process with a specific doc. type.
    We ahave checked as well the content repository which seems correctly configures.
    We are using opentext solution successfully on others systems to do the same and customizing seems equivalent on both systems, and we are not able to find the reason why it is not working.
    Spool is considered as " Transferred by Command to the Host Spool" but not completed and we have nothing on dedicated archived directory.
    Did anyone already faced to that message ?
    best regards
    P. alexandre

    The result is identical, I got two lines in SP02 :
    One for archiving with same status and message and another one status"completed"  because it has been printed
    I imagine that the message "transferrred by command to the hist spool" is corresponding to a missing customizing to go on further...
    EDIT
    The archived printlist is generated on the shared directory but not visible as archived file. A link seems to miss between SAP and Opentext server : the issue is more on opentext side....
    Edited by: Philippe ALEXANDRE on Sep 1, 2009 11:06 AM

  • [SOLVED] python-efl: command 'gcc' failed with exit status 1

    Hi everyone! I'm running an x86_64 system with Enlightenment. I'm trying to install econnman from source to have a simpler life trying to connect to my University's wifi network. However, it misses the python-efl dependency. I downloaded it from the AUR, but I get the error message "error: command 'gcc' failed with exit status 1"  when running 'python setup.py build'. This is the complete terminology output:
    [dude@susan python-efl-1.8.0]$ sudo python setup.py build
    Checking for Eina: OK, found 1.11.2
    Checking for Eo: OK, found 1.11.2
    Checking for Evas: OK, found 1.11.2
    Checking for Ecore: OK, found 1.11.2
    Checking for EcoreFile: OK, found 1.11.2
    Checking for Edje: OK, found 1.11.2
    Checking for Emotion: OK, found 1.11.2
    Checking for DBus: OK, found 1.2.0
    Checking for Elementary: OK, found 1.11.2
    running build
    running build_py
    creating build/lib.linux-x86_64-3.4/e_dbus
    copying compat/e_dbus/__init__.py -> build/lib.linux-x86_64-3.4/e_dbus
    running build_ext
    building 'eo' extension
    gcc -pthread -Wno-unused-result -Werror=declaration-after-statement -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -fPIC -DEFL_BETA_API_SUPPORT -Iinclude/ -I/usr/include/python3.4m -c efl/eo/efl.eo.c -o build/temp.linux-x86_64-3.4/efl/eo/efl.eo.o -I/usr/include/efl-1 -I/usr/include/eo-1 -I/usr/include/efl-1 -I/usr/include/eina-1 -I/usr/include/eina-1/eina
    efl/eo/efl.eo.c: In function ‘__pyx_pf_3efl_2eo_4event_global_freeze_get’:
    efl/eo/efl.eo.c:1127:3: warning: implicit declaration of function ‘eo_event_global_freeze_get’ [-Wimplicit-function-declaration]
    eo_do(((const Eo *)eo_base_class_get()), eo_event_global_freeze_get((&__pyx_v_fcount)));
    ^
    efl/eo/efl.eo.c: In function ‘__pyx_f_3efl_2eo_object_from_instance’:
    efl/eo/efl.eo.c:1445:3: warning: implicit declaration of function ‘eo_base_data_get’ [-Wimplicit-function-declaration]
    eo_do(__pyx_v_obj, eo_base_data_get(__pyx_k_5, (&__pyx_v_data)));
    ^
    efl/eo/efl.eo.c: In function ‘__pyx_f_3efl_2eo__eo_event_del_cb’:
    efl/eo/efl.eo.c:2050:3: warning: implicit declaration of function ‘eo_base_data_del’ [-Wimplicit-function-declaration]
    eo_do(__pyx_v_self->obj, eo_base_data_del(__pyx_k_5));
    ^
    In file included from efl/eo/efl.eo.c:317:0:
    efl/eo/efl.eo.c: In function ‘__pyx_pf_3efl_2eo_2Eo_4__repr__’:
    efl/eo/efl.eo.c:2286:30: error: too many arguments to function ‘eo_parent_get’
    eo_do(__pyx_v_self->obj, eo_parent_get((&__pyx_v_parent)));
    ^
    /usr/include/eo-1/Eo.h:588:8: note: in definition of macro ‘_eo_do_common’
    __VA_ARGS__; \
    ^
    efl/eo/efl.eo.c:2286:5: note: in expansion of macro ‘eo_do’
    eo_do(__pyx_v_self->obj, eo_parent_get((&__pyx_v_parent)));
    ^
    In file included from /usr/include/eo-1/Eo.h:1112:0,
    from efl/eo/efl.eo.c:317:
    /usr/include/eo-1/eo_base.eo.h:37:12: note: declared here
    EOAPI Eo * eo_parent_get(void);
    ^
    efl/eo/efl.eo.c: In function ‘__pyx_f_3efl_2eo_2Eo__set_obj’:
    efl/eo/efl.eo.c:2496:3: warning: implicit declaration of function ‘eo_base_data_set’ [-Wimplicit-function-declaration]
    eo_do(__pyx_v_self->obj, eo_base_data_set(__pyx_k_5, ((void *)__pyx_v_self), NULL));
    ^
    In file included from efl/eo/efl.eo.c:317:0:
    efl/eo/efl.eo.c: In function ‘__pyx_pf_3efl_2eo_2Eo_14parent_get’:
    efl/eo/efl.eo.c:2963:28: error: too many arguments to function ‘eo_parent_get’
    eo_do(__pyx_v_self->obj, eo_parent_get((&__pyx_v_parent)));
    ^
    /usr/include/eo-1/Eo.h:588:8: note: in definition of macro ‘_eo_do_common’
    __VA_ARGS__; \
    ^
    efl/eo/efl.eo.c:2963:3: note: in expansion of macro ‘eo_do’
    eo_do(__pyx_v_self->obj, eo_parent_get((&__pyx_v_parent)));
    ^
    In file included from /usr/include/eo-1/Eo.h:1112:0,
    from efl/eo/efl.eo.c:317:
    /usr/include/eo-1/eo_base.eo.h:37:12: note: declared here
    EOAPI Eo * eo_parent_get(void);
    ^
    efl/eo/efl.eo.c: In function ‘__pyx_pf_3efl_2eo_2Eo_20event_freeze_get’:
    efl/eo/efl.eo.c:3104:3: warning: implicit declaration of function ‘eo_event_freeze_get’ [-Wimplicit-function-declaration]
    eo_do(__pyx_v_self->obj, eo_event_freeze_get((&__pyx_v_fcount)));
    ^
    error: command 'gcc' failed with exit status 1
    Can anyone help me? Please tell me every output you need. Thanks and a good day to you, sir!
    Last edited by HisDudeness (2014-10-02 08:47:15)

    You know what? You're right!
    I don't know how I exactly got that version... I got back to the AUR and downloaded the new one. The strange thing is, while that old version's tar.gz conained a lot of files like I'd expect from a source archive, the current version only contained the files .AURINFO and PKGBUILD. Guess that's the way it should be, I'm new to all of this so I was initially surprised. Obviously, running makepkg here worked like a charm and downloaded everything that was needed for it to install. Then, econnman installed just fine too. What I can't explain to myself is why 1.8.0's tar.gz contained all those files.
    In the end, I couldn't use nor connman cli nor econnman to connect to my Campus' WiFi but, after a lot of trouble, I got it to work with dhclient and wpa_supplicant like it's suggested. This hasn't been useless anyway, I saw how to install from the AUR for the first time.
    I'll mark the post as solved, but I got one last question: provided I don't need econnman anymore, do you suggest me to keep python-efl or to remove it? Is it needed for something else I'll certainly run into in the future?

  • Event Log The request failed with HTTP status 401: Unauthorized. workstation to server fetch some reports

    The request failed with HTTP status 401: Unauthorized.
       at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods()
       at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname)
       at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
       at Microsoft.Reporting.WinForms.ServerReport.GetExecutionInfo()
       at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
       at Accounting.Reports.UI.FormReportPreview.LoadReport()
       at Accounting.UI.FormBase.PreLoadReportComponents()
    Please help me with this can't figure out, don't know how to troubleshoot this 5 days working on this error no changes so far, thanks in advance if u can figure it out....

    Hi willjohn520,
    Based on your description, it seems that you are getting the error when you connect to report server reports in workstation. If in this scenario, the issue can be caused by “Host Header”(<foo>) in  a URL that looks like http(s)://<foo>/reports
    is neither the machine name nor the loop back IP address nor the machine's IP address.
    For more details information about this issue, please refer to the following blog:
    http://blogs.msdn.com/b/lukaszp/archive/2008/07/18/reporting-services-http-401-unauthorized-host-headers-require-your-attention.aspx
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Set Media to Archive Status

    Aloha Everyone-
    I have a workflow that has worked well for us to archive to LTO tape and I would like to continue this workflow if possible. I copy my data to a raid and place it into a folder called LTO001 etc. I import these files into Final Cut Server and this works very well. If I unmount the drive from my server I experience a bug. When I right click on the the file it breaks the link to the proxy. If I just click the movie icon I can retrieve the proxy with no problem, but the ones I broke do not work anymore. I can not click analyze because the drive is not present.
    Is there a way to set the file to archive status (when it shows the drive icon in the top left corner) If I can do this it will not expect the device to be there. Using the archive command does not work well for me as I am doing this with red footage and I need more than this file to go to the archive device so I must move the footage manually. This is why I chose to import it into FCS after I have moved it to the archive device. If I leave the drive mounted I have no challenges, but I will need to delete the folders (since they are backed up on LTO) and I will have this challenge anyway.
    Mahalo for any help in this process
    scott

    Thanks for your answer-
    I have what seems to be a good solution. After I import my files into FCS I can tell FCS to archive them, and since I catalogued the tiny _M files from the red camera this archive is very small. Then I can delete my folders and all works very well. I am still testing possible challenges but am optimistic of this workflow. In addition I don't think I would ever need to delete the FCS archived files as they do not take up much room. Then in the future I can restore the whole tape and tell FCS to restore the archive and all is back online.
    mahalo
    scott
    P.S. this workflow seems excellent for red, and a little more trouble for regular quicktimes, but since most of my footage is red I am happy with it so far.

  • "workflow.asmx" method The request failed with HTTP status 404: Not Found.

    When consuming workflow.asmx webservice from , I am getting an error on below line number 3.
    1.POC.SPasmxWF.Workflow objSPasmxWF = new POC.SPasmxWF.Workflow();
    2.objSPasmxWF.Credentials = System.Net.CredentialCache.DefaultCredentials;
    3. XmlNode dataNode = objSPasmxWF.GetWorkflowDataForItem("http://in-mum01:7000/sites/PPP/2014-0002/PPPLibrary/GBL-IQ00120140008.doc");
    Error details: {"The request failed with HTTP status 404: Not Found."} "   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean
    asyncCall)\r\n   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)\r\n   at POC.SPasmxWF.Workflow.GetWorkflowDataForItem(String item) in E:\ERT\\Web References\\SPasmxWF\\Reference.cs:line 234\r\n
      at POC.Program.Main(String[] args) in E:\\POC\\POC\\Program.cs:line 27\r\n   at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)\r\n   at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()\r\n   at System.Threading.ExecutionContext.Run(ExecutionContext
    executionContext, ContextCallback callback, Object state)\r\n   at System.Threading.ThreadHelper.ThreadStart()"

    Hi,
    For a better troubleshooting, I suggest you to do as follows:
    1. On server side you can access the Workflow.asmx from IE to make sure there are no problems in code logic.
    2. On client side you can also access Workflow.asmx from IE to see if it returns error.
    3. Check the link below:
    http://www.mail-archive.com/[email protected]/msg02092.html
    If you want to operate the workflow in Client-Side,  we can use Client Object Model in SharePoint 2010 to achieve it.
    http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.workflow(v=office.14).ASPX
    Thanks,
    Dennis Guo
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Dennis Guo
    TechNet Community Support

  • Order with CLSD status selected

    Hey All
    I am not sure if this is question in CO but While calculating variances the orders with status as CLSD are also being selected. The system in the output shows the orders with CLSD status which is causing long runtime issues. I am sure that orders with status as CLSD are excluded from processing . Can anyone help me on this
    Thanks
    Ankur

    Hi ,
    You need to regulary set the deletion flag in the closed process orders . Please refer Note 397110 - Performance: Archiving manufacturing orders.
    Also refer Note : 393686 on other performance related issues in Cost Object Controlling..
    Regards
    Sarada

  • MAIL XI FTP;mails are in XI with error status,need 2 transfer as local file

    i m doing a scenario, where i need to pick a file from INBOX and need to place as a file in my sys.
    well, it is picking up my mails, so far my mail box is empty.
    now, when i checked my presentation server, i havent got the file.
    and when i checked " Monitor for processed XML Message" in  SXMB_MONI, i can see my messages with RED STATUS FLAG.
    error category: mapping
    error id: exception during execute
    PLEASE come up with suggestions and solutions
    now i have two issues,
    1. i need to place that file in presentation server.
    and to run this config successfully,
    2. how to transfer those file from XI SERVER TO presentation
    regards
    shahid
    Message was edited by:
            shahid mohammed syed
    Message was edited by:
            shahid mohammed syed

    Hi ,
             If you are reading row by row from the attachment of Mail or data .
           <b>   Did u specied the Interface and namespace in the  Mail sender Adpater ?</b>                 
                        If u have specified then it will come as row by row in XML format. Then write your own XSLT maping or java mapping to convert it into required format !
             Once it transformed then only it will come for receiver determination .
          <b>   Check in the Communication channel monitoring  does it contains any error or not ?</b>
      Regards.,
    V.Rangarajan

  • Error Message: The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. The request failed with HTTP status 404: Not Found.

    I have a web page that contains a ReportViewer control.  I am trying to display a report, which is an .rdl file located on the SSRS server, in this ReportViewer control.  I have set the ReportPath and ReportServerUrl correctly.  I am
    getting an error message.
    Am I suppose to use an .rdlc file rather than a .rdl file?  Does the web server configuration need to use a certain account?
     I am getting the following error message:
    The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version.
    The request failed with HTTP status 404: Not Found.

    Hi bucaroov,
    The error "The request failed with HTTP status 404: Not Found." means the ReportServerURL configured in the ReportViewer control is invalid.
    Please follow these steps to solve the issue:
    Logon the Report Server machine.
    Open the Reporting Services Configuration Manager.
    Copy the Report Server URL from 'Web Services URL'.
    Logon the application server(in this case, it is the server that host the web page), check if we can use the URL we got from step 3 to access the Report Server. If so, please replace the ReportServerURL in the ReportViewer control with this URL. If it is
    not available, could you please post the error message.
    Additionaly, we don't need to provide the extension for a server report. The ReportPath should be like: /<reports folder>/<report name>
    For more information, please see:
    Walkthrough: Using the ReportViewer Control in Remote Mode:
    http://msdn.microsoft.com/en-us/library/ms251669(VS.80).aspx
    If you have any more questions, please feel free to ask.
    Thanks,
    Jin Chen
    Jin Chen - MSFT

  • SMS_WSUS_CONFIGURATION_MANAGER - MessageID 6600 - The request failed with HTTP status 503: Service Unavailable

    Hi all,
    knowning that there are already a lot of posts concerning above message, I have to write an additional one as I could not find a solution on the web yet.
    Situation:
    Windows Server 2008 forest including empty root and two child domains, one child domain does have SCCM SP1 (central primary site WND) installed on W2k8 x64 machine including WSUS 3.0 SP1 => everything is working fine.
    Second child domain also contains a SCCM SP1 server  (primary site HUN) running on W2k8 x64 and is defined as child site of central site WND => everything is working fine too - except Software Updates.
    WSUS 3.0 SP1 installed on both SCCM servers by creating additional web site (not using "defautl web site") and configured ports 8530 and 8531 (SSL not used!). No proxy necessary/used. All WSUS 3.0 requirements for W2k8 are installed (IIS roles)
    Error:
    SMS_WSUS_CONFIGURATION_MANAGER - MessageID 6600:
    SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "xxxx0003".
    Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted.
    Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.
    wsusutil checkhealth =>OK
    downloading updates from WSUS at central site (SUSDB and WSUS folder equal in size) =>OK
    wsus admin console able to connect and configuration possible => OK
    IIS ports configured within SMS are equal to those configured for WSUS website
    SCCM config (using Configuration Manager Console) does look correct - ConfigMgr Software Update Point role properties and Software Update Point Component properties
    wcm.log does report an error: (SCCM Log files at the end.)
    "The request failed with HTTP status 503: Service Unavailable"
    IIS log files of both websites (default web site and WSUS Administration website) do not show any errors.
    Questions:
    What else should I look at? (registyr, SUSDB content,..)
    What exactly does happen during the attempt to configure the upstream server by the SMS_WSUS_Configuration_Manager component? I guess a SMS process tries to contact a webservice - would it be possible to debug in more detail ?
    And finally - Who does know the solution ?
    wcm.log:
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
    System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
    Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
    STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4468 GMTDATE=Mi Jul 16 10:49:47.758 2008 ISTR0="xxxx0003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
    Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
    wsusctrl.log (looks fine to me - is able to connect to local WSUS !):
    SMS_EXECUTIVE started SMS_WSUS_CONTROL_MANAGER as thread ID 6156 (0x180C). SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 2732 (0x0AAC)
    This is a WSUS Role as WSUS registry key exists. SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Waiting for changes for 0 minutes SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Timed Out... SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    There are no unhealthy WSUS Server components on WSUS Server xxxx0003 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
    Successfully checked database connection on WSUS server xxxx0003 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:02 6156 (0x180C)
    Waiting for changes for 57 minutes SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:02 6156 (0x180C)
    wsyncmgr.log (as a result of being not able to configure upstream server I guess):
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4476 GMTDATE=Mi Jul 16 10:03:51.481 2008 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 16.07.2008 12:03:51 4476 (0x117C)
    Sync failed: WSUS server not configured. Source: CWSyncMgr:oSync SMS_WSUS_SYNC_MANAGER 16.07.2008 12:08:51 4476 (0x117C)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4476 GMTDATE=Mi Jul 16 10:08:51.636 2008 ISTR0="CWSyncMgr:oSync" ISTR1="WSUS server not configured" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 16.07.2008 12:08:51 4476 (0x117C)

    I just experienced the exact same scenario.  After much digging I found that csakg6so posted a fix at
    Windoows-Noob
    Run Internet Explorer as the SYSTEM account (psexec -s -d -i cmd.exe & C:\Program Files\Internet Explorrer\iexplore.exe)
    Go to internet options
    Go to conections
    Go to LAN settings
    Uncheck all boxes
    The original post said to reboot, but that wasn't necessary for me.
    After initiating a manual Software Update sync the WCM.log and WSyncMgr.log errors do not return and new updates are synchronized.

  • In the MMC, the dispatcher stays yellow, with the status

    Hi all,
    In My Solution Manager system, In the MMC, the dispatcher stays yellow, with the status 'Dialog Queue Info unavailable'.
    However, the system continues to run. Can you please help on this.
    Thanks
    suman

    Hi,
    for this problem, check SAP note 396309 and 72248.
    Thanks
    Sunny

Maybe you are looking for