Release Procedure&Workflow
Hello,
I try to implement workflow using the mulitilevel release procedure of purchase order (copy of WS20000075), my question is how you can achive the situation that workitem will be send to the receiver (next person in release level hierarchy) only when the previous approver approved it?
Greetings
Karol
refer the following links
http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/e0bbdb3c-d640-2a10-d3b2-e4d9b90536a6
http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/30488d68-8451-2a10-d993-bb36e56a1dc8
http://www.youtube.com/watch?v=2DjFcyiVXvU
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70fef212-b6cb-2c10-e085-c84b80d7068e
Similar Messages
-
Workflow in PR release procedure
Dear All,
Can anybody help me to know, the config steps used in PR release workflow and also the front end process of WF , how it works, any ref doc??
Thanks
RajeevHi Saini,
here are the useful links for your reference,
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM
chenna kesava reddy -
PO - Workflow for release procedure
hi Gurus,
i need your help for configuration Workflow for PO IN release procedure. Send e-mail... menssengers...etc.
tanks for send me doc´s and sap materials for configurations.
tks very much.hi,
check at SPRO --> MM --> Purchasing --> PO --> release procedure --> rel. proccedure w/o classification --> Define rel procedure for PO --> here do settings for workflow -
Workflow Concept for Release Procedure in SAP MM
Dear Support,
Please help me to understand the concept of Workflow in Release Procedure , and pls provide me any usefull Configuration
document so that I can able to Map .
So pls help me to sending document for workflow for Release Procedure.
ThanksDear Mr. venkatesh,
Mail will trigger in mentioned combination.
If you have mentioned same login id then mail go to one login id related mail or if you have mentioned different login then go to diffrenet login id.
1R 01 HOD IT US SAPMM01
1R 02 HOD HR US SAPPM01
1R 03 HOD FI US SAPPS01
1R 03 HOD FI US SAPPS01
Thanks
madhurendra Sharma -
Purchase Requisition Release Procedure Modification
Hi
In Purchase Requisition Release, we have two deviations in business requirement from standard SAP behaviour:
1. In multistep release, system allows PR release to be revoked by a lower level release authorized person even though higher level release has been done. Example, PR Release has release codes A1, A2 and A3, A2 can revoke release even after A3 has released the same. How do I prevent this from happening?
2. If business requirement is to have release procedure based on item cost per unit and not on total value of the line item, how can this be achieved?
Appreciate any guidance on these issues
Thanks
SriramHi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
gwa_event_container-element = 'PurchaseRequisition'.
gwa_event_container-value = gwa_im_eban-banfn.
append gwa_event_container to gi_event_container.
clear: gwa_event_container.
gwa_event_container-element = 'ItemOfRequisition'.
gwa_event_container-value = gwa_im_eban-bnfpo.
append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
and bnfpo = gwa_im_eban-bnfpo .
if sy-subrc <> 0 .
call function 'SWE_EVENT_CREATE'
exporting
objtype = 'BUS2009'
objkey = gwa_objkey
event = 'zcreated'
tables
event_container = gi_event_container
exceptions
objtype_not_found = 1
others = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi -
I have configured the PO release procedure for PO with header value of more then 25000. In the process I have created the following -
1. Custom Characterstic
2. Custom class
3. Release group
4. Release code
5. Release indicator
6. Release strategy
but the problem I am having is that the workflow event 'ReleaseStepCreated' is generated in the system even for PO with header value of less than $25000. Also the 'Release' tab is not appearing in the PO header.
Please help. Appreciate you time.
Sridhar JamiI think this issue is also related to mis entries in SWEC.
Go thru' this Note 797775 - Entry in Transaction SWEC hinders workflow. Verify all the steps stated in this note even you think it might not be the right note.
Regards, IA -
Hi SAP Gurus,
We do release procedure in PR with Account assignment category K.Here ,for collective release in pr (ME55),check box is disabled... Kindly help me how we enable the check box.We use scope of list as "F".All customization for release procedure is correct.
Thnks & Regards
SAP MM UserYou use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
Features
Each person involved in the release procedure effects release (signifies approval) via a release transaction, using his or her release code. Once effected, a release can also be cancelled with the same code (that is to say, the original status is reinstated).
If linkage to SAP Business Workflow has been defined for a release code, rejection is also possible. This is only possible for purchase requisitions.
Which Documents Can be Released (Approved)?
Release procedures can be defined for the following documents:
Purchase Requisition
The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet
Release Procedure for Purchase Requisitions
Two different procedures are available for requisitions:
With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
Without classification
With this procedure, requisitions can only be released at item level.
The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
Release Procedure for External Purchasing Documents
External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
sri -
Purchase requisition release procedure through User-Exit
Hi Workflow Guru,
I have a requirement to configure purchase requisition workflow . the workflow should trigger through release strategy.
The approver should determine through user-exit and the approver should determine based on value and quantity and that can be define in user-exit. as per my knowledge the value should mantain in SPRO-Release procedure. Please clarify me is it possible through user-exit. I am worked on user-exit for release procedure based on purchasing group.
Thanks in advance.
Regards,
Ranjan TiwariHi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
gwa_event_container-element = 'PurchaseRequisition'.
gwa_event_container-value = gwa_im_eban-banfn.
append gwa_event_container to gi_event_container.
clear: gwa_event_container.
gwa_event_container-element = 'ItemOfRequisition'.
gwa_event_container-value = gwa_im_eban-bnfpo.
append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
and bnfpo = gwa_im_eban-bnfpo .
if sy-subrc <> 0 .
call function 'SWE_EVENT_CREATE'
exporting
objtype = 'BUS2009'
objkey = gwa_objkey
event = 'zcreated'
tables
event_container = gi_event_container
exceptions
objtype_not_found = 1
others = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi -
Release procedure in POs and classes.
Hi,
in SPRO, Logistics - General, Materials Management, Purchasing, Purchase Order, Release Procedure for Purchase Orders, Edit Class, I see a long list of class.
If 032 is specific for a release strategy what are the others classes useful for ?
Best regardsHi,
To work with workflow you have to define work flow at the time of Release code creation then with respective role has defined & assigned to the concerned user.
Regards
Ravi shankar. -
hi sapgurus,
here is the scenario,
i have as issue ( for P.O value only)
1) if the value is < 2 lacks then one person will release.
2) if the value is > 2 lacks then 2 persons will releasehi,
3.4.24 Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1 Creation of Characteristics
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Characteristic
Transaction Code CT04
2. On the Characteristic screen, make the following entries.
3. In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name Description User action and values Note
Select Addnl Data tab
Table Name Table Name CEKKO
Field Name Field Name GNETW
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab
Description Description Total net order value
Status Status Released
Data Type Data type Currency format Selected by system
Number of characters Number of characters 15
Decimal places Decimal places 2
Currency Currency INR
Interval vals allowed Interval values allowed Check this tick box
Multiple Values Multiple values allowed Select this radio button
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2 Creation of Class
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Class
Transaction Code CL02
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Class PORELPROC
Class Type Class Type 032
Choose Create icon or white paper icon to create new class.
Description Description Purchase Order Release Procedure
Status Status Released
Choose Char. Tab to input characteristic name.
Characteristic Characteristic POVAL Created in above step
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3 Configuration of Release Procedure
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Define Release Procedure for Purchase Orders
Transaction Code SPRO
2. On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Rel. Group Release Group 02
Class Class Name PORELPROC Created in above step
Description Description PO Release Procedure
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the entries.
6. Choose yellow arrow to go back to popup screen.
7. Choose Release Codes to select.
8. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Grp Release group 02 Created in above step
Code Release Code 01
Workflow Workflow Leave it blank
Description Description Purchase Officer
Grp Release group 02 Created in above step
Code Release Code 02
Workflow Workflow Leave it blank
Description Description Materials Manager
9. Choose Enter to complete the entries
10. Choose Save icon or Ctrl + S to save the entries.
11. Choose yellow arrow to go back to popup screen.
12. Choose Release indicator to select.
13. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Release ind. Release Indicator 1
Released Released Leave it blank
Chgable Changeability 4
Value change % Change of value 10%
Description Description Purchase Order Blocked
Go to 2nd line and input the following values:
Release ind. Release Indicator 2
Released Released Select Check box
Changeable Changeability 6
Description Description Purchase Order Released
14. Choose Enter to complete the entries
15. Choose Save icon or Ctrl + S to save the entries.
16. Choose yellow arrow to go back to popup screen.
17. Choose Release Strategies to select.
18. Choose New Entries icon and make the following entries:
19. System will give new screen New Entries: Details of Added Entries
Field name Description User action and values Note
Release Group Release group 02
Rel. Stategy Release Strategy S1
Capital Items Release
Release Code Release Code 1 01
Release Code Release Code 2 02
20. Choose Enter to complete the entries.
21. Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22. Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
23. Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24. Choose Next Screen icon or choose F8 to continue.
25. If you want to simulate the release procedure you can choose Release Simulation icon.
26. Choose Enter to complete the entries.
27. To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4 Assignment of Values to Release Procedure
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Cross-Application Components Classification System Assignments Assign Object to Classes
Transaction Code CL20N
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Type Class Type 032
Choose Enter to Assign values.
Release group Release Group 02
Rel. Strategy Release strategy S1
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Follow these steps
G.Ganesh Kumar -
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.
ManjitHi 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 -
Work Flow and Release procedure
Hi,
What is the coorelation between the Work flow and Release Procedure in the MM Module.
Where exactly they both correlate ????
Where the Release Procedure stops and where the Work flow takes over ???
If with an example it wud be easy.
wth rgds
SVU123check
/people/sapna.modi/blog/2007/02/19/workflows-for-dummies--introductionpart-i
/people/sapna.modi/blog/2007/04/27/workflows-for-dummies--workflow-builderpart-ii -
PO Release strategy workflow configuration
Hi All,
I am doing PO release strategy workflow configuration in PFTC, Please tell me in this which all configurations come in workbench transport request and which all come in automatic transport request.
Please guide me
Thanks in advance
PavanThe PR WS00000038 standard Workflow is very simple, you don't have to create a new one, it works, the think is that you need to make some configs in the SPRO
spro
Material Management/Purchaising/Purchase Requisition/ Release Procedure / Procedure With Clasification / Set up procedure with classification/ Workflow
In this config you need to add the: Release Group / release code / object type( US for user id's) / and the User. You have to add one line for each release code that you configured in your release strategies.
After that you have to review the linkage table Tcode: SWETYPV, find the object type BUS2105 and activate the linkage for the event releaseStepCreated, in this you will see the WS00000038.
Now you can start to testing the notifications in the inbox(SBWP) for the configured users using the me51 tcode. -
Release Procedure for every Purchasing documents
Hi,
for a procument of material eg:- Material007
Can I set Release Procedure for Purchase rquisition
then after releasing Purchase rquisition i need to create a RFQ
which is also subject to Release Procedure ,After releasing RFQ I should able to enter into a Contract,which also subject to Release Procedure ,After releasing Contract i need to create a Purchase Order which is also subject to Release Procedure,After releasing Purchase Order only I should be able to Receive the goods.
Is it possible to do this way ?Can any one help me?
ThanksWhy you want to put so many locks??????
well if case your required use below steps for all document typew in IMG.
suggestion to download the BBP from below link also
http://help.sap.com/bestpractices/BBLibrary/bblibrary_start.htm
3.4.24 Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1 Creation of Characteristics
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Characteristic
Transaction Code CT04
2. On the Characteristic screen, make the following entries.
3. In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name Description User action and values Note
Select Addnl Data tab
Table Name Table Name CEKKO
Field Name Field Name GNETW
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab
Description Description Total net order value
Status Status Released
Data Type Data type Currency format Selected by system
Number of characters Number of characters 15
Decimal places Decimal places 2
Currency Currency INR
Interval vals allowed Interval values allowed Check this tick box
Multiple Values Multiple values allowed Select this radio button
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2 Creation of Class
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Class
Transaction Code CL02
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Class PORELPROC
Class Type Class Type 032
Choose Create icon or white paper icon to create new class.
Description Description Purchase Order Release Procedure
Status Status Released
Choose Char. Tab to input characteristic name.
Characteristic Characteristic POVAL Created in above step
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3 Configuration of Release Procedure
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Define Release Procedure for Purchase Orders
Transaction Code SPRO
2. On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Rel. Group Release Group 02
Class Class Name PORELPROC Created in above step
Description Description PO Release Procedure
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the entries.
6. Choose yellow arrow to go back to popup screen.
7. Choose Release Codes to select.
8. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Grp Release group 02 Created in above step
Code Release Code 01
Workflow Workflow Leave it blank
Description Description Purchase Officer
Grp Release group 02 Created in above step
Code Release Code 02
Workflow Workflow Leave it blank
Description Description Materials Manager
9. Choose Enter to complete the entries
10. Choose Save icon or Ctrl + S to save the entries.
11. Choose yellow arrow to go back to popup screen.
12. Choose Release indicator to select.
13. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Release ind. Release Indicator 1
Released Released Leave it blank
Chgable Changeability 4
Value change % Change of value 10%
Description Description Purchase Order Blocked
Go to 2nd line and input the following values:
Release ind. Release Indicator 2
Released Released Select Check box
Changeable Changeability 6
Description Description Purchase Order Released
14. Choose Enter to complete the entries
15. Choose Save icon or Ctrl + S to save the entries.
16. Choose yellow arrow to go back to popup screen.
17. Choose Release Strategies to select.
18. Choose New Entries icon and make the following entries:
19. System will give new screen New Entries: Details of Added Entries
Field name Description User action and values Note
Release Group Release group 02
Rel. Stategy Release Strategy S1
Capital Items Release
Release Code Release Code 1 01
Release Code Release Code 2 02
20. Choose Enter to complete the entries.
21. Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22. Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
23. Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24. Choose Next Screen icon or choose F8 to continue.
25. If you want to simulate the release procedure you can choose Release Simulation icon.
26. Choose Enter to complete the entries.
27. To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4 Assignment of Values to Release Procedure
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Cross-Application Components Classification System Assignments Assign Object to Classes
Transaction Code CL20N
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Type Class Type 032
Choose Enter to Assign values.
Release group Release Group 02
Rel. Strategy Release strategy S1
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic. -
Hello All,
Users have created purchase order and then submitted for release using workflow. And later at they deleted the PO. The Manager now has a notification in his Business Workplace Inbox asking him to release the purchase order but he can't release it since it is deleted and he can't delete the notification since he hasn't activated it.
standard delete and resubmit options are greyed out and not available in the inbox.
Now How to delete this notification in his inbox.
Any help will be appreciated a lot.
Regards
SamsonHi,
For mail facility, you need to activate workflow for PO release procedure;
Go to SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
Now come to SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
Now Go to OOCU > here under MM, go to MM-PUR,
Now click on "activate event linking"
Here open "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button
Here activate "Event linkage activated" and also activate "Enable usage of event queue"
and Save data.
Same way and click on "Assign agents" and proceed all above steps.
Now create a PO and check the SBWP for SAP Mail of respective Users
Maybe you are looking for
-
Zen Vision M Recognized by XP Pro, but not by Creative Media Organizer or other transfer softw
I have a Zen Vision M. It worked perfectly for months. Suddenly, it wouldn't turn on. I started it in Rescue Mode, did a clean up and several reboots. It started doing a rebuild on every start. Now when I plug it into the USB port, my computer recogn
-
On the fifa 14 iTunes app it won't let me turn on device music, how can I get this to work?
On the fifa 14 iTunes app it won't let me turn on device music, how can I get this to work? I have bought full access to it.
-
Iphone 3G does not scroll all the e mails is it the phone or the soft ware software
having trouble scrolling a full page of e-mails, there isa blank spac at the bottom of the bottom any ideas
-
Outbound file adapter for multiple record write
am using jdev 10.1.3.1 and SOA suite 10.1.3.1 I am trying to read a table and write the records to a csv file. The bpel process I have constructed is : receive > assign input value to table select parameter > select records from table > assign table
-
I accidentally deleted "My Picture" folder and tried to do a recover to earlier version and am getting the error code "0x800704c8 the requested operation cannot be preformed on a file with a user-mapped section open". I am using Windows 7 on an HP P