Scribd Logo
Upload

Welcome to Scribd!

  • 2X Interface To MM

    Uploaded by

    Yong Benedict
    6 views2 pages
    1. The Ariba procurement process involves raising a purchase requisition (PR) in Ariba, approving the PR, converting it to a purchase order (PO) in SAP, generating a goods receipt (GR) in Ariba, and replicating the GR in SAP. 2. The Concur procurement process involves creating and submitting an expense claim in Concur, approving the claim, transferring it to SAP for posting, and updating the claim status to posted and paid. 3. Both processes use adaptors to interface between the third-party system and SAP for master data transfer and transaction synchronization.

    Original Description:

    Original Title

    2X Interface to MM

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    1. The Ariba procurement process involves raising a purchase requisition (PR) in Ariba, approving the PR, converting it to a purchase order (PO) in SAP, generating a goods receipt (GR) in Ariba, and replicating the GR in SAP. 2. The Concur procurement process involves creating and submitting an expense claim in Concur, approving the claim, transferring it to SAP for posting, and updating the claim status to posted and paid. 3. Both processes use adaptors to interface between the third-party system and SAP for master data transfer and transaction synchronization.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    6 views2 pages

    2X Interface To MM

    Uploaded by

    Yong Benedict
    1. The Ariba procurement process involves raising a purchase requisition (PR) in Ariba, approving the PR, converting it to a purchase order (PO) in SAP, generating a goods receipt (GR) in Ariba, and replicating the GR in SAP. 2. The Concur procurement process involves creating and submitting an expense claim in Concur, approving the claim, transferring it to SAP for posting, and updating the claim status to posted and paid. 3. Both processes use adaptors to interface between the third-party system and SAP for master data transfer and transaction synchronization.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 2

    IF101 Ariba Procurement Process Benedict YONG, Certified SDMM,

    FICO
    Ariba to ERP interface. Weekly Sharing Session, Singapore
    PR and GR at Ariba; PO and IV at SAP

    ARIBA ERP

    Event
    Start

    1a. Ariba Adaptor 1b. Masterdata


    Configurati

    Masterdata

    active transferred
    on+

    (overnight)

    2. Raise PR
    Requestor

    6. Perform GR

    4a. PR generated 5. PR converted


    Yes
    3. Approve to PO
    Procureme

    No
    nt

    4b. Update SAP 7. GR replicated


    PR number to
    Ariba PR
    Finance

    8. Receive
    Account
    Invoicing End
    Payable
    IF102 Concur Procurement Process Benedict YONG, Certified SDMM,
    FICO
    Concur to ERP interface. Weekly Sharing Session, Singapore
    Claim at Concur; Payment at SAP

    CONCUR ERP

    Event
    Start

    1a. Concur Adaptor 1b. Masterdata


    Configurati

    Masterdata

    active transferred
    on+

    (overnight)

    2a. Create Claim


    Requestor

    2b. Submit Claim

    4. Transfer to 5. Posting into


    No Yes ERP, SAP FI. [Concur *Concur Native Adaptor
    3. Approve
    immediately Adaptor] Allow programmatic checks
    on budget via BADI
    Supervisor

    7b. Supervisor 7a. Push Claim


    No Yes
    rejects the claim, back for 6. Error
    for re-submit correction

    **Concur Native Adaptor 8. Update Claim


    Allows 2-ways flow
    Status = Posted
    Finance

    9. Update Claim
    Status = Paid Payment Run
    (Periodic)

    You might also like