Documentation for COM interface

After iTunes 10 has been released, I thought there would be new documentation for the COM interface.
Anybody know where to find it?
Regards
Thomas

I second Dave's message. The only available version of the documentation is V.8.1.0.52. There have been significant changes such as the creation of the Media Kind property which have yet to be reflected in a new SDK, although as far as I can tell, the methods & properties provided in the older document are all still valid. If you need help finding the "current" documentation start here:
http://www.paraesthesia.com/archive/2009/05/20/itunes-com-for-windows-sdk-now-in -adc.aspx
tt2

Similar Messages

Documentation for com.sap.isa.FrameworkConfigManager

Hi,
We have a new Java developer that doesn't have experience with SAP E-Commerce 5.0 (specifically B2B) and I have been given the task to gather up as much documentation as possible for him.
So far I have found these documents:
- IPC in SAP ECommerce for mySAP ERP.pdf
- SAP E-Commerce for mySAP ERP: Business Scenario Configuration Guide.pdf
- SAP E-Commerce 5.0: Examples and Tutorials.pdf
- SAP E-Commerce 5.0 u2013 Landscape, Basics and Concepts.pdf
- SAP Internet Sales (R/3 Edition) in a B2B Scenario.pdf
He now came back to me and wants specific documentation on: com.sap.isa.FrameworkConfigManager
Does anyone know where I can find this?
Thank you in advance!
Neil

Hi Neil,
If you are looking for java documentation.
then
[thread for java documentation|SAP CRM Internet Sales (ISA) Java Framework API;
Regards,
Devender V

Documentation for com.waveset.provision.WorkflowServices

There seems to be little documentation I can find that describes the various options (specifically, the various <Argument> names) that are used by
the WorkflowServices object.
My immediate challenge is simply sending an email from a workflow. I keep getting the error message: "com.waveset.util.WavesetException: msgBody must be specified." I'm assuming that the Arguments passed to the task should match the variable names used by the email template.
Also, there seem to be inconsistencies in naming: 'to' vs. 'toAddress', 'from' vs. 'fromAddress', etc. Again, due to templates?
Thanks in advance for help/pointers.

I ran in to a similar problem.
It turned out that my email template was corrupt. I also didn't find out what the argument name should be. msgBody didn't seem to work.
BR
Per

Documentation for Objects exposed by the Acrobat COM

I am a developer trying to automate several parts of the Adobe Acrobat Pro functionality, however I cannot seem to find documentation describing the Object Model behind Acrobat Pro. I have seen many example for performing very simple operations (opening, printing, modifying PDFS) however the actions i am looking to do are much more complex, and I need to know the limitations behind the exposed interface to Acrobat. More specifically, I am looking to automating the following:
1. A PDF file is created via another automative process
2. A Visual Basic script, using the COM interface activates the PDF as a document that can be "reviewed"
3. The script than drops the file into the designated PDF Review Server location.
4. The script than needs to use the Acrobat COM to communicate with the server and register the PDF as a document ready to be reviewed.
5. Finally, the reviewers need to be added to the document.
A really good start would be a document that describtes the basic COM objects, i.e. what is the difference between an AcroPDDoc and an AcroAVDoc.
Thanks for the help guys.

All the documentation is in the Acrobat SDK.

Documentation for Oracle XML parser Classes and Interfaces

I would like to use the oracle XMLParser V2 classes with JDeveloper 3.1, but I cannot find any reference documentation for the classes and interfaces in help.
I am especially interested in a documentation for the XSLProcessor class. The only information I found was provided with the few provided samples.

I don't think the javadoc for this was included in the release. You can get the Javadoc (as well as the latest version of the XML Parser v2) here on OTN.
Take Care,
Rob
null

Error: the QueryInterface call on the COM component for the interface with IID '{00063033-0000-0000-C000-000000000046}' failed due to the following error: Library not registered.

I have a outlook 2007 plugin created in VS 2008 that reads calendar meetings. This plugin also works with outlook 2010. I used to debug this application from VS 2010 as well.
Last month, I installed Office 365 to test something. Later I uninstalled this version but after that my plugin application is crashing, every time a new appointment/meeting is created in calendar.
I get the below error:
Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Office.Interop.Outlook._AppointmentItem'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{00063033-0000-0000-C000-000000000046}'
failed due to the following error: Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED)).
Tekriti Software

Thanks for your sharing and have a nice day.
Yoyo Jiang[MSFT]
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

COM interface SDK call for "Media Type = Audiobook?"

I imported the type library from iTunes 8.0.1 this afternoon, and it seems identical to the library from iTunes 7.
Is there an interface or API call I can use to retrieve and/or set the "Media Type" field on an audio file? (To set it to either "Music" or "Audiobook"?)
I had thought it might share an interface with the "VideoKind" call, since they share a pull-down in iTunes now, but both .m4b format and .mp3-tagged-in-"Get Info" style audiobooks read the same as music files on that interface.

Your question inspired me to finally update my Audiobook helper application to work with iTunes 8. Since there doesn't appear to be a COM interface for the Media Kind, I used AutoIT to simulate keypresses and GUI events. You can download it here:
http://mysite.verizon.net/teridon/audiobook_helper/index.html
Take a look at the AutoIT source included in that download (teridonsaudiobookhelper.au3) starting at line 1360. You may wish to install AutoIT so you can look at the help file for the functions I used.
http://www.autoitscript.com/AutoIt/
The forum TOS requires me to say: "I may receive some form of compensation, financial or otherwise, from my recommendation or link" because I have a paypal donation link on my webpage, but the program is free (donation totally optional)
HTH,
Rob

ITunes COM Interface Documentation

hi all
I want to know ,how to add the photos to ipod in iTunes COM Interface Documentation .
please help me ,
thanks.
my email: [email protected]

I don't think the COM interface supports what you want to do. You can get the documentation here:
http://developer.apple.com/sdk/itunescomsdk.html

I can't find documentation for this app

Hello,
Where is the documentation for GarageBand for iOS? I installed it on my iPod, but the interface is confusing, so I need to find the right manual. All the manuals for GB on the Apple manuals page seem to be for desktops and laptops, etc.
I know there are help files, but I do not have a wireless account so I can't access the Internet from my iPod.
Any suggestions? Thank you!

And here is a link to the iPhone/iPod version of the online help:
http://help.apple.com/garageband/iphone/1.3/index.html
Download the pages on a computer, that has internet and print them to pdf, then combine them to one pdf document and sync that document as an iBook to your iPod using iTunes.
You may want to use the Send feedback. link to let Apple know that a pdf version of the Help is needed.

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

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 wouldnt 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. Lets 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.
Dont worry if the deadline message doesnt 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 users 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 users 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 wouldnt 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

Technical documentation for Procurement Scenario

Hi,
Does anyone have the technical documentation for the Procurement Scenario? We would like to enhance this scenario but first, we would like to understand all the components it uses, from the user interface layer down to the backend layer. So far all the documentation I have seen from SAP are for business/functional demonstrations, but there are no documents that go into the technical level.
Any help would be greatly appreciated.

Hi basilio,
see these links
https:/.../irj/sdn/go/portal/prtroot/docs/webcontent/uuid/ff03d072-0501-0010-aa88-8018506a2ebe?prtmode=print - 32k
help.sap.com/saphelp_srm30/helpdata/en/d3/4b9c3b122efc6ee10000000a114084/content.htm - 47k
help.sap.com/bp_bblibrary/600/Documentation/J49_Scen_Overview_EN_TH.ppt
www.learn4good.com/jobs/language/english/search_resumes/info_technology/uk_england/cv/205032/ - 42k
thanks
karthik
happy learning

Documentation for ant task wscompile ??

Is there any documentation for the ant task wscompile? In the HelloWorld example, the task is mapped to this class:
com.sun.xml.rpc.tools.ant.Wscompile

I do not know if any documentation exists but I have generated some for my own use. You are welcome to it and please let me know of any inaccuracies :)
Attribute : Description => Required
classpath : Specify where to find input class files. => Yes.
base : Specify where to place generated output files. => No; defaults to present directory.
define : Defines a service using the Java classes. => No, but exactly one of the import, define, or client attributes must be specified.
features : Enable the given features. => No; Features should be specified seperated by a space character.
debug : Generate debugging info. => No; defaults to false.
both : Generate both client and server artifacts (ties, etc.) => No; defaults to false.
client : Generate client artifacts (stubs, etc.). => No, but exactly one of the import, define, or client attributes must be specified.
server : Generate server artifacts (ties, etc.). => No; defaults to false.
source : Generate code for the specified JAXRPC SI version. Supported values are: 1.0.1, 1.0.3 and 1.1 => No; defaults to 1.1
proxyServer : URL of the proxy server including hostname and port. => No; defaults to localhost:8080.
import : Generate interfaces and value types only. => No, but exactly one of the import, define, or client attributes must be specified.
keep : Keep generated files. => No; defaults to true.
mapping : Write the 109 mapping file to the given file. => No.
model : Write the internal model to the given file. => Yes.
nonClassDir : Specify where to place non-class generated files. => No; defaults to present directory.
optimize : Optimize generated code => No; defaults to false.
config : Configuration file for generating webservice. => Yes.
sourceBase : Directory for storing the generated source files. => No; defaults to present directory.
verbose : Output messages about what the compiler is doing. => No; defaults to false.
version : Prints version information. => No; defaults to false.
xPrintStackTrace : Prints stack trace of the errors. => No; defaults to false.
xSerializable : Generate value types that implement Serializable interface. => No; defaults to false.
xDebugModel : Write readable version of the model to a file. => No.

Documentation for developing non-syncML iSync plugins

Hi there,
I'm interested in developing a third-party iSync plugin/conduit for a phone that, for reasons unknown, doesn't support SyncML; I have the graces of its developers in order to do so, and I will shortly be supplied with adequate documentation for the protocol used. However, nowhere on developer.apple.com can I find any pertinent information of how to instigate a different exchange method rather than SyncML. If anyone has any pointers, I'd really appreciate them!

However, nowhere on developer.apple.com can I find any pertinent information of how to instigate a different exchange method rather than SyncML.
There isn't any other exchange methods that iSync can use - it's all SyncML based. SyncML is the industry standard, so if the phone doesn't use it, you'll have to write a proprietary application to sync it, which would work independently of iSync.
Once you've read data off the phone into the proprietary application, you could interface with SyncServices (the Mac OS X framework that handles all system-wide syncing) to get that data into Address Book and iCal.
http://developer.apple.com/macosx/syncservices.html
To be honest, supporting proprietary syncing protocols is a dead-end cause and even Apple abandoned it with the release of iSync 2.
Depending on how much you value your time at, it would be many times cheaper just to buy a SyncML enabled phone that would work with iSync from the outset.

Documentation for timesheet WDA app in EP5?

Hi All,
Please let me know where i can find documentation for WDA timesheet application . I heard this was included in the EP 5.
I do not have EP5 , so i require the documentation/links to the interface, functionalities of the application.
Thanks for the help.
Pris

Hi Rajeev,
Please create role/group for WD applciation which you want to assign read/read & write to the users. Access the role/group in WD application and restrict the access to UI Element properties.
Refer to below documents for protecting Access to the Web Dynpro Application Using UME Permissions.
[help.sap.com|http://help.sap.com/saphelp_nw04/helpdata/en/f3/a64d401be96913e10000000a1550b0/content.htm]
[Exmaple|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/297f35cf-0201-0010-00b2-fe2f3e23d360?QuickLink=index&overridelayout=true]
Hope it will helps
Regards
Arun

Documentation for COM interface

Similar Messages

Maybe you are looking for