Payment Release workflow WS00400012

Hi,
I am using payment release workflow WS00400012,in configuration I have given subworkflows WS00400011,WS00400021 & Ws00400022 with different amounts.But when i  post the document it only goes to one level ie.WS00400011, I checked workflow WS00400012 there in step 82 , one level subworkflow (WS00400011) is given in task, so the system takes only one level of release irrespective of amount of document.
My Question : How to call different release level in workflow based on amount.
Is any changes are required in standard workflow WS00400012 for having amount wise release level.
Thanks
Nishant Mittal

Hi Nishant ,
Why dont you have a look at the release authorizations in SPRO. Try to give varying amounts.
Meanwhile , let me have a look. Will revert by Monday -21.08.2006.
Cheers
Kartik

Similar Messages

  • Error in Payment Release Workflow in the task Determine Subworkflow

    Hi Experts,
                      I am working on Payment release workflow WS00400012. When a document is posted I am getting an error in the task TS00407859 (Determine Subworkflow Release for Payment). Within this I found "SUBWFDETERMINE" is getting executed in this task I am getting an error. I did debug the method SUBWFDETERMINE from SWO1 there I am gettng an error "Error in workflow customizing" this is because the field SUBNR is initial. Can anybody tell me in the customizing where I am doing the mistake.
    Thank you.
    Srija

    Hi Arghadip,
                         Thank You.
                         I checked out the table VBWF01 I found the subworkflow "WS00400011" in SUBNR field.would be there any other reasons why its getting error?
    Please suggest me.
    Thank you.
    Srija

  • FI Payment Release Workflow Agent assignment and SPRO settings.

    Hi Experts,
                     I am working on Payment release workflow for 2 stages. So for this i have activated the main workflow WS00400012 and for First level release WS00400011 and for second level release WS00400021.
    Now where should i assign the agent for First level release and second level release ? and what setting should i do in SPRO as FI settings.
    Any of you suggestions will be of great help me to resolve this issue.
    Regards,
    Hari

    Hi,
    Thank you for your reply.Should i mention the main workflow number in SPRO or
    just the subworkflows alone ?.
    Assign main workflow number
    Can i assign users directly in workflow itself insteas of assigning position in SPRO.
    Don't assign users inside the workflow, if the user id you want to change then again you have to change the workflow.
    Regards,
    Surjith

  • Payment Release Workflow for PO invoice

    Hi folks,
                  Need to develop Payment Release Workflow for PO related invoice which are triggered via MIRO.
                  Can i use Business object BUS2081 for the purpose ?
                  WS00400012 is the standard workflow for the same purpose for NON PO invoices.
                  Is there any standard Workflow for the PO Invoices. Do we need to trigger this as BTE ?
                  Please suggest.
                        Thanks in advance,
                        Shyam.
    Edited by: shyam prasad on Feb 22, 2012 7:13 AM

    Hi Amanullah, How are you?
    Did you get an answer about this situation ? I am trying to do the same thing by FI or by MM and I'm worrying if we can to do by Standard SAP. In FI I'm trying to do via spro:
    SAP Customizing Implementation Guide=>Financial Accounting=>Accounts Receivable and Accounts Payable=>Business Transactions=>Release for Payment
    Did you remember how can you get the solution?
    Thanks and regards,
    Jeovana

  • Payment Release Workflow

    Hi Folks,
             We are working on Payment Release workflow in AR module.
             Once the invoice is posted, workflow is able to block the payment, but not sending mails to the agent for approval.
             For testing, i have entered a dummy userid as the agent and checking for the mails.
             How can we debug or monitor to check why the agent is not getting mails in SBWP.
             Pls suggest how to solve the problem.
    Thanks in advance,
    Shyam.

    Hello,
    Okay, let me correct that for you:
    "We are working on Payment Release workflow in AR module.
    Once the invoice is posted, workflow is able to block the payment, but not sending WORKITEMS to the agent for approval.
    For testing, i have entered a dummy userid as the agent and checking for the WORKITEMS.
    How can we debug or monitor to check why the agent is not getting WORKITEMS in SBWP.
    Pls suggest how to solve the problem."
    Have you looked in SWI5 to see if it is listed for the user there? Check that there are no excluded agents.
    The solution is likely that you haven't set the task to General Task, as already suggested.
    regards
    Rick Bakker
    hanabi technology

  • Payment release workflow thru F-53 Transaction  help needed

    Hi gurus,
    I am trying for payment release workflow using F-53 which is the client requirement. As there is no parking option in the transaction i created a custom event "parked" in the transaction .I tried using BTE. but i m not able to find the right product no in infosystems of BTE for the transaction F-53. Is there any way for payment approval workflow.
    Thanks and Regards,
    Kumar

    Hi Kumar,
    Actually, what you may do is setup a workflow for automatic payment with approval/rejection process which would trigger a BAPI for f-53 process.
    And keep the below items in mind before finalize:
    a. F110 will not clear any blocked invoices.
    This is the default setting, as a security for the blocked items stay in the system
    (blocks are always there with a reason).
    b. In F-53 you can control what you want to clear (not automatic),
    therefore some blocks can be redefined allowing F-53 to clear SPECIAL-BLOCKED items
    You may find more options too.
    Thanks
    MKS

  • Payment release workflow for MIRO documents

    Hi,
    I have activated payment release function and successfully able to get workflow item for payment release for FI invoices posted through F-43 and FB60, but not on RE documents which are posted through MIRO,
    Can some body provide inputs on how to trigger a payment release workflow for MIRO documents.
    Thanks
    Amanullah

    Hi Amanullah, How are you?
    Did you get an answer about this situation ? I am trying to do the same thing by FI or by MM and I'm worrying if we can to do by Standard SAP. In FI I'm trying to do via spro:
    SAP Customizing Implementation Guide=>Financial Accounting=>Accounts Receivable and Accounts Payable=>Business Transactions=>Release for Payment
    Did you remember how can you get the solution?
    Thanks and regards,
    Jeovana

  • Error in Payment Release Workflow

    Hi friends,
    I am working on the Payment Release workflow.I am using the standard WF for this.But my workflow is throwing an error if i am not maintaining the SPRO setting "Assign Release Approval Paths for Release for Payment".
    <b>The error is It is not able to determine the Subworkflow.</b>Is it mandatory to do this setting.If so then we have to maintain a release group for all the vendors but my client is saying that he dont want to do this. Kindly suggest how to proceed..
    Rgds

    Please do not add new questions in an existing thread. Two good reasons for this are that it prevents us from upping the food program donation from SAP (since you can not award any "good reply" points), and that it is easier for people to find previously answered questions if we limit ourselves to one topic per thread.
    Now, to your question: I believe this would be solved by only defining release approval paths for specific release approval groups. Then, for those vendors that don't have a release approval group there should be no blocking. I am however not sure about it, and if you have tried this and it failed (you don't say whether you have tried) - perhaps a workable alternative would be to use a particular release approval group for these vendors and define a release approval for these where the clerks can release any amount.

  • Vendor payments release workflow!!!

    Hi all
    Can somebody explain to me how we setup standard workflow so that all vendor invoices greater than 100.000 can be blocked for payment automatically & released by some other user?
    I tried to give the document type "KR" to the workflow variant & tried to do invoicing for the vendor.  But I do not how I could release that blocked invoice...Is there any specific tcode or I have to go to the proposal & change the blocked reason from P to 'space'.
    Thanks for all your time....

    Hello Morgan,
    Payment Release Process
    Purpose
    For each workflow variant, you can specify the amount from which a payment release should be triggered.
    You can differentiate between one, two, and three-level release. This enables between one and three people to be involved in the release procedure, thus supporting both dual and triple control.
    Prerequisites
    You have made the following settings in Customizing:
    Release approval procedure
    (document type and amount for each workflow variant)
    Assign persons with release authorization
    In order to do this, you must first create release approval groups that can be entered in the customer and vendor master records.
    Depending on these criteria and the release level, you can assign release authorizations in the form of organizational objects (job, position, organizational unit) in Customizing. If you do not define any criteria (such as release approval groups), the system takes the initial value of these criteria when the payment program is run. For example, if the system was unable to determine the release approval group, the release approval procedure and the employees with release authorization are determined on the basis of release approval group zero.
    Process Flow
    Minimum requirements:
    The payment release function must be activated.
    The relevant document type must be defined.
    An item containing the following specifications must be created for employees with release authorization:
    Workflow variant
    Initial release approval path
    Initial level
    Maximum amount
    Employees with release authorization can also be determined and assigned by user exits at each stage of the release approval procedure.
    Result
    If, when the payment run is made, the system could not determine an employee with release authorization, then it sends a message to the inbox of every person who has been assigned the task "payment release". Only after all these people have released the payment will the payment block be removed.
    If a line item is refused for release, it is forwarded to the clerk who entered it for correction. After the document has been changed, the payment release procedure begins again. If changing the line items necessitates further actions, these must be defined within the Workflow component. The event CHANGED has been preconfigured for this purpose in the standard workflow model. If you run this event, the system assumes that the line item was rejected for payment. However, the item is NOT forwarded for correction to the clerk who entered it.
    If an item is cleared before it is released, the payment release procedure is terminated (event CLEARED).
    ===========================================================
    Workflow settings: The standard system contains several workflow models for payment release: One workflow framework (WS00400012) and three sub-workflows. In Customizing for Financial Accounting, you can specify which sub-workflow should be used when the workflow framework is run. You can also enter your own sub-workflows. They must however send and receive the same data from the workflow framework as the workflow models do.
    You can use the standard sub-workflows (WS00400011, WS00400021, and WS00400022) to carry out a one, two, or three-level payment release procedure. If you require more than three release levels, you can copy the workflow models, enhance them and then enter the enhanced workflow definition in Customizing for Financial Accounting.
    Event Linkage for the Event CREATED
    If an amount requires a payment release, the event CREATED is triggered when a document is posted.
    In this case, you must go into the workflow framework in the Workflow Workbench and enter the event linkage for this event, as described below:
    Data for Event Linkage
    Object type
    BSEG
    Event
    CREATED
    Receiver type
    WS00400012
    Receiver module
    SWW_WI_CREATE_VIA_EVENT
    Check Function
    Receiver type
    FM (function module)
    Global
    X
    Enabled
    X
    Standard Tasks for the Event CREATED
    The standard system contains two standard tasks that are triggered from the workflow mailbox and used in the workflow models.
    Payment release (line item)
    Change (line item)
    Creating and Assigning Organizational Objects for Payment Release
    You must assign organizational objects (organizational units, jobs, positions) to the standard tasks. These organizational objects can be created either in Personnel Planning and Development, via the Workflow Workbench, or in Customizing for Financial Accounting (assignment of release authorization to employees).
    When you create organizational units, you must assign them to jobs or positions. You can then assign users to the positions.
    Examples for assignments:
    Organizational unit X < Position Y < User
    Organizational unit X < Job Y < Position Z < User
    In Customizing for Financial Accounting, you can assign organizational objects to the workflow variant, the release approval path, the release approval level, and the amount. These objects then release the amount depending on these criteria.
    The organizational objects for payment release defined in Customizing for Financial Accounting are automatically assigned in the background to the standard payment release task (TS00407862).
    The organizational objects for changing line items after they have been rejected for payment must be assigned to the standard task "Change line item" (TS00407864), either in Personnel Planning and Development, or via the Workflow Workbench. Alternatively, you can define the task as a general task (Additional data -> Classification).
    Changing Line Items
    The workflow models described above all contain a pre-configured event (CHANGED), which triggers other events in the same fashion as a rejection does. This event can be triggered by change documents. You must define it via the Workflow Workbench.
    Hope I had been able to help you. Please assign points.
    Rgds
    Manish

  • Agent problem in Payment Release Workflow   - SPRO

    Hi FI PRof's,
    I am using the standard workflow WS00400012 for Payment Release.I am using two level approval process.If the invoice amount is less than 20,000 it should goto approver X and if it more than that it should do for X first and then to Y.
    I have assigned the agents in SPRO Customizing as follows :
    WF Variant - 2000 Approval path - 0001 Level - 1 R.Amt - 10,000 Agent - X
    WF Variant - 2000 Approval path - 0001 Level - 2 R.Amt - 999999... Agent - Y
    I am using the standard rule 00400125 for agent asssignment.
    My Problem for single level release the agent is found(X) and WF is fine.
    But while two level release the responsible agent is not found..What could be the problem. Am I missing any thing in Customization.
    Rgds

    Hi,
    You had any response about this problem or able to solve it?
    I'm having the same current problems and have not found a solution!
    Regards!
    Ariel Prebianca

  • Agent problem in Payment Release Workflow

    Hi WF PRof's,
      I am using the standard workflow  WS00400012 for Payment Release.I am using two level approval process.If the invoice amount is less than 20,000 it should goto approver X and if it more than that it should do for X first and then to Y.
    I have assigned the agents in SPRO Customizing as follows :
    WF Variant - 2000 Approval path - 0001 Level - 1 R.Amt - 10,000 Agent -  X
    WF Variant - 2000 Approval path - 0001 Level - 2 R.Amt - 999999... Agent -  Y
    I am using the standard rule 00400125 for agent asssignment.
    My Problem for single level release the agent is found(X) and WF is fine.
    But while two level release the responsible agent is not found..What could be the problem. Am I missing any thing in Customization.
    Rgds

    I can't check it since I don't have access to a SAP system here, but don't you have to define the first-level approvers separately for the two scenarios? Perhaps my memory is incorrect, but I seem to remember that you can have one first-level approver for the low amounts, and a different first-level approver for the high amounts.
    This is mostly a chore that just requires additional maintenance since it seems "everyone" is using the same first-level approver independent of amount, but flexibility is highly regarded in SAP...

  • Workflow WS00400012 Release for Payment not getting triggred

    Hi,
    As mentioned in the help docs we have done the following settings for Release for payment, yet the Workflow is not getting triggered.
    SPRO->Financial Accounting (New)->Accounts Receivable and Accounts Payable->Business Transactions->Release for Payment                                             
    Create Workflow Variant for Release for Payment                                             
    XX01     WS004MSBT Payment release                                        
         Workflow var.   XX01                                        
         Currency        INR                                        
         WF var.name     WS004MSBT Payment release                                        
         Prelimenary posting release                                        
          Release from    1.00                                        
          Subworkflow     WS00400012                                        
         Payment release                                        
         Release payment          X                              
         Creater permitted          X                              
          Payt release    1.00                                        
          Pmnt rel.var.   CC                                        
    Assign Company Code Workflow Variant for Release for Payment                                             
         Compamy Code     Workflow Var     WF Var. Name                              
         XXXX     XX01     WS004 Payment release                              
    Define Release Approval Groups for Release for Payment                                             
         0001     Vendor A                                   
         0002     vendor B                                   
         0003     Vendor C                                   
         0004     G/L accounts                                   
    Define Release Approval Paths for Release for Payment                                             
         0001     Vendor high                                   
         0002     Vendor middle                                   
         0003     Vendor low                                   
         0004     G/L accounts                                   
         0005     Other                                   
    Assign Release Approval Paths for Release for Payment                                             
         Workflow Variant      Doc. Type      Release Group     Approval Path                         
         XX01     KR     0001     0001                         
         XX01     KR     0002     0002                         
         XX01     KR     0003     0003                         
         XX01     KZ     0001     0001                         
         XX01     KZ     0002     0002                         
         XX01     KZ     0003     0003                         
         XX01     SA     0001     0001                         
         XX01     SA     0002     0002                         
         XX01     SA     0003     0003                         
    Assign Release Approval Procedure for Release for Payment                                             
         Wrkf      ApPath     Amt To            Curr     Rel levels     Swf Amt rel     Swf pnmt rel           
         XX01     0001     5,000.00       INR     1     WS10000052     WS00400011          
         XX01     0001     10,000.00     INR     2     WS10000053     WS00400021          
    Define Relevant Document Types for Release for Payment                                             
         Workflow Variant     Type                                   
         XX01                       KR                                   
         XX01                       KZ                                   
         XX01                     SA                                   
    Define Users with Authorization to Payment Release                                             
         XX01     1     1     5,000.00     INR                    
         Assigned Authorization Object                                        
         Production manager                                        
         XX01     1     2     10,000.00     INR                    
         Assigned Authorization Object                                        
         Comp Admin                                        
    Carry Out Function Enhancements for Release for Payment                                             
    Define Payment Block Reason for Payment Release                                             
               Free for payment                                   
         *     Skip account                                   
         A     Locked for payment                                   
         B     Blocked for payment                                   
         I     CML:InvestorContract                                   
         N     Postprocess inc.pmnt                                   
         P     Payment request                                   
         R     Invoice verification                                   
         V     Payment clearing                                   
    We are using Tcode FV60 for Park Vendor invoice                                        
    We are trying to post the Document thru Tcode FBV0 , But the Post field is grey and system shows error: func not possible as document is in not released. The Workflow is not getting triggered. And hence its not possible to release the doc.
    The workflows have been activcated
    We have done Eventlinkage and activated it.

    In future when you post question please do some formatting. It seems like a novel.
    Have you checked in SWEL whether the event CREATED of Business Object BSEG getting triggered. I hope you have activated the linkage between event and workflow from PFTC or SWE2 transaction code.
    Thanks
    Arghadip

  • Work flow for payment release

    Hi,
    i hv configured payment release workflow for vendor payments, now the system is creating an auto block for invoices parked thru FB60. Now I desire to release the invoice for payment, so that my workflow gets triggered. But I dont know which Tcode to use to release the invoice for payment. If F110 can be used to relase the payment, kindly let me know how it is to be done. As I tried doing it but was not successfull.
    Regards,
    Krishna

    Hi
    If you have not assigned any agents to payment release task, then go to SAP Business workplace (ctrl+F12) and check in your inbox. You would have received an email through SAP workflow. Click on the email and it will direct you to release the invoice for payment.
    Though you release the invoice it can not be paid unless you activate a task for "Reset Payment block"
    You need to activate two tasks as below
    Release for payment
    and
    Reset Payment block.
    Once the invoice is released for payment then the status of BUS # changes to Released. You need to activate the task " Reset Payment block" with triggering event "Released".
    Once the invoice is blocked for payment through workflow, the blcok can never be removed manually. This should be removed only through Workflow.

  • Workflow for payment release

    Hello ,
    I  have done the configuration of workflow variant for payment release but  the invoice with the payment block can be  paid without any release approval  .
    Find below the configuration done for it . SPRO-Accounts Receivable and Payable-Business Transactions-Release for payment
    1.t.code PPoce: Users is assigned to each position and this was assigned to approval path
    2. Create workflow variant
    subworkflowWS00400012
    3.Assign Company code to workflow variant
    4.Define Release Approval Groups for Release for Payment
    5.Define Release Approval Paths for Release for Payment
    6.Assign Release Approval Paths for Release for Payment
    7.Assign Release Approval Procedure for Release for Payment
    2010-2010-1000-inr-WS00400012-WS00400011
    9.Define Users with Authorization to Payment Release
    11.Define Payment Block Reason for Payment Release ( payment block P selected with a tick in Not changeable )
    Then in the vendor master i have inputted the relase group also  and the payment term which is having the block .
    While executing f-02 , debiting the expense and crediting the vendor , I get the following error Line item not relevant for payment release for which  i changed the message to warning and saved it . but when i executed f-53, it doesnt go for approval .
    But in my inbox . the item is flowed with red colour and the erro log is
    Error in workflow Customizing of payment release
    Message no. FP162
    Diagnosis
    The system could not determine a subworkflow for the payment release. Check the workflow Customizing for the payment release, in particular the settings for transaction OBWE and the preceeding settings.
    The message is output from the method SUBWFDETERMINE of the BOR object BSEG.
    System Response
    The workflow was started, but the system could not create an executable dialog workitem for the line item payment release. However, you cannot release the document directly, it must be released in the workflow. A subworkflow for the payment release must be determined in the sample workflow WS00400012; the clerks are determined in role 00400125.
    Role 00400125 is based on the function module PR_WF_ACTOR1_DET.
    Procedure
    Change the payment release Customizing in Accounts Payable/Accounts Receivable Accounting. SAP delivers a sample subworkflow for payment release, WS00400011.
    Procedure for System Administration
    Restart the incorrect workflow (transaction SWPR) once you have maintained the Customizing for the payment release.
    Kindly guide me . and let me  know which setting i have missed .
    thanks

    Hi,
    Have you tested those workflows separately? I can't even view WS00400012 in my ECC 6.0 system!
    The workflows supplied by SAP are usually pretty bare-bones. More ofthen than not you have to copy them and fix them up.
    You might be able to test them via SWUS or trigger them via SWUE.
    If you create a new copy, remember to put that in the customizing.
    hope this helps
    Paul

  • Workflow assignment to Payment Release

    Hi, some of our documents are being assigned a payment release using the WORKFLOW MM PURCHASING and other documents are using the correct WORFLOW FI-AP which is asking for release from the FI guy. The first one is asking the MM guy for release, but he has no authorization to do so. How do you suggest I fix this?
    Thanks

    Thanks Kiran ,
    Now hte invoice is getting blocked automatically and i am getting the error as
    Line item not relevant for payment release
    Message no. F5783
    for which i changed the error message to warning mgs and saved the invoice .
    But while making the payment i was not getting any payment block. I was able to make the payment
    Actually I should get the payment block while I am making the payment and then i should release it through FB13 .
    Please let me know if I am wrong .
    Thanks

Maybe you are looking for

  • XP doesn't work - ME does!!

    have the following problem when connecting my 20G 4th Generation iPod. It was 1 week out of warranty (typical!!) when I noticed I couldn't connect to my HP laptop with XP home edition and iTunes 7. I get the message "iTunes has detected an iPod that

  • Problem in displaying data in sapscript

    Hi, I am working on the sapscript for the tcode QC21 and the form name is 'YQM_QCERT_02'. here the data is represented in the column wise and i want to disply the data row wise. Plzz provide me guidlines how to display the row wise data in the SAPSCR

  • FrameMaker and ArborText

    Can two groups within the same company, one using FrameMaker and the other using ArborText, open and edit each other's documents and then bring them back into the original program? Thanks! Lisa

  • Thumbnail Settings not taking effect

    WCC 11.1.16.0 IBR installed Outbound provider setup for IBR Thumbnails requested for doc, docx etc. I have added ThumbNailWidth=240 ThumbNailHeight=240 into the config.cfg (For IBR and UCM) - ..\user_projects\domains\portal\ucm\cs\config\config.cfg a

  • Re: Nextver field

    The other thread was locked, so I need to respond here. The nextver field is a comma-separated list of version numbers. They are not always 5 digits, but they can be. Version numbers are created with a sequence. The row can be split until the size of