Can any one let me how to approve Journal entry document .I have parked a document and now i have to approve this in different user , just for testing of work flow .Urgent ...
I am afraid FBV0 is to post it, but not to approve / refuse it. In order to approve / refuse, you need a workitem in your workflow inbox (transaction SBWP). When you execute the workitem, you will see 2 buttons (Approve / Release).
If you do not have any workitem received, you should check your workflow definition and/or the organizational assignments. Perhaps your are not entered there as an approver.
Hm, this is hard to analyze from the distance. If you have a workitem, you really should see those buttons.
Do you have any authorization issues (check out SU53 right after you have executed the workitem).
Are you using a standard workflow? Check out workflow variant assigned to your company code on OBWJ, then go to OBWA and doubleclick that workflow variant. Under "Preliminary posting release" you should see an amount and a subworkflow number. What is it?
If you go to FBV0 and display your parked document, check out the document header (use the appropriate button). How about the fields in the "Workflow control" screen block? Especially approval path, release levels, and 3 checkboxes Release necessary, Document complete and Released ?
Just to add a little something to the discussion...In our system "parking" alone will not start the necessary workflow. If create a parked JE document and just click "saved parked document" the document will stay in my workplace in a parked status (not completed). It is only when I click "save as completed" that the work item is sent to the approver. The approver will then see the additional buttons (at the top of the item when opened from their inbox) beside editing options to either "Release" or "Refuse". And the user that is doing the approval must have access to transaction FBV0.
yes, Will is absolutely right, I thought this was obvious. At least for the standard workflow WS10000051, the subworkflow (which may be a 1-level or 2-level release) is started only after the document has reachd the "completed" status.
That's why I recommended to chck out the 3 chckboxes in the document header:
Release necessary = this really should be active, otherwise we have a more general problem
Document complete = if not set, (sub)workflows are not yet started
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.