I did a pr on e-cat this afternoon under pascal decamps logon. I have few questions after this exercise.

I took AXCELIS as supplier with plant of crolles 200 (0300/0323)

1. On actual Axcelis catalog (MDM) we have some items link to priority order. Like this :

Or on my test, I can’t see this information. In this way how we can inform supplier about the priority that we need the parts ? from manufacturing plant, shopping cart creator use these items at each shopping cart. It depends on which priority, spares parts can arrive by taxi in the day or later if there is no emergency.[Rohit]  - Similar to MDM catalog these priority items can also be maintained in the Ariba Catalog and selecting while creating PR to indicate priority. The current catalog on test site are just samples configured for testing and practice. If you need we can ask Axcias to add similar kind of lines on Test Catalog.

2. When I made my pr, the purchasing group associated was Wiam Akel. In approval flow the buyer approver was Giuseppe Palmieri. This means that the purchasing group defines at catalog level does not define the buyer in charge ?
   
3.  – There are two points in this :-
   

1. Purchase Group – The Purchase Group on the PR line is determined by Commodity& Plant combination , this is maintained in ZARIBACMDTY in SAP . This PGrp will be printed on the PO which is a change from the current setting of AMK-Muar but will be available at the time of Deployment Go-Live in EU.
2. Approval on PR – The Buyer approval on PR will only appear if PR amount is above threshold . This approver will be the Buyer who is responsible for the supplier and has approved the catalog this is maintained in ZARIBASUPPLIER in SAP . In some of the cases this approver can be different from the Purchase Group Buyer determined on the basis of commodity and Plant. This point is under discussion with Giuseppe and Pascal whether we want to keep this approval at Global Buyer Level or move it to local buyer determined on the commodity and plant.

3. At level of the OCI catalogues, how the supplier does the price change, obsolescences part ect… for my understanding it will be the same of today, in their environment ! thanks to confirm. Change is applicable to MDM catalogs only, supplier must post their price list themselves to ARIBA. We receive questions from our suppliers on this point, some of them deny to use ARIBA if this will generate additional work. – In case of Punchout (OCI) catalogs all the changes after activation of the catalog will be done in the supplier’s environment and this will not require any approval from ST side. The supplier is bound by the OCI contract and they should maintain accordingly.

In case of Static(MDM) catalogs supplier needs to make the changes in the catalogs and upload on Ariba by themselves (Not a very complex thing to do its just a file upload) , the idea is to maintain the ownership supplier will maintain what they are selling to us and at what price , we just validate . Any change in Static Catalog will require Buyer and Buyer Manager approval.

4. For notifications and approvals of buyer in charge of catalog :

From my understanding, Buyer must validate the changes of the catalogues when it concerns additions items or price change. In case of  obsolescence, no approval is requested from the buyer ? tell me if I’m correct ?-Any change (Addition, Deletion of particular item , price change) in static catalog will require approval from buyer and Buyer manager . In case of complete removal of catalog by supplier it does not require any approval from ST side , Catalog Admin will receive a notification of catalog removal and this needs to be informed to the respective Buyer.

5. About additional costs such as delivery costs, when the order is less than 100 euros, as an example with INMAC (OCI catalog). Can you confirm us that the users will not have the hand to cancel  this line ? All the restriction and validation in case of a Punchout Catalog are controlled by what supplier has configured on their website . Requestor cannot do anything ( Quantity Increase/Decrease , Addition of Item , Deletion of item..) without going back to supplier’s website. They will get a message like below when they try to edit item of punch out PR .

             The only action allowed before submitting the PR is to remove all the line which will essentially stop the PR creation.