Manual Exportation Interface by Work Order
STA System version 4.7.1
Date: July 23, 2020
Version: 1.0
Table of Contents
1 Introduction..................................................................................................................... 2
2 Interface Structure............................................................................................................ 3
3 Interface Scope and Set-up ................................................................................................ 3
3.1. MX Custom ........................................................................................................... 3
3.2 US Custom ............................................................................................................ 4
3.3 Set-up .................................................................................................................... 4
3.3.1 Application Set-up ........................................................................................... 4
3.3.2 Interface set-up ............................................................................................... 8
4 Validating information ..................................................................................................... 11
4.1 validating Export Invoice ..................................................................................... 11
4.1.1 Mexican invoice ............................................................................................. 11
4.1.2 BOM for Annex 24 ......................................................................................... 14
4.2 validating Kit Components ................................................................................... 17
4.2.1 Mainx30......................................................................................................... 20
4.2.1 American Invoice ........................................................................................... 22
1 Introduction
The Work Order interface is a program which is designed to load Exportation Invoices Automatically with
A Special BOM for every shipment, this information will be provided by the ERP and it also going to feed
the specified files in interaction with the interface, this interface will also load the specific Kit used for
this Export.
2 Interface Structure
3 Interface Scope and Set-up
3.1. MX Custom
For annex 24 purposes this interface will load a new Export Invoice with the exact BOM structure which
is provided by the ERP JDE, and it must contains all BOM levels In order to make the complete Backflush
of every component within the BOM
And the Mexican invoice need to be processed as is regularly made, and The Backflush process will
remain the same
3.2 US Custom
For US customs purposes this interface will load the FDA Kits provided by JDE in the BOM reference File,
As the requirement made by BARD this interface will only consider the parts which has FDA regulations
And going to load a completely new Kit BOM which in turn going to be referenced to the new Export
invoice, this information will be visualized on the American Invoice and it also could by transmitted to
the US broker on the MAINX file as well.
3.3 Set-up
3.3.1 Application Set-up
Any configuration on the application it’s through parameters of the system
For parameter configuration follow these steps:
1. In the Main menu go to datos generales \ Tablas
2. Type the parameter code given by the Engineer of the vastera account
And press buscar button
3. Type the required information in description field then click on grabar
The STA vastera System needs to be set up with the following parameters:
Required:
951P is the path of the JDE input Files, Reference BOM and Export files, this path can be filled with
the exact file location (ip..\d$\Apps\ etc.) or relative (example. ..\JDE\files\),
951M is the path for the files that were processed by the WO interface
951H this is the directory which contains all the reports generated on every data load
951KIT for activate this option fill with “S”, this will enable the load of the Kit Components
Optional:
SERVER IP or server name of the Email server, this is used for sending Emails
951T this is the Material Type of the invoice example: MP, PT etc. If it’s in blank the default is the
material type is going to be taken from the JDE export file
3.3.2 Interface set-up
In order to make the proper setup of the interface, the first we need to do is to load
The update package to the application server, which includes ad951bard.xfg file
And do the following:
- Create a batch file with this structure-
set fip=*ad951bard$ad951bard$ad951bard$127.0.0.1$7001
..\server\fipw504
Where:
*system$cia$user$servername or ip$port
- Create a new task on windows task scheduler triggering the batch file and running
repeatedly each 5min indefinitely.
4 Validating information
4.1 validating Export Invoice
4.1.1 Mexican invoice
The interface will load a New Mexican invoice by naming it according with the consecutive number
Of the Material Type, by example:
Material Type MP-005, in the next invoice will be the MP-006 and so on, to identify the Invoice vs the
Export file you need to validate the reference number that will match with the description of the
invoice,
For the Mexican pedimento it will take an opened pedimento of the week
After validating all the information of the invoice, save the invoice and proceed
Pressing actualiza button, this will process the invoice and make the backflush process in order to print
the invoice
To check the invoice information matches the information of the file, please check the Export Layout
Records:
- H is the Header of the invoice which includes Material Type , plant code , date and the
vendors
- D is the detail of the invoice, which includes the line item information as the
Part number , quantity exported, UOM , gross and net weights etc.
Example files:
det12546.txt exp12546.txt
Export Layout;
4.1.2 BOM’s and Backflush for Annex 24
For validating the BOM loaded for that invoice, check the Backflush by invoice report:
NOTE: this report can only be ran after processing the Export Invoice
In the Main menu navigate to Exportaciones \ Reportes de Exportación \ Reporte de descargas por
Factura
Type the invoice to report and choose how is going to be the output, excel, screen, pdf etc.
And check Imprime descargas
In this report you can find the quantity required of each component and the quantity discounted from
the balance, and weight and value as well, the BOM used for discharges of that specific invoice is
displayed as a list, and the totals are below at the final of the report, which is separated by Finished
good ,
4.2 validating Kit Components
For validation of Kit components, navigate to: Partes \ ABC de Kits (Costos de Produccion)
Type the product kit that you already load with the interface in the Export Invoice,
There will display the list of the KITs generated with that product, to check the ID that matches the
Invoice, search for the latest id loaded, you can also do the match by date,
Click the id to edit the KIT,
Then go to BOM button,
Here you will find the BOM loaded for that KIT,
Considering that the components shown in this list will be only the components on the BOM file which
contain FDA regulations for that product, check if the CO is the same as in the file, and validate quantity
and costs,
4.2.1 American Invoice
Navigate to Exportaciones \ ABC Facturas de Exportacion
Then look for the invoice which matches the description with the Export file,
Then click on Imprimir
Now choose Factura americana with number 1, then click on Aceptar
There will appear a preview of the format of the printed invoice,
In the format you will find this label: this product contains, which means that this product is containing
kit components, now check if the quantity shipped matches with the BOM quantity multiplied by the
quantity of the product, validate the FDA information as the Affirmation codes
Also check unit value and duty for each component
4.2.1 Mainx30 file
After generating the Entry for the Export invoice, generate the MAINX file
And search for a component of the KIT,
On the IV22 record check the UOM and the quantity matches with the quantity of the BOM file,
And also in the IV24 record if the component contains a second UOM
Example
mainx30.dat