AIA documentation for operations

I am looking fror documentation to operate and monitor AIA.
- How to monitor ESB/BPEL processes
- Error handling
- Stop/start server
- Retry failed processes
- Analyze errors
This information is probably scattered in BPEL PM, Enterprise Manager, ESB and AIA documentation.
Is there also an overview document referencing the detailed manuals?
We're using AIA 2.0.1 on 10.1.3.3
Thanks,
Jan Willem

In the doc folder inside the dev tools zip file you downloaded from MetaLink is the documentation for how to use the tools.

Similar Messages

  • Where I can find documentation platforms (operating systems) CERTIFICATES for earlier versions of ASE (15.5, 15.0, 12.5, etc)?

    Hi....
    Where I can find documentation platforms (operating systems) certificates for earlier versions of ASE versions of ASE (15.5, 15.0, 12.5, etc)?

    The detailed certification information that used to be available on the Sybase web site is not currently externally accessible since SAP decommissioned the site - all that is currently available is the basic information in the SAP Product Availability Matrix (PAM) and the base release information available in the ASE documentation.
    ASE support is looking into ways of restoring external access to the certification reports, possibly here as SCN documents or on the SCN wiki.  I don't have any estimate for when this will be available, though.
    If you have a support contract, you can open an incident to ask about specific versions/platforms; we still have internal access to the reports.  If the support engineer doesn't know how to access the reports, ask them to get in touch with me.
    -bret

  • Documentation for AIA Tool (PIP Auditor, XMAN, Artifact Generator,Template)

    Hi
    I need complete information how to use all AIA Tools. I need some documentation or tutorial on these.
    I visited [AIA Tool|http://www.oracle.com/technology/products/applications/aia/aiatools.html], also metalink 782351.1 . I found how to install the tool, but nt how to run it and analyse the result.
    Also reffered AIA Developer guide (2.4). Not found anything.
    Can anybody provide any pointer to this?
    Thanks In Advance
    priyadarshi

    In the doc folder inside the dev tools zip file you downloaded from MetaLink is the documentation for how to use the tools.

  • Could not find binding output for operation getMessage

    Hi,
    I am getting a error while involking a service which is implemented using Axis2.
    The error is "[email protected]1 : Could not find binding output for operation getMessage".
    Please help me in solving the problem. The WSDL of the service looks like this...
    <wsdl:definitions xmlns:axis2="http://ws.fs.com" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns0="http://ws.fs.com/xsd" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://ws.fs.com">
    <wsdl:documentation>GetMessageService</wsdl:documentation><wsdl:types><xs:schema xmlns:ns="http://ws.fs.com/xsd" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://ws.fs.com/xsd">
    <xs:element name="getMessage">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="param0" nillable="true" type="xs:string" />
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getMessageResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="return" nillable="true" type="xs:string" />
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema></wsdl:types><wsdl:message name="getMessageMessage"><wsdl:part name="part1" element="ns0:getMessage" /></wsdl:message><wsdl:message name="getMessageResponse"><wsdl:part name="part1" element="ns0:getMessageResponse" /></wsdl:message><wsdl:portType name="GetMessageServicePortType"><wsdl:operation name="getMessage"><wsdl:input xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" message="axis2:getMessageMessage" wsaw:Action="urn:getMessage" /><wsdl:output message="axis2:getMessageResponse" /></wsdl:operation></wsdl:portType><wsdl:binding name="GetMessageServiceSOAP11Binding" type="axis2:GetMessageServicePortType"><soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /><wsdl:operation name="getMessage"><soap:operation soapAction="urn:getMessage" style="document" /><wsdl:input><soap:body use="literal" /></wsdl:input><wsdl:output><soap:body use="literal" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:binding name="GetMessageServiceSOAP12Binding" type="axis2:GetMessageServicePortType"><soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /><wsdl:operation name="getMessage"><soap12:operation soapAction="urn:getMessage" style="document" /><wsdl:input><soap12:body use="literal" /></wsdl:input><wsdl:output><soap12:body use="literal" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:binding name="GetMessageServiceHttpBinding" type="axis2:GetMessageServicePortType"><http:binding verb="POST" /><wsdl:operation name="getMessage"><http:operation location="getMessage" /><wsdl:input><mime:content type="text/xml" /></wsdl:input><wsdl:output><mime:content type="text/xml" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:service name="GetMessageService"><wsdl:port name="GetMessageServiceSOAP11port_http" binding="axis2:GetMessageServiceSOAP11Binding"><soap:address location="http://192.168.74.248:8080/axis2/services/GetMessageService" /></wsdl:port><wsdl:port name="GetMessageServiceSOAP12port_http" binding="axis2:GetMessageServiceSOAP12Binding"><soap12:address location="http://192.168.74.248:8080/axis2/services/GetMessageService" /></wsdl:port><wsdl:port name="GetMessageServiceHttpport" binding="axis2:GetMessageServiceHttpBinding"><http:address location="http://192.168.74.248:8080/axis2/services/GetMessageService" /></wsdl:port></wsdl:service></wsdl:definitions>
    Thanks in advance.
    Kiran

    Im having the exact same problem.
    Has anyone found out how to fix this? Ive removed any extra soap bindings generated by axis2 and fixed a few problems with the wsdl but to no avail.
    Any ideas?
    Thanks in advance,
    Ian Harrigan

  • Could not find binding output for operation ...

    Hi all !!!
    I have a big problem:
    [email protected]5 : Could not find binding output for operation getScore
    I invoke a web service called IPODShopService from my process BPEL.
    this is the WSDL:
    wsdl:definitions targetNamespace="http://service.integration.ipodshop.it">
    <wsdl:documentation>
              Please Type your service description here
         </wsdl:documentation>
    −
         <wsdl:types>
    −
         <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://service.integration.ipodshop.it/xsd">
    −
         <xs:element name="getScore">
    −
         <xs:complexType>
    −
         <xs:sequence>
    <xs:element name="nome" nillable="true" type="xs:string"/>
    <xs:element name="cognome" nillable="true" type="xs:string"/>
    <xs:element name="email" nillable="true" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    −
         <xs:element name="getScoreResponse">
    −
         <xs:complexType>
    −
         <xs:sequence>
    <xs:element name="return" nillable="true" type="xs:int"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    −
         <xs:element name="CreateOrder">
    −
         <xs:complexType>
    −
         <xs:sequence>
    <xs:element name="nome" nillable="true" type="xs:string"/>
    <xs:element name="cognome" nillable="true" type="xs:string"/>
    <xs:element name="email" nillable="true" type="xs:string"/>
    <xs:element name="list" nillable="true" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    −
         <xs:element name="CreateOrderResponse">
    −
         <xs:complexType>
    −
         <xs:sequence>
    <xs:element name="return" nillable="true" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>
    </wsdl:types>
    −
         <wsdl:message name="CreateOrderMessage">
    <wsdl:part name="part1" element="ns0:CreateOrder"/>
    </wsdl:message>
    −
         <wsdl:message name="CreateOrderResponse">
    <wsdl:part name="part1" element="ns0:CreateOrderResponse"/>
    </wsdl:message>
    −
         <wsdl:message name="getScoreMessage">
    <wsdl:part name="part1" element="ns0:getScore"/>
    </wsdl:message>
    −
         <wsdl:message name="getScoreResponse">
    <wsdl:part name="part1" element="ns0:getScoreResponse"/>
    </wsdl:message>
    −
         <wsdl:portType name="IPODShopServicePortType">
    −
         <wsdl:operation name="CreateOrder">
    <wsdl:input message="axis2:CreateOrderMessage" wsaw:Action="urn:CreateOrder"/>
    <wsdl:output message="axis2:CreateOrderResponse"/>
    </wsdl:operation>
    −
         <wsdl:operation name="getScore">
    <wsdl:input message="axis2:getScoreMessage" wsaw:Action="urn:getScore"/>
    <wsdl:output message="axis2:getScoreResponse"/>
    </wsdl:operation>
    </wsdl:portType>
    −
         <wsdl:binding name="IPODShopServiceSOAP11Binding" type="axis2:IPODShopServicePortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    −
         <wsdl:operation name="CreateOrder">
    <soap:operation soapAction="urn:CreateOrder" style="document"/>
    −
         <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    −
         <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    −
         <wsdl:operation name="getScore">
    <soap:operation soapAction="urn:getScore" style="document"/>
    −
         <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    −
         <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    −
         <wsdl:binding name="IPODShopServiceSOAP12Binding" type="axis2:IPODShopServicePortType">
    <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    −
         <wsdl:operation name="CreateOrder">
    <soap12:operation soapAction="urn:CreateOrder" style="document"/>
    −
         <wsdl:input>
    <soap12:body use="literal"/>
    </wsdl:input>
    −
         <wsdl:output>
    <soap12:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    −
         <wsdl:operation name="getScore">
    <soap12:operation soapAction="urn:getScore" style="document"/>
    −
         <wsdl:input>
    <soap12:body use="literal"/>
    </wsdl:input>
    −
         <wsdl:output>
    <soap12:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    −
         <wsdl:binding name="IPODShopServiceHttpBinding" type="axis2:IPODShopServicePortType">
    <http:binding verb="POST"/>
    −
         <wsdl:operation name="CreateOrder">
    <http:operation location="CreateOrder"/>
    −
         <wsdl:input>
    <mime:content type="text/xml"/>
    </wsdl:input>
    −
         <wsdl:output>
    <mime:content type="text/xml"/>
    </wsdl:output>
    </wsdl:operation>
    −
         <wsdl:operation name="getScore">
    <http:operation location="getScore"/>
    −
         <wsdl:input>
    <mime:content type="text/xml"/>
    </wsdl:input>
    −
         <wsdl:output>
    <mime:content type="text/xml"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    −
         <wsdl:service name="IPODShopService">
    −
         <wsdl:port name="IPODShopServiceSOAP11port_http" binding="axis2:IPODShopServiceSOAP11Binding">
    <soap:address location="http://192.168.0.4:8083/IPODv7/services/IPODShopService"/>
    </wsdl:port>
    −
         <wsdl:port name="IPODShopServiceSOAP12port_http" binding="axis2:IPODShopServiceSOAP12Binding">
    <soap12:address location="http://192.168.0.4:8083/IPODv7/services/IPODShopService"/>
    </wsdl:port>
    −
         <wsdl:port name="IPODShopServiceHttpport" binding="axis2:IPODShopServiceHttpBinding">
    <http:address location="http://192.168.0.4:8083/IPODv7/services/IPODShopService"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    and the bpel code:
    <partnerLink name="ServiceIPOD_v6.1"
    partnerRole="IPODShopServicePortType_Role"
    partnerLinkType="ns31:IPODShopServicePortType_PL"/>
    <invoke name="CustInfofromIPOD_v4" partnerLink="ServiceIPOD_v6.1"
    portType="ns31:IPODShopServicePortType" operation="getScore"
    inputVariable="CustInfofromIPOD_v1_getScore_InputVariable"
    outputVariable="CustInfofromIPOD_v1_getScore_OutputVariable"/>
    <definitions
    targetNamespace="http://service.integration.ipodshop.it"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:axis2="http://service.integration.ipodshop.it"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    >
    <import namespace="http://service.integration.ipodshop.it" location="http://localhost:8083/IPODv7/services/IPODShopService?wsdl"/>
    <plnk:partnerLinkType name="IPODShopServicePortType_PL">
    <plnk:role name="IPODShopServicePortType_Role">
    <plnk:portType name="axis2:IPODShopServicePortType"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>
    do have you any idea?
    please, help me!
    thanks
    Stefano

    Hi,
    Just in case someone runs into the same problem, I live here my solution:
    In may case the problem was the wsdl definition. I developed the web service in java and generated the wsdl with Maven. Automatically it generates the wsdl like this (I just copy the last section):
    <wsdl:service name="tso-ws">
    <wsdl:port name="tso-wsHttpSoap11Endpoint" binding="ns:tso-wsSoap11Binding">
    <soap:address location="http://localhost:8080/axis2/services/tso-ws"/>
    </wsdl:port>
    <wsdl:port name="tso-wsHttpSoap12Endpoint" binding="ns:tso-wsSoap12Binding">
    <soap12:address location="http://localhost:8080/axis2/services/tso-ws"/>
    </wsdl:port>
    <wsdl:port name="tso-wsHttpEndpoint" binding="ns:tso-wsHttpBinding">
    <http:address location="http://localhost:8080/axis2/services/tso-ws"/>
    </wsdl:port>
    </wsdl:service>
    The problem was the <wsdl:service name="tso-ws"> section. There were 3 port definitions with 3 different bindings but all of them have the same service location. So In the BPEL process I created the partner link using the service location.
    I guess BPEL was using the http binding, so I deleted two of the por definitions and just left this in the <wsdl:service name="tso-ws"> section of the wsdl
    <wsdl:service name="tso-ws">
    <wsdl:port name="tso-wsHttpSoap12Endpoint" binding="ns:tso-wsSoap12Binding">
    <soap12:address location="http://localhost:8080/axis2/services/tso-ws"/>
    </wsdl:port>
    By doing this, it works. I read in some forums that BPEL doesn't work with the http_post protocol so that's why I deleted that definition. And someone told me that it uses soap12 so that's why I deleted that definition also.
    That's the way I solved it. Hope this helps.
    Regards,
    Zaloa

  • Overhauling the Documentation for Director

    Hi Everyone,
    Please excuse this cross-post. You can also find it on the Direct-L mailing list and on the Director Online Forum. I will post a summary of answers to each of these places.
    Rajnish Bharti, Product Manager for Director and Shockwave, asked me last week for my input on how best to overhaul the documentation for Director.  In particular, he asked me to give him an idea of what the Table of Contents should look like.
    You can find my first draft of the Table of Contents here:
    http://www.openspark.com/adobe/Director_Documentation_01.zip
    While preparing this, I contacted a number of Director teachers and trainers, talked to some newcomers to Director, consulted dozens of Director books (mostly from the Macromedia days) and pored over the various reincarnations of Director's own help.
    Examples
    Lots of real-life examples that you can copy and paste and
    know that they will work
    Images
    Clear and concise screen shots that capture the essence of
    a concept at a glance
    Fast and Powerful Searching
    Beginners don't know which menu item or scripting term they
    are looking for.  The search engine should help users to home
    in from a layman's expression to the appropriate documentation
    article.  Articles should be intelligently cross-referenced.
    I have suggested dividing the documentation into three sections:
    1. Director Step by Step
    A series of short hands-on tutorials which introduce all the
    commonly-used features of Director in the context of simple
    movies.  Beginners can start here.
    This section imagines that you have never used Director or
    studied its documentation before.  You select a project that
    is similar to the one you are planning, and the documentation
    shows you how to achieve your goal using Director.
    Hyperlinks lead you to more in-depth entries in the Feature
    Guide on how a feature works, or to the appropriate entry in
    the Scripting Dictionary.
    2. Feature Guide
    This section will give detailed explanations of each feature,
    category by category.  It will be divided into three main
    chapters:
    The Workspace
    Working with the various windows and menus
    The Raw Materials
    Understanding sprites, members, the various media types
    and data types
    The Process
    Designing your project, animating sprites, using scripts
    and publishing your work.
    This section will give you a categorized view of what Director
    does.  It imagines that you start with a "How do I..." type of
    question, and guides you to the appropriate part of the
    User Interface or the correct scripting terms to use.
    It will contain links both to the Step by Step tutorials and
    to the entries in the Lingo Dictionary.
    3. Alphabetical Scripting Dictionary
    I have abandoned the idea of having the Dictionary divided
    into categories.  I believe it is much easier to find an
    entry without having to wonder whether it is a keyword, a
    method or an operator.  If you don't know what entry you
    should be looking for, the Feature Guide will help you.  If
    you do know the word you are looking for, then you only
    need to know the alphabet.
    Each entry in the Scripting Dictionary should link back to
    the articles in the Feature Guide which refer to it, and to
    each of the tutorials in the Step by Step section which use
    the term.
    I also suggest (Section 4) implementing a much more powerful Search engine than the D11.5 browser-based help currently features, but that is not really a part of the Table of Contents.
    The document that I have posted at...
    http://www.openspark.com/adobe/Director_Documentation_01.zip
    ... is by no means definitive, but it is at a point where I am ready to share it, to check if my general approach is acceptable.
    I have not gone into much greater detail in some areas than in others, so past the 4th level, you may find certain areas are still vague.  You may have better ideas for the Step by Step tutorial movies than the ones I have included.
    Red text indicates new content.
    I welcome feedback from all members on the community, both in terms of the content and the structure.
    Once we have a comprehensive list of all the topics to cover and a consensus on the structure, then we will have to work out the most cost-effective way of generating the actual content.
    Let me know what you think,
    James

    James, this looks outstanding!
    I'm too far behind in versions to offer much here, but one thing I noticed that, I think is an oops:
    3.4.    Java Dictionary
    should be:
    3.4.    JavaScript Dictionary
    Unless they brought back the Java beast, that is.
    Mark A. Boyd
    Keep-On-Learnin' :-)

  • Need documentation for writing GPIB drivers for RTOS-32 using Borland C 5.51

    Greetings,
    I need to develop GPIB drivers (using the NI GPIB card) for the RTOS-32 operating system (by On-Time). I am using Borland C 5.51 as the compiler. I am looking for info/examples on writing/porting low level drivers for the GPIB. The examples I have found come with the low levels drivers in an object file which you link in, but nothing on how to write the low level drivers.
    Any pointers on what documentation/examples that I should look at would be greatly appreciated.
    Thank you for your time,
    Fred A. Ennerson
    Electro-Optical/Sonatech

    Fred,
    National Instruments offers a DDK for customers to develop NI-488 drivers for operating systems that we do not support directly. Refer to the following product data sheet on using the NI-488DDK. http://www.ni.com/pdf/products/us/4gpib664.pdf
    Craig A
    National Instruments Engineer

  • Hi all ,i need a good documentation for a beginner in WORK FLOW ?

    hi all ,
    i need a good documentation for a beginner in WORK FLOW ?
    please,try to send the attached documents as much as u can apart from giving the weblinks ?
    hope you will send it soon ....
    thanks & regards
    vishnuvardhan k.v.

    Hi
    Developing a simple application using steps "User Decision" and "Mail"
    Basic terminology used in the workflow:
    The workflow definition is the set of rules that determine the path that the process takes. For example, how a purchase requisition is processed, from the initial request to the creation of the purchase order
    A Workflow Instance, which is often simply referred to as the workflow, is a single workflow run. For example, the processing of a single purchase requisition for computers.
    The Tasks are the steps in the process, which have to be performed either by people or automatically by the software. For example, to check for the availability of the spare computers in the company.
    A Work item is the task instance that is performed as a single workflow step. For example, check that there are no spare computers available in the company.
    Agents are the people who process the tasks (via the work items). For example, requisitioner and a member of the purchasing department.
    Container is the place where all the data used in the workflow is collected.
    Binding is the set of rules that define which data is passed to which part of the process.
    Building a simple workflow application
    The central tool for creating, displaying and processing a workflow is the workflow builder (Transaction SWDD). Within the workflow builder you can create all components of a workflow, including all the containers you need for getting the data from one step to another.
    Generally, most of the workflows are started by an event (for example, when a material is created or when a new purchase requisition arrives). You define which data from this event needs to be passed to the workflow via binding.
    However you can also start any workflow directly. Let us create a simple workflow and start the workflow directly, using the testing tools.
    Call transaction SWDD. When the workflow builder is called for the first time, a newly created initial workflow definition appears or else last created workflow appears. In such cases you can opt to create a new workflow by pressing “Create New Workflow”(ctrl + shft + F5). The following screen appears.
    The initial workflow screen has the following parts:
    a. The start of the workflow definition, indicated by .
    b. The end of the workflow definition, indicated by .
    c. The area in which you insert the new workflow definition is indicated by .
    Now select the undefined step and select Create step or double click the undefined step. Now among the different steps chose the User Decision by double clicking on it.
    Developing a simple application using steps "User Decision" and "Mail"
    Previous
    Now enter the title for the user decision “ Please make a decision”. Also enter the decision texts as Approve and Reject. On pressing enter, the outcome values default to the Decision texts but you can specify your own names, if desired. Now we need to select the agent. Agent is the person to whom the work item needs to be sent.. Since this is just a beginning, we would hardcode the user name. Select the User from the drop down list and enter the user name to whom the work item needs to be sent. In general, this type of agent assignment is not done. Agents are generally assigned using the expression, agent assignment rule or organization object (job, position etc.).
    Now select Transfer and to graphic button. Following screen appears:
    Now we need to include a mail step to be sent to the requestor. Now select the line “Approve” and do a right click. Different options on shown on the context menu. Select Create.
    Now select the step “Send Mail” from the list.
    Developing a simple application using steps "User Decision" and "Mail"
    ...Previous
    Now enter the subject and the body of the message for the mail to be sent.
    Do not change the recipients. Our mail is intended for the persons who triggered this workflow. &_WF_INITIATOR& contains the value who executed the workflow. Since this is a test object, we are using &_WF_INITIATOR&. But we wouldn’t be using this variable in real time scenarios. We would discuss about this in the coming documents.
    Now select Transfer and to graphic button.
    A popup appears requesting for the abbreviation and the name for this task. Enter the same and press enter.
    Now enter the package as local object and press enter.
    Follow the steps 5 through 9 for the step “Reject”. The following screen appears:
    Press SAVE to save the workflow application. You need to enter an abbreviation and name for your workflow as shown below. You can change any of these at any later point. After saving, a number is assigned to your workflow starting with WS, as shown below.
    Developing a simple application using steps "User Decision" and "Mail"
    ...Previous
    To execute the workflow, activate it by choosing the activate button.
    Test the workflow by choosing Test. The following screen appears.
    Now choose Execute to start the workflow.
    Now the recipient would receive a work item in his SAP® inbox (Transaction SBWP).
    Now execute the work item by pressing “Execute”. The following screen appears:
    Choose one among Approve or Reject as part of the user decision. He can select the third option to retain the work item in his inbox and make the decision later. Now suppose that the recipient has chosen one of the first options. Now a mail would be sent to the requestor with the status of his request.
    Creating a Container element
    This document details about creation of a container element in workflow and using it in the step "Mail".
    Pre-requisites:
    It is assumed that the reader of this Tutorial is aware of creating a workflow definition with the step “Mail”. If not, please go through the document on creating the same available, by clicking here.
    Steps:
    1. Create a workflow definition using the transaction SWDD.
    2. Let’s create a container element for Carrier id. Click on the “Workflow Container” on the left side of the screen (as shown in the screenshot below):
    3. Now double-click on “Double-Click to Create”
    4. Enter the details pertaining to CARRID here.
    5. Click on tab “Properties” and select “Import”.
    6. Click on “Confirm (Enter)”.
    7. Now the element created could be seen on the left side, below the “Workflow Container”.
    Creating a Container element
    Previous
    1. Create a “Mail” step by double-clicking on “Undefined” step in the workflow.
    2. Enter the recipient details in the “Recipients” box.
    3. In the subject line, enter “Carrid value entered is:” and click on “Insert Expression”.
    4. Select the element “Carrid” from the list.
    5. Similarly enter the content in the “Body” area.
    6. Save and activate the application.
    Testing the Workflow application:
    7. Test the workflow by clicking F8.
    8. Enter the value of the Carrid as shown above and press execute.
    9. A mail would be sent to the recipient mentioned earlier with the carrid value entered.
    Condition Step
    Agenda:
    This document details about the steps “Condition”.
    Pre-requisites: It is assumed that the reader of this document has a preliminary understanding of workflow and has worked with the container elements earlier. If not, please go through the first two Tutorials of workflow available in this site. (More details)
    Procedure:
    1. Create a new workflow definition.
    2. Create a container element, CARRID (as demonstrated in tutorial 2).
    3. Now click on undefined step and create the step “Condition”.
    4. Enter the step name of your choice.
    5. We would have the following condition here:
    If carrid = ‘AA’.
    Do this.
    Else.
    Do this.
    Click on “Click here to create a new condition”. Following screen appears.
    Double click on “Carrid”. Next click on “=” and enter the value “AA” in the constant field and press ENTER.
    Enter the outcome names of your choice as shown above.
    Click on “Transfer and go to graphic”.
    As shown above, there are two branches here. One navigates to true, if CARRID = ‘AA’ else the control takes the branch “False”.
    Test the above scenario by inserting mail steps in the above 2 branches and by passing different CARRID values.
    Condition Step
    Agenda:
    This document details about the steps “Multiple Condition”.
    Pre-requisites: It is assumed that the reader of this document has a preliminary understanding of workflow and has worked with the container elements earlier. If not, please go through the first two Tutorials of workflow available in this site. (More details)
    Procedure:
    1. Create a new workflow definition.
    2. Create a container element, CARRID (as demonstrated in tutorial 2).
    3. Now click on undefined step and create the step “Multiple Condition”.
    4. Enter the step name of your choice.
    5. We would have the following condition here:
    If carrid = ‘AA’.
    Do this.
    Elseif carrid = ‘AH’
    DO this.
    Elseif carrid = ‘SQ’
    Do this.
    Else.
    Do this.
    Select the “CARRID” using the F4 help for the comparison basis field.
    Enter the values of the carrid under the Comparison values with the corresponding outcome name (of your choice)
    Double click on “Carrid”. Next click on “=” and enter the value “AA” in the constant field and press ENTER.
    Click on “Transfer and go to graphic”.
    As observed above, there are different branches for each value of CARRID mentioned above.
    Test the above scenario by inserting mail steps in all the branches and by passing different CARRID values.
    Using "Container Operation" step
    Agenda: Usage of step “Container Operation”.
    Pre-requisites: It is assumed that the reader of this tutorial has worked in the concepts that are dealt in earlier tutorials. (click here for more details)
    Scenario: In this tutorial, we would deal about how to work with the step “Container Operation” with an example of calculating the available seats by subtracting occupied seats from the maximum seats at the workflow level.
    Procedure:
    1. Create a new workflow definition using the transaction SWDD.
    2. Create two container elements MaxSeats, Occ_Seats with the “import” property set. You can use the reference fields sflight-seatsmax, sflight-seatsocc for this.
    3. Create another container element AvailableSeats without setting either import or export property as this is calculated within the workflow and used within the workflow. You might use any of the above reference fields as data types.
    4. Define a new step “Container Operation” in the workflow definition by double-clicking on the “Undefined step”.
    5. In this step, we would calculate the available seats from the max seats and seats occupied.
    I would recommend entering all the container elements from the F4 help instead of typing them manually.
    6. Return to the main screen.
    7. Create a mail step after this to send the available seats information.
    8. Test the above functionality by passing some values to the maximum and the seats occupied.
    9. Result would be as follows:
    Triggering Events Programmatically
    Purpose: This document details the procedure in triggering the business object events programmatically.
    Pre-requisites: It is assumed that the reader of this document is aware of the business object concepts and good in ABAP.
    Procedure:
    In this document, we would take an example of the business object BUS1001006 (Material) and the event CREATED. In general, this event is triggered whenever a material is created using a standard procedure like MM01 or any others. Now we would trigger this event from our own programs.
    Following are the screenshots of the business object BUS1001006 and the event CREATED. Go to transaction SWO1 for more information of the business object.
    Double-clicking on the key field parameter gives you technical information of the field.
    In order to trigger an event programmatically, we would use the function module SWE_EVENT_CREATE.
    Following is the sample code to trigger the events programmatically:
    REPORT ZDEMO_TRIGGER_EVENT.
    DATA: KEY LIKE SWEINSTCOU-OBJKEY.
    KEY = '1163'. “ Material Number (hard-coded)
    CALL FUNCTION 'SWE_EVENT_CREATE'
    EXPORTING
    objtype = 'BUS1001006'
    objkey = KEY
    event = 'CREATED'
    CREATOR = ' '
    TAKE_WORKITEM_REQUESTER = ' '
    START_WITH_DELAY = ' '
    START_RECFB_SYNCHRON = ' '
    NO_COMMIT_FOR_QUEUE = ' '
    DEBUG_FLAG = ' '
    NO_LOGGING = ' '
    IDENT =
    IMPORTING
    EVENT_ID =
    TABLES
    EVENT_CONTAINER =
    EXCEPTIONS
    OBJTYPE_NOT_FOUND = 1
    OTHERS = 2
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ELSE.
    WRITE 'Event Triggered'.
    ENDIF.
    COMMIT WORK.
    In order to test whether the event is getting triggered or not, we can make use of Event Trace. Switch on the event trace using the transaction SWELS.
    Press ‘Switch On”.
    Now execute the program developed earlier. Now switch-off the event trace using the same transaction SWELS.
    Now go to transaction SWEL. Here you can list out the events triggered in the particular period of time. Here is the event-trace list:
    Deadline Monitoring in SAP Workflow
    A major advantage of workflow is the ability to monitor the workflow steps according to a predefined schedule. Following are different deadlines that can be monitored against each workflow step:
    • Requested Start
    • Latest Start
    • Requested End
    • Latest End
    In this example, we will define a deadline to the User Decision example created earlier (click here). Following is the screenshot of the application developed using the User Decision example:
    We would extend this example to the deadline monitoring.
    In the User Decision step, click on the “latest end” tab.
    By default, No deadline monitoring is active (as seen in the above screenshot).
    Choose the “Work Item Creation” from the list box.
    After selecting “Work Item Creation”, chose an offset of 5 minutes. This means that the work item must be executed within 5 minutes of the creation, if not this would trigger.
    Deadline Monitoring in SAP Workflow
    Enter recipient details to whom the message to be escalated, if the work item is not executed with in 5 minutes after work item creation.
    Save and activate the workflow definition.
    Testing the workflow application:
    • Execute your workflow.
    • Check for the work item in the SAP Inbox. This time do NOT execute the work item.
    • Wait for the deadline to be triggered. After that, a deadline message is delivered to the recipient mentioned in the “Latest End” tab. See the screenshot below.
    Don’t worry if the deadline message doesn’t appear immediately after 5 minutes. This depends on various factors including how the deadline monitoring program is scheduled and also on the availability of the background processors.
    Use SWWA to check how the deadline monitoring program is scheduled in program.
    For example, assume that our work item has been created at 09:10 hrs and the deadline message is expected to trigger at 09:15 hrs. From the above screenshot, it is understood that the background program is scheduled to execute for every 3 minutes. Assume that the last run of the program is at 09:14hrs and the next run is expected at 09:17hrs. So even our deadline expires at 09:15, the deadline message would appear only at 09:17hrs after execution of the background program.
    Some more points
    In our above example, we have used the deadline on the “Work Item” creation time. i.e., 5 minutes after creation time, the deadline message would be sent. Now we would check the other option “Expression”. Here we can mention the date and time, when the deadline message should appear irrespective of the work item creation date/time.
    As seen in the above screenshot, we can provide the target date and time by which the task should be finished. Container elements could be used in this case. Please refer to our example on creation of container elements (click here).
    Personal Substitute in Workflow
    Requirement: Need to have at least one substitute who can act upon work items in your absence.
    Important: The appointed substitute would be able to see all your work items. A substitute cannot be assigned for only particular area of organization or any other item. So need to ensure that the substitute have the necessary authorizations to act upon the work items.
    Procedure:
    1. Go to SAP Business Work Place (TCode: SBWP)
    2. Now from the menu bar, select Settings à Workflow settings à Maintain Substitute
    3. Highlight/Select the name on the window, in this case SAPDEV02 and click on “Create Substitute”.
    4. List of users available in the system are displayed.
    5. Select the required substitute user name. Following screen appears.
    Validity field describes about the period in which the setting would be active. Note that the dates on the screen would range from the current date to 31st Dec 9999.
    Regarding the checkbox “Substitution active”, it is advised to leave this checkbox unchecked for system performance reasons. A check in this box indicates that the substitution is “permanent” and if left unchecked it is treated as “as-needed”. A permanent substitute will automatically receive the primary users work items in their own box. In the case of “as-needed”, substitute must manually adopt the work items from the primary user’s inbox.
    6. Save the entries
    7. Click Enter to leave the screen.
    Adopting a Substitute in Workflow
    If you have been designated as an “as-needed” substitute, you must manually adopt the substitution. If you are designated as a “permanent” substitute, the work items would automatically appear in the inbox.
    Before adopting a substitution, there are 19 work items in the inbox. See the screenshot below:
    To adopt a substitution, select Settings à Workflow settings à adopt substitution.
    Select the corresponding User-id (if you have been assigned as a substitute for multiple people, then this option would allow you to select the user name of whom you would to check the work items)
    The corresponding user’s work items would appear in our inbox now.
    You can end the substitution, by selecting settings à Workflow settings à End substitution.
    Note: Substitutes can only adopt work items that are directly routed to the person for whom they are a substitute. If you are a substitute for a user (SAPDEV02) who has been made a substitute for another user (SAPDEV01), you will only see work items for user SAPDEV02 and not of the user SAPDEV01.
    Notification of Work Items via e-Mail
    SAP provides us with a facility of notifying the user via the email address of your choice when there are any pending work items in the SAP Inbox..
    1. Go to Transaction SO13.
    2. Click on Automatic Forwarding tab.
    3. Click on Create icon .
    4. Enter the details in the above screen.
    5. Click ENTER to complete the entries.
    6. Now the notification would be received at the provided email address if there are any pending work items in the inbox.
    Filtering the Work Items in the SAP Inbox using BADI
    This document details about the procedure in filtering some of the work items from the SAP inbox using a BADi.
    Following is the screenshot of the SAP inbox, before implementing BADi:
    The BADi that is used in filtering the work items is WF_BWP_SELECT_FILTER. To implement the BADi, go to transaction SE18. From the menu, select Implementation à Create. (See the screenshot below)
    Enter the implementation name and press ENTER
    Enter any meaningful short text for the implementation and click on the tab “Interface”
    The implementing class, ZCL_IM_BWP_SELECT_FILTER, is automatically proposed. Double click on the implementing class name.
    You are now navigated to the class builder. Now double-click on the method name shown on the screen (see the snapshot below)
    Now let us filter out the work items belonging to the task TS2000066. See the code below:
    Activate the method and also the implementation. In the state of active, you wouldn’t be able to make any changes. To make any changes, we need to deactivate it and then make the changes.
    Now check the inbox and would notice that the work items related to that task are no more appearing.
    To notice the differences, try activating and deactivating the BADi implementation.
    Workflow tutorials with step-by-step and with screenshots are available at http://www.****************/Tutorials/Workflow/Workflow.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/42/c14a9b55103116e10000000a1553f7/frameset.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/c5/e4a930453d11d189430000e829fbbd/frameset.htm
    http://www.sapgenie.com/workflow/
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2857887
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2855919
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2735228
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    debug a workflow.
    This has a step by step procedure :
    http://fuller.mit.edu/workflow/debugging.pdf
    www.erpgenie.com/sap/workflow/debugging.htm
    http://www.erpgenie.com/workflow/debugging.htm?2b5de440

  • BAPI for operation change in production order?

    Hi there,
    I want to change operation data in a production order and I can only find this BAPI:
    BAPI_ALM_ORDER_MAINTAIN
    Can this BAPI also be used for changing an production order? Because in the documentation of the BAPI this function isn't really mentioned...
    Can you give me some hints or the name of another BAPI doing this task?
    Kind regards
    Max

    yep it can be used for that, the documentation for this bapi is ( very unusual for bapis I know ) available
    call the bapi in se37. goto -> documentation
    I don't have an example for changing orders and operations but I use it to copy serviceorders (only difference between serviceorder and production order is that you can enter a customer at serviceorders)
    which are quite extensive with lot of operations and components and functional locations
    here my example for creation. for change I believe you also have to fill the UP structures accordingly to what you want to update
    kind regards
    arthur
    gs_meth-refnumber  = 1.
      gs_meth-objecttype = 'HEADER'.
      gs_meth-method     = 'CREATE'.
      gs_meth-objectkey  = c_init_ordid .
      append gs_meth to gt_meth.
      move-corresponding gs_meth to gs_ext.
      gs_meth-refnumber  = 1 .
      gs_meth-objecttype = 'PARTNER'.
      gs_meth-method     = 'CREATE'.
      gs_meth-objectkey  = c_init_ordid.
      append gs_meth to gt_meth.
      h_refnumber = 1.
      loop at gt_operations_i into gs_operations_i.
        concatenate c_init_ordid gs_operations_i-activity into gv_so_operation.
        gs_meth-refnumber  = h_refnumber.
        gs_meth-objecttype = 'OPERATION'.
        gs_meth-method     = 'CREATE'.
        gs_meth-objectkey  = gv_so_operation.
        append gs_meth to gt_meth.
        add 1 to h_refnumber.
      endloop.
      clear h_refnumber.
      loop at gt_components_i into gs_components_i.
        add 1 to h_refnumber.
        gs_meth-refnumber  = h_refnumber.
        gs_meth-objecttype = 'COMPONENT'.
        gs_meth-method     = 'CREATE'.
        concatenate c_init_ordid
                    gs_components_i-activity
                    gs_components_i-item_number
        into gs_meth-objectkey.
        append gs_meth to gt_meth.
      endloop.
      clear h_refnumber.
      loop at gt_texts into gs_texts.
        add 1 to h_refnumber.
        concatenate c_init_ordid gs_texts-activity into gv_so_operation.
        gs_meth-refnumber  = h_refnumber.
        gs_meth-objecttype = 'TEXT'.
        gs_meth-method     = 'CREATE'.
        gs_meth-objectkey  = gv_so_operation.
        append gs_meth to gt_meth.
      endloop.
    * gebruikte objecten cq functieplaatsen
      clear h_refnumber.
      loop at gt_objectlist_i into gs_objectlist_i.
        add 1 to h_refnumber.
        gs_meth-refnumber  = h_refnumber.
        gs_meth-objecttype = 'OBJECTLIST'.
        gs_meth-method     = 'CREATE'.
        gs_meth-objectkey  = c_init_ordid.
        append gs_meth to gt_meth.
      endloop.
      clear h_refnumber.
    if p_objrel = 'X' and gt_relation_i is not initial.
    * koppeling functieplaats met operatie
    * kunnen geen meervoudige koppelingen gemaakt worden in BAPI
    * dus hier 1 koppeling maken en na BAPI de rest aanleggen
      read table gt_relation_i into gs_relation_i index 1.
      add 1 to h_refnumber.
      gs_meth-refnumber  = h_refnumber.
      gs_meth-objecttype = 'OLISTRELATION'.
      gs_meth-method     = 'CREATE'.
      gs_meth-objectkey  = c_init_ordid.
      append gs_meth to gt_meth.
    endif.
      gs_meth-refnumber  = c_init_ordid.
      gs_meth-objecttype = space.
      gs_meth-method     = 'SAVE'.
      gs_meth-objectkey  = c_init_ordid.
      append gs_meth to gt_meth.
    * BAPI-call
      refresh: gt_ret, gt_numbers.
      clear:   gt_ret, gt_numbers.
      call function 'BAPI_ALM_ORDER_MAINTAIN'
        destination 'NONE'                       " --> Zie note 770626 !
        tables
          it_methods             = gt_meth
          it_header              = gt_header_i
    *       IT_HEADER_UP           =
    *       IT_HEADER_SRV          =
    *       IT_HEADER_SRV_UP       =
    *       IT_USERSTATUS          =
          it_partner             = gt_partner_i
    *       IT_PARTNER_UP          =
          it_operation           = gt_operations_i
    *       IT_OPERATION_UP        =
    *       IT_RELATION            =
    *       IT_RELATION_UP         =
          it_component           = gt_components_i
    *       IT_COMPONENT_UP        =
          it_objectlist           = gt_objectlist_i
          it_olist_relation       = gt_relation_i
          it_text                = gt_texts
          it_text_lines          = gt_text_lines
          extension_in           = gt_ext
          return                 = gt_ret
          et_numbers             = gt_numbers.
      call function 'BAPI_TRANSACTION_COMMIT'
        destination 'NONE'
        exporting
          wait          = 'X'
    *         IMPORTING
    *           RETURN        =
    *   Zie note 770626 ...
      call function 'RFC_CONNECTION_CLOSE'
        exporting
          destination                = 'NONE'
    *       TASKNAME                   =
        exceptions
          destination_not_open       = 1
          others                     = 2
    Edited by: A. de Smidt on Feb 26, 2009 5:20 PM

  • Documentation for register level programming of PCI-62XX cards

    I'm looking for documentation for register level programming of PCI-62xx series cards. Does such a document exist?
    Thanks

    Scott,
    At this time we do not have a comprehensive M Series RLP manual available.  I was not aware of any plans to deliver this document last month, so you may have been given some incorrect information, in which case I apologize.  Currently, we provide the register map along with several examples showing how to program the boards for different types of operations.  If you have any specific questions, you can post them to this forum where our developers and other customers can help out.  I hope this helps. 
    Jeremy

  • Documentation for oracle 10g graphs - pie

    Is there a documentation for building a pie chart graph using oracle 10g.
    Can someone clarify also the difference between group and slice.
    thanks.

    I run Oracle Lite on Pocket PC, and I make some simple program which did some operations on database. I know that the support for .NET is small. But I'm writing the master of science work about three mobile databases (sql ce, oracle lite and sybase) and I have to write a program which will be testing performance of those databases on the mobile device.
    Generally I hope this program will work ok. But I also have to write about fuures for example oracle database lite RDBMS, but in documentation there is only few generally informations and almost all document is about how to configure it and how to do something.
    So if you have some generally documents (I have those white papers and other pfd on oracle site) please send it to me [email protected] .

  • AIA PIP for CRM On-demans for R12

    Folks,
    One of our client is looking for AIA PIP for CRM On demand interface along with R12.
    We have never done this before, however, our understanding at the high-level is that it would require R12, FP, SOA Suite, Oracle Service Bus. Can someone point us right direction on this?
    1)What are the required components for this installs?
    2)Any documentations or links would be good
    Cheers,
    Thiru

    Can someone from this forum help us?
    Thiru

  • Documentation for category "My LiveCycle Tools", createDomDocument

    Using LiveCycle Workbench ES2, v 9.0.0.1.20100511.1.236086
    Disclaimer - I'm a novice in Workbench, and with adobe development tools, so please be patient if I am asking naive questions or going about things in a goofy way, or neglecting to include salient details.
    We are attempting to use the "createDomDocument" service operation provided by service "myLiveCycleTools".  I have been unable to find any documentation for this category or service.  Does it exist?
    We are using the DOM Document that this service operation creates to store data extracted from a barcode.  In the event the barcode is not found, we would prefer to not generate an XML file with empty tags.  We were told by an adobe rep that if the "Document" variable is NULL that the file won't be written.  I can ensure that all of the internal tags are null, but not the root element which is specified as part of the configuration of the process properties in Workbench.  I was hoping the documentation would tell me how to null out the root element as well.  Other approaches to solve the problem of creating unnecessary empty files are welcome.
    Thanks!

    I took a look at a couple of our installations for LC ES2 Update 1 (also known as 9.0.0.1) and I don't see a createDomDocument or a myLiveCycleTools service.  It looks like it may be a custom component/service.  Is there a possibility that someone in house or a contractor developed this for you?
    If you use the BarcodedFormsService operation "Extract to XML" then you can get the data into an XML format.  Then using a setValue operation with the Node Set count function should tell you how many nodes there are in your XML.  That should allow you to make decisions as to if the XML object is empty or not.

  • RE: Documentation for Forti

    Marcus Wilson wrote:
    Does anyone know of any other documentation that
    has been written for Forte' users? I've just started
    using Forte' and I was wondering if there is a book
    available that may contain sample code, examples,
    etc.I don't know of any such book, but it so happens that a colleague and I are
    hoping to fill that void. Bob Griffin and I, both in Digital's consulting
    organization, are working on a book that will capitalize on our experience on
    several Forti projects, numerous consulting engagements, and lots of teaching.
    We plan to cover the development cycle, from requirements through deployment
    and operation, with lots of specific tie-ins to Forti features, design options
    and abundant examples.
    We hope to have the book ready by mid-year or so, and are working with people
    in Forti Software, Inc. to include them in our review cycle.
    So, watch this space. If any of you think of specific topics that would be
    particularly valuable to you, please let us know and we'll see about including
    them if they aren't already in our plans.
    Tim Quinn ([email protected])
    Digital Equipment Corporation
    Nashua, NH
    (603) 881-0426

    Confirmation of reading: your message -
    Date: 6 Mar 96 14:19
    To: [email protected]
    Subject: Re: Documentation for Forte'
    Was read at 12:40, 9 Mar 96.

  • Memory full.Not enough memory for operation.

    To the Report Design Team,
    It has been suggested that I post this issue here based on another thread I started: Re: Memory full.Not enough memory for operation.
    The template contains a single 24 bit PNG image as a background in the Page Header section, plus 9 image records from a SQL Server image field over 3 pages (3 images per page).  The images are all JPG at 3000x2000 (digital camera).
    To summarize, we are experiencing three problems.
    1. CR2008SP2 Designer issues a Memory Full error when Exporting to PDF.
    2. Using a 3rd party PDF Printer (Bullzip PDF) and CR2008SP2 Designer generates a PDF, however, the CR2008SP2 API throws a "Memory full" exception suggesting Designer and API are different (see stack trace in linked message above).
    3. With only 3 images on 1 page, CR2008 Designer Export to PDF takes 110 seconds to generate a 24MB PDF while our third party PDF Printer generates the same report in 17 seconds and 580KB.
    Edited by: Don Williams on Sep 30, 2009 6:43 AM

    The .rpt file size is 14MB with the Data Save option enabled, 12MB without Data Save.  Presumably the 12MB file size is because of the 24bit PNG we have as our background.
    The Designer executes the report in less than a second and we can scroll through all pages and see the image fields perfectly.
    When we Export to PDF, the Designer takes a long time, eventually gets to the 77%, the 7th record and returns "Export report failed" followed by "Memory full".  If we export only page 1 of the 3 pages, it also returns a Memory full error.  However, when the same report is run with only 1 page, that page exports to PDF but with a ridiculously large size and export time.
    The machine has 2GB of physical memory with an 8GB pagefile with Windows 2003 (latest everything).  The process runs up to about 1GB before reporting the memory full error.
    We've also tried a variety of other suggestions posted in the other thread with no success.
    We're happy to provide the RPT file to the Report Team to diagnose the problem.  Ultimately, we need to be able to produce a 15 page report with approximately 45 images.
    Our preferred scenario is fixing problem 2.  The CR Designer seems quite capable of rendering our report and printing it to our third party PDF printer in a timely manner with small size.  However, the API reports memory full.
    The API resides in a dedicated reporting web service with NO other code except for loading the report, setting parameters and printing.  When executing, it uses up to about 1.1GB before reporting the error.
    Are there any other suggestions for fixing what we have?  Are there known problems with large images in reports?  Do we need to lodge a formal support request?
    Regards,  Grant.
    PS.  Grr and my message formatting is lost when I edited this message!!!
    There is a 1500 character limit and then all formatting is removed to save space. Break you posts into separate entries.
    Edited by: grantph on Sep 30, 2009 2:49 AM

Maybe you are looking for