<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title>SAP Inside.com</title>
		<link>http://www.sapinside.com/</link>
		<description>All of SAP R/3</description>
		<language>ko</language>
		<pubDate>Tue, 19 May 2009 19:30:07 +0900</pubDate>
		<generator>Tistory 1.1 (http://www.tistory.com/)</generator>
		<image>
		<title>SAP Inside.com</title>
		<url><![CDATA[http://cfs10.tistory.com/upload_control/download.blog?fhandle=YmxvZzE4OTQzMEBmczEwLnRpc3RvcnkuY29tOi9hdHRhY2gvMC8wLmpwZw%3D%3D]]></url>
		<link>http://www.sapinside.com/</link>
		<description>All of SAP R/3</description>
		</image>
		<item>
			<title>[SAP SD] Sales Order Confirm Quantity Date</title>
			<link>http://www.sapinside.com/676</link>
			<description>&lt;br /&gt;
&lt;STRONG&gt;Confirm quantity date is next day.&amp;nbsp; I have created a sales order for 6 Tons.I have a stock of 10 Tons which is not reserved for any Sales order. I mean it is unrestricted stock.&amp;nbsp;&amp;nbsp; After creating sales order system should show as Doc date for confirming quantity for dispatch but it is showing the next day in the schedule line.&amp;nbsp; What could be the reason?&lt;FONT color=#000000&gt;&lt;/FONT&gt;&lt;/STRONG&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;The reason could be there should be processing times configured in the system like..pick/pack times, transit time. Please check the shipping point and also the route for different lead times.&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;The other possibility could be holidays.&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;First check what the requested delivery date you have put in the order. Next check the lead times, for that you can go to the schedule line of the item and click on the Procurement tab.&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;Check in OVLZ ---&amp;gt; In Pick/pack time wrkdys, any value is maintained there. For example, if 5 is given in this field, even if stock is available on the same day of order creation, system will allow to do PGI only after 5 days from the date of order created.&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;Also go to VOV8, select your sale order type and check the Field &quot;Lead Time in Days&quot;.&lt;/FONT&gt; &lt;br /&gt;
&lt;FONT color=#000000&gt;&lt;/FONT&gt;&amp;nbsp;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;B&gt;&lt;FONT color=#000000&gt;I&#039;m using service material in my sales order and I need the schedule line to confirm the quantity always in the actual day (not depending on the delivery date).&lt;/FONT&gt;&lt;/B&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;T. Code: VOV8&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;Select your Sales Doc. type and Double-Click.&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;In Tab: Shipping,&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;Check Box: Immediate Delivery (press F1 to read more about this functionality).&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;Note: There are few more settings that you may check:&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;1. T. Code: OVLZ&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;Field: Pick/pack time wrkdys whether you have maintained any value. It should have been blank&amp;nbsp;&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;2. T. Code: VOV8&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;Check how many days mentioned in Lead time in Days. If it is mentioned any days, remove it.&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;3. T. Code: OVZ9&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;Checked the Box: Check without RLT .&lt;/FONT&gt;&lt;FONT color=#000000&gt;&lt;/FONT&gt; 
&lt;P&gt;&lt;FONT color=#000000&gt;4. Check in material master MRP2 view how many days are maintained for the fields In-House production and GR Processing Time.&lt;/FONT&gt; &lt;/P&gt;&lt;div class=&quot;entry-ccl&quot; style=&quot;clear: both; text-align: right; margin-bottom: 10px&quot;&gt;
	&lt;img id=&quot;ccl-icon-676-0&quot; class=&quot;entry-ccl-by&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black01.png&quot; alt=&quot;저작자 표시&quot;/&gt;
	&lt;img id=&quot;ccl-icon-676-1&quot; class=&quot;entry-ccl-nc&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black02.png&quot; alt=&quot;비영리&quot;/&gt;
	&lt;img id=&quot;ccl-icon-676-2&quot; class=&quot;entry-ccl-nd&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black03.png&quot; alt=&quot;변경 금지&quot;/&gt;
	&lt;!--
	&lt;rdf:RDF xmlns=&quot;http://web.resource.org/cc/&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;
		&lt;Work rdf:about=&quot;&quot;&gt;
			&lt;license rdf:resource=&quot;http://creativecommons.org/licenses/by-nc-nd/2.0/kr/&quot; /&gt;
		&lt;/Work&gt;
		&lt;License rdf:about=&quot;http://creativecommons.org/licenses/by-nc-nd/&quot;&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Reproduction&quot;/&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Distribution&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Notice&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Attribution&quot;/&gt;
			&lt;prohibits rdf:resource=&quot;http://web.resource.org/cc/CommercialUse&quot;/&gt;
		&lt;/License&gt;
	&lt;/rdf:RDF&gt;
	--&gt;
&lt;/div&gt;
</description>
			<category>SD</category>
			<category>sd</category>
			<author>ynzyna ynzyna</author>
			<guid>http://www.sapinside.com/676</guid>
			<comments>http://www.sapinside.com/676#entry676comment</comments>
			<pubDate>Mon, 23 Feb 2009 08:20:13 +0900</pubDate>
		</item>
		<item>
			<title>[SAP QM] How To Configure A Certificate Profile</title>
			<link>http://www.sapinside.com/675</link>
			<description>&lt;P&gt;&lt;B&gt;&lt;/B&gt;&amp;nbsp;
&lt;P&gt;&lt;B&gt;1. What is certificate profile? What is the use of certificate profile in QM?&lt;/B&gt;&lt;B&gt;&lt;/B&gt; 
&lt;P&gt;&lt;B&gt;2. I have created certificate Profile using T-code. qc01 and assigned that to material with the help of QC15. Suppose I forgot that material No. and after some days I want to know for which material I have attached that cerificate profile.&lt;/B&gt; 
&lt;P&gt;&lt;B&gt;COA Profile&lt;/B&gt; &lt;br /&gt;
A certificate profile controls inspection lot selection, the sequence of characteristics, and the characteristic data.COA Profile contains the List of MICs in desired sequence in which the result for them is supposed to be printed in the COA. 
&lt;P&gt;Within the certificate profile, you determine the selection and sequence of the characteristics whose results are to be documented on the certificate. You can vary the origin and representation of the data for each characteristic. You can also withhold certain information from the certificate, if, for example, you do not want to reveal a certain measured value. 
&lt;P&gt;At the header level of the certificate profile, you can define restrictions for selecting inspection lots and partial lots. For example, you may want to specify that only lots with a quality score of at least 80 are considered. At certificate creation, the system selects all inspection lots and partial lots for the material (and batch, if necessary) that meet the selection criteria and have a usage decision. The characteristics are then retrieved from the most recent inspection lot or partial lot in this list. (The lot creation date is the determining factor.) 
&lt;P&gt;In COA Profile, you want to know what are the materials assigned. &lt;br /&gt;
Here are the options available: &lt;br /&gt;
1. In COA profile QC02/QC03 screen there is a tab available named as &quot;ASSIGNMENTS&quot;, just click on it and it will give you the details. &lt;br /&gt;
2 The best way is Run trx QC17. and know the list. 
&lt;P&gt;&lt;B&gt;How to configure a certificate profile on QC01/QC02. In fact, I need to know how to make for the inspection results of the characteristics be printed under a form of a short text.&lt;/B&gt; 
&lt;P&gt;The steps for Certificate profile creation ( QC01) are: &lt;br /&gt;
&amp;nbsp; &lt;br /&gt;
- Assign a name to the Certicate profile. &lt;br /&gt;
- Select the Certificate type &lt;br /&gt;
- Assign a selected set (here you have to select a Form. The defaut one is:&amp;nbsp; &lt;br /&gt;
&amp;nbsp; QM_QCERT_01. &lt;br /&gt;
- Add a search field and short text (It´s as a reference), &lt;br /&gt;
- Press &quot;Charcterisitc&quot; bottom and add the characteristic you want to be printed in the quality certificate. The first column &quot;Number&quot; indicates the positions about the characterisitcs (sequence) &lt;br /&gt;
- By each char. select the &quot;Result Selection level&quot;, &quot;Short Text&quot;, &quot;Insp Spec Origin&quot;, &quot;Strategy for Skip&quot; &lt;/P&gt;&lt;br /&gt;&lt;div class=&quot;entry-ccl&quot; style=&quot;clear: both; text-align: right; margin-bottom: 10px&quot;&gt;
	&lt;img id=&quot;ccl-icon-675-0&quot; class=&quot;entry-ccl-by&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black01.png&quot; alt=&quot;저작자 표시&quot;/&gt;
	&lt;img id=&quot;ccl-icon-675-1&quot; class=&quot;entry-ccl-nc&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black02.png&quot; alt=&quot;비영리&quot;/&gt;
	&lt;img id=&quot;ccl-icon-675-2&quot; class=&quot;entry-ccl-nd&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black03.png&quot; alt=&quot;변경 금지&quot;/&gt;
	&lt;!--
	&lt;rdf:RDF xmlns=&quot;http://web.resource.org/cc/&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;
		&lt;Work rdf:about=&quot;&quot;&gt;
			&lt;license rdf:resource=&quot;http://creativecommons.org/licenses/by-nc-nd/2.0/kr/&quot; /&gt;
		&lt;/Work&gt;
		&lt;License rdf:about=&quot;http://creativecommons.org/licenses/by-nc-nd/&quot;&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Reproduction&quot;/&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Distribution&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Notice&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Attribution&quot;/&gt;
			&lt;prohibits rdf:resource=&quot;http://web.resource.org/cc/CommercialUse&quot;/&gt;
		&lt;/License&gt;
	&lt;/rdf:RDF&gt;
	--&gt;
&lt;/div&gt;
</description>
			<category>QM</category>
			<category>QM</category>
			<author>ynzyna ynzyna</author>
			<guid>http://www.sapinside.com/675</guid>
			<comments>http://www.sapinside.com/675#entry675comment</comments>
			<pubDate>Mon, 23 Feb 2009 08:18:37 +0900</pubDate>
		</item>
		<item>
			<title>Reading attribute of a BOR (Business Object)  in ABAP</title>
			<link>http://www.sapinside.com/674</link>
			<description>&lt;br /&gt;

&lt;P&gt;Many times I&#039;ve looked at transaction SWO1 for a business object and seen how it displays all sorts of useful functions (e.g Line Item Texts etc. etc.). Many of these attributes can only be got at in normal programming via convoluted abap tinkering. -- How many times for example do you want to get texts to include on a smartform etc. 
&lt;P&gt;However it&#039;s really easy to get the attribute from the BOR itself using very simple coding. 
&lt;P&gt;Most people shy away from this since a BOR is usually used in SAP workflow and most abap developers haven&#039;t had a lot of exposure to OO programming or SAP workflow. 
&lt;P&gt;Anyway here&#039;s sample code to return an Attribute of a BOR.&amp;nbsp; &lt;PRE&gt;program zzreadbor.

* Get an attribute of a business object.

parameters: p_busobj(10) type c default &#039;BUSISM007&#039;,&amp;nbsp; &quot;IS Media&amp;nbsp;
customer
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; p_key(70) type c,
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; p_attr(32) type c default &#039;Xmediacustomer&#039;.
data:
&amp;nbsp;&amp;nbsp;&amp;nbsp; i_objtype TYPE swo_objtyp,
&amp;nbsp;&amp;nbsp;&amp;nbsp; i_objkey TYPE swo_typeid,
&amp;nbsp;&amp;nbsp;&amp;nbsp; i_element TYPE swo_verb.
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DATA object TYPE swo_objhnd.
&amp;nbsp;&amp;nbsp;&amp;nbsp; DATA verb TYPE swo_verb.
&amp;nbsp;&amp;nbsp;&amp;nbsp; DATA return TYPE swotreturn.
&amp;nbsp;DATA lt_container TYPE STANDARD TABLE OF swcont.
&amp;nbsp;data line type swcont.

i_objtype = p_busobj.
i_element = p_attr.
i_objkey = p_key.
*&amp;nbsp; instantiate the business object. I.e give it a key and create it.
&amp;nbsp; CALL FUNCTION &#039;SWO_CREATE&#039;
&amp;nbsp;&amp;nbsp;&amp;nbsp; EXPORTING
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; objtype = i_objtype
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; objkey&amp;nbsp; = i_objkey
&amp;nbsp;&amp;nbsp;&amp;nbsp; IMPORTING
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; object&amp;nbsp; = object.

* return attribute.
&amp;nbsp; CALL FUNCTION &#039;SWO_INVOKE&#039;
&amp;nbsp;&amp;nbsp;&amp;nbsp; EXPORTING
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; access&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = &#039;G&#039;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; object&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = object
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; verb&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = i_element

&amp;nbsp;&amp;nbsp;&amp;nbsp; IMPORTING
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; return&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = return
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; verb&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = verb
&amp;nbsp;&amp;nbsp;&amp;nbsp; TABLES
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; container&amp;nbsp; = lt_container.
* the attribute value is returned in field line-value.
&amp;nbsp; IF return-code = 0.
&amp;nbsp; loop at lt_container into line.
&amp;nbsp; write: / line-value.
&amp;nbsp; endloop.
endif.&lt;/PRE&gt;* The above example will return an &#039;X&#039; if the customer is an IS Media customer or blank otherwise. 
&lt;P&gt;Other good business objects to use are sales docs (header / line items), invoices, Info types etc etc. 
&lt;P&gt;You can also call methods this way as well -- change the access to &#039;C&#039; in the SWO_INVOKE and pass the parameters to the method. Method name is in VERB. A bit more complex as in the case of Supertypes you need to find the program -- will post an example later --however to start with even the attributes are useful since on &quot;Instantiation&quot; of the BOR you have access to ALL the attribites of that BOR. &lt;/P&gt;&lt;div class=&quot;entry-ccl&quot; style=&quot;clear: both; text-align: right; margin-bottom: 10px&quot;&gt;
	&lt;img id=&quot;ccl-icon-674-0&quot; class=&quot;entry-ccl-by&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black01.png&quot; alt=&quot;저작자 표시&quot;/&gt;
	&lt;img id=&quot;ccl-icon-674-1&quot; class=&quot;entry-ccl-nc&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black02.png&quot; alt=&quot;비영리&quot;/&gt;
	&lt;!--
	&lt;rdf:RDF xmlns=&quot;http://web.resource.org/cc/&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;
		&lt;Work rdf:about=&quot;&quot;&gt;
			&lt;license rdf:resource=&quot;http://creativecommons.org/licenses/by-nc-fr/2.0/kr/&quot; /&gt;
		&lt;/Work&gt;
		&lt;License rdf:about=&quot;http://creativecommons.org/licenses/by-nc-fr/&quot;&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Reproduction&quot;/&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Distribution&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Notice&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Attribution&quot;/&gt;
			&lt;prohibits rdf:resource=&quot;http://web.resource.org/cc/CommercialUse&quot;/&gt;
		&lt;/License&gt;
	&lt;/rdf:RDF&gt;
	--&gt;
&lt;/div&gt;
</description>
			<category>Tips</category>
			<author>ynzyna ynzyna</author>
			<guid>http://www.sapinside.com/674</guid>
			<comments>http://www.sapinside.com/674#entry674comment</comments>
			<pubDate>Mon, 02 Feb 2009 08:30:19 +0900</pubDate>
		</item>
		<item>
			<title>[SAP WF] Workflow of Purchase Requisition Release Strategy</title>
			<link>http://www.sapinside.com/673</link>
			<description>&lt;br /&gt;

&lt;P&gt;&lt;B&gt;Configuration of Purchase Order Release Strategy&lt;/B&gt; 
&lt;P&gt;&lt;B&gt;Following is the procedure for workflow enabling of “Purchase Requisition Release Strategy”:&amp;nbsp;&lt;/B&gt; 
&lt;P&gt;1.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The standard workflow template provided by SAP for PR Release is WS00000038. This information could be retrieved from the SAP help. 
&lt;P&gt;2.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; It is assumed that the release procedure has been setup in the system by the functional consultant, as shown below:&amp;nbsp; &lt;br /&gt;
&lt;IMG height=391 alt=&quot;PR Workflow : Change View Release Strategies Classification&quot; src=&quot;http://www.sap-img.com/workflow/prworkflow1.jpg&quot; width=486&gt; 
&lt;P&gt;3.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The customization of the PR Release Strategy could be verified at the following location: &lt;br /&gt;
SPRO à SAP Reference IMG à Material Management à Purchasing à Purchase Requisition à Release Procedure à Procedure with classification à Setup procedure with classification&amp;nbsp; 
&lt;P&gt;4.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Click on workflow in the above screen (screenshot shown below):&amp;nbsp; &lt;br /&gt;
&lt;IMG height=311 alt=&quot;PR Workflow : Release Procedure Purchase Requisitions&quot; src=&quot;http://www.sap-img.com/workflow/prworkflow2.jpg&quot; width=385&gt; 
&lt;P&gt;5.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Now define the recipients of the PR Release work item as per the release group (refer to screenshot below). For testing purposes, the recipient type is taken as “US”, instead this can also be taken as Position, Organization Unit and others. &lt;br /&gt;
&lt;IMG height=159 alt=&quot;PR Workflow : Change View Assignment of Role to Release Code&quot; src=&quot;http://www.sap-img.com/workflow/prworkflow3.jpg&quot; width=390&gt; 
&lt;P&gt;6.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Now go back to the previous screen and click on “Release Codes”. Here enter the value “1” in the workflow column for the release groups the workflow has to be configured.&amp;nbsp; &lt;br /&gt;
&lt;IMG height=291 alt=&quot;PR Workflow : Change View Release Codes Overview&quot; src=&quot;http://www.sap-img.com/workflow/prworkflow4.jpg&quot; width=389&gt; 
&lt;P&gt;7.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Activate the event linkage of the workflow either in SWDD or PFTC.&amp;nbsp; &lt;br /&gt;
&lt;IMG height=279 alt=&quot;PR Workflow : Workflow Builder Display wf_req_rel Active Saved&quot; src=&quot;http://www.sap-img.com/workflow/prworkflow5.jpg&quot; width=576&gt; 
&lt;P&gt;8.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Mark all the tasks (unless background tasks) as “General Task” in the agent assignment and generate. &lt;/P&gt;&lt;div class=&quot;entry-ccl&quot; style=&quot;clear: both; text-align: right; margin-bottom: 10px&quot;&gt;
	&lt;img id=&quot;ccl-icon-673-0&quot; class=&quot;entry-ccl-by&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black01.png&quot; alt=&quot;저작자 표시&quot;/&gt;
	&lt;img id=&quot;ccl-icon-673-1&quot; class=&quot;entry-ccl-nc&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black02.png&quot; alt=&quot;비영리&quot;/&gt;
	&lt;!--
	&lt;rdf:RDF xmlns=&quot;http://web.resource.org/cc/&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;
		&lt;Work rdf:about=&quot;&quot;&gt;
			&lt;license rdf:resource=&quot;http://creativecommons.org/licenses/by-nc-fr/2.0/kr/&quot; /&gt;
		&lt;/Work&gt;
		&lt;License rdf:about=&quot;http://creativecommons.org/licenses/by-nc-fr/&quot;&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Reproduction&quot;/&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Distribution&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Notice&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Attribution&quot;/&gt;
			&lt;prohibits rdf:resource=&quot;http://web.resource.org/cc/CommercialUse&quot;/&gt;
		&lt;/License&gt;
	&lt;/rdf:RDF&gt;
	--&gt;
&lt;/div&gt;
</description>
			<category>WF(Workflow)</category>
			<category>WF</category>
			<author>ynzyna ynzyna</author>
			<guid>http://www.sapinside.com/673</guid>
			<comments>http://www.sapinside.com/673#entry673comment</comments>
			<pubDate>Mon, 02 Feb 2009 08:28:50 +0900</pubDate>
		</item>
		<item>
			<title>[SAP WF] Purchase Order and Sales Order Workflow</title>
			<link>http://www.sapinside.com/672</link>
			<description>&lt;br /&gt;

&lt;P&gt;Purchase Order workflow ( Transaction : ME23N) determines the approval path for the buying organization . It first goes to the buyer, buyer&#039;s manager &amp;amp; thereafter based on the cost center &amp;amp; the associated amount, it goes for approval through the Cost Center organization . 
&lt;P&gt;i.e, 
&lt;P&gt;Buyer ( Requestor in the procurement deptt. of the buying organization) 
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; v &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Procurement Manager &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; v &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Cost Center org. approval ( based on amount &amp;amp; Sign.Authority level) &lt;br /&gt;
&amp;nbsp; 
&lt;P&gt;Regarding , Sales Order( Transaction: VA01); it is created in the Sales Org of the company&amp;nbsp; &amp;amp; basically governs the pricing structure of the order .The routing of an SO is 
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Sales Org. ( based on the cost center of the sold item) 
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; v &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Distribution Channel&amp;nbsp; &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; v &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Division &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; v &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Reg. Sales office &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; v &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Sales Group &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; | &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; v &lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Sales Person &lt;br /&gt;
&lt;/P&gt;&lt;div class=&quot;entry-ccl&quot; style=&quot;clear: both; text-align: right; margin-bottom: 10px&quot;&gt;
	&lt;img id=&quot;ccl-icon-672-0&quot; class=&quot;entry-ccl-by&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black01.png&quot; alt=&quot;저작자 표시&quot;/&gt;
	&lt;img id=&quot;ccl-icon-672-1&quot; class=&quot;entry-ccl-nc&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black02.png&quot; alt=&quot;비영리&quot;/&gt;
	&lt;!--
	&lt;rdf:RDF xmlns=&quot;http://web.resource.org/cc/&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;
		&lt;Work rdf:about=&quot;&quot;&gt;
			&lt;license rdf:resource=&quot;http://creativecommons.org/licenses/by-nc-fr/2.0/kr/&quot; /&gt;
		&lt;/Work&gt;
		&lt;License rdf:about=&quot;http://creativecommons.org/licenses/by-nc-fr/&quot;&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Reproduction&quot;/&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Distribution&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Notice&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Attribution&quot;/&gt;
			&lt;prohibits rdf:resource=&quot;http://web.resource.org/cc/CommercialUse&quot;/&gt;
		&lt;/License&gt;
	&lt;/rdf:RDF&gt;
	--&gt;
&lt;/div&gt;
</description>
			<category>WF(Workflow)</category>
			<author>ynzyna ynzyna</author>
			<guid>http://www.sapinside.com/672</guid>
			<comments>http://www.sapinside.com/672#entry672comment</comments>
			<pubDate>Mon, 02 Feb 2009 08:27:46 +0900</pubDate>
		</item>
		<item>
			<title>[SAP WF] Table list for Workflow</title>
			<link>http://www.sapinside.com/671</link>
			<description>&lt;br /&gt;

&lt;P&gt;&lt;B&gt;Do you know what the transaction code is to list all the workflows in the system (including standard &amp;amp; customised workflows).&amp;nbsp;&lt;/B&gt; 
&lt;P&gt;Use se16 and table name &#039;HRSOBJECT&#039;&amp;nbsp; 
&lt;P&gt;It will list all the workflows. It also lists Roles but you can restrict by selecticng TS, TG and WS.&amp;nbsp; 
&lt;P&gt;&lt;IMG height=218 alt=&quot;List all workflow in system&quot; src=&quot;http://www.sap-img.com/workflow/workflowtcode.jpg&quot; width=737&gt;&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;/P&gt;&lt;div class=&quot;entry-ccl&quot; style=&quot;clear: both; text-align: right; margin-bottom: 10px&quot;&gt;
	&lt;img id=&quot;ccl-icon-671-0&quot; class=&quot;entry-ccl-by&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black01.png&quot; alt=&quot;저작자 표시&quot;/&gt;
	&lt;img id=&quot;ccl-icon-671-1&quot; class=&quot;entry-ccl-nc&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black02.png&quot; alt=&quot;비영리&quot;/&gt;
	&lt;!--
	&lt;rdf:RDF xmlns=&quot;http://web.resource.org/cc/&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;
		&lt;Work rdf:about=&quot;&quot;&gt;
			&lt;license rdf:resource=&quot;http://creativecommons.org/licenses/by-nc-fr/2.0/kr/&quot; /&gt;
		&lt;/Work&gt;
		&lt;License rdf:about=&quot;http://creativecommons.org/licenses/by-nc-fr/&quot;&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Reproduction&quot;/&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Distribution&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Notice&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Attribution&quot;/&gt;
			&lt;prohibits rdf:resource=&quot;http://web.resource.org/cc/CommercialUse&quot;/&gt;
		&lt;/License&gt;
	&lt;/rdf:RDF&gt;
	--&gt;
&lt;/div&gt;
</description>
			<category>WF(Workflow)</category>
			<author>ynzyna ynzyna</author>
			<guid>http://www.sapinside.com/671</guid>
			<comments>http://www.sapinside.com/671#entry671comment</comments>
			<pubDate>Mon, 02 Feb 2009 08:26:19 +0900</pubDate>
		</item>
		<item>
			<title>[SAP WF] How are workflows triggered?</title>
			<link>http://www.sapinside.com/670</link>
			<description>&lt;br /&gt;

&lt;P&gt;Workflows can be triggered automatically by changes in the system or manually by an operator. Manually triggered workflows are good for processes that remedy a problem the operator has noticed or for dealing with a forms-based requests (E.g. my PC won&#039;t boot). Automatically triggered workflows are useful because the operator does not even&amp;nbsp; &lt;br /&gt;
have to be aware of the workflow&#039;s existence to trigger it. In addition to triggers embedded in transactions there are also generic triggering mechanisms such as a change in the status of a business object or a change in the HR data. Irrespective of how the workflow is triggered, it is linked to the business object as described in the previous answer and can be tracked easily. Because WebFlow is part of the basis system, this triggering is reliable and easy to implement. 
&lt;P&gt;Workflows may be triggered by events but this is not essential. The event-handling makes it easy to trigger workflows from transactions and system changes without you having to make modifications. If you are creating your own report or transaction which triggers a workflow, avoid events and trigger the workflow directly with the WAPI function call. This is particularly important&amp;nbsp; when triggering a workflow from outside the SAP system. This method reduces flexibility (the workflow ID is hard-coded) but increases performance if this is an issue (we&#039;re talking about 50 000 work items a day here!). 
&lt;P&gt;Any exception handling workflows that are intended to be triggered manually can be triggered from the system menu when &lt;br /&gt;
viewing the relevant transaction. The SAP system has the intelligence to suggest workflows that can be triggered manually based on the authorization of the operator and the context that the operator is working in. No additional customizing is needed &lt;br /&gt;
here. &lt;/P&gt;&lt;div class=&quot;entry-ccl&quot; style=&quot;clear: both; text-align: right; margin-bottom: 10px&quot;&gt;
	&lt;img id=&quot;ccl-icon-670-0&quot; class=&quot;entry-ccl-by&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black01.png&quot; alt=&quot;저작자 표시&quot;/&gt;
	&lt;img id=&quot;ccl-icon-670-1&quot; class=&quot;entry-ccl-nc&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black02.png&quot; alt=&quot;비영리&quot;/&gt;
	&lt;!--
	&lt;rdf:RDF xmlns=&quot;http://web.resource.org/cc/&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;
		&lt;Work rdf:about=&quot;&quot;&gt;
			&lt;license rdf:resource=&quot;http://creativecommons.org/licenses/by-nc-fr/2.0/kr/&quot; /&gt;
		&lt;/Work&gt;
		&lt;License rdf:about=&quot;http://creativecommons.org/licenses/by-nc-fr/&quot;&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Reproduction&quot;/&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Distribution&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Notice&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Attribution&quot;/&gt;
			&lt;prohibits rdf:resource=&quot;http://web.resource.org/cc/CommercialUse&quot;/&gt;
		&lt;/License&gt;
	&lt;/rdf:RDF&gt;
	--&gt;
&lt;/div&gt;
</description>
			<category>WF(Workflow)</category>
			<author>ynzyna ynzyna</author>
			<guid>http://www.sapinside.com/670</guid>
			<comments>http://www.sapinside.com/670#entry670comment</comments>
			<pubDate>Mon, 02 Feb 2009 08:24:42 +0900</pubDate>
		</item>
		<item>
			<title>[SAP WF] How can I check the status of a workflow?</title>
			<link>http://www.sapinside.com/669</link>
			<description>&lt;br /&gt;

&lt;P&gt;This is one of the very cool features of SAP Business Workflow. You can usually navigate directly from the business&amp;nbsp; &lt;br /&gt;
object to check the workflow progress. For example, while viewing a purchase order you can select &quot;workflow&quot; from&amp;nbsp; &lt;br /&gt;
the system menu or toolbar and you will see a list of workflows related to the purchase order. Usually just one, but if you have created a few of your own and these have been triggered you will see the status of these too. And that is not all. You also see a simplified summary of all the steps that have taken place so far including who performed them, when they were executed and which ad hoc notes were attached. &lt;/P&gt;&lt;div class=&quot;entry-ccl&quot; style=&quot;clear: both; text-align: right; margin-bottom: 10px&quot;&gt;
	&lt;img id=&quot;ccl-icon-669-0&quot; class=&quot;entry-ccl-by&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black01.png&quot; alt=&quot;저작자 표시&quot;/&gt;
	&lt;img id=&quot;ccl-icon-669-1&quot; class=&quot;entry-ccl-nc&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black02.png&quot; alt=&quot;비영리&quot;/&gt;
	&lt;!--
	&lt;rdf:RDF xmlns=&quot;http://web.resource.org/cc/&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;
		&lt;Work rdf:about=&quot;&quot;&gt;
			&lt;license rdf:resource=&quot;http://creativecommons.org/licenses/by-nc-fr/2.0/kr/&quot; /&gt;
		&lt;/Work&gt;
		&lt;License rdf:about=&quot;http://creativecommons.org/licenses/by-nc-fr/&quot;&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Reproduction&quot;/&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Distribution&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Notice&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Attribution&quot;/&gt;
			&lt;prohibits rdf:resource=&quot;http://web.resource.org/cc/CommercialUse&quot;/&gt;
		&lt;/License&gt;
	&lt;/rdf:RDF&gt;
	--&gt;
&lt;/div&gt;
</description>
			<category>WF(Workflow)</category>
			<author>ynzyna ynzyna</author>
			<guid>http://www.sapinside.com/669</guid>
			<comments>http://www.sapinside.com/669#entry669comment</comments>
			<pubDate>Mon, 02 Feb 2009 08:23:58 +0900</pubDate>
		</item>
		<item>
			<title>[SAP WF] How are users notified about their work pending?</title>
			<link>http://www.sapinside.com/668</link>
			<description>&lt;br /&gt;

&lt;P&gt;The users are informed by a work item which you may think of as being very like an e-mail. The difference is the work item contains intelligence and by executing the work item you will be taken to the form or SAP transaction that makes up the step in the workflow. This form or transaction could be a decision, a request for information or a request for confirmation that a particular task has been performed. &lt;br /&gt;
The work item is usually accompanied by a description of what has to be done, where to refer to when assistance is needed (help desk, intranet...) and a summary of information about the business object or process which enables the operator to attack the task immediately. 
&lt;P&gt;This work item can be received and executed in MS Outlook, Lotus Notes, mySAP Workflow MiniApp or the SAP integrated&amp;nbsp; inbox. If this is not enough, the workflow system can transmit e-mail notifications directly to any mail system, informing the user of the need to log in to the SAP system to execute the task. The e-mail notification is done on a subscription basis so that users can de-subscribe from this service if they already check their work item inbox regularly&lt;/P&gt;&lt;div class=&quot;entry-ccl&quot; style=&quot;clear: both; text-align: right; margin-bottom: 10px&quot;&gt;
	&lt;img id=&quot;ccl-icon-668-0&quot; class=&quot;entry-ccl-by&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black01.png&quot; alt=&quot;저작자 표시&quot;/&gt;
	&lt;img id=&quot;ccl-icon-668-1&quot; class=&quot;entry-ccl-nc&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black02.png&quot; alt=&quot;비영리&quot;/&gt;
	&lt;!--
	&lt;rdf:RDF xmlns=&quot;http://web.resource.org/cc/&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;
		&lt;Work rdf:about=&quot;&quot;&gt;
			&lt;license rdf:resource=&quot;http://creativecommons.org/licenses/by-nc-fr/2.0/kr/&quot; /&gt;
		&lt;/Work&gt;
		&lt;License rdf:about=&quot;http://creativecommons.org/licenses/by-nc-fr/&quot;&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Reproduction&quot;/&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Distribution&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Notice&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Attribution&quot;/&gt;
			&lt;prohibits rdf:resource=&quot;http://web.resource.org/cc/CommercialUse&quot;/&gt;
		&lt;/License&gt;
	&lt;/rdf:RDF&gt;
	--&gt;
&lt;/div&gt;
</description>
			<category>WF(Workflow)</category>
			<author>ynzyna ynzyna</author>
			<guid>http://www.sapinside.com/668</guid>
			<comments>http://www.sapinside.com/668#entry668comment</comments>
			<pubDate>Mon, 02 Feb 2009 08:22:58 +0900</pubDate>
		</item>
		<item>
			<title>[SAP WF] What is the strengths of  SAP WebFlow?</title>
			<link>http://www.sapinside.com/667</link>
			<description>&lt;br /&gt;

&lt;P&gt;WebFlow is the internet functionality of SAP Business Workflow. Based on customer feedback from the various regional users groups, the main strengths of SAP Business Workflow are:&amp;nbsp; &lt;br /&gt;
Robust production workflow system, (upgrade continuity with the rest of the SAP system, versioning, scalability, no &lt;br /&gt;
gluing....) &lt;br /&gt;
Standard workflow templates delivered by SAP can be used out-of-the-box or tweaked to deliver the optimum business &lt;br /&gt;
process for your company. Workflows can be up and running including training in under a day (thanks to the&amp;nbsp; &lt;br /&gt;
knowledgeware delivered as part of the template packet). &lt;br /&gt;
Seamlessly integrated into the SAP environment, be it R/3, Business to Business Procurement, CRM, APO, &lt;br /&gt;
mySAP.com.... Examples of integration are: 
&lt;UL&gt;
&lt;LI&gt;Business Reporting (WIS), 
&lt;LI&gt;Context sensitive availability at any time through the system menu (available anytime, anywhere) 
&lt;LI&gt;More and more standard SAP functionality is being provided by using SAP Business Workflow so your homegrown 
&lt;LI&gt;workflows fit the landscape exactly, 
&lt;LI&gt;More and more workflow functionality is available directly within the SAP transaction or Web MiniApp. &lt;/LI&gt;&lt;/UL&gt;WebFlow is becoming more and more important because companies are no longer being judged by their own performance but by the combined performance of the company AND its partners. In other words it is not enough that the business processes within your company run smoothly and faster than your competitors. You have to ensure that the processes between you and your partners are also as fast, efficient and flexible as possible. WebFlow delivers this. &lt;div class=&quot;entry-ccl&quot; style=&quot;clear: both; text-align: right; margin-bottom: 10px&quot;&gt;
	&lt;img id=&quot;ccl-icon-667-0&quot; class=&quot;entry-ccl-by&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black01.png&quot; alt=&quot;저작자 표시&quot;/&gt;
	&lt;img id=&quot;ccl-icon-667-1&quot; class=&quot;entry-ccl-nc&quot; src=&quot;http://cfs.tistory.com/static/admin/editor/ccl_black02.png&quot; alt=&quot;비영리&quot;/&gt;
	&lt;!--
	&lt;rdf:RDF xmlns=&quot;http://web.resource.org/cc/&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;
		&lt;Work rdf:about=&quot;&quot;&gt;
			&lt;license rdf:resource=&quot;http://creativecommons.org/licenses/by-nc-fr/2.0/kr/&quot; /&gt;
		&lt;/Work&gt;
		&lt;License rdf:about=&quot;http://creativecommons.org/licenses/by-nc-fr/&quot;&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Reproduction&quot;/&gt;
			&lt;permits rdf:resource=&quot;http://web.resource.org/cc/Distribution&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Notice&quot;/&gt;
			&lt;requires rdf:resource=&quot;http://web.resource.org/cc/Attribution&quot;/&gt;
			&lt;prohibits rdf:resource=&quot;http://web.resource.org/cc/CommercialUse&quot;/&gt;
		&lt;/License&gt;
	&lt;/rdf:RDF&gt;
	--&gt;
&lt;/div&gt;
</description>
			<category>WF(Workflow)</category>
			<author>ynzyna ynzyna</author>
			<guid>http://www.sapinside.com/667</guid>
			<comments>http://www.sapinside.com/667#entry667comment</comments>
			<pubDate>Mon, 02 Feb 2009 08:22:03 +0900</pubDate>
		</item>
	</channel>
</rss>
