Problem in Rejecting the purchase order release workflow

Hai Friends ,
I did the purchase order workflow. it will working fine. when a approver refused the release, the intimation need to send to the previous approvers as well as po creator. but there is no method available in the bus2012 for purchase order rejected. what i want to do ?
i did the purchase requisition workflow also. In that workflow there is a method in the name of " InfoReleaseRejected". i used this method in my task it will working fine. but there is no method available for Purchase Order.
Regads,
R. Sathis Kumar

Hai suthakar,
I created the customized workflow. this workflow working well when the approvers approved. but it is not do anything when approver reject the release.
Regards,
Sathis Kumar R

Similar Messages

Dead Line Monetering in Purchase Order Release Workflow

Hi Experts,
I have activated Standard Purchase Order Release workflow and it works fine now i have a requirement of Dead Line monetering for 2 days. In Standard Release Activity TS20000166 if i give 2 days in Latest End.
Will it work in such a way that if the first approvar does not take any action for 2 day then it automatically esculates to the next person in the release strategy.
Or should i use Modeled Deadline for esculation to next Level.
Regards,
Hari

Hi,
If you just have 2 days on the latest end tab, the workflow will only send a deadline notification to the current agent and WILL NOT escalate.
You have to use modelled deadline and in that branch route the workflow to the next approver based on your agent determination rules.
Satish

Idoc will trigger after purchase order release workflow

Hi Workflow Guru,
I have a requirement to configure Purchase Order release workflow. I am configure the same its working fine, but my client requirement is when the purchase order finaly release one IDOC will be trigger and the document will send to other system. We have PI for Interface.
I want to add new activity step in my workflow template to trigger a Idoc after final release.
Please give me a idea , how to do this.
Thanks in advance.
Regards,
Ranjan

Hello,
Use the standard IDoc LOIPRO01. Have a look at program RCCLORD. use it in the method of the business object you are using.
You'll need to configure the idocs and partner profiles as normal.
Regards,
Kiran Telur

HOW CAN I GET THE PURCHASE ORDER RELEASE DATE

Dear All,
HOW CAN I GET THE PURCHASE ORDER RELEASE DATE - any reprot is there?
Thank you
Ahmad

Hi,
u goto that PO and select Environment on top line .under that select header changes if u click on that u will get entire details who reased when released, date , time etc
regards,
Srinivas Kona

Problem in Purchase Order Release Workflow

Hello Experts,
I am working in a workflow for releasing PO.In this workflow I have created just one activity step type to release a purchase order.Here I have taken PO(BUS2012) object as input parameter.In the activity step type I am using a custom task(TS99900011).In this task I have used BUS2012 as Business Object and SINGLERELEASE as method.Here I have used 3 terminating events of BUS2012 object.They are Released, Reset and significantly changed. I have just copied the standard task (TS20000166).
Now my activity step has four outcomes.We can see them in Outcomes tab.
1.Purchase Order Released(Cgy:External Events)
2.Not Used(Cgy:External Events)
3.Purchase Order Changed Significantly(Cgy:External Events)
4.Processing obsolete(Cgy:Internal Events).
I have set agent assignment as user Manas.
Now, when I am testing the workflow with a valid PO number as input the work item goes to my inbox for release the PO as expected.There I can release or reject the PO.But while saving after releasing or rejecting the PO the work item still remains in Workspace Inbox.Any of the four outcomes is not appropriate for the activity.
Can anybody suggest any solution to overcome the situation.
Are the external events are really helpful in developing workflow activity?Please suggest.

Hi Manas,
There is one option, where you can stop the workitem and even entire workflow.
Use Fork for parllel processing
Have a Wait step with BUS2105-Significantlychanged event and outcome to the end of workflow.
Thanks,
Sudhir.

Purchase order release workflow - urgent

Hi friends
When iam creating purchase order it trigger the workflow WS20000075 for releasing purchase order in that purpose what can i do..
How can i set the Agents
How can i trigger the events - i think in that purpose using pftc we trigger the workflow.. so i need clear steps from beginning onwards..
my exact requirement
once i create purchase order, the workflow will be triggered..
after that the mail goes to the approver.. if he/she click that mail purchase order release statement want to be open.. after that he/she release purchase order it will goes to the next level..anyone give the step by step procedure..for that
Thanks
Gowrishankar

yes prabakar.. but iam confused..
You can get step by step workflow for PO using standard workflow
Release of Purchase Order :WS20000075
And for two levels of approvals you have to configure in SPRO the path is
Purchase Order:
SPRO> Material Management->Purchasing->/Purchase order-->Release procedure ---> Procedure with classification ---> set up procedure with classification ---> double click on Release strategies and Workflow.
If you don't know about this configuration, you have to confirm with your MM consultant.
after finish this iam triggering events using pftc
in that pftc iam choosing business object bus 2012 for po release..
i think thats enuf..
After that it is possible to trigger workflow.. when iam create purchase order..
Thanks
Gowrishankar

Purchase Order Release Workflow

Hi,
I need to create the Workflow for the PO approval process. I am new to workflow.There are 4 level based on different dollar value.The email should go from one level to next for the approval.
Dollar value
1-10               level1
11-20            level2
>20              level3
If we get Order for 25 dollar then email shoudl go to level1,level2 and level3.
My question
1 Should I copy standard PO approval workflow WS20000075 Release of purchase order into new workflow ?
2 What are the steps in configuring this - Agent assignment,tcode etc?Kindly provide details as possible.
Note- aWill be rewarded in points
Thanks
Prashanta

Hi Prashantha,
First of all, You need not have to copy and make a new workflow if the requirement is only to
approve. You can use the standard workflow.
You have to carry on the following activites:
1) Define Organisation Struture
2) Application specific customizing
     A) Define Characteristic values
     B) Define release codes and make them Workflow relevant
     C) Define release strategy
         Based on the characteristic values the Purchase Order will be applied to a particular release
         strategy and will fall under specific catagory to pass through different level of approvals
     D) Assign release codes to corresponding Orgnisational Objects with ID
3) Task specific customizing
    A) Activate the event linkage for the standard workflow WS20000075
    B) Do the agent assignment for the TS20000166
    C) Make other two tasks as General Tasks (TS20000168,TS20000167).
4) Delete the row for event "Releasestepcreated" from SWEC (OSS Notes: 797775)
Voilla !!!    You have now successfully completed. Bingo !
Please award me points as promised.
Thanks,
Deb
Edited by: debabrata mohanty on Dec 4, 2008 1:59 PM

Want to restrict the Purchase order release at lower level...

Dear Friends,
The Problem i am facing is that the release strategy defined in Purchase order is such that it will be released by four authorities,
& When 4th One, The Highest authority releases the order it should not get unreleased by lower level authorities.I want to configure this.
Partially it is completed, as if Tcode me29n is used for cancel release then it is restricted by Going into
SPRO-MM-Purchasing-Purchase Order-Release Procedure for Purchase Order- Define Release Procedure for Purchase Order
& suggesting it there.into Release Indicator
But still it can get unreleased by Tcode me28.
Kindly Suggest,
Gaurav Chopra

Hi,
This is the standard like release srtetegy will not have the restriction only the release do the release . He can also should de release the document.
this can't control.
SAM

Rgarding Purchase order release workflow

Hi Gurus,
What is the roll of an abaper while using standard workflow for any thing like Purchase order release ?
If any one worked pls send me the screen shot both functional as well as technical documentation. Becasue our team is new to workflow.
Already i searched in sdn.sap.com as well as **************** etc........
In **************** they gave screen shots but some thing is missing . Pls any one worked on workflow( standard sap scenario).forward those documents to me
Thanks in Advance,
Nag

Hi Naganjana,
In SWDD transaction open the PO std workflow template (WS20000075). Then click on the Basic data icon (hat icon). Go to start events tab --> Click on the Activate (A). Then now open every task. Go to additional data --> Maintain Agent --> General Task. Generate Index. Now come back to workflow screen. You have define agent. As you are going to determine the agent based on PO value you have write your own rule. For this go to PFAC tcode. Create a rule.
Check out the link below which gives you an idea on how to create a rule.
[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d053fe48-6513-2b10-a59f-871923ff99d8]
Then define this rule in your workflow taks. Do proper binding. Save and activate your workflow.
Validation : Go to SWE2/SWETYPV tcode. Check if event linkage is active between workflow template (WS20000075) and Event BO : BUS2012 and RELEASESTEPCREATED (Check if the checkbox for event linkage is checked).
Let me know if you have any queries.
Regards,
Raj

Problem in enhancing the Purchase Order BADI with custom fields

Hi All,
I have problem in populating the cutom fields for the Purchase Order. I have created a custon include and i am passing the values to the extension of the Function module BAPI_PO_CHANGE In ECC 6.0. I have one currency field (ZZMASSIST) in the header level and three curr fields in the item level , due to this currfields we are getting the errors like "Error transferring ExtensionIn data for enhancement CI_EKPODB" and "Error transferring ExtensionIn data for enhancement CI_EKKODB" .
So i am looking to implement the BADI "ME_BAPI_PO_CUST " . Please provide me the sample code for maintain the currency fields in method IF_EX_ME_BAPI_PO_CREATE_02~MAP2I_EXTENSIONIN.
Thanks in Advence.
Regards,
Venkat Appikonda.

Hi Venkat,
Saw that you solved the issue, can I ask how do you implement it? Is the implementation done in the BAPI itself?

Purchase order release workflow rule

Hi ,
I have made a zcopy of standard workflow(WS20000075) for PO release. My requirement is that there are three level of approvers who have to release the PO. MM consultant says he will assign the approvers for all three levels from SPRO. As per the std workflow there is only one level of approval as far as i have understood .every time if approver rejects the po the mail should go to outlook also , to initiator and the next approver .
standard rule 20000027 is taken care for all three levels of approvals ..what is the binding for rule to workflow?
from workflow side what are the customize things should i follow..i am new to this MM workflow can u please guide me ..
thanks,
sandeep chennoju .

Hi Sandeep
The requirement changed!!!! :-)
Okay...for the email on DEADLINE BREACH
1) You Do not need the fork in the deadline branch
2) Instead, call an Activity Step which calls a method -> Input: WF Initiator (full US + Username), PO Number and the Current Release code
3) In the method coding, call rule 20000027 using FM RH_GET_ACTORS, get the agents (with OTYPE) for the PO and Current Release code
4) Now Fill an internal table (of type TSWHACTOR) with OTYPE and OBJID returned from the above Function Call
5) Append WF Initiator to this table -> OTYPE = US and OBJID = username
6) So you have a table with CURRENT Approvers and the Initiator
7) Pass back this table to task and workflow
8) Now use a mail step, Set Recipient Type as 'G' (org Object) and EXPRESSION = that TABLE passed from above call (type TSWHACTOR)
9) Ensure that the settings are done for SO16 -> Tab Mail Sys Grp -> Send to users home address is selected (in each client – this is not transported, hence maintain in every system once)
10) Ensure that the users have their email ID maintained in User Master (SU01) and the communication Method Set as INT (OR Email is maintained in HR Master Infotype 0105 - if your setup is using that)
11) Ensure Job SWWDHEX is running periodically in the background
12) Ensure Basis Settings and send job are in place to send outbound emails
What will happen when the deadline gets over:
1) SWWDHEX job will pick up the item and the control will come to deadline branch
2) The new step/method will get the agents of Current release code using the FM Call; it will also add WF Initiator to the list
3) The mail step will send to the ORGNIZATIONAL Objects (the Usernames, Positions passed to it in table of type TSWHACTOR)
4) SO16 settings will ensure that the mail is sent to the email address
5) Email address is picked up by the system automatically from User Master or HR Info type 0105 (order is really not known)
6) Basis settings and send job will send the email out of the system
I hope I was able to get your requirements right this time and these will not change :-)
Regards,
Modak

Problem in replicating the purchase order items

Hi,
The Requirement is to replicate the line items of Purchase Order in ME23N which is extracted from BAPI_PO_GETDETAIL1 and copy it in BAPI_PO_CHANGE .
The problem is when i am passing ACCTASSCAT(Account assignment category) it is not replicating else it is replicating.
while debugging the program the i am getting the data into internal table but it is not getting updated in database (ME23N).
I am getting messages in RETURN table as follows:
Instance 4200000020 of object type PurchaseOrder could not be changed
Purchase order item 00170 still contains faulty account assignments
Please also populate interface parameter POITEMX
Account 402201 requires an assignment to a CO object
Please find the code below.

move 'X' to LT_ITEMX-HL_ITEM.
    move 'X' to LT_ITEMX-GR_TO_DATE.
    move 'X' to LT_ITEMX-SUPP_VENDOR.
    move 'X' to LT_ITEMX-SC_VENDOR.
    move 'X' to LT_ITEMX-KANBAN_IND.
    move 'X' to LT_ITEMX-ERS.
    move 'X' to LT_ITEMX-R_PROMO.
    move 'X' to LT_ITEMX-POINTS.
    move 'X' to LT_ITEMX-POINT_UNIT.
    move 'X' to LT_ITEMX-POINT_UNIT_ISO.
    move 'X' to LT_ITEMX-SEASON.
    move 'X' to LT_ITEMX-SEASON_YR.
    move 'X' to LT_ITEMX-BON_GRP2.
    move 'X' to LT_ITEMX-BON_GRP3.
    move 'X' to LT_ITEMX-SETT_ITEM.
    move 'X' to LT_ITEMX-MINREMLIFE.
    move 'X' to LT_ITEMX-RFQ_NO.
    move 'X' to LT_ITEMX-RFQ_ITEM.
    move 'X' to LT_ITEMX-PREQ_NO.
    move 'X' to LT_ITEMX-PREQ_ITEM.
    move 'X' to LT_ITEMX-REF_DOC.
    move 'X' to LT_ITEMX-REF_ITEM.
    move 'X' to LT_ITEMX-SI_CAT.
    move 'X' to LT_ITEMX-RET_ITEM.
    move 'X' to LT_ITEMX-AT_RELEV.
    move 'X' to LT_ITEMX-ORDER_REASON.
    move 'X' to LT_ITEMX-BRAS_NBM.
    move 'X' to LT_ITEMX-MATL_USAGE.
    move 'X' to LT_ITEMX-MAT_ORIGIN.
    move 'X' to LT_ITEMX-IN_HOUSE.
    move 'X' to LT_ITEMX-INDUS3.
    move 'X' to LT_ITEMX-INF_INDEX.
    move 'X' to LT_ITEMX-UNTIL_DATE.
    move 'X' to LT_ITEMX-DELIV_COMPL.
    move 'X' to LT_ITEMX-PART_DELIV.
    move 'X' to LT_ITEMX-SHIP_BLOCKED.
    move 'X' to LT_ITEMX-PREQ_NAME.
    move 'X' to LT_ITEMX-PERIOD_IND_EXPIRATION_DATE.
    move 'X' to LT_ITEMX-INT_OBJ_NO.
    move 'X' to LT_ITEMX-PCKG_NO.
    move 'X' to LT_ITEMX-BATCH.
    move 'X' to LT_ITEMX-VENDRBATCH.
    move 'X' to LT_ITEMX-CALCTYPE.
    move 'X' to LT_ITEMX-NO_ROUNDING.
    move 'X' to LT_ITEMX-PO_PRICE.
    move 'X' to LT_ITEMX-SUPPL_STLOC.
    move 'X' to LT_ITEMX-SRV_BASED_IV.
    move 'X' to LT_ITEMX-FUNDS_RES.
    move 'X' to LT_ITEMX-RES_ITEM.
    move 'X' to LT_ITEMX-GRANT_NBR.
    move 'X' to LT_ITEMX-FUNC_AREA_LONG.
    move 'X' to LT_ITEMX-ORIG_ACCEPT.
    move 'X' to LT_ITEMX-ALLOC_TBL.
    move 'X' to LT_ITEMX-ALLOC_TBL_ITEM.
    move 'X' to LT_ITEMX-SRC_STOCK_TYPE.
    move 'X' to LT_ITEMX-REASON_REJ.
    move 'X' to LT_ITEMX-CRM_SALES_ORDER_NO.
    move 'X' to LT_ITEMX-CRM_SALES_ORDER_ITEM_NO.
    move 'X' to LT_ITEMX-CRM_REF_SALES_ORDER_NO.
    move 'X' to LT_ITEMX-CRM_REF_SO_ITEM_NO.
    move 'X' to LT_ITEMX-PRIO_URGENCY.
    move 'X' to LT_ITEMX-PRIO_REQUIREMENT.
    move 'X' to LT_ITEMX-REASON_CODE.
    move 'X' to LT_ITEMX-LONG_ITEM_NUMBER.
    move 'X' to LT_ITEMX-EXTERNAL_SORT_NUMBER.
    move 'X' to LT_ITEMX-EXTERNAL_HIERARCHY_TYPE.
    move 'X' to LT_ITEMX-RETENTION_PERCENTAGE.
    move 'X' to LT_ITEMX-DOWNPAY_TYPE.
    move 'X' to LT_ITEMX-DOWNPAY_AMOUNT.
    move 'X' to LT_ITEMX-DOWNPAY_PERCENT.
    move 'X' to LT_ITEMX-DOWNPAY_DUEDATE.
    move 'X' to LT_ITEMX-EXT_RFX_NUMBER.
    move 'X' to LT_ITEMX-EXT_RFX_ITEM.
    move 'X' to LT_ITEMX-EXT_RFX_SYSTEM.
    move 'X' to LT_ITEMX-SRM_CONTRACT_ID.
    move 'X' to LT_ITEMX-SRM_CONTRACT_ITM.
    move 'X' to LT_ITEMX-BUDGET_PERIOD.
    append LT_ITEMX.
    clear LT_ITEMX.
endloop.
describe table LT_ITEM1 lines LV_NO.
sort LT_ITEM1[] by PO_ITEM.
read table LT_ITEM1 index LV_NO.
append lines of LT_ITEM1 to LT_ITEM.
clear LT_ITEM.
LV_NUM = LV_NO * 10.
condense LV_NUM.
concatenate '000' LV_NUM into LV_NUM.
loop at LT_ITEM where PO_ITEM is not initial.
    LV_INDEX = SY-TABIX.
    read table LT_ITEM1 with key PO_ITEM = LT_ITEM-PO_ITEM.
    if SY-SUBRC eq 0.
      if LV_INDEX gt LV_NO.
        LT_ITEM-PO_ITEM = LT_ITEM-PO_ITEM + LV_NUM.
        modify LT_ITEM transporting PO_ITEM.
      endif.
    endif.
endloop.
*LOOP at i_item.
call function 'BAPI_PO_CHANGE'
    exporting
      PURCHASEORDER = LS_TAB-V_EBELN
    tables
      RETURN        = LT_RETURN
      POITEM        = LT_ITEM
      POITEMX       = LT_ITEMX.
*ENDLOOP.
if not lt_iTEM[] is initial..
    call function 'BAPI_TRANSACTION_COMMIT'
      exporting
        WAIT   = 'X'.
     importing
       RETURN = LT_RETURN.
   WRITE: I_RETURN-MESSAGE.
endif.
endform.

Multi-Step Purchase Order Release Workflow FRGSX/FRGCO

Hello everyone,
I'm about to pull my hair out over here with this workflow.
-We're using ECC6
-We've configured multi-step release strategies for some of our PO's.
-I've linked the RELEASESTEPCREATED event from BUS2012 to WS20000075.
-The workflow is failing at agent determination, prior to creation of the workitem.
-It appears that the Release Strategy (FRGSX) is being passed in the RELEASE CODE parameter of the workflow container, rather than the actual Release Code (FRGCO), causing the agent determination to fail.
-Both the rule and the entire workflow work flawlessly when executed manually using the Release Code (FRGCO).
What's going on here? Can WS20000075 handle multi-step approvals out of the box? I've read conflicting opinions all over the internet, and still haven't been able to find a straight answer. Does anyone have any suggestions for a fix?
I'm very new to Workflow, so be gentle.
Thanks,
Jarrod

Hi Sue!
Thanks for chiming in. It looks as if TS20000166 is bound to the release step, and while there was one previous version, it appears to be a duplicate of the original.
Below is some additional error info from the step history:
AC20000027 - Element REQUISITION is not available in the container
EVALUATE_AGENT_VIA_RULE - Error in resolution of rule 'AC20000027' for step '0000000093'
CREATE_VIA_WFM - Agent determination for step '0000000093' failed
CREATE_WIM_HANDLE - Error when creating a work item
CREATE - Error when creating a component of type 'Step'
PROCESS_NODE - Error when processing node '0000000093' (ParForEach index 000000)
Exception occurred - Error when starting work item 000000451141
Also, if I examine the contents of the container, the ReleaseCode parameter contains the FRGSX value (7D), rather than the FRGCO value (D7), despite the fact that the definition for the expression specifies T16FC-FRGCO.
I've tried debugging the ME_REL_GET_RESPONSIBLE FM from the rule, but my breakpoint doesn't hit when I'm creating PO's, only if I start the workflow manually.
Might I have mis-diagnosed my problem?
Thanks for your help,
Jarrod

Multi-step Purchase Order Release Workflow

Hello everyone,
I'm about to pull my hair out over here with this workflow.
-We're using ECC6
-We've configured multi-step release strategies for some of our PO's.
-I've linked the RELEASESTEPCREATED event from BUS2012 to WS20000075.
-The workflow is failing at agent determination, prior to creation of the workitem.
-It appears that the Release Strategy (FRGSX) is being passed in the RELEASE CODE parameter of the workflow container, rather than the actual Release Code (FRGCO), causing the agent determination to fail.
-Both the rule and the entire workflow work flawlessly when executed manually using the Release Code (FRGCO).
What's going on here? Can WS20000075 handle multi-step approvals out of the box? I've read conflicting opinions all over the internet, and still haven't been able to find a straight answer. Does anyone have any suggestions for a fix?
I'm very new to Workflow, so be gentle.
Thanks,
Jarrod

Hi Jarrod,
You might get a better response if you post in the workflow forum.
SAP Community Network Forums » SAP NetWeaver » SAP Business Workflow
Brenda

HOW TO BLOCK THE PURCHASE ORDER AND MARK FOR DELETION ?

Hi ,
During the Creation of the Purchase order in the SAP System... After creation of the Purchase order should be blocked and a work item is created for the approver. If the Approver approves the Order then the Order is Unblocked and a mail send to the initiators inbox and the Order is Released. Similarly if the Approver Rejects the Purchase Order then its set for Mark for Deletion.
I did Po creation and release part. But i am facing problem during the Blocking & Unblocking the Purchase order. If he rejects i need to set for "Mark For Deletion". plz help me to solve this...

Hi,
You can use bapi 'BAPI_PO_CHANGE' to change the status of PO and for release use bapi BAPI_PO_RELEASE.
Hope this will help you.
Smit

Problem in Rejecting the purchase order release workflow

Similar Messages

Maybe you are looking for