Purchase Order Step-by-Step

Dear All Experts,
Can anyone help me out with the step-by-step configuration process of creating a Purchase order. this will help me to go ahead.
Thanks to all,
Mohit.

Hello Mohit,
Please check configuration documents in SAP Solution Manager. or
<a href="http://service.sap.com/ibc-srm">http://service.sap.com/ibc-srm</a>
Regards,
Masa

Similar Messages

WM -Purchase order and configuration steps

HI Gurus,
             kindly help me to configure the ware house management to create the purchse order and i want to move the
            raw material to production order..i have the confusion, what i maintain in the WM-ACTIVITIES -MOVEMENT TYPE
           pls help me to do the configuration
with regards
dinesh

warehouse managment does not create purchase orders.
you create your POs like you do it without WM.
WM is a sublevel to a storage location.
If WM is activated and you post a receipt to a PO to this storage location, at the same time a quant is created in interim storage type 902 along with a transport request to putaway that wuant into its final bin in the warehouse.

Purchase Order Workflow - dialog step not receiving terminating event

Hi,
We have a scenario wherein based on the release groups and release strategies, different peope need to release the PO's.
I have been able to develop the workflow for this successfully, but here is where I am facing an issue.
After the PO has been created, based on the release group and strategy, it gets routed to the appropriate 1st approver. On their approval, the PO gets routed to the 2nd approver. Once the 2nd approver approves, the dialog step doesnt get completed and is still waiting for the terminating event. Event trace shows that the event is getting published, but there is no workitem to receive the terminating event. I am not sure why this is occuring for only 2nd approver onwards whereas for the 1st approver, the terminating event is received by the workitem.
I am using start conditions for my workflow to ensure only 1 instance of the workflow is triggered for a rel groups and rel strategy and release code, else I am multiple instances each time an approver approves the PO. I am not sure if the start conditions are causing this issue with the terminating events not being received with the workitems.
Any assistance is welcome.
Thank you,
Satish

From the information provoided it seems you are using PO that is subjected to Release of PO for multiple Release Code and each Release Code Release is being done by one approver. If that is the case then I think the Terminating event should get caught. Please check whether the Terminating event that is getting triggered is specific to the Release Code or not.
Thanks
Arghadip

Idoc for purchasing order

can any1 explain the steps needed to send a purchase order through ALE/IDOCS
pls explain it with reference to PURCHASE ORDER

Hi,
cehck the same...
This method is used for distributing transaction data like purchase order, sales order etc.
In this method the extra transaction code that we use is we41 (outbound process code) and we use this in the message control tab in the partner profiles.
The transaction codes that are required for this method are
We81
We30
We31
We82
We21
We20
Bd64
Nace
Me22n (purchase order), va02 (sales order) etc.
Ex: purchase order.
Message type: ORDERS
Idoc type: ORDERS05
Outbound process code for purchase order: me10
The steps that are to be followed are:
Check for the message type in the transaction in we81.
check for the idoc type in the transaction we30.
check we82 in which the link between message type and idoc type is there.
create the port in we21.
Configure the partner profiles in we20.
Click on the + button outbound parameters and give the message type, receiver port
Idoc type.
Now press on the message control tab, this is the place where u give the outbound process code. The message type in the message control is the output type that is used in the nace transaction.
Create a distribution model in bd64.
Go to purchase order transaction (me22n).and press the messages tab
In the messages tab give the output type and the distribution medium as distribution-ale and then save it.
Reward if helpful.
Regards,
Nagaraj

Release Procedure in Indent/Purchase Order

I want to customise release strategy in indent and Purchase order in SAP. Kindly provide me steps to configure this. will apperitiate your efforts.
Manjit

Hi Manjit,
Release Procedure for Purchase Orders
In this section, you set up a release procedure for purchase orders (POs).
Requirements
If you want to use workflow to release POs, you must make the standard and basic settings for workflow (Basis -> Business Management -> SAP Business Workflow).
How do you set üp a release procedure for POs?
To set up the release procedure, you must make a series of settings in Customizing. This section provides you with an overview of the necessary activities.
You must perform the following steps:
1. Create characteristics and classes
For more on this topic, see Edit Characteristics and Edit Classes.
Note
If you wish to link your release procedure to workflow, you must perform steps 2 and 3 . You make these settings in Customizing for Business Workflow (Basis -> Business Management).
Otherwise, continue with step 4.
Define organizational plan
For more on this topic, see Edit Organizational Plan.
Assign standard tasks and activate event-receiver linkage.
For more on this topic, see Perform Task- Specific Customizing.
1. Set up release procedure for RFQs
a) Create release group
b) Create release code
c) Create release indicator
d) Create release strategy
Note
You need only carry out the following step if you wish to link your release procedure to workflow.
e) Assign release code to a user
For more on this topic, see Define Release Procedure for POs.
2. Check release strategies
For more on this topic, see Check Release Strategies.
Further notes
For more information, refer to
· Implementation of a Release Procedure for Purchasing Documents
· Release of Purchasing Documents (SAP Library -> Basis -> Business Management (BC-BMT) -> SAP Business Workflow (BC-BMT-WFM) -> Reference documentation -> BC Workflow Scenarios in the Applications -> MM Materials Management: Workflow Scenarios)
Edit Characteristic (CT04)
In this step, you create characteristics for a release procedure for purchase orders (POs).
Classification characteristics are the criteria for a release condition. If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchasing document (e.g. purchase order or RFQ).
Example
Release condition for release strategy EA:
Characteristic Characteristic value
Total net value of PO Above $10,000
If the total value of a purchase order exceeds $10,000, release strategy EA is assigned to this PO.
Requirements
In communication structure CEKKO you will find all the fields that can be used as characteristics for a release condition (e.g. BSART for the order type and GNETW for the total order value).
Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEKKO in the field Database table , and choose "Display".
Note
If you wish to define a separate release strategy for the various document categories (PO, RFQ, etc.), you must create a characteristic for each relevant document category.
Activities
1. Create a characteristic for each field from communication structure CEKKO that is to be a criterion for your release strategy. You have a free choice of names for the characteristic.
2. Enter the table name and the field name on the tab page Additional data (for example, table CEKKO for field GNETW).
Note
o Do not select any of the indicators in the area Procedure for value assignment on the tab page Additional data. Only if none of these indicators is marked can you assign a value or value interval to the characteristic when defining your release strategy.
o When you create a characteristic for a currency-dependent field (e.g. GNETW), a box appears in which you must enter the currency for the relevant value. The system then converts the currency of the purchasing document into this currency.
3. Check the data for the chosen field on the tab page Basic data.
If you want to enter several values or a value interval for a characteristic, set the Multiple values indicator in the area Value assignment.
Note
Value intervals can only be specified for numerical values (e.g. an interval of $10,000 to $15,000 for the value of the purchase order.
4. Check the texts for the field on the tab page Descriptions.
5. You can maintain default values for a characteristic on the tab page Values.
If you maintain values here, these values will be displayed as input help under Create Procedure with Classification -> Release Strategy -> Classification . If you wish to use not only the input help but also other values, you must select the Additional values indicator.
Note
You can also maintain ' ' as a default value. For example, for account assignment: ' ' for stock material, 'k' for cost center, and 'a' for asset.
6. If you want to restrict the use of a characteristic to particular class types, specify the relevant class types on the tab page Restrictions. For example, class type 032 for the release strategy.
Further notes
Further information on characteristics is available in this Customizing activity via Help -> Application help.
Customer exits
Customer exit M06E0004 enables you to change the communication structure for determining the release strategy for purchasing documents.
Edit Class( CL02 )
In this step, you create classes for a release procedure for purchase orders (POs).
You use a class to group together characteristics that are to constitute a release condition for a release strategy. In the step "Define Release Procedure for Purchase Orders " you assign this class to the release strategy.
Activities
1. Create a class with the class type 032. You have a free choice of names for the new class (e.g. REL_RFQ for the release of RFQs).
2. Assign a name for the new class on the tab page Basic data.
3. You can view an error message if different characteristics with identical values have been assigned to a class. To be able to do so, select the Check with error message indicator in the Same classification area.
4. If appropriate, select terms to be used as search criteria in searches for your class on the Keywords tab page.
5. Assign your characteristics to the class via the tab page Characteristics.
Further notes
Further information on classes is available in this Customizing activity under Help -> Application help.
Define Release Procedure for Purchase Orders
In this step, you set up the release procedure for purchase orders (POs) and can link it to workflow. (Note that in this context "releasing" means "approving", or giving the "green light" to a document.)
Requirements
· In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).
· You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure ( Authorization Management -> Create Authorization Profiles and Assign to Users).Activities
Here you define the following:
·     Release group
·     Release codes
·     Release indicator
·     Release strategy
·     Workflow
Release group
Create a release group for your release procedure and assign it to a class. In the process, you assign release conditions to the release procedure.
Release codes
Here you create the release codes you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field
The Workflow indicator is also used to control role resolution:
·     "1 - Role Resolution with Group, Code and Plant (T16FW)"
Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).
·     "9 - Role Resolution via User Exit"
Here you use the customer exit M06E0005 to define a role resolution of your own.
Release indicators
A release indicator shows the release status of a PO.
Via the following settings, you can define the release indicators you need for your release procedure:
·     The Released indicator is used to specify whether messages (PO documents in output format) may be transmitted for a purchase order with this indicator.
·     The Changeability indicator shows the effect of changes to the PO (a change to a PO may require a new release strategy to be determined, for instance).
·     By means of the Value change indicator, you can specify that the release strategy is to be re-started if a PO is changed and the value of a PO item thereby increases by a certain percentage (e.g. 10%). Set the Changeability indicator to "4 - Changeable, new release in case of new strategy or value change" or "6 - Changeable, new release in case of new strategy or value change/outputted" and enter a percentage in the Value change field.
Attention:
The following release indicators are necessary for every release procedure:
o     Release indicator for initial status
If the PO is subject to a release strategy, it must normally be released before it can be transmitted to the vendor. Therefore, when a PO is created, it is assigned a release indicator that blocks it from being outputted in message form.
The Released indicator must not be selected for this indicator.
o     Release indicator for released status
This indicator is assigned to the PO when it is released.
The Released indicator must be selected for this indicator.
Release strategies
Create a release strategy for your release group and assign your release codes accordingly.
·     Release prerequisites
With the release prerequisites , you specify the order in which the individual release points (individuals or departments) represented by the release codes may release the document.
Example
The following table shows release prerequisites for a strategy with four release codes.
Code/Release prerequisite
          01     02     03     04
     01     -
     02          -
     03               -
     04                    -
In this release strategy, the codes 01, 02, 03, and 04 must successively release the purchase order.
Read the table from left to right. For instance, the third line for release code 03: For code 03, release via code 01 and code 02 is a prerequisite. That is to say, the PO must be released via codes 01 and 02 before it can be released via code 03.
·     Release statuses
Here you specify the status a PO has after certain release points have effected release.
Specify which release indicator/status a PO is to have after having been released via a certain release code.
·     Classification
In classification, you maintain the values assigned to the characteristics. Via the characteristics and their values, you specify the POs to which your release strategy is assigned.
Maintain values (individual values or intervals) for your characteristics.
Example
Two characteristics and their values have been maintained in classification for release strategy 'EA':
- Document type - 'NB - standard purchase order'
- Total value - above $10,000
All POs with the document type 'NB' and a total value in excess of $10 ,000 are thus subject to a release procedure with the release strategy 'EA'.
·     Release simulation
The release simulation function enables you to check which status a PO will achieve with your release strategy if release is effected by a certain release point.
Choose "Simulate release" and release the document with the desired release code by double-clicking. The system shows you which status the PO now has as a result of this release.
Workflow
Assign a processor ID to your workflow-relevant release codes. The processor (member of staff responsible for processing the document) will then receive a work item when he or she is required to effect release.
You can assign a processor ID either directly or indirectly:
o     Direct processor assignment:
Enter a user name.
o     Indirect processor assignment:
Enter a job, for example, or a position. At runtime, the system will then determine the member(s) of staff responsible for processing the document.
Customer exit
Customer exit M06E0005 enables you to define your own role resolution which determines the person responsible for releasing purchasing documents in workflow.
Further notes
Further information on how to set up a release procedure linked to workflow is available via the menu options Help -> Application Help.
Check Release Strategies
In this step, you can check whether the basic settings for your release strategy are complete and correct.
Checks
The following checks are carried out for purchasing documents:
·     Basic checks
The system checks whether the necessary release groups exist in the system. For example: Whether a release group has been deleted even though an associated release strategy still exists.
·     Checks regarding release groups and release classes
The system checks whether the release groups and the assigned classes have been maintained correctly. For instance, whether
o     A class has been assigned to the release groups and whether it exists in the system
o     Characteristics - which exist in the system and are linked to the communication structure - have been assigned to the class
o     A customer exit must be maintained for a characteristic
·     Checks regarding release codes
The system checks whether the release codes have been maintained correctly
·     Checks regarding release indicators
The system checks whether the release indicators have been maintained correctly. For example: Whether release indicators exist for the statuses "Blocked" and "Released".
·     Checks regarding release strategies
The system checks whether the release strategies have been maintained correctly. For example, whether:
o     Release codes have been assigned to the release strategy
o     The relevant release indicators have been assigned to the initial and final statuses of a release strategy
·     Checks regarding link to workflow
The system checks whether the link between your release procedure and workflow has been maintained correctly. For example, whether:
o     A processor (member of staff responsible for processing) has been assigned to a workflow-relevant release code and is defined in the organizational plan
o     A customer exit is necessary for the role resolution
Result
The result of these checks is displayed in a log. Further information is available in the Customizing activity under Help -> Application Help.
Activities
1. Start the check by performing the Customizing activity.
2. Check whether any error or warning messages are displayed.
3. If necessary, correct your Customizing settings for the release procedure.
4. Re-run the check after making corrections.
Rewards if Helpful
Regards
Sanjay L

Steps for free goods, purchase order and sales order

Hi all,
I am just starting to learn SAP and would appreciate it anyone can guide me along with navigation/steps for the below questions:
1) can we create free goods automatically when purchase order is generated?
2) Can we duplicate data from the purchase order to the inputs of sales order?
Thank you so much for your help!

Hi Experts,
I set Free Goods determination Inclusive Calculation Rule 1=Pro Rata and Cal Rule 2=Unit reference both are working fine.
When trying for cal Rule 3 it gives error message "The system determined free goods with quantity 0 for item 000010
Means for 10Ton of A product 10% means 2To are free. If I apply quantity in multiple of 10 i.e.10, 20 30 free goods are determined, delivery & billing is working well.
But if I apply 25Ton or 38ton, it is not even giving minimum discounts say for 25ton, it should give atleast 20ton equivalent fre goods. I checked in rounding rule OB90 where my company code3000 is giving 10 2 digit for USD currency. I set like this. When I checked pricing for condition type R100 it says requirement 055 not fulfilled. However I have maintained Req 055 & BaseType 28 in pricing procedure.
For cal rule 3 what else setting I should check.
Early reply with detail steps shall be highly appreciated.
Thanks

Steps to create a purchase order in SAP r/3

Hi All,
    I need to create a purchase order in SAP R/3,I am very new to SAP R/3 just started using material managements module in R/3.Could any one please help me to know what all steps i need to take for creating a PO.Do i require some pre-requisite data in R/3?
Waiting for your reply!
Thanking you.
Regards,
Namrata.

Trigger
A purchase order needs to be created, and the vendor is known
Business Process Description Overview
A purchase order is a legal document issued by the buyer to the vendor to supply materials or service at the agreed price, terms and conditions. The Purchase Order forms the basis for all follow-on activities like Goods Receipt, Invoice Verification, etc. The Purchase Orders can be created directly by entering all the required data, copying already created purchase order, with reference to an RFQ/Contract or with reference to a PR.
Purchase Order creation is possible only if sufficient budget allocation is there for the Fund Centers. It is not possible to create Purchase Orders for a Vendor who is blocked for procurement or not maintained in source list for that item. Also it is not possible to create PO for Quantity more than the PR quantity.
All the price components which are to be paid to vendors and requires to be inventoried has to be included in PO.It is possible to add different vendors for delivery costs. The tax codes should be correctly maintained in PO for the purpose of Cenvat availment etc.
The payment term defaulted from Vendor Master or RFQ has to be verified and changed if required.
The incomplete Purchase Orders can be saved as HOLD document and later completed and saved thru Change PO menu
Input - Required Fields     Field Value/Comments
Vendor     Vendor number
Purchasing Organization     1000
Purchasing Group     Purchasing Group code
Date     Purchase order date
Account assignment category     Where costs will be allocated
Delivery Date     Anticipated Delivery Date
Plant     For which plant we are buying the material
Output - Results     Comments
Purchase order document     Can be changed, displayed or printed which can then be mailed to vendor
Tips and Tricks
The Purchase Orders can be created directly by entering all data required for creating PO or by copying another PO or with reference to RFQ/Contract/PR.To create a purchase order by copying existing document (PO/RFQ/PR), you can either select the desired document in the document overview   .and adopt it in the current purchase order in the right-hand area of the screen using the ADOPT button   .In addition you can drag it onto the shopping basket symbol   with the left-hand mouse button.
Click the Personal Settings button on the tool bar, this function is for default information for purchase order header data and also purchase order item data. This will reduce the amount of redundancy in the data entry, i.e. plant, company code.
One Purchase Order may be created for several purchase requisitions
Procedural Steps
1.1.     Access transaction by:
Via Menus     Logistics èMaterials ManagementèPurchasingèPurchase OrderèCreateèVendor/Supplying Plant Known.
Via Transaction Code     ME21N
1.2.     Double-click
On screen Create Purchase order
On screen select Domestic Purchase order in this screen . You can also select other document if you want to create other. Here drop down menu is available.
Click   to enter the organization data.
Screen will change in the header; enter data as given in the table below:
Field Name     R/O/C     Description
Purchasing Org.     R     Enter the purchasing organization code.
Example: 1000
Purch. Group     R     Enter the purchasing Group which is procuring the material
Example: P01
Company Code     R     Enter the company code under which above purchasing
Organization is.
Example: 1000
After entering the organization data enter the vendor or material supplier in the field    here drop down is available.click   to see the drop down.
Field Name     R/O/C     Description
Search term     O     Text that describes the vendor in more detail.
Example:     MICON
Vendor     O     Description of the vendor.
Example:     100008
Click   .
System displays all possible entries available as per data entered
Restrict value range (1)   1 Entries found
To select required Vendor Click   .
Click   .
Vendor selected
Now go to   ,here the system will pick up the data automatically from the vendor master but if you want to chane the data you can change the data. Here drop down menu is available.
Now go to   to mainatin the text.
After maintaining the text if you want to see or change the vendor address click   and do the amendments.
Now Go to   and click to enter the Items and other data as per the table given below:
Field Name     R/O/C     Description
Account Assignement     R     Key that identifies specific settlement receiver types such as cost centers, internal orders, work orders, asset accounts, or project WBS elements.Example: K
drop down menu is available here.
Item Cateogry     O     How the procurement of a material is controlled.
Drop down menu is available here.Example: Standard
Material     R     Here you will enter the material to be purchased from the
Vendor.
Here also drop down menu is available. Use the following
to select the material. Example ZROH-DEMO
In the figure above enter the search cretira for the material for example ZROH-DEMO and click
. The follwing result will appear on the screen select the line item and click   to select
the material.
Short Text     R     Enter here short description about the material,if the text is not
automatically picked up from the material master.
PO Quantity     R     Enter here quantity to be ordered.
Example 10
Order unit     R     Here we enter the order units of measurement.
Here also drop down menu is available.
Example : KG
Category of delivery date     O     Here you can enter deleviery date format.
Here also drop down menu is available.
Example : Day format
Delivery date     R     Enter the delivery date. You can use the calender provided by
the system.
Example : 28.02.2006
Net price     R     Enter the net price of the material here
Example : 1000 INR
Material group     R     Enter the material group to which that material belongs.Here
also drop down menu is available. This field is also automatic
picked up field.
Example : M10001
Plant     R     Enter the plant code for which you are purchasing the material
Here also drop down menu is available.
Example : 1100
Storage location     O     Here you will enter where the material is to be stored. Drop
Down menu is available here.
Example WH01
Click Enter and system will give you message
You will now see the screen
Field Name     R/O/C     Description
Cost Centre     R     The purchase is done for which purpose. Here also drop down
Menu is available.
Example: 11050 for CDU/VDU /SGU OP
G/L Account     R     G/L account from which payment will be done.
It will be automatically be picked up from the material group
You can change it also.
Unloading Point     O     Specifies the point at which the material is to be unloaded.
Recipient     O     Specifies the recipient for whom the material is destined.
Click   to see and to change the Tax Code at item level.
Select    to view the taxes applied on the line item.
click   to go back to the previous screen .
On the main screen in the same tab if you want to change the taxe select the tax code from the drop down available
After selection again, Select    to view the taxes applied on the line item.
If you want to add more conditions click   tab and enter the conditions from the drop down
You can also maintain the text at item level by clicking   tab.
After completeing this all click   to check wether here is any error in the purchase order , If there will not
                         ↓
any error then on the screen following line will appear.
If there will be some error the system will throw the message on the screen
select the line item and click   to see the detail of the error.
close this window now and goto main screen to rectify the error.
After rectifying the error again click   to check wether here is any error in the purchase order.
Now click   to save the purchase order, after clicking the button the following message will appear

Steps to edit standard purchase order layout

hi.......
plz tell me
steps to edit standard purchase order layout and printing program............

Hello,
          The Standard Layout Set for Purchase Order is MEDRUCK. However, you need to Copy the Form and Make changes to the Layout.
          First of all, you need to identify the Elements of the Layout as to where exactly you need Customer Modifications for your client's requirement.
         Then go ahead and make changes to the Copied Version (Not the Standard Layout Set).
        Then from NACE the Output Type can be configured for the New Layout Set.
Hope it was helpful.
Thanks and Regards,
Venkat Phani Prasad Konduri

Workflow step Mail with purchase order number is not executing

Hi All,
I created aworkflow which gets triggerd when a Purchase Order is created. I have mentioned the BUS 2012 event 'Release Step Created' as starting condition for the workflow. My workflow is triggering correclty. I need to send a mail to the initiator stating that the purchase order <po. no.> has been created. But I am not getting the PO number and workflow is stopping at the step mail where subject is mentioned with element &BUS2012.PURCHASEORDER&.
If I didnot mention the PO number workflow is executing correclty. I have done all the necessary binding also.
Thanks in advance,
Sri Suktha.

Hello,
This can often be caused by not adding 'US' to the username, check if that's the case here.
I would try creating a test workflow which does nothing but send a mail, try to get that working first.
regards
Rick Bakker
hanabi technology

One step purchase order approval - Trigger only in certain cases.

Hi,
I want to trigger the one step workflow approval for Purchase Orders only in ceraitn cases.
When the PO is created from a shopping cart it has to be automatically approved. In other cases the workflow has to be triggerred.
I tried setting the no_further_approval flag to 'X' in the Approval BADI but did not work.
Any Suggestions?
Does the BADI BBP_WFL_APPROV_BADI work for one step approval or is it only for the n step?
Is it better to manipulate the start conditions?
Any help is appreciated.
Joe Vellaiparambil

Hi
If the workflow is not working as expected, refer to SAP Note 322526, Analysis for workflow problems.
You should go with making the start conditions work, as you are aware that only 1 level Approval is required. Try making changes in the start conditions by using transaction - SWB_PROCUREMENT.
Note ->This BADI - BBP_WFL_APPROV_BADI is only recommended for N-step dynamic approval workflow. I don't think you need this BADI as the first alternative.
Refer to few links as well.
http://help.sap.com/saphelp_srm50/helpdata/en/ee/277e3c281f1817e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/2c/e68d406b305537e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/0e/bc7d3c6715c854e10000000a11402f/content.htm
Regards
- Atul

One step purchase order approval

Hi,
I have activated the one step PO approval workflow. How do I assign the agents. I have tried to do it in SPRO - Maintain agent assignemnet for tasks but was unable to do it as I did not get the link.
Any help is appreciated.
Joe Vellaiparambil

Hi
In the SRM transaction OOCU, use path / link
SRM --> SRM-EBP --> SRM-EBP-WFL then you will find agent assignment tab.
Please refer to these links as well.
one step approval
http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/ee/277e3c281f1817e10000000a114084/frameset.htm
PO: 1 step approval - agent assignment
how to start one-step workflow..
Re: how to start one-step workflow..
Workflow without approval not working
Workflow configuration step by step guide...
Re: WS14000145 Approval N-Step for PO skips others approvers
One step purchase order approval
Also try this...
Suggest you to go through the documentation before actually doing it at least once.
Please check this link:
https://websmp208.sap-ag.de/ibc-srm
You will find scenario specific config guides for EBP40. Download the config guide for self-service procurement and gothrough workflow configuration section. This is still the same in SRM50 also.
Regards
- Atul

Need Example screenshots : Purchase Order Approval 2/3 steps

Hi,
I'm new to workflow.
Need screen-shots of workflow customization for Purchase order approval with 1, 2 or 3 steps.
Also if you could provide detail on the Container element used for purchase order
regards,
Chandeep Singh
[email protected]

Hi chandeep,
Check out this link . the link is pretty gud with pictorial representation .
http://www.codeproject.com/useritems/POWorkflow.asp
this definitely helps you.
Regards,
sateesh.

Steps for deleting release stretagy for Purchase Order

Hi,
Could you please help in deleting / cancelling the exisiting PO release stretagy? I need to create new release stretagy which is totally different from the existing one.
What are the steps in cancelling existing release strategy.
Can the same steps be used for cancelling release stretagy for Purchase Requistion?
Thanks.
Anand

Hi,
you goto
spro> mm>purchasing> purchase order> release procedure
there you go to to release strategy
then follow following steps.
1.delete release strategy
2.delete release codes
3.delete release groups
then to create new release strategy and follow following steps
1 create characteristics ( use table cekko)
2 create class( class type 032)
3 . create release group and assign class to it.
4 create release codes
5 then create release strategy using release group and release code.
hope this will solve your problem
Regards,
Vijay

Create a purchase order strategy with four release steps.

Hi all,
how can I create a purchase order release strategy with 4 release steps?
The steps have to be the following:
AC (Buyer);
CO (Controller);
FI (Finance);
AD (CEO).
I couldn't configure and add entries in "Release prerequisites" (trx.OMGS).
Best regards

Hi ,
The implemantation steps as follows ;
Materials Management -- Purchasing -- Purchase Order --Release Procedure for Purchase Orders
1 . Edit Characteristic ; You must create characteristics that related your strategy first . IN additonal data screen use "CEKKO " as table and appropriate field as field name .
2. Edit Class ; Create your class with class type - 032 . And enter your characteristics that created first step .
3. Define Release Procedure for Purchase Orders
                a.Create Release Groups and enter your class
                b.Create release codes related with Buyer , controller etc.
                c.Create Release indicator
                d. Create Release Strategies ; Enter your release codes and in classificaiton area , you must enter your values that related with characteristics that created step 1.

LSMW Steps to create purchase order

Hi all ,
Tell me steps using LSMW to create purchase order .
Any suggestiosns welcome,
Regards,

hi,
Follow this link for step by step tutorial.
http://www.****************/Tutorials/LSMW/LSMWMainPage.htm
Hope this helps, Do reward.

Standard n-step approval workflow for Purchase Order in sap 4.7?

Hello friend,
In SAP 4.7 there is any standard template for n-step approval workflow for Purchase Order.
thanks in advance.

Hi AM,
there is no std template for n-step approvals but for Single Release.
What you could do is create a custom one as per the number of approvals for PO.
Also note a PO Release Strategy can handle only 8 levels of approval.
Hope it helps.
Aditya

Purchase Order Step-by-Step

Similar Messages

Maybe you are looking for