Work instruction for Monitor and process R91 files from QAD to

SCM server

Propriety and Confidential Rev 1.0 Page 1 of 6

Revision Revision date Description of change

1.0 (08-03-2019)  Initial update

Prepared Approved Released

Process Leader Subject Matter Expert Process Champion BOS Regional Team

Alejandro Hernandez Mera (NA)

Kotresh Nerki Suresh Kumar
Signature (optional) Signature
Approval records maintained by BOS Team

Process Leader: Leads / coordinates development of this work instruction.

Subject Matter Expert: Resource with specific knowledge of the process (may be same as Process
Leader).

Process Champion: Responsible for process and authority for area (scope) impacted – Not mandatory to
be directly responsible for the Process Leader or Subject Matter Expert.

BOS Regional Team: Manages document posting / revision control.

1.0 Purpose
This work instruction describes information on steps involved for how to monitor and process
missing R91 files from QAD to SCM destination

2.0 Scope
NA
This work instruction applies to MFG/PRO application specifically for L2 Support team.

3.0 Responsibility
The Support group responsible for coordinating with EI team and confirm with plant on whether R91
files processed successfully and reached SCM destination or not.

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.

 Work instruction for Monitor and process R91 files from QAD to
SCM server

Propriety and Confidential Rev 1.0 Page 2 of 6

4.0 Process

R91 files are related to MFGPRO menu 5.5.12 Transport Desk export-PACKINS.

This file is required to reach SCM team (Supply Chain team) to create Top 20 report to give the
information on inventory details. This file contains all packaging data like container details, container
capacity, purchase order details, product line, currency etc.

File prefix: R91

This is automatic process. Batch job setup has been done in each plant to generate the file each week.
Every week one R91 file will generate for each plant. It is having one-week data.

Batch job name: PMFGH-PACKINS-DB name ex: PMFGH-PACKINS-AMFP787P

Batch id: packins

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.

 Work instruction for Monitor and process R91 files from QAD to
SCM server

Propriety and Confidential Rev 1.0 Page 3 of 6

Every Sunday batch job will execute from TWS. Once batch job executed then R91 file will generate and
file will stored in /global/mfgpro/home/packins/archive/DBname

Ex: /global/mfgpro/home/packins/archive/amfp787p

File output will be in .csv format

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.

 Work instruction for Monitor and process R91 files from QAD to
SCM server

Propriety and Confidential Rev 1.0 Page 4 of 6

Destination of the R91 file:

SCM is the destination to receive the R91 files and server will be A700M745

SCM destination
MFGPRO R91 files EI interface A700M745

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.

 Work instruction for Monitor and process R91 files from QAD to
SCM server

Propriety and Confidential Rev 1.0 Page 5 of 6

5.0 Steps to validate and process R91 files

If R91 file for specific plant not reached to SCM team then plant will raise a request to validate from
MFGPRO end.

A) We need to check whether batch job PMFGH-PACKINS-DB name executed or not on Sunday. If
job executed, then batch id packins in 36.14.3 will be “COMPLETE” status and file will be present
in /global/mfgpro/home/packins/archive/DBname

If job not executed, then we have to ask TWS team to execute the job for previous week which duration it
failed to execute.

B) If everything is fine then need to contact EI team, whether files are processed from EI end to
SCM destination or not.

Below Inputs required to share from MFGPRO end to EI team:

 Interface name: I1472 and Server details

 Ex: Server: s021u016.autoexpr.com
 File path and file name

Ex:

C) If JFTT writer is hung up status in EI end, then it will not process the files from EI to SCM team.
Then EI team needs to restart the JFTT writer to process the file. Once files processed from EI
end, files will reach to SCM destination as mentioned above server.

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.

 Work instruction for Monitor and process R91 files from QAD to
SCM server

Propriety and Confidential Rev 1.0 Page 6 of 6

6.0 Pre-requisites
MFGPRO L2 support team needs to take action for this alert

7.0 Records/Logs
Logged in the project repository system

Work instruction Document link:

https://connect.adient.com/sites/ITAMOMFGPrblmMngmnt/MFGPRO%20NA%20supprt%20documents
%20repository/Forms/AllItems.aspx?RootFolder=%2Fsites%2FITAMOMFGPrblmMngmnt%2FMFGPRO
%20NA%20supprt%20documents%20repository%2FUser%20Guides%2FQAD%20NA%20internal
%20process%20activities&FolderCTID=0x012000891B74302637584983B524871C2ACC7B&View=
%7B7EED2F1A%2DA815%2D4F35%2DA02F%2D2CA331AD999F%7D
8.0 Reference

Document to be delivered under “7.0 Records/Logs”.

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.