Context
MFP and AP accept hierarchy and data files directly, as <interface>.hdr.csv.dat files dropped in the application’s FTS incoming folder. At P&C the upload is done with the FTS helper script puc_fts_files.sh (client script, kept outside this vault); the arguments are <app> UPLOAD <environment> <destination folder> <file>. UAT1 below is the environment.
Used by MFP Implementation (before the build) and AP Implementation (after the build).
Quick access
MFP
- Create
vath.hdr.csv.dat. - Upload it to
planning/mfpscs/incoming/input:
./puc_fts_files.sh MFP UPLOAD UAT1 planning/mfpscs/incoming/input vath.hdr.csv.dat
AP
- Create the direct load files:
| File |
|---|
asrt.hdr.csv.dat |
pos1.hdr.csv.dat |
pos2.hdr.csv.dat |
csls.hdr.csv.dat |
cver.hdr.csv.dat |
curv.hdr.csv.dat |
sspc.hdr.csv.dat |
- Upload each one to
planning/apcs/incoming/input(one call per file):
./puc_fts_files.sh RPAS UPLOAD UAT1 planning/apcs/incoming/input asrt.hdr.csv.dat
Tasks>Administration>Online Admin Tools>Submit An Admin Task>Configured Batch Tasks>Run Batch Task Group.- Choose Load Hierarchies and submit.
File layouts not documented here
The plan records only the file names. The column layout of each interface is in the application’s Implementation Guide (links below).