5 Replies Latest reply on May 13, 2015 12:33 AM by Nandu VC

    PO (created after the PR is approved) in Ariba P2O -Should NOT be sent to Ariba Network instantly as PO but to ECC as PR

    Nandu VC Journeyman

      Question: PO (created after the PR is approved) in Ariba P2O -Should NOT be sent to Ariba Network instantly as PO but to ECC as PR

       

      Standard Ariba Functionality: PR (Shopping Cart) is created in Ariba. Passes through approval sequence and once Fully approved creates a PO. This PO is then "carbon copied to ECC" and also sent to Ariba Network (AN).

       

      Side Note: Our Integration scenario is SAP PI between downstream P2O and ECC and also SAP PI between ECC and AN

       

      Our Requirement: We have certain unique requirement from a Govt Business Standpoint that the all PR's should have a DPAS (Defence Priorities and Allocation System) rating to be associated to them. There is a fairly large custom code functionality that we have in ECC today, which is able to peg the DPAS rating to all the PR created in the System. We dont intend to re-build this custom functionality within Ariba. So the following is our requirement:

       

      Step 1) PR (Shopping Cart) is created in Ariba. Passes through approval sequence and once Fully approved creates a PO.

      Step 2) This PO is Not sent to AN from P2O rather should be copied to ECC as PR

      Step 3) These PR in ECC would flow through the custom program in ECC and get DPAS rated.

      Step 4) This DPAS rated PR should now become a PO in P2O and can be carbon coped to ECC and also sent to AN

       

      Question 1) So essentially what we need is that the PO created in P2O in Step 1 should not be sen to AN. Is there a way to achieve this?

      Question 2) Can we built an integration scenario for a PO in P2O to create a PR in ECC?

      Question 3) Can we built an integration scenario for a PR in ECC to become a PO in P2O

       

      Any thoughts or a different approach to this requirement would be highly appreciated.

       

      Thanks,

      Nandu

        • Re: PO (created after the PR is approved) in Ariba P2O -Should NOT be sent to Ariba Network instantly as PO but to ECC as PR
          Vilas Swamy Master

          Hi Nandu,

           

          Another approach would be more robust and comparatively easy to be build.

           

          PR created in Ariba with "DPAS_Rated" flag set to 'false' by default-> Approvals in Ariba -> PR post approvals sent to ECC as a PR -> DPAS Rating obtained for PR in ECC -> DPAS Rated PR exported from ECC via IDOC/SOAP/WSDL to Ariba (standard Req Import) -> All Req import set as auto approved in Ariba -> PO sent to Ariba Network.

           

          The only problem with this approach is that for every purchase request there will be two PR#'s generated in Ariba so few more customizations to handle user notification and correct reporting should be done.

           

          Regards

          Vilas

            • Re: PO (created after the PR is approved) in Ariba P2O -Should NOT be sent to Ariba Network instantly as PO but to ECC as PR
              Nandu VC Journeyman

              Many Thanks. My response is late, as we went and researched your answer and following is what we found. Not sure of what I present is correct, maybe you could validate?

               

              1) When the PR's (with DPAS_RATED" flag set to "False") are fully approved, it immediately creates a PO in Ariba and is carbon copied to ECC. We are unable to stop the Automatic process of "Fully Approved" PR from getting converted to PO automatically. If there was a way to break the sequence, and not have the fully approved PR'sin Ariba to automatically convert to PO (in Ariba) then your comment could be researched further.

               

              So the Question is, Is there a way that these Ariba PR's which are fully approved, should NOT be converted to PO's automatically, but be converted to PO, based off some other mechanism?

               

              2) From your feedback, it looks like PR's from ECC be IMPORTED as "PR's" in Ariba? (Is that a correct Statementt)?

               

              3) Business may not approve the possibility of Duplicate PR's because budget is consumed against the Original PR's. Now after importing PR's from ECC (which create new Ariba PR's which are auto approved) should not consume the Budget once again?

               

              Your response and the community's feedback is highly valued.

               

              Many thanks,

            • Re: PO (created after the PR is approved) in Ariba P2O -Should NOT be sent to Ariba Network instantly as PO but to ECC as PR
              Vilas Swamy Master

              Hi Nandu,

               

              Recently I attended a refresher session on new features and functionality and based on the information I gained can I request your to ignore my earlier comments as those now appear to be an out dated design.

               

              Achieving your goal looks much easier with new features and a recommended flow would be as follows:

              1. PR created in ECC using Ariba Catalog option at line level

              2. DPAS rating obtained as usaul on the PR in ECC

              3. The DPAS rated PR's in ECC are imported in Ariba using standard Req Import functionality

              4. The order is generated and sent to AN via Ariba P2O and is carbon copied to ECC

               

              Please let me know if you have already tackled this in similar way or otherwise.

               

              Regards

              Vilas

              1 of 1 people found this helpful
                • Re: PO (created after the PR is approved) in Ariba P2O -Should NOT be sent to Ariba Network instantly as PO but to ECC as PR
                  Nandu VC Journeyman

                  Many Thanks Vilas.

                   

                  Exactly. We are at the moment considering the design on the lines of End

                  User creating Requisition in ECC and branching out to APC (for CIF catalogs

                  or Level 1 catalogs or Level 2 catalogs), and then on completion of the

                  shopping cart, control transfers to ECC where the DPAS rating and the

                  complex DOA (Delegation of authority --> budget based complex approval

                  logic existing in ECC can be triggered). Once completion of DPAS and DOA,

                  we are thinking about importing the PR to Ariba for Ariba to then send out

                  the order to AN and carbon copied to ECC.

                   

                  But we are still deliberating other potential issues in the above design

                  ...which I will post shortly.

                   

                  Your design feedback has been valuable and food for thought.

                   

                  Many thanks,

                  Nandu

                   

                   

                   

                  On Wed, May 13, 2015 at 12:28 PM, Vilas Swamy <dont-reply@exchange.ariba.com