Regarding releasing external purchase documents using workflows

Hi,
i am working on "releasing external purchase documents" scenario. For this i am having STANDARD workflow which is "WS20000075" and using "RELEASE STEP CREATED" event in object type BUS2012 . I have created release strategies for all POs. But whenver i create a PO the event RELEASE STEP CREATED is not getting activated. So, can anyone tell me do i need to anything in configuration part. tell me when this event will get triggered and how to do it..
Thanks and regards,
Ravi varma

YOu have to some configurations like:
Specify whether each release code is relevant to workflow
Assign a release point to workflow-relevant release codes
Activate your workflow.
Have you done all those things or do you need input for that?
Thanks,
Shweta

Similar Messages

Is not post parked document using workflow

Hi friends!!!!
Weu2019re using workflow for document parked through FIPP_FRAME_1 template and task Task WS10000051 delivered by SAP
The system does not post parked document parked that are processed via the workflow although they have been released, but, when we try posting it through the menus u201CDocuments > Complete" in the Tcode FBV0 the document parked is not post.
When checked in the Tcode SWIA, We´re having an endless loop
the moment we choose workflow logs option. The items keep on
repeating on a loop giving us a long scroolbar with repeated lines.
Thanks!!!!

In FBV0 use document list and the try and post it
Cheers
Prakash

Moving document using workflow from sub site to site collection

Hi,
I was looking for steps to move documents from sub sites to site collection or from sub site to sub-site in SharePoint 2013. I tried with reusable workflow but unable to set the target library which is in site collection level. Its not listing down the site
collection libraries. It is showing libraries in sub site.
Any ideas how it can be done by workflow? or any other approaches there ?
Your suggestion would be appreciated.
Thanks., Prakash

Hi,
According to your post, my understanding is that you wanted to move document from one site to another site using workflow.
There is no out of the box action to achieve it in SharePoint.
However, there is an avaiable activity Copy List Item Extended Activity in the CodePlex, you can have a look at it.
http://spdactivities.codeplex.com/
Note: the activity should be used in the SharePoint 2010 workflow platform.
We can also use the site content and structure to achieve it(within the site collection ) .
Make sure you have following features activated:
Site Collection feature: SharePoint Server Publishing Infrastructure
Site Feature: SharePoint Server Publishing
Then go to: Site Actions >> Site Administration>>Content and Structure
Please refer to 'Move items' topic in this post
http://office.microsoft.com/en-us/sharepoint-server-help/work-with-site-content-and-structure-HA010131723.aspx
What’s more, we can also achieve it programmatically.
http://social.technet.microsoft.com/Forums/sharepoint/en-US/139e54de-bfa3-47b2-a56b-641830f76a0c/move-folders-and-items-across-diferent-sites-collections?forum=sharepointdevelopmentprevious
http://www.codeproject.com/Articles/408817/Workflow-to-copy-a-file-from-one-site-to-another-s
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

ABAP runtime error in FBV2 Change parked document using workflow

Hi,
When selecting screen template variant in tcode FBV2 change parked document, I get abap runtime error DYNPRO_NOT_FOUND
Tcode- FBV2
Program- SAPLF040
Screen- SAPLF040 0310
Main Program - SAPMF05V
Information on were terminated.
Program SAPLF040 - in " %_CTL_END "
In the source code you have the termination point in line 50 of the (Include) program " <SYSINI> "
How can we solve this error. We are on ECC6 with release 600.
Thanks,
Mark

Hi Mark,
We have this same issue in transaction F-65
I believe that when a new screen template is configured, a new screen is generated within function group F040. A later action (applying a hotpack??) has removed this screen, but the config (in table T021D) still points the processing to the screen even though it has been removed.
Did you find a solution? We want to get the screen back as it is still valid to use this screen template in the business
Thanks
Ben

Release for purchase order for workflow

explain me about the release procedure for purchase order i am comfortable with all steps but for the last step were we will be defining the settings for workflow

It's all fine and dandy that you want to be polite and reply to every reply with a "thanks for your reply", but it isn't very informative. In fact, I'm leaning towards calling it SPAM, but that is perhaps going a bit too far. Such replies do not add one bit of information, they just mark the thread as having contents added since I last visited, and wastes my time as I look at the thread to see what new information has come up.
At the risk of sounding rude, could you please quit your habit and <u>instead</u> mark the question as answered if any of the answers solved your problem (handing out forum points where appropriate)? If none of the replies solved your problem, then please tell us how far they got you and what's stopping you now.
Thank you.

Releasing a Purchase Order Using ME28

Hi,
Is there any kinda IDOC which we can trigger when we release an order through ME28. If yes please tell me how can we configure that.
Thanks,
Neha

Hi Neha,
There is no such IDOC.
Regards
Abhii

Can't use Overall Release for Purchase Requisitions

I have two groups, AA and ZZ. Each group has it's own Class.
Group AA uses Cost Center Class (CN) (uses Characteristics Cost Center and Line Amount)
Group ZZ uses Order Class (OC) (uses Characteristic Order)
I have built one and only one Release Strategy for each of these Groups. These Strategies both work successfully when I select the other group to be the group for Overall Release. That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully. However, if I modify the req the strategy for ZZ, does not get applied.
The opposite is true. When AA is set to be for Overall release, then ZZ works. However, if I modify the req, then AA's release strategy does not get applied.
Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release. However, neither strategy works if its group is set to be the one for Overall Release.
What am I missing? I only have two classes, two groups, and two release strategies.

SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
Release procedure is of two types
Release Procedure without classification
             This procedure is applicable only for Purchase Requisitions.
             Here PR is released Item by Item only.
Release Procedure with classification
            This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract and scheduling agreements.
            Item by Item and Header level releases can be configured
            For PR - both item by item and Header level release can be configured
            For external purchasing documents - Release is possible only at Header level.
Step 1:
Create Characteristics
In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
            1) Total value of PR more than Rs 50,000
               create characteristic as "Release_PR_total_value" in transaction code CT04.
              Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg. INR or USD"
              Tab -values key in > 50000 INR
              Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"
              Tab - Restrictions - class type - 032 - Release strategy
            2) Plant
                 Create characteristic "Release_PR_plant" in transaction code CT04.
                 Tab - Basic data - Data type - CHAR; Number of chars - 4
                 Tab - Values - Key in all the plants for which you are required to configure release proc. eg. 1000,2000,3000
                 Tab - Additional data - Table name CEBAN and Field Name is WERKS.
            3) Purchaisng Group
                 Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                Tab - Basic data - Data Type - char, Number of chars eg. 3
                Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
Step 2:
Define class in transaction code CL02
Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
Tab - Basic data - Enter description as "PR_Release-Proc",
status- Released, Same classification - check the push button - Warning Message
Tab- CHAR Enter above created 3 characteristics
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
here define
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
Here assign class "PR_Release_proc" against release code "01"
check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user            - Level -             Release code
PR creator - clerk or Business user -
Approver    - Supervisor                 -   R1
Approver -   Project Lead              -   R2
Approver   - Asst. Manager             - R3
Approver   - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
For detailed info please refer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
Release indicators show the release status of a Purchase Requisition.
For detailed info please refer SAP Help official site
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
4.Release Pre requisites:
These define the order in which individuals or departments release the PR in sequence.
3.Release strategies
Create a new release startegy eg ."A1" or "U1" , write its description PR release for value >1 lakh
Now select release codes according to the Chart of Authority set by your client.
Eg.
Release startegy " A1 - PR release for value >1 lakh"
R1 - Supervisor
R2- Project Lead
R3- Asst. Manager
R4- General Manager
Now click on" Release Prerequisites "push button and check all the boxes in ascending order.Save the document
click on "Release statuses" push button, check release statuses then click on "Continue" push button.
In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
Classification data for example
1. Value - > 100000
2. Plant - 1000,2000,3000 etc
3. Purchasing groups - 101,102,103 etc
By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
In this way you can configure all the required Release startegies.
Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
Tcode - ME54N - For Individual Release
Tcode - ME55 - For Collective Release
For detailed info please visit SAP HELP website
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Regards,
Indranil

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?
Thanks

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

Purchasing vendor block(MK01) using workflow

Hi,
Can any body help to blcok purchasing vernder using workflow.
Right now i am doing with Userexit & BTE.
Can any body help me the same using Change document procedure.
Regards
kalyan.

HI Manahor,
Thanks for your quick reply.
I am dooing as
1)I created a custome business object
2)i am calling the same in BTE(1420) and i am uing user exit to get EKORG..
i need to block the vendor based on Purchase organization(EKORG).We are having LFA1 but here there is no EKORG in LFA1.
Same thing i want to do using change document procedure.I found change document KRED.But it is not working.
can you tell me how to do the same using Change Document Procedure Or can you tell me any other better solution other than User exit & BTE.

Send Purchasing Documents via email/fax to vendor

Hi all,
I have a customer requirement wherein Purchasing documents such as RFQ, PO etc need to be sent to vendors via email/fax. To cater to the customer's form requirements, we developed smartforms instead of using the standard MM purchasing smartforms. To call these smartforms in the print programs, we copied the standard print program SAPFM06P and commented out the function module ME_PRINT_PO in the routine ENTRY_NEU and added the our own code to call the custom smartform. The custom code segment in the print program is attached for reference.
Now, when we are trying to generate messages for the purchasing documents using output type External Send, the custom program does not pick up the email address maintained in the vendor master and instead picks up email address maintained in RFQ or PO initiator's user profile. We have made the required configuration for SCOT and SOST tcodes.
We tested the same scenario requirement using the standard print program and got the desired results i.e. the print program picked up the email address maintained in the vendor master. But with this approach, we cannot use our custom smartform.
Any help in this matter will be appreciated.
Regards,
Saad

Hi Biju !
Thanks for the response but I think you missed the point here. I am using different output types for RFQ and PO as well as different custom smart forms and we are using the same custom print program to generate output for both.
The issue is with the print program and not the output type as I mentioned that I have already got this thing working on our IDES using the standard print program and standard forms.
Tomas Talpa's response seems to be helpful. I'll get my technical consultant to amend the code accordingly and see if it works.
Regards,
SaaD Karim Mallick.

Amount release triggered at document posting, not parking

Our objective is to have senior accounting personnel approve/release journal entries that exceed a certain value, say $100,000. We have configured the release function for parked documents, using workflow WS10000051 with business object 'FIPP', event "COMPLETED" and release amount of $100,000. However, this appears to assume that staff have authorization only for parking, because if you have posting authorization, nothing stops you from posting a document over $100,000. It seems illogical that you have to exceed a certain $ value before the release will trigger, but if your document is below the amount, you can't post it because you can only park.
In order to avoid making approvers release every single journal entry, what we want is for users to be able to post any document below $100,000.00, but be forced to park ( save as completed) all documents >/= this limit. We tried setting up a validation on the document amount, but the error message forces us to exit completely, i.e. doesn't allow us to park the document.
Is there perhaps a different workflow that triggers at the point of posting, rather than parking, that will accomplish what we want?
Thanks,
Kathryn

Hi Kathryn,
Were you able to find a solution for this problem. We have the exact same requirement. Any pointers will be helpful. Thanks.
Regards,
Anuj

What is the difference between po and purchase document

Hi experts,
What is the difference between purchase order and purchase document.
Are they both same ?
Regards,
Nishuv.

Dear,
Purchasing document can be RFQ,PO,PR...RFQ...Contratc...etc
PR is interanl document that can be changed at any given point of time.
PO is external legal document and is formal request to vendor for materials.
External docments are legal documents used for procuremnt/quotation etc.
Internal documents like PR are for internal use.
Brgds,
Ashok

Badi for emailing the release for purchase order,

hi all,
in me28->release (approve) purchasing documents->release purchasing document..there u have a button (release+save ) button
i want to enhance at that pointi.e when u select the po no and click the button,automatically trigger an email to the vendor.
i tried for enhancement-point,badis,user exits....nothing is getting hit.
plz help,
points wiil be rewarded,
regards,
johnson

Hi
In the PO, you maintain output messages for Printing ./ Emailing/ Faxing the Purchase order.
The message has the despatch time maintained.
There are 4 different Depatch times.
1 - Send with periodically scheduled job
2 - Send with job, with additional time specification
3 - Send with application own transaction
4 - Send immediately (when saving the application)
When you select 4 in the message , whne the PO is finally released, the message will be processed automatically.
When you select 3, you need to run ME9F transaction to process the message output.
You can change the message in the PO , by clicking on the message button in ME22N transaction.
So if the user has released the PO in me28 & clicked on Save this will process the message output
Thanks & Regards
Kishore

Badi for release for purchase order.

hi all,
in me28->release (approve) purchasing documents->release purchasing document..there u have a button (release+save ) button
i want to enhance at that pointi.e when u select the po no and click the button,automatically trigger an email to the vendor.
i tried for enhancement-point,badis,user exits....nothing is getting hit.
plz help,
points wiil be rewarded,
regards,
johnson

Hi Johnson,
Check if your requiremnt can be satisfied by triggering OUTPUT type. Your functional person should be
able to help you with this.
Regards
Saket Sharma

Displaying documents using adf

hi:
i've a table that hase a column that carries the link to the directory where my word documents are stored, iwant to display thsi column as a hyperlink that when user clicks it will open the word file,but when i add href tags around the column value it displays nothing.
this what i do
<a href="<c:out value=${bindings.DocLink"/>">view document
any help will be apprciated
regards

A: displaying documents using adf

Are you using ADF Faces for the user interface?
If you are then you can use a goLink component and then bind the text and destination items to your data.
<af:goLink binding="#{backing_browse.outputText5}"
id="outputText5" text="#{row.Title}"
destination="#{row.Location}"/>

Regarding releasing external purchase documents using workflows

Similar Messages

Maybe you are looking for