Scribd
Upload
30 views1 page

P2P Note

The document outlines a concept note for reengineering sourcing solutions to create an agile Design to Warehouse process, addressing challenges such as dual purchase cycles, data duplication, and integration issues. Key outcomes include reducing PO creation time, improving master data governance, and establishing a single source of truth for costs and schedules. Proposed solutions involve creating a unified purchase system, enhancing integration with existing systems, and implementing rule-based governance for data security.

Uploaded by

scribd_girish
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
30 views1 page

P2P Note

The document outlines a concept note for reengineering sourcing solutions to create an agile Design to Warehouse process, addressing challenges such as dual purchase cycles, data duplication, and integration issues. Key outcomes include reducing PO creation time, improving master data governance, and establishing a single source of truth for costs and schedules. Proposed solutions involve creating a unified purchase system, enhancing integration with existing systems, and implementing rule-based governance for data security.

Uploaded by

scribd_girish
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Reengineering current Sourcing solutions – Concept note.

Goal – To create an agile, streamlined Design to Warehouse process backed up with necessary
systemic changes. Support the needs for upcoming sourcing and supply chain transformation
projects and set them up for success.

Current Challenges:

We have a dual process for Core and Fashion for the purchase cycles.

- Costing cycle ( RFQ P4 to confirms PO costs P1),


- OTB management for finance control
- Friction in applying changes to PR through PO.
- Duplication of effort for new FG code (for the same style) if there is a revision in the PO.
- Master data synchronisation issues
- Duplication of data structures and errors thereof between 2 systems – 3P system which
interfaces with vendor – ProACT and internal application D2W.
- Integration of the complete purchase cycle upto the point of ASN at Warehouse.
- Innerwear structure does not comply to current D2W logics
- Creation of FG code is not currently in D2W- Shifted to FMS (validation error in D2W)
- Core orders are created in D2W for USPA/Arrow/FM, but there is no validation of batch and
age is identified based on GRN date which is laborious.
- Costing Duplication both in Proact and D2W ( Since approvals happens in D2W by product
and sourcing)

Outcomes to be addressed:

1. Cut down PO creation time by x%


2. Have unlimited flexibility to add new FG codes basis previous style codes
3. Master data governance setup.
4. Visibility to the OTB on real time and at the time of creating the PR, eliminating expensive
rejection times and errors
5. Single source of truth of the final cost, quantity and supplier schedules.

Likely Solutions:

1. Create a single source of Purchase system (for bulk and sampling) within the Proact solution
framework
2. Tighter integration with Proact and SAP to ensure synchronous data and better feedback
visibility of potential issues
3. Rule based governance basis the ITGC compliance recommendations to strengthen security
of data.

Key considerations:

1. Security and renewed NDA / MSA


2. Use of the current Arvind integration architecture to contain costs and better synergise with
SAP.
3. A SaaS based solution where Procurement team adopts solutions so that upgrades and
solutions demands can grow with the market leading innovations.
4. Lead the innovation and enable AFL monetise on the changes through competitive license
structures.

You might also like