Minutes of Meeting

Topic Kick-off & Requirement Analysis and Clarification for MDM Integration

Participants SandV Team :

Mr.  Patrick Goodman
Mr. Khalid
Mwasalat Team :
Mr. Shabib Mohamed Redha Mustafa
Chainsys Team :
Mr. Ashraf Bilal
Mr. Manoharan P
Mr.Hemadri Harish

Venue Remote discussion Room

Scheduled Start date and time 24-Dec-2019  11:00 AM End date and time 24-Dec-2019  12:00 AM
 

Actual Start date and time 24-Dec-2019  11:00 AM End date and time 24-Dec-2019  12:00 AM
 

Prepared by Mr. Ashraf Bilal R Prépared on : 24-Dec-2019

Circulate to Mr. Ravi (IITC)

(apart from Mr. Srinivas (Chainsys)
participants) Mr.Amit (IITC)
Points Discussed:–

1. Scope of the development and Integration Process Flow is discussed.

2. SandV to provide the data in JSON format for ERP team to consume and interface it to Oracle.
3. Mr.Khalid to provide Source URL where data in JSON format is placed.
4. Sample JSON data for Item, Vendor and Customer master is available in the document, but in ERP to interface Item, Vendor and Customer
few additional information would be required
such as Item Category, default codes etc. This must be checked with the concern business users.
5. Template for Purchase Order Integration with its relevant mapping is discussed in detail.
1. Shared Template clearly shows the fields which are mandatory, Optional and fields which refers to Primary Key of corresponding
master.
2. Following are the fields highlighted in the template as was particularly discussed over the call
1. PURCHASE ORDER ID - PO HEADER ID of Purchase Order in ERP.
2. PO LINE ITEM NUMBER - PO Line Number which is unique in a Purchase Order.
3. MATERIAL CODE - segment1 from MTL_SYSTEM_ITEMS_B.
4. COMPANY ID - Unique ID to identify the OPCO. This data is not available in ERP as it is assigned by MDM tool to a unit.
5. VENDOR CODE - Segment1 of AP_SUPPLIERS.
6. PROCUREMENT CODE - As per the template Purchase Order is placed against a unique category of items such as Fuel,
Stationery etc. Need to discuss with Purchasing team for this mapping.
7. PROCUREMENT CATEGORY - Description of the category provided in the point 6.
 8. COST CENTRE CODE - Refers to the department segment to which creator of the Purchase Order is linked.
9. COST CENTRE NAME - Description of the Segment discussed in the point 8.

Other Mandatory fields of the template are clearly described in the Document shared and Optional fields are not the discussed in the meeting
will be taken up for discussion later.

Next Level Action Points – Planned:

SI.No Agenda Responsibility

1 Discussion with ERP Business User of NFC team NFC

2 Provide the JSON format to ERP team SandV Team

3 Provide URL where the JSON data placed Mr.Khalid (SandV team)

4 Build the extract logic for PO transactions Asraf Bilal (Chainsys)