F-47 park and post option OR F110 block option for payment requests

HI experts,
current business scenario:
F-47 payment request by AP users
F110 payment run (including payment requests) by manager
so between F-47 & F110 system doesnt trigger for payment approvals
Business requirement:
After F-47 system should trigger workflow to concerned manager for approval
OR
At F110 (payment run) system should proceed after approvals if payment requests includes in the run
Limitation:
Business doesnt use F-48 ( post down payment) because check is processed by Bank
Pls suggest workflow after F-47 or at F110 which wil intimate the concerned manager
and stops &/ block the concerned payment till approval.
regards
Edited by: melgibson on Jan 16, 2012 8:30 AM

Hi,
Now i got your point. your requirement can be achived using a ABAP development.
1) Create a Z table to store down payment requests (with all fields, those you use in F-47) and this table needs to be maintained via a Ztcode. (ZF-47). As soon as the user enter the DP request data in Ztcode, system should trigger the WORKFLOW and will send these requests to the manager's SAP Inbox. So once the manager approves few of them, those requests only will be processed by a Zprogram, which will create SAP standard DP requests using F-47 in background.
Note: Please make sure that, your Ztable should have one special field called STATUS, which will be depending on manager's approval. If the manager rejects it, then status should be automatically updated to the Ztable.
2) anyhow bank will automatically creates DP for all F-47 requests, which were pre approved above.
This logic should work and fits to your requirement.
Cheers,
Srinu

Similar Messages

Park and Post for Down Payment Request (F-47)

SAP Gurus,
We are having requirement for park and post in Down Payment Request (F-47). So that it is approved by an authoriser.
Hence, Is it possible to workflow a down payment request to an authoriser for approval
Please share with me options available for this Down payment request
Regards,
Raj

Hi Raj,
Please check with your workflow consultant. Anyway, I'd like to share with you how to know whether there is a standard workflow for application component in question. T-Code SWDD -> Workflow -. Other Workflow/Version. Then drilldown on the task field. Then choose structure search. You will find the standard workflow for each of the component. Unfortunately, there is no standard workflow for downpayment but if you have workflow consultant, they may be able to help.
Regards
Fauzi

Regarding Parking and Posting access

Hi All,
The requirement for my client scenario is as follows:
There are about 6 company codes (lets name it as AAA) which need to be isolated based on the following rule:
Users belonging to AAA should be able to PARK as well as POST to all entities whereas Users belonging to other than AAA should not be able to POST to AAA. They should be able to POST to non AAA only and PARK everywhere.
Also a user who PARK's should not be able to POST.
Options which I have tried are -
- Created a separate role with activity 01 for the object F_SKA1_BUK and gave the AAA entities only and at the same time removed 01 activity for the same object in a separate role. The combination of these two roles gave the result as
- Was able to PARK and POST to AAA entities using FB01 (True)
- Was unable to post to other entities (Failed - user should have been able to)
- The person who parked was not allowed to Post (True)
The other combination with 01 activity to non-AAA entities and minus 01 activity to AAA entities:
- Failed to PARK to non AAA entities (Failed - user should have been able to) failed at 01 activity
- Was able to PARK to only non AAA. (True)
- Was unable to POST to AAA entities (True)
- The person who parked was not allowed to Post (True)
I came to know that this can be achieved by creating separate roles for posting and parking Tcodes and using SOD.
I have an already existing GL role - I removed all the posting tcodes in the original GL role so that it can allow only parking to all entities. Then I created a separate role and put all the Posting Tcodes in it and maintained the objects in the same was as they were maintained in the original GL role but here I have given only the AAA entities. Can some one help me in this approach.
Regards
Shakeel

The objects designed to protect posting of accounting documents directly in FI are F_BKPF, F_SKA1 protects the Chart of Accounts maintenance by company code.
You should generate two master roles, one with the activity 77 in all F_BKPF* Objects and other with activity 77 and 01
The first one only lets you parking documents. The second one parking and posting too.
Be careful with the tcodes you are going to use. The FB01 does not work if you don't have 01 in your authorizations for the F_BKPF_BUK object.
The Tcodes for excellence for parking documents are:
Invoices ( Vendors and Customer)
FV60
FV65
FV70
FV75
GL Documents
F-65
FV50
Regards!!

How to identify Parked and Posted Documents in GL Line Item Report

Is there any way to identify parked and posted documents in GL Line Item Report S_ALR_87012282? If i tick the parked documents in the further selection tab in the selection parameter, report will list all documents (parked and posted).
There is no available field in the layout. Is there any other way?
Thanks!

HI,
The other way to know the parked document details
use tcode: FBV3 - Display
OR
you can go to SE16 and enter table name VBKPF -Document Header for Document Parking
BSTAT = V
V = parked document
and ececute u will get the details of parked document.
Edited by: Manohar Mathkunti on Sep 13, 2008 11:11 AM

Security Segregating Park and Posting Vendor invoices

I'm working to create a role that allows a user to create & park but not post an invoice. The objects that I would think should be checked are not and if I give access to create for F_BKPF_BUK and F_FAGL_SEG it allows parking and posting.
I don't really understand why object F_BKPF_BLA isn't restricting it when it has values for create, change and post (post not being checked it appears).
Any suggestions? the role I've created for parking is using trxns: F-42 and F-63.

Obviously from a SOD standpoint you need to split the park and post functions. What I have done in the past is to use primarily F-47 and F-63 in the Park Role and have 77 (pre-enter) as the value for the F_BKPF* objects. Make good use of SU22 or SU24 (though these are not always 100% correct) to help you determine the correct values and sometimes you need to "right-click" on the activity box then select "more values"

GL Park and Post Automation

I am in process for the GL Park and Post automation from current manual process.
Accountetn - Park
Mgr - Post
Mgr II - Post
1) 50,000.99 and below will park and post without approval
2) 50,001 to 20 M will require approval and post by next level manager
3) 20 m and all above have to approval and 2nd level approval would require.
4) If under scenario 2 primary level manager not available then in certain amount of time automation will trigger to next level manager for approval.
We have Cross Company with Multiple company codes
What test scenario i can use please help me

Hi,
Please do the following configuration :
1. Define Tolerance Groups for Employees (OBA4)
Menu Path
IMG --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable --> Business Transactions --> Open Item Clearing --> Clearing Differences --> Define Tolerance Groups for Employees
In that create tolerance groups
This are the examples of tolerance groups. You can create of your own choice depending on amount.
2. Assign to users (OB57)
Menu Path
IMG --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable --> Business Transactions --> Open Item Clearing --> Clearing Differences --> Assign Users to Tolerance Groups
In Username enter User ID and in Tolerance group enter Tolerance group created by you in OBA4.
Please do not delete User ID - SMITH
3. Give park and Post authorization. You can see user is able to park items in all cases but will be able to post only as per his / her tolerance limit.
Hope, this solves your issue else revert.
Regards,
Tejas

IDCO for Parking and Posting of FI documents

Hi all,
Could you please help me the IDCO for Parking and Posting of FI documents.
Regards
Paul

Hi Gomathy,
Can you please confirm whether this IDOC is used to park or post FI documents, when I checked the documention of the IDOC it says it is used for posting , kindly confirm the same.
Regards
Dhanoo

Read parked and posting document from one FM

Hi all,
IS theere any FM avaliable to read parked and posting document from one function module.
Please let me know if anything is there.
Thanks

Hi T,
have u searched in SE37 with words park?,i'm sure we have few FMs which will do the same.
regards
Prabhu

Park and Post for recuring entries

Hi,
Can anyone tell me is it possible to have SOD in park and post for recurring entries documents - f.14?
For the purpose of segregation of duties, I need accountant A to allow to create/park recurring entries but not post. Acccountant B will be allow to post the recurring documents created by account A.
Pls help.
Thanks.

Hi,
Here's my thoughts on this.
As it is Recurring entries is a two step transaction.
Have "Segregation of Responsibilities" at the time of creation of the Recurring entires itself.
and have the second person to post it. Of course you can prevent the second person from changing any thing in the recurring document.
Rather than Parking the recurring documents.
Regards,

Workflow on invoice parking and posting

Hello,
Can anybody guide me how to configure the workflow for invoice parking and posting in detaills?
Thanks
Nilesh

hello ,
Prerequisites
In the Implementation Guide (IMG) for Logistics Invoice Verification, you can specify for which company code, which vendors, which invoices, and above which amount a document is subject to release. In an invoice document that is completed for posting, the amount that is subject to release is based on the gross amount. (Logistics Invoice Verification ® Document Parking ® Define Release Criteria)
Technical Implementation (MM-IV-LIV)
Object Types
Object technology is used to create the interface between the ERP functions and the Workflow system. The information given below is primarily of a technical nature and is not necessary for an initial overview.
Incoming invoice
Object type Bus2081 (Incoming invoice)
Workflow Template
The actual operational procedure is implemented as a workflow template. You will find this workflow template in your ERP system.
Workflow template: WS 20001004
Description: Release the Completed Log. IV Document
Triggering Event for Workflow Template
The event for workflow template IncomingInvoice.CompletedToRelease is triggered if the parked document is complete for posting (RBKP-RBSTAT='B') and is subject to release (RBKP-RFGKZ='X').
This coupling between the event and the workflow template to be started is deactivated in the standard system. If you want to use the workflow template, you have to activate it in Customizing for Logistics Invoice Verification.
User Roles
You complete parked invoices for posting and release them at the following organizational levels.
Processor Determination: Clerk Responsible for Releasing Invoices
If you have already maintained an organizational unit, you can use it here.
If no organization unit is available, create an organizational unit that includes the people responsible for releasing invoice documents that are complete for posting.
Use the organizational unit in Customizing for Logistics Invoice Verification in the activity for defining release criteria.
Processor Determination: Clerk Responsible for Completing Invoices for Posting
If you have already maintained an organizational unit, you can use it here.
If no organization unit is available, create an organizational unit that includes the people responsible for completing parked invoice documents for posting.
Link the organizational unit to the single-step task TS20000879:
· By simple processor assignment
All users in the organizational unit receive the work item.
· By defining an individual role
Only selected users in the organizational unit receive the work item.
Authorization Objects
You must have maintained the authorization to display invoices (activity 03, M_RECH_WRK) for users who are responsible for releasing invoices.
You must have maintained authorization to change parked invoice documents (activity 77, M_RECH_WRK) for users who are to complete parked invoice documents for posting.
Several other specific customizing steps are necessary for this workflow template in addition to the general customizing that is necessary to make sure that the workflow system functions properly.
Activating Event-Receiver Linkage
The event IncomingInvoice.CompletedToRelease (Invoice document completed for posting and subject to release) for object type BUS2081 (Incoming invoice) is an event that triggers workflow template WS 20001004 and is entered in the event linkage table as such as the standard event.
This coupling between the event and the workflow template to be started is deactivated in the standard system. If you want to use the workflow template, you activate the linkage between the triggering event and the workflow template as receiver of the event in Customizing for Logistics Invoice Verification. (Logistics Invoice Verification ® Document Parking ® Activate Workflow Template for Release for Posting.)
Use
The release of invoice documents that have been completed for posting is supported by a link to a workflow procedure.
Prerequisites
The event IncomingInvoice.CompletedToRelease must be triggered for an invoice (BUS2081) so that a release procedure is started. We recommend implementing this workflow together with the SAP workflow template WS20001003.
In Customizing for Logistics Invoice Verification, you maintain the activity Define Release Criteria under Document Parking.
Features
Release for Posting
In the release step, the person responsible for releasing the invoice document decides if it should be released. The system uses the virtual attribute ReleaseAgent for object type BUS2081 to determine the person responsible for releasing the document. The release criteria in Customizing for Logistics Invoice Verification are checked for this.
If the person responsible decides to release the document, it is first released in the background and then posted.
If he or she decided to reject the document, it is forwarded for further processing to the accounts payable clerk responsible for completing invoice documents for posting. The rejection reason should have been entered using the memo function.
Completing Invoices for Posting
The accounts payable receives a work item in his or her inbox. In this work item, he or she can read the reason why the invoice document was rejected and change it. If the accounts payable clerk parks the changed invoice document, saves it as complete, deletes it, or posts it, the workflow ends. It makes sense to save the invoice document as complete and therefore trigger the release workflow again, assuming that the invoice document is subject to release.
If the invoice document is parked, deleted, posted, or released in the background outside the workflow process, the workflow ends.
regards
venga

Park and Post management review step for manual journal entries

We are implementing SAP and want to discuss the best way to automate in SAP a high dollar/value (maybe $100K and above) "park and post" management review step for posting manual journal entries. I believe SAP does not offer dollar/value limits as standard functionality for defining a park & post process. If this correct, what have you seen from your other clients using SAP park & post? Is there a different way to get where we want without customizing a workflow or generating a new transaction set?

Hi you could limit the authorisation for the users only to park and then a responsible person could review it and post. You can set a tolerance limit for customers and vendors.

Controller role Park and Post

Hi Experts
Here's what I got.
I need roles for my customer to park and post documents. This is what he is asking for:
Controller Role: No park, only post
Cost Acct Role: Park and Post, but no posting their own parked docs
Acct Clerk Role: Can only Park
I asked that he send me the transaction codes they will be using for this. Also, I thought I would use tcode SU24 and identify which authorization objects need to be interrogated. Anyone have a better solution?
I was able to get the tcodes the customer wants to use:
FB50 would be post only.
FV50 would be park only.
Edited by: Jim McCollum on Sep 10, 2008 10:50 PM

Dear JIM,
There is a useful document with screenshots on this wonderful functionality of SAP and this has saved lot of writing.
Link: [Click here|http://www.whypad.com/posts/sap-how-to-post-a-parked-document-fbv0/56/|Tip]
Trust this helps much and solves your problem!
Regards,
Ashok SINGH

Park and Post for Depreciation Run - AFAB

Hello Experts,
We have around 15,000 assets in our company code. We have requirement that, asset management team will check the depreciation and execute the depreciation for all 15000 depreciation. However at this time, FI postings should not be available.
Later the finance team will re-check the depreciation on test check basis and post it to FI. Trial balance will be updated.
In short, I require park and post for depreciation run in SAP.

Hi Meena,
You can verify planned depreciation in Asset report S_ALR_87011990 and do not tick depreciation posted check box and give report date as the last date of the month you want to verify.
It will give depreciation planned details up to the month in the field dep for the year.
After verifying this you can run AFAB then check the same T code and this time tick depreciation posted check box. Now it will give you depreciation posted.
There is no parking concept in Asset module.
Hope it solves.
Regards,
GSR

Park and Post with ME22N

Hi All -
We are currently using ME22N to park and post a PO.
User with just the PO Processor role is now able to post with AR Approver role
(without the PO Approver role). The authorization objects related to
post are being shared across different modules. These object are
available in all the approver roles and it gives the ability for the
user to post a PO even without a PO Approver role.
It appears as if the F_FICA_FOG, F_FICA_FSG, F_FICB_FKR, and F_FMMD_MES
are being shared across multiple FI modules. One role has the park
(actvt 11) access (PO Processor) and the other role (AR Approver) has
posting capabilities (actvt 10).
We are leaning towards creating custom authorization objects to achieve this. We are trying to prevent Segregation of Duty conflicts in our system. Are there any standard was to prevent someone from posting a parked document in the purchasing module (a PO) if the person has access to post AR documents (AR Invoices)?

We decided to have the DEV team create a custom auth object and custom table to handle this issue. In the table there is a listing of activities, for example:
PO1 - PO Processor Park
PO2 - PO Approver Post
AR1 - AR Processor Park
AR2 - AR Processor Post
In the PO Processor role, in the custom object, the value would be PO1, and in the AR Approver, the custom object would have AR2. This will require a lot of testing. I hope this helps someone in that may have this problem in the future.
Edited by: T on Feb 10, 2011 9:43 AM

Parking and Posting Documents FEBP,F-21,FV60 and FB60

Hello All,
Could anybody please suggest me how is the Parking and Posting Take place in SAP.
And do some Transactions like F-21 had to be given with FB01/FB02?
If FB01 is given what are the restrictions?
Are there any specific SOD's involved..
Replies and links would be greatly appreciated.
Thanks

Parking is a temporary hold of data for the FI doc. You don't need to have all the required data to park. Parking does not impact the financials for a company.
Posting does impact the financials.
F-21 is a parameter tcode for FB01 - so you don't need to have FB01 to use F-21.
SODs ? Depends on what your SOD matrix is.

F-47 park and post option OR F110 block option for payment requests

Similar Messages

Maybe you are looking for