Usage > Trade connectors > APS > APS > APS interface launch 

This function is used to manage the flows coming from and designed to the advanced planning and scheduling product (APS): ORTEMS.

This processing uses the setups specified in the ORTEMS setup function.

SEEREFERTTO The principles of the interface functioning are given in the documentation about the ORTEMS setup. 

    Prerequisite

    SEEREFERTTO Refer to documentation Implementation

    Screen management

    Entry screen

    Presentation

    Terms for the interface implementation (in interactive mode)

    It is required to install ORTEMS on the client to launch the interface.
    The interface proceeds in two main steps. They have to be carried out independently:

    1/ Picking the data to export:

      • Selection of the data and constitution of the the work files.
      • Use of the files and opening of the planning in ORTEMS (*). 

    2/ Update the database:

      • Extraction of the ORTEMS planning data (*).
      • Direct integration of the results in Sage X3.

    (*) This stage is carried out if the ORTEMS Integration box is checked.

    The interface processing can be carried out in Simulationor in Update mode.

    • To integrate a planning of WOs, it is necessary to launch the two distinct steps in Sage X3:
       
      --> Preparation of the data, in Update mode.
      --> Update of the results.
    • In order to carry out a valuation/simulation of planning on WOs, it is only necessary to launch the step: Preparation of data in Simulationmode.

    For the Preparation of data, it is possible to:

    - select the production site concerned,
    - enter a date range that defines the period concerned,
    - enter a selection formula,
    - select the orders to analyze according to their status: planned, firm or suggested,
    - possibly change the release margin,
    - specify if the product code if of Range or Producttype,
    - specify if the type of the project is Journal or Project
    - indicate if the log file has to include the orders retained in the selection,
    - possibly modify the root directory and the ORTEMS environment reference.

    For the Update of the results, it is possible to:
     
    - select the production site
    - specify if the log file created at the end of the processing has to include the list of optimized orders,
    - modify the information (root directory and environment code) required when launching ORTEMS automatically.
     

    Close

     

    Fields

    The following fields are present on this tab :

    Block number 1

    • Identifier (field ID)

    Identification code of the interface setup.

    • field INTIT

     

    Processing

    • Action (field OPTION)

    Select the type of action implemented by the processing:

    • Preparation of the data:
       
      - Selection of the data and construction of the work files.
      - Use of the files and opening of the planning in ORTEMS (*).
       
    • Update of the results:

      - Extraction of the ORTEMS planning data.
      - Integration of the files and opening of the planning in ORTEMS (*). 

    (*) This stage is carried out if the ORTEMS Integration box is checked.

    • Processing mode (field TRTMOD)

    Select the processing mode of the action:

    • Update: the manipulations carried out in the WOs in the selection in order to smooth the load on the work centers introduce modifications to the order dates for the whole application.

    • Simulation: all the manipulations carried out on the WOs in the selection will be lost at the end of the simulation. It is not possible to display the planning of orders prepared in simulation mode.

    Selection criteria

    The production site associated with the user is proposed by default. It can be modified by another site authorized for the operator, depending on its authorizations.

    • Start date from (field STRDAT)

    Enter the start and end date ranges to select the period concerned.

    The start date is initialized with the current date. In case of modification, it is possible to reinitialize it by checking the box: Current date.

    • Current date (field STRDAYFLG)

    This box has to be checked in order to reinitialize the start date with the current date.
    The end date cannot be modified then.

    • End date until (field ENDDAT)

    Enter the start and end date ranges to select the period concerned.

    La date de fin est initialisée avec la date du jour + Délai de planification affiché (renseigné sur l'écran de paramétrage de l'interface). Elle reste modifiable ; l'horizon est toutefois limité à 2 ans.

    • Planning leadtime (field ORTLTI)

    The planning lead-time cannot be modified; it is entered in the interface setup screen and is used to calculate the horizon end date using the entry start date.

    • field FILJOUR2

     

    Enter, select or build an Enterprise Management filter calculation expression using the formula editor.

     An error message is displayed if you refer to tables which are not generally used by the configurator, or to unknown variables.

    Statuses

    • Planned work orders (field WOPFLG)

    It is possible to select the orders to analyze according to their status.
    Tick this box to analyze the planned WOs.

    • Firm work orders (field WOFFLG)

    It is possible to select the orders to analyze according to their status.
    Tick this box to analyze the firm WOs.

    • Work order suggestions (field WOSFLG)

    It is possible to select the orders to analyze according to their status.
    Tick this box to analyze the suggested WOs.
    It is possible to choose to work with suggestions coming from the MRP, the MPS, or both.

    • Suggestion filter (field MRPFLG)

    This flag is used to filter the suggestions based on their origin.

    Optimization

    • Release margin (field WOMAR)

    This setup defines the maximum downstream shift for each work order.
    Expressed in number of days, it is used to calculate the "Earliest" start date of each order.


    • field FILJOUR1

     

    Extraction

    • Product code (field RELITM)

    Select a type of product code for the extraction in the case of data preparation:

    • Routing
    • Product.
    • Project (field PJTCOD)

    Select a type of project for the extraction in the case of data preparation:

    • Project
    • Journal.

    Log

    • Selected work orders (field TRACE1)

    Depending on the type of requested processing, it is possible to activate one of the log file types:

    • Log file of the orders included in the study: 
       
      This log file can be activated for the Data preparation processing: it is then suggested before displaying the Gantt and contains the list or orders of the selection.

    • Log file of optimized orders: 
       
      This log file can be activated for the Result update processing: it is suggested on exiting the function if an optimization has been requested in update mode.
    • Optimized work orders (field TRACE2)

     

    Directories

    • Destination type (field TYPEXP)

    Select the type of sender: customer or server.

    • Log (field TRACE)

     

    • Index destination (field VOLFILISS)

     

    • Directory to be scanned (field VOLFILRCP)

     

    • Storage directory (field VOLFILSTO)

     

    Close

     

    Entry point

    • The SUBOROINT entry points are used to add specific processings before or after having been triggered.
    • The PITMFG entry points have an impact on the selected elements.

    Batch task

    This function can be run in batch mode. The standard task OROINT is provided for that purpose.

    Error messages

    The only error messages are the generic ones.

    Tables used

    SEEREFERTTO Refer to documentation Implementation