SAP SNC (Supply Network Collaboration) Machine-2 ... - Sagemcom
SAP SNC (Supply Network Collaboration) Machine-2 ... - Sagemcom
SAP SNC (Supply Network Collaboration) Machine-2 ... - Sagemcom
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>SAP</strong> <strong>SNC</strong> –Typical move from old portal to new one<br />
<strong>SAP</strong> <strong>SNC</strong> – You’re connected to <strong>Sagemcom</strong> existing portal<br />
• Date = T0 – <strong>Sagemcom</strong> and Supplier agree on electronic Order exchange relationship<br />
• Date = T1 – Supplier and <strong>Sagemcom</strong> agree on backlog at a definite date<br />
• Supplier user names are exchanged, <strong>Sagemcom</strong> creates <strong>SNC</strong> account on <strong>SNC</strong> system<br />
• Supplier’ users must be trained, thanks to training support<br />
• Date = T2 – Supplier and <strong>Sagemcom</strong> agree on moving-to-<strong>SNC</strong> date (arranged with<br />
local <strong>Sagemcom</strong> purchaser/MRP controller)<br />
• Date = T3 – Supplier checks that its users are able to display the Quick view and the<br />
orders as mentionned in the training document<br />
• Date = T4 – <strong>Sagemcom</strong> switch from old Portal to <strong>SNC</strong>-portal. Supplier check on correct<br />
orders receiving status<br />
• Date = T5 – After several weeks, <strong>Sagemcom</strong> and Supplier make a status<br />
<strong>SAP</strong> <strong>SNC</strong> – It is your first portal use with <strong>Sagemcom</strong><br />
• No legacy to take into account. Nothing specific to do, just do it !<br />
<strong>SNC</strong>-E2E-P1 | Ph.Longuet | 4/03/22 16<br />
Ce document et les informations qu'il contient sont la propriété de <strong>Sagemcom</strong>. Ils ne doivent pas être copiés, ni communiqués à un tiers sans l’autorisation préalable et écrite de <strong>Sagemcom</strong>.