Urgent! Tutorial or documentation for JDev 3.2

Please anyone can help me with some good tutorial or documentation about JDev 3.2 online.
Thanx.

Hi,
Shipped with JDeveloper 3.2.3 is a great tutorial and sample applications. You can read all about it by invoking 'HELP' and going to 'Tutorials and Sample Applications' in the contents tab. The tutorials take you through building applications from the business tier to developing several types of clients on top of it.
If you haven't already downloaded it, I recommend taking a look at Oracle9i JDeveloper version 9.0.2. This will also have samples and tutorials, but we have even more resources on the JDeveloper OTN site with samples, whitepapers, howto's.
Good luck.

Similar Messages

  • URGENT: Can not find SOA extension for JDev 11.1.1.5 anymore????

    I do not see the SOA extension when I did a check for updates anymore. Do you know where I can download this extension for JDev 11.1.1.5 please?
    Thanks

    check here at ..
    http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/156082.xml

  • Has anyone got OA Framework Tutorial working on R12 Jdev 10g?

    I have successfully got the tutorial for OA Framework working on my Apps 11.5.10 install with very few problems.
    I now have Apps R12 installed and have downloaded the correct Jdev 10g with OA Framework patch, but I am hitting some a number of errors. I can see that the tutorial code and documentation is the same as Jdev 9i, and has not been updated. Taking this in to account I am adapting the tutorial to the Jdev 10g, but I am hitting deployment problems in the local OC4J container, where AppsLogin is being requested and not found.
    I therefore wonder whether anyone out there has got the tutorial to work in Jdev 10g?
    I'm happy to try and figure it out for myself, but I would prefer to know that it is relatively straight forward to do.

    Yes I'm getting the following error message:
    oracle.apps.fnd.framework.OAException: Application: FND, Message Name: SECURITY_APPL_LOGIN_FAILED.
    I have seen this elsewhere on the forum but they all relate to Jdev 9 on 11.5.10. I wanted to know whether anyone else had got OA framework tutorial working on R12 because then I know from that one fact whether it is possible on the code that Oracle has released; any problems I encounter are then likely to be setup/installation/config issues that I should be able to resolve myself.
    I'm surprised that no one has yet just given me a 'yes' given the number of experienced developers on the forum.
    BTW, the full stack trace is:
    oracle.apps.fnd.framework.OAException: Application: FND, Message Name: SECURITY_APPL_LOGIN_FAILED. at oracle.apps.fnd.framework.server.OAExceptionUtils.processAOLJErrorStack(Unknown Source) at oracle.apps.fnd.framework.OACommonUtils.processAOLJErrorStack(Unknown Source) at oracle.apps.fnd.framework.CreateIcxSession.getEncryptedSessId(Unknown Source) at oracle.apps.fnd.framework.CreateIcxSession.createSession(Unknown Source) at runregion.jspService(_runregion.java:136) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448) at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239) at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34) at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298) at java.lang.Thread.run(Thread.java:595)
    Cheers
    Andy

  • JavaDoc documentation for new BC4J UI classes

    Hi All
    I could not find JavaDoc documentation for new UI packages (
    oracle.jbo.uicli.*** ) in JDeveloper 9i RC. Does anybody have an
    idea where can I find them?
    Regards,
    Shota

    The Javadoc for the Release Candidate is not accessible directly from the help system. You can, however, open the javadoc by using the
    "Browse Javadoc" command in the Code Editor: 1. Highlight the symbol in the Code Editor (for instance, type "JUApplication" anywhere in a
    .java file that you open in the Code Editor), 2. Right click and choose "Browse Javadoc". JDev will open the javadoc for the highlighted symbol
    and you can use the Prev link to traverse the tree until you find the desired package. In the Production release, the Javadoc will be
    accessible directly from the HelpViewer Contents pane (and thus allow searches on the Javadoc). FYI: All Javadoc appears in the /jdev/doc/ohj/
    folder in your installation.

  • Technical documentation for ADF projects - how to and best practices

    Hi,
    I have a question how to create technical documentation for ADF project expecialy ADF BC and ADF Faces. Is there any tool or JDev plugin for that purpose? What informations should contains documentation for that project, any principles ?Has anybody any experienece. Are there something like documentation best practices for ADF projects? E.g. how to create documentation for bussiness components.
    Kuba

    I'm not sure there is "best practices" but some of the things that can help people understand are:
    An ADF BC diagram - this will describe all your ADF BC objects - just drag your components into a new empty diagram
    A JSF page flow - to show how pages are called.
    Java class diagram - for Java code that is not in the above two
    One more thing to consider - since ADF BC, JSF page flow and JSPX pages are all XML based - you could write XSL files that will actually transform them into any type of documentation you want.

  • 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' :-)

  • Documentation for the As-Is and To-Be process.

    Can any one send some material regarding how to write documentation for the AS-IS and TO-BE business process for the business blue print.
             My requirement is to <u>automate the process which are receiving goods from the gate entry to GR level and finally posting goods issue</u> all should done automatically .
    Now we are gathering  information from the client according to their business process.
    Our client is digital meter product based company.
    Its an urgent thanks in advance.

    Probably the best thing to do is go to your boss/team lead/project manager/client contact and ask them what documentation they want you to produce and what should go in it.  No-one here can guess at that.
    Gareth.

  • 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

  • Demo Documentation for a Simple Cartridge Creation

    Hi,
    Thus anyone knows where i could find a Tutorial or a Demo documentation for implementing a Simple Cartridge in OSM 7.0.2?
    I'm trying to use all the components supplied from the Design Studio but i'm not understanding how to relate them and how to configure them in the correct way just by reading the documentation supplied in the installation.
    All Oracle documentation talks about concepts and the components in a separate matter, but no in a fully detailed How to implement a Cartrigde step by step, using all the components. The only tutorial that i saw was in the Developers Guide and is very, very simple.
    Thanks

    Hi,
    Following are some of the resources:
    1. From Design Studio: File -> New -> Example -> 2 examples under "Design Studio Order and Service Management Provisioning Examples"
    2. Sample SOM cartridge cartridge on OTN (I will put in some Orchestration Samples soon) -> https://www.samplecode.oracle.com/sf/projects/som/
    3. You can download the productize O2A cartridge cartridges from https://edelivery.oracle.com/. However, I would suggest you to look at option 1 & 2 before looking at the O2A cartridges.
    Cheers,
    Deepankar (Deep) Dey

  • Integration documentation for sap sd with fico and mm

    hi Sappers,
    I need Documentation for SAP SD with FICO and MM Module
    its very urgent.
    mail id : [email protected]

    <b>Some basic information :</b>
    FI-MM: The integration between FI-MM happens in T-code: <b>OBYC</b>
      1. When PO is created :
    No Entry -
      2. When GR is posted 
          Inventory Account dr (Transaction Key BSX in OBYC)
                To GRIR account (T.Key WRX in T-code OBYC)
      3. When Invoice is posted
          GRIR account Dr.
          Vendor account  Cr.
      4. Payment made to Vendor
          Vendor A/c Dr
                To Bank Clearing A/c Cr.
    Points to know : Movement Types, Assignment of Movement types to T-keys (T-code OMJJ), Value string (I also need some information on this) , OMWN and OMWB transactions. 
    There is a close integration b/w FI & MM, actually document flows from MM to FI in the following areas such as,
    <u> 1. Movement Types:</u>
    Used to enable the system to find the predefined posting rules determining how the accounts of financial accounting system are to be posted & to update the stock fields in the matrl master data.(Goods Receipt, Goods Issue, etc)
    <u> 2. Valuation Class:</u>
    Assignment of material to grp of gl account, used to determine the gl accounts that are updated as a result of goods movement.
    <u>3. Transaction/Event key:</u>
    Used to control the storage or filing of documents & assignment of documents.Used to differeniate b/w various transactions such as goods movement tht occur in inventory.
    <u> 4. Material Type:</u>
    Each material should assign mtrl type in mtrl master record used to update whether changes made in qty are updated in material master record & change in value also updated in stock account.
    <u><b> FI-SD Integration:</b></u>
    The integration is done in T-code VKOA
    <u>  1. Sales Order Created</u> 
            -No Entry-
      <u>2. PGI done (Goods issue)</u>
          Cost of Goods Sold     Dr (Configured in OBYC GBB T-Key)
               To Inventory Account
    <u>  3. Billing document released to Accounting</u>
            Customer Account Dr.
                  To Sales Revenue Account (ERL T-key in Pricing procedure)
      Note : The GL account is assigned to this ERL in VKOA
    <u> 4. Payment Received</u>
            Bank Clearing A/c Dr
                           Customer A/c Cr. 
    Points to Know : Good to understand the pricing procedure and how the different transaction keys are used like ERL, ERS etc

  • Documentation for DNG Profile Editor??

    Hi. I am looking for the tutorial and documentation on Adobe DNG Profile Editor (v 1.0.0.39 beta 2). I assume this is the latest release, but if not, I would appreciate a link to the latest. I tried downloading documentation and tutorial from the following link, but the site never comes up.
    http://labs.adobe.com/wiki/index.php/DNG_Profiles
    I'd like to build some profiles for my 5DmkII and studio lighting situations, specifically for portrait / skin tone type work. Suggestions welcome.
    Thanks,
    Lou Dina

    In the past I did some research in these fields and I want to share the fruit of that work (but English language is a problem).
    > There can be Variations Among cameras.
    I have analyzed two sets of cameras, two Canon 40D and two 400D illuminated by Solux Daylight 4700K bulbs.
    The first test was done with a 400mm. Unfortunately, very little movement of the lens at f/5.6 (a mistake) has darkened the upper rows of ColorChecker and I had to correct them with the brush of ACR Exposure (the worst intervention reaches 0.17). After this intervention the cameras differ by an average error of delta E 2000 0.30 and a maximum of 0.75.
    Link: http://www.boscarol.com/forum/viewtopic.php?f=58&t=321
    The second test was done with a Canon 400D and a Canon Rebel XTi. In theory, the same model but for different markets.
    Here the things were particularly interesting because:
    - the cameras could be build from different processes due to different market areas
    - the cameras were put on the market in 2006, and were produced with the technology of almost five years ago
    - the cameras belonged to the entry level market segment, the techniques of production could be consistent with this low target
    All these factors could lead really to differences in behavior. The results were an average error of 0.65 and a maximum of 1.26.
    Link: http://www.gialandra.it/blog/files/343e438a6021337b5fdffb2cfbe0f08b-0.html
    And probably if these tests had been made in laboratory the differences were even smaller.
    I concluded that the differences in the behavior are all to prove.
    On the Internet I found nothing of scientific.
    > There are subtle Also Variations Among Conditions lighting, as well as chart shooting conditions (Exactly how the light is falling on the chart, the angle at Which you photograph the chart, etc.)..
    These are the most important points. If the chart shooting conditions are a bit easier to control with geometry, get a light with a spectral power distribution right it is very difficult (and I suspect that even Adobe has not a decent D65 simulator). To obtain a light close to illuminant D50 I use 4700K Daylight Solux bulbs without glass diffuser. In front to the lamps I mounted a shape ring protection with a hole less than two centimeter (to avoid protection I have tried the black back version of the Solux bulbs but they do not have the correct spectral power distribution). Bulbs are powered by an adjustable power supply. Using the spectrometer as a feedback I can reach a CRI of 97.
    It seems to me that even the not winter sunlight when the atmosphere is really clear is close to the D50, but I've never had a chance to measure it. In this condition the problems of non-uniform illumination do not exist, but be careful with the camera and target angles because the light is even more violent, the target should be perfectly at 45 degrees and the sensor should be parallel to the target.
    Finally to have a more homogeneous illumination and all other problems I use only the mini format of the ColorChecker.
    > There Are Also Among Variations lenses (eg, spectral transmission of Canon 50 f/1.4 is Not the same as Canon 180 f/3.5 macro, But They Are close).
    I have studied the effect of five very different lenses in type, brand, cost, etc.. The spectral transmittance of the lens was so different to cause a shift of the white balance of 450K. On films this would lead to very different results, on digital system instead the human visual system is not able to appreciate differencies (worst deltaE 2000 is 1)
    Link: http://www.photoactivity.com/Pagine/Articoli/052ResaCromaticaObiettivi/Resa_cromatica_degl i_obiettivi_ENG.asp
    For my studies and my experience at this moment I think the best way to find the faithfull to the scene with a safe semi-universal profile is using the calibration sliders in D50 condition. From the linked experience below this gives faithfull from tungsten light (2600K) to above 10000K, of course this last only in daylight.
    Link: http://www.photoactivity.com/Pagine/Articoli/023%20Calibratori%20al%20sole/Calibratori%20a l%20sole_en.asp
    In this context I still use the script of Tindemans but it is time (many years now) that Adobe produces his matrices tweaker (XRite Passport stresses the matrices as far as possible before creating some sort of table)
    I hope that I'm not boring
    Ciao
    Marco

  • How to write professional documentation for java

    Hi, I have few application I need to write documentation for. Im ok with the user and serwer technical stuff. But how to write proper documentation for source code? Any tutorial or howto?
    Best regards.

    Phenom7 wrote:
    Hi, I have few application I need to write documentation for. Im ok with the user and serwer technical stuff. But how to write proper documentation for source code? Any tutorial or howto?A pointer: be explicit and specific when writing Javadocs. If your method never returns null, make sure you say so. If it can't accept null as a parameter, be sure to say what the consequence will be if it happens (but it's OK to say the result is undefined!). A well-written method Javadoc will make users of any API you make a lot more happy, rather than keeping them guessing or making them inspect your source code.
    It's expected that while the implementation of a method will change, its pre and post-conditions will not. Therefore, having a good method-level Javadoc is critical to both the people counting on your code and the people maintaining your code.

  • Documentation for Menu widget... forget it!

    Why do we have no manual or documentation foe Adobe Muse?
    Just try and find documentation for the menu widget, first go on line because there is no help for Muse with the software. There is no menu widget listed. Guess "slideshows and widgets", expand more to see all the items - wow, I found it! Click on "Customizing the state of the Horizontal Menu widget". Perfect. Click on it. You go to "Building your first website with Muse" page. Great a tutorial, not documentation - oh well. Look for menu.
    It doesn't actually appear there - sorry! Find it yourself. Look its says they already showed it in part 2. Great, I love spending time just looking for help. Click on part 2.
    Read the whole page - a tutorial. No documentation for the submenus. Of course, it's a tutorial, not a manual.
    Go back to the help page, type Muse menu widget in the search box. Great a video tutorial. Watch it, then it refers to the next video where we will style the video.It's not listed on the page anywhere. You must have to buy the series.
    Screw the docs, try it yourself. Look - edit together is on, change the font, they all change but only in that sub menu. Change the menu item size, only that one changes. Oh so edit together only refers to each submenu and not all the changes. Wow, I should read the documentation - oh I forgot, THERE ISN'T ANY.
    Am I the only one who wishes we could get a reference doc for this app or is that to much to ask of Adobe? What good is saving time building websites with Muse when you have to be a detective and spend lots of time finding out how to use it. This is SO LAME. We need a manual. Not just "lets build a website tutorials".

    With the rapid growth of Muse a manual just wouldn't be practical. There are plenty of resources on the web; Adobe site, Lynda.com, lots of independant tutorials and probably the best resource (besides Lynda.com) is this forum right here. Google is everyone's friend ..... can find anything and faster than in any manual.
    But with the way technology software changes at such a high rate manuals would be out of date before they are printed. I doubt we will see manuals for any Adobe software. It's just not Adobe going this way.

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

  • Documentation for wscompile?

    I finally got around to updating to jwsdp-1_0_01 and was surprised to find that xrpcc was replaced by wscompile in many build.xml files. Except for a few very general remarks in the Tutorial, I can't find any documentation for wscompile at all (Google returns only 4 pages for "wscompile"!).
    Is xrpcc deprecated? (When my old build.xml runs xrpcc, it gives a warning that "sun.tools.javac.Main is deprecated".) Is there a man page, etc., for wscompile?
    Thanks,
    Mike

    Oops, the format of my last message got munged. Here's anoter try:
    Date: 28 Aug 2002
    Title: The JAX-RPC wscompile and wsdeploy Tools
    1 The wscompile Tool
    The wscompile tool generates stubs, ties, serializers,
    and WSDL files used in JAX-RPC clients and services.
    The tool reads as input a configuration file and either
    a WSDL file or an RMI interface that defines the service.
    1.1 Syntax
    wscompile [options] <configuration-file>
    By convention, the configuration file is named config.xml,
    but this is not a requirement.
    The following table lists the wscompile options.
    Note that exactly one of the -import, -define,
    or -gen options must be specified.
      Option                    Description
      -classpath <path>         specify where to find input class files
      -cp <path>                same as -classpath <path>
      -d <directory>            specify where to place generated output files
      -define                   read the service's RMI interface,
                                define a service
      -f:<features>             enable the given features (See the below
                                table for a list of features.  When
                                specifying multiple features, separate
                                them with commas.)
      -features:<features>      same as -f:<features>
      -g                        generate debugging info
      -gen                      same as -gen:client
      -gen:client               generate client artifacts (stubs, etc.)
      -gen:server               generate server artifacts (ties, etc.) and
                                the WSDL file (If you are using wsdeploy
                                you do not specify this option.)
      -gen:both                 generate both client and server artifacts
      -httpproxy:<host>:<port>  specify a HTTP proxy server (port defaults to 8080)
      -import                   read a WSDL file, generate the service's RMI
                                interface and a template of the class that
                                implements the interface
      -keep                     keep generated files
      -model <file>             write the internal model to the given file
      -nd <directory>           specify where to place non-class generated files
      -O                        optimize generated code
      -s <directory>            specify where to place generated source files
      -verbose                  output messages about what the compiler is doing
      -version                  print version information
    The following table lists the features (delimited by commas) that
    may follow the -f option.
      Feature                   Description
      datahandleronly           always map attachments to the DataHandler type
      explicitcontext           turn on explicit service context mapping
      infix=<name>              specify an infix to use for generated serializers
      nodatabinding             turn off data binding for literal encoding
      noencodedtypes            turn off encoding type information
      nomultirefs               turn off support for multiple references
      novalidation              turn off full validation of imported WSDL documents
      searchschema              search schema aggressively for subtypes
      serializeinterfaces       turn on direct serialization of interface types
    1.2 Configuration File
    The wscompile tool reads the configuration file (config.xml),
    which contains information that describes the web service.
    The basic structure of config.xml follows:
    <?xml version="1.0" encoding="UTF-8"?>
    <configuration 
        xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
       <service> or <wsdl> or <modelfile>
    </configuration>
    The <configuration> element may contain exactly one
    <service>, <wsdl>, or <modelfile> element.
    1.2.1 The <service> Element
    If you specify this element, wscompile reads the
    RMI interface that describes the service and
    generates a WSDL file.
    In the <interface> subelement, the name attribute specifies the
    service's RMI interface, and
    the servantName attribute specifies the class that implements
    the interface.
    For example:
    <service name="CollectionIF_Service"
             targetNamespace="http://echoservice.org/wsdl"
             typeNamespace="http://echoservice.org/types"
             packageName="stub_tie_generator_test">
         <interface name="stub_tie_generator_test.CollectionIF"
          servantName="stub_tie_generator_test.CollectionImpl"/>
    </service>
    1.2.2 The <wsdl> Element
    If you specify this element, wscompile
    reads the service's WSDL file and generates
    the service's RMI interface.
    The location attribute specifies the URL of the WSDL
    file, and the packageName attribute specifies
    the package of the classes generated by wscompile.
    For example:
    <wsdl    
        location="http://tempuri.org/sample.wsdl"
        packageName="org.tempuri.sample" />
    1.2.3 The <modelfile> Element
    This element is for advanced users.
    If config.xml contains a <service> or <wsdl> element,
    wscompile generates a model file that
    contains the internal data structures that describe
    the service.
    If you've already generated a model file in
    this manner, then you can reuse it the
    next time you run wscompile.  For example:
    <modelfile location="mymodel.xml.gz"/>
    2.0 The wsdeploy Tool
    The wsdeploy tool reads a WAR file and the jaxrpc-ri.xml
    file and then generates another WAR file that is ready for
    deployment.
    Behind the scenes, wsdeploy runs wscompile with the -gen:server option.
    The wscompile command generates classes and a
    WSDL file which wsdeploy includes
    in the generated WAR file.
    2.1 Syntax
    The syntax for wsdeploy follows:
    wsdeploy <options> <input-war-file>
    The following table lists the tool's options.
    Note that the -o option is required.
      Option                    Description
      -classpath <path>         specify an optional classpath
      -keep                     keep temporary files
      -o <output-war-file>      specify where to place the generated war file
      -tmpdir <directory>       specify the temporary directory to use
      -verbose                  output messages about what the compiler is doing
      -version                  print version information
    2.2 The Input WAR File
    Typically, you create the input WAR file with a
    development tool or with the ant war task.
    Here are the contents of a simple input WAR file:
    META-INF/MANIFEST.MF
    WEB-INF/classes/hello/HelloIF.class
    WEB-INF/classes/hello/HelloImpl.class
    WEB-INF/jaxrpc-ri.xml
    WEB-INF/web.xml
    In this example, HelloIF is the service's RMI interface
    and HelloImpl is the class that implements the interface.
    The web.xml file is the deployment descriptor of a
    web component.  The jaxrpc-ri.xml file is described
    in the next section.
    2.2.2 The jaxrpc-ri.xml File
    The listing that follows shows a jaxrpc-ri.xml file
    for a simple HelloWorld service.
    <?xml version="1.0" encoding="UTF-8"?>
    <webServices
        xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
        version="1.0"
        targetNamespaceBase="http://com.test/wsdl"
        typeNamespaceBase="http://com.test/types"
        urlPatternBase="/ws">
        <endpoint
            name="MyHello"
            displayName="HelloWorld Service"
            description="A simple web service" 
            interface="hello.HelloIF"  
            implementation="hello.HelloImpl"/> 
        <endpointMapping
            endpointName="MyHello"
            urlPattern="/hello"/>
    </webServices>
    The <webServices> element must contain one or more <endpoint>
    elements.  In this example, note that the interface and
    implementation attributes of <endpoint> specify the
    service's interface and implementation class.
    The <endpointMapping> element associates the service
    port with an element of the endpoint URL path
    that follows the urlPatternBase.
    3 Advanced Topics
    This section is for developers who are familiar with
    WSDL, SOAP, and the JAX-RPC specifications.
    3.1 Namespace Mappings
    Here is a schema type name example:
    schemaType="ns1:SampleType"
    xmlns:ns1="http://echoservice.org/types"
    When generating a Java type from a schema type,
    wscompile gets the class name from the local part of
    the schema type name.
    To specify the package name of the generated
    Java classes, you define a mapping between
    the schema type namespace and the package name.
    You define this mapping by adding a <namespaceMappingRegistry>
    element to the config.xml file.  For example:
    <service>
        <namespaceMappingRegistry>
                <namespaceMapping            
                namespace="http://echoservice.org/types"
                packageName="echoservice.org.types"/>
         </namespaceMappingRegistry>
    </service>
    3.5 Handlers
    A handler accesses a
    SOAP message that represents
    an RPC request or response.
    A handler class must implement
    the javax.xml.rpc.handler interface.
    Because it accesses a SOAP message,
    a handler can manipulate the message with
    the APIs of the javax.xml.soap package.
    Examples of handler tasks:
    * Encryption and decryption
    * Logging and auditing
    * Caching
    * Application-specific SOAP header processing
    A handler chain is a list of handlers.
    You may specify one handler chain for the client
    and one for the server.
    On the client, you include the <handlerChains> element
    in the jaxrpc-ri.xml file.  On the server, you
    include this element in the config.xml file.
    Here is an example of the <handlerChains> element
    in config.xml:
    <handlerChains>
      <chain runAt="server"
         roles=
          "http://acme.org/auditing 
           http://acme.org/morphing"
           xmlns:ns1="http://foo/foo-1">
        <handler className="acme.MyHandler"
          headers ="ns1:foo ns1:bar"/>
          <property 
            name="property" value="xyz"/>
        </handler>
      </chain>
    </handlerChains>
    For more information on handlers, see the SOAP Message Handlers chapter
    of the JAX-RPC specifications.

Maybe you are looking for