Parking and posting invoice document (MIR4 & MIR7)

Hi Expert,
We Have 2 different SAP User IDs (MMADMIN/FIADMIN) having same role and profile (SAP All Authorisation). The Functionality is like that we parked (MIR7) invoice document through MMADMIN and we need to post that one through FIADMIN (MIRO).
Now we have Parked document through MMADMIN by MIR7 Transaction, But when I entered in MIRO transaction through FIADMIN and click on Show Worklist,
We havenu2019t seen that list in FIADMIN.But list has been seen in MMADMIN.
Thanks
Lavlesh

Hi,
the purpose of worklist is little bit different. Here is a quote from [SAP documentation|http://help.sap.com/saphelp_erp2005/helpdata/EN/14/ce4738c8a64338e10000009b38f842/content.htm]
You can use the worklist in the applications Enter Invoice and Park Invoice. The worklist displays invoice documents that you have already processed using the transactions Enter Invoice or Park Invoice, but which have not yet been posted and for which you are the last processor. The documents are displayed under the following nodes:
Basically the user needs to be last processor. But SAP support entering invoice by more than one user. Again more info in [SAP documentation|http://help.sap.com/saphelp_erp2005/helpdata/EN/82/5c2f38e80d2805e10000009b38f889/content.htm]. User FIADMIN can also use report MIR5 to get all parked documents.
Cheers

Similar Messages

  • OCR Solution: wrokflow on MIRO ( Park and Post Invoices)

    Hello one and All,
    We are planning to introduce a OCR solution which will scan and read the incoming paper invoices and it will then do the 3 way match on a daily basis and park the correct invoices.These invoices that are parked by the system should then be workflowed to an approveru2019s inbox in the SAP Business workplace.
    can any one came accross the above requirment and let me know your suggestions to procedd further.
    Raj

    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

  • Parking and Posting of Documents

    Hi Frnds,
    Can i park the documents relating to Incoming and Outgoing Payments???
    thanks in advance........
    Regards,
    Jigar

    Hi,
    You can use document parking to enter and store (park) incomplete documents in the SAP System without carrying out extensive entry checks.
    You can definitely park the documents relating to Incoming and Outgoing Payments.
    When documents are parked, data (for example, transaction figures) is not updated. The only exception to this is in Cash Management. Data from parked documents can however be used for evaluations by the system. For example, amounts from parked invoices can be used for the advance return for tax on sales and purchases. Using payment requests, parked invoices can be paid punctually and without loss of discount.
    Menu path: Accounting -> Financial accounting -> General ledger -> Reporting -> Tax reports -> General -> Input tax from parked documents
    I hope it will help.
    If helpful, please assign points.
    Regards,
    Manju

  • FV65 - WorkFlow Implementation for parking and posting invoices

    Hi All,
        We are implemetnig workflow for vendor invoices. can anyone implemented this for FV65 can help us which workflow template to use and what are the configuration settings for this.
    Regards
    Purna

    Hi:
    Refer to this documentation.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMMM/BCBMTWFMMM.pdf
    Please let me know if you need more information.
    Assign points if useful.
    Regards
    MSReddy

  • 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

  • How can we distinguish between post, parked and rejected invoice in SAP

    Hi Guys,
    Is there any way by which we can distinguish post, parked and rejected invoice. I mean to say any field gets updated after doing any of these activity...
    Help from you all will be highly appreciated...
    Thanks in advance,
    Vikash

    Hi,
    If BKPF-Bstat is space then its a normal document and if it is A then its clearing..
    A     Clearing Document
    B     Reset clearing document
    D     Recurring entry document
    M     Sample document
    S     Noted items
    V     Parked document
    W     Parked document with change of document ID
    Z     Parked document which was deleted
    I hope this helps.
    Regards
    Ravinagh Boni

  • Error in documents parking and posting

    Hello,
    After I parked the document of vendor payment using F-65 , While I validate and post the documents using FBV0 I met a error as following:
    " Formatting error in the field BSEG-PRCTR; see next message
    Message no. 00298
    Diagnosis
    During batch input or when executing CALL TRANSACTION... USING a screen field was filled with an invalid input format.
    System Response
    Processing was terminated.
    Procedure
    The screen field has the technical name BSEG-PRCTR . The cause of the error is described in the following message.
    Correct  the appropriate BDC data."
    How can i add the field profit center in F-65 of in FBV0 while posting the parked document ?
    Thanks

    Hi Tarek
    at first please check field status transaction with OB14, OB41.
    Please also check in transaction OBC4 for the relevant field status variant and the relevant field status group in "Additional account assignments" that "Profit center is not set as required.                           
    do you have an asset line inside the document ?
    When a classicaly parked document or a document parked by the complex  posting via ENJOY is posted, a CALL TRANSACTION USING is run through. It can be compared with a batch-input session in the background.
    If a document is parked with an asset line, it might be that in the asset line account assignments were derived by parking the document, although they are not open for entry. For making sure, that the CALL TRANSACTION USING is not failing for such lines, the settings of the asset  accounting have to be disregarded and the fields have to be opend.
    Then only the fieldstatus of posting key and G/L account are regarded. Since the fieldstatus of PRCTR is defined as required, the posting fails. If it was optional, everything would have worked properly.                                                                               
    Kindly revise your field status customizing
    Kind Regards
    davide

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

  • 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

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

  • Parked and Blocked Invoice

    Hi Gurus,
    What is the difference between parked and blocked invoice? Under what situations we go for parked invoices and under what situations for blocked invoices? When there is a quantity and price variance, invoice gets blocked. Can we go for parked invoice in case of quantity and price variance? A detailed explaination will be really helpful.
    Thanks,
    Kumar

    HI,
    Parked Invoices
    You can park invoices or credit memos. This means that you enter the invoice data or credit memo data in the system and save it in a document, but the system does not post this invoice initially.
    You can change a parked document as often as you wish, for example, by adding or correcting data. The changes are logged. When you have finished changing the document, you can post the parked document. Only when you post an invoice or credit memo, does the system carry out the normal account movements and make the necessary updates.
    To park a document, choose Logistics Invoice Verification -- Document Entry -- Park Invoice
    Blocked Invoices
    You can block an invoice manually. You have two options for doing this when you enter the invoice:
    You can block an invoice by entering an R in the field Payment block in the document header data.
    You can block an item by selecting the Ma (manual blocking reason) field in the item list. When you post the invoice, the system automatically sets an R in the field Payment block in the vendor line of the accounting document. Manually blocked items are given the blocking reason Manual block (M).
    Logistics Invoice Verification -- Further processing -- Release invoices
    Specify the Selection of blocked invoices
    Select the type of Processing
    Select a Blocking procedure
    Exceute
    Thanks & Regards,
    Kiran

  • 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

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

Maybe you are looking for