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

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

  • 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

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

  • 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 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

  • 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

  • Material number changed after purchase order released

    Hi Experts
    Please we are experiencing this behavior in our system.
    A purchase order for a specific material number is created and released, after this we can change the material number and its plant ¿is this a standard and right be way of SAP?
    Thank for your help
    JM

    Hi,
    You can design your process as the business demand.You can set Release Indicator 1 in designing Release procedure for  PO , where release Indicator 1 is used for purchasing document cannot be changed/Change not allowed after release.
    Regards,
    Biju K

  • Issue with ORERS05 IDOC sending immediately after Purchase Order creation.

    Hello,
    When output mode of an outbound partner profile was setup as Transfer
    immediately then when ever EDI output is generated in Purchase Order then
    system creates IDOC and sends immediately out of system. But middle
    ware has received only control record and whole data records were missing in IDOC file received by middle ware and we were receiving status 29 back from middle ware.
    Right now we changed outbound partner profile, output mode was set to
    Collect IDOC's and we are running RSNAST00 program in background to send those IDOC's but we
    were looking into go for first option to send idoc out of system as soon EDI output is generated in Purchase Order.
    Is there any way of fixing this issue.
    Thanks in advance.
    Regards
    Prasad

    Yes, I'm facing with PO IDOC only and as I said it is not issue with middle ware as they were receiving only IDOC control record.
    If I resend same idoc by setting status back to 30 they were able to receive whole IDOC and more over if we set partner profile to Collect IDOC and schedule back ground job every 5mins then middleware was bale to get whole idoc.
    Looks like it is SAP issue as this the message I got from SAP.
    The problem only exists if the messages are supposed to be output by
    means of transmission time-spot
    4, that is 'immediately' (during the saving of the application).
    With the output of the change message, the change documents are read for the purchasing document (all as of the last successful transmission).
    With the transmission time-spot 4, it can occur that the change
    documents do not physically exist on the database yet. No change message can be generated in this case and the system generates message ME140 or ME760 in the message log.

  • 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

  • Message trigger after Purchase Order Change

    Hello all,
    I have a requirement whereby system should trigger output message ater PO change. I have maintained message type for the PO using MN04.
    However still I am not able to get message tirggered afer change. System is triggering ourput message after creation only.
    Kindly advice places where I can look into. .
    Thanks in advance.
    regards,
    Parshuram
    Edited by: parshuram manjrekar on Nov 27, 2009 4:05 PM

    Hello Guys,
    I have created new message type which should get triggered after PO document creation/change.
    I have assigned this message type to PO type using MN04. I have removed all other message types assigned to this order type.
    However when document is PO created is created, I am not able to see any output assigned to PO.
    When I go in change mode, and try to manually trigger new output message type, system is not showing me new message type but showing all old message types as possible entries.
    Have I missed any config.
    regards,
    Parshuram

  • 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

  • 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

  • Creating  workflow for purchase order release.

    Hi friends
    I want step by step detail about creation of workflow for purchase order release..
    After release purchase order it will goes to the two level of approval..
    after that the workflow should be completed...
    how can i develope the workflow for that scenario..
    Thanks
    Gowrishankar

    Hi Gowrishankar,
    You can get step by step workflow for PO using standard workflow
    <b>Release of Purchase Order :WS20000075</b>
    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.
    Thanks and Regards,
    Prabhakar Dharmala

  • Workflow - Purchase order Release strategy

    Hi All,
    Good Morning
    I had created workflow for Purchase order release strategy with steps(To Determine Agents, Release of Purchase order, Release of PO effected) and in Me21N I created PO and PO came to my SAP inbox(SBWP) and I released that PO and saved it.
    but My problem is after releasing PO when I checked my Inbox again still that PO is sitting there, it is supposed to disappear from there
    Can anyone please assist me to resolve this issue .
    Thanks in advance.

    Hi,
    In standard SAP workflow, SAP is sending a mail item (notification) to SAP mail inbox. There is no action is required from there. So mail will remain their as mark as read. If you want to remove it than one needs to delete it from respective mail box.
    Best Regards,
    Bhagat

Maybe you are looking for