VMI using SNC/SNP

[Former Member]

What would be the key selling point for VMI using SNC RR compared with VMI using APO SNP? Do I need some kind of contract in case SNC RR with the customer which is not the case for SNP VMI?

[Former Member · Accepted solution]

Hi Rahul

I am not much aware about how VMI works in case of APO SNP but main advantage of using SNC is cost of infrastracture for using APO is much higher than SNC.

APO is planning module and SNC is used for collaboration and execution.

Also in case of SNC its only the internet connection required for customer to access all demand and order data and all the updates happen real time.

Thanks

pravin

[Former Member · Accepted solution]

Hi Pravin,

thanks for your response. I am just wondering about the various use cases for using VMI with SNC and not SNP. So if a customer is already having APO, then it will be completely new setup for SNC.

Additionally, EDI852 communication is supported with SNC and default mapping is available within PI. Not sure for VMI using SNP.

Customer need not login to SNC as long as we are communicating the right PO to them and it is reflect correctly in their planning/executiong system. Not sure whether default PO creation after the planning is supported with SNP.

Also, planning is supported in SNC for VMI as well as SNP.

Hope there are few more key criteria available which we can find out.

Rahul

[Former Member · Accepted solution]

Hi Rahul,

If customer is having APO then it is better to go for APO VMI.

Normally VMI process a company is implementing APO/SNC will be supplier.

In APO:All demand data and stock data releated to customer will come from supplier ERP(Customer will send there stock data to supplier ERP via EDI)

There is no custom mapping required as all the data flow will happen from CIF to supplier ERP(both ways)

and from supplier ERP purchase order,ASN will be sent to customer system here EDI mapping is required.

TLB is a very good functionality in APO which will help to create SO and PO in Supplier ERP which will be trigger from APO only.

see the below link for more details

http://help.sap.com/saphelp_scm70/helpdata/EN/48/03f69d67b34aa7e10000000a421937/content.htm

In SNC:All demand data and stock data releated to customer will come from supplier ERP.

Here stock data customer can send to SNC driectly without sending to Supplier ERP via PI but from PI to customer ERP there is a need for custom mapping which is not standard until and unless customer system is also SAP.

OR

Customer can send stock data to supplier ERP and from supplier ERP to SNC via PI.

As you already know there is no login for customer in SNC(company who is implementing will be the supplier)

Here very limited planning functionality as compare to APO which has good planning functionalities with advanced TLB functionalities.

If you are going for SNC as a VMI then just keep in mind integration effort is more as there is a need for integration between PI to customer ERP.

Summary:If client is having APO then it is best to have APO VMI and client is not having APO then SNC by keeping in the mind limited planning functionalities and more of integration efforts.

Regards,

Nikhil

[Former Member · Accepted solution]

Hi Nikhil,

Thanks for the link. It was useful. TLB is offered in SNC also but the way it is integrated in APO and it can be utilized better there.

Also, SNC comes with some out of the box integration mechanisms empowered via PI mappings. With APO, some advanced planning capabilities for vendor to do internal planning. an be exploited which might not be the case with only SNC.

I agree with your summary to go with APO VMI is APO is already present.

Regards,

Rahul

[Former Member · Accepted solution]

Rahul,

Mainly functionality around Purchase orders and data integration is what is a big plus of SNC vs. SNP. So for VMI SNC would be a better option.

J.