Show TOC

Background documentationCustomizing for ALE for Communication with SAP OEE

Prerequisites

  • You have created a plant in SAP ERP.

  • You have configured SAP MII Message Listener.

  • You have authorizations included in the following single roles in SAP ERP to maintain ALE settings:

    • SAP_IDOC_IMPLEMENTATION

    • SAP_WPS_ADMIN with additional object B_ALE_LSYS

    • SAP_AUDITOR_SA_BC

Activities

Maintaining a Logical System

  1. In Customizing for Logistics - General, choose Start of the navigation path Supply Chain Planning Interfaces (SCPI) Next navigation step Production Optimization Interface (POI) Next navigation step ALE settings for POI Next navigation step Maintain logical system End of the navigation path.

  2. On the Change View “Logical Systems”: Overview screen, choose New Entries.

  3. Enter the following data:

    Field

    Description

    User Action and Values

    Comments

    Log.System

    System in which applications run integrated on a shared data basis

    Enter the name of the RFC destination previously created

    Limit name to CHAR 10 to facilitate naming conventions of related objects

    Name

    Short meaningful description of the logical system

    Enter a short meaningful description

  4. Save your entries.

Defining RFC Destination

  1. In Customizing for Logistics - General, choose Start of the navigation path Supply Chain Planning Interfaces (SCPI) Next navigation step Production Optimization Interface (POI) Next navigation step ALE settings for POI Next navigation step Define RFC Destination End of the navigation path.

  2. On the Configuration of RFC Connections screen, select the TCP/IP connections node and choose the Create icon.

  3. On the RFC Destination screen, enter the following data:

    Field

    Description

    User Action and Values

    Comments

    RFC Destination

    Standard name of an RFC destination

    Enter a meaningful name that identifies both the SAP MII Message Listener and SAP ERP

    You will enter the RFC destination name several times. We recommend that you keep it simple and memorable.

    We also recommend that the RFC Destination, Program ID, and SAP MII Message Listener have the same name. The name must be all uppercase as some fields are case sensitive. This will ensure consistency throughout the process.

    Connection Type

    Type of RFC connection

    Enter T

    Type T destinations are connections to external programs that use the RFC API to receive Remote Function Calls.

    Description 1

    Short description of the RFC destination

    Enter a short meaningful description (Optional)

  4. Press Enter.

  5. On the Technical Settings tab page on the RFC Destination screen, enter the following data:

    Field

    Description

    User Action and Values

    Comments

    Activation Type

    Radio buttons

    Choose Registered Server Program

    Using the registering feature of the SAP gateway, RFC server programs can be started before; register at this SAP gateway and then wait for RFC call requests.

    Start on Application Server

    Program

    Identification of a registered RFC server program

    Enter the same name as the RFC Destination

    We recommend that you use both the name of the RFC server program and the host name of the RFC server program.

    The Program ID you enter here corresponds to the Message Listener in SAP MII and must therefore have the same name.

    Gateway Options

    Gateway Host

    Gateway host name

    Enter the SAP system application server

    You can find out the name of the gateway service by logging on the application server you defined above and starting the transaction SMGW. The name of the gateway server can be looked up in the menu Start of the navigation path Goto Next navigation step Parameters Next navigation step Display End of the navigation path

    Gateway Service

    Gateway service

    Enter sapgw<SAP system number>

    You can find out the name of the gateway service by logging on the application server you defined above and starting the transaction SMGW. The name of the gateway server can be looked up in the menuStart of the navigation path Goto Next navigation step Parameters Next navigation step Display End of the navigation path

  6. Save your entries.

  7. Ensure that the communication type is unicode.

  8. (Optional) If you configured SAP MII IDoc Listener, test the RFC connection.

Defining a Logical Port

  1. In Customizing for Logistics - General, choose Start of the navigation path Supply Chain Planning Interfaces (SCPI) Next navigation step Production Optimization Interface (POI) Next navigation step ALE settings for POI Next navigation step Define port End of the navigation path.

  2. On the Ports in IDoc processing screen, select the Transactional RFC node and choose the Create icon.

  3. In the Ports in IDoc processing dialog, select the own port name and enter a descriptive port name. We recommend that you use the same name as that of the RFC connection previously created.

  4. Choose the Enter icon.

  5. On the Ports in IDoc processing screen, enter the following data:

    Field

    Description

    User Action and Values

    Description

    Short description of the port

    Enter a short meaningful description

    Version

    Enables system select appropriate control record

    Select IDoc record types SAP Release 4.x

    RFC destination

    Standard name of an RFC destination

    Enter the name of the RFC destination previously created

  6. Save your entries.

Maintaining a Partner Profile

  1. In Customizing for Logistics - General, choose Start of the navigation path Supply Chain Planning Interfaces (SCPI) Next navigation step Production Optimization Interface (POI) Next navigation step ALE settings for POI Next navigation step Maintain partner profile End of the navigation path.

  2. On the Partner profiles screen, create a new profile for Partner Type LS.

  3. Enter the following data:

    Field

    Description

    User Action and Values

    Comments

    Partner no.

    Uniquely identifies a vendor, customer, or a logical system

    Enter the logical system previously created

    Ty.

    Classifies the recipient of error notifications

    Enter C (Job)

    Agent

    Specifies the job (person or group of people) to be notified if processing errors occur

    Use matchcode search to select the job number responsible for error handling

    Job key is internally generated when creating agents

  4. Save your entries.

  5. Under the Outbound Parameters table, choose the Create Outbound Parameter icon.

  6. On the Partner profiles: Outbound parameters screen, enter the following data for each message type:

    Field

    Description

    User Action and Values

    Comments

    Message Type

    Uniquely assigned to SAP ERP document types

    Enter the following:

    MATMAS

    LOIPRO

    LOIWCS

    LOICAL

    /OEE/CONF_CLASSIFICATION

    /OEE/CONF_CLASSIFICATION_RECO

    /OEE/CONF_DCELEM

    /OEE/CONF_DCELEM_RECO

    /OEE/CONF_DCE_CTX

    /OEE/CONF_DCE_CTX_RECO

    /OEE/CONF_KPI

    /OEE/CONF_KPI_RECO

    /OEE/CONF_MCGRP

    /OEE/CONF_MCGRP_RECO

    /OEE/CONF_PRDACT

    /OEE/CONF_PRDACT_RECO

    /OEE/CONF_PRODMODE

    /OEE/CONF_PRODMODE_RECO

    /OEE/CONF_RC

    /OEE/CONF_RC_RECO

    /OEE/CONF_SHIFT

    /OEE/CONF_TIMEELEM

    /OEE/CONF_TIMEELEM_RECO

    /OEE/CONF_TIMEEL_TP

    /OEE/CONF_TIMEEL_TP_RECO

    /OEE/PLANT_HIERARCHY

    /OEE/PLANT_HIERARCHY_REC

    /OEE/STDVALKEY_FORMULAPARAM

    /OEE/STDVALKEY_PARAM_RECO

    SYNCH

    T006_A

    Receiver port

    Specifies how the IDocs are transferred to the EDI subsystem

    Enter the logical system previously created

    Output Mode

    Output is started immediately for each individual IDoc

    The external subsystem is not started from SAP ERP. It must become active itself in order to fetch the data.

    Select Transfer IDoc Immed. and Do not start subsystem

    IDoc Type

    Basic type

    Can be used without additional coding for data communication

    Enter the following:

    MATMAS05

    LOIPRO01

    LOICAL01

    LOIWCS02

    LOIWCS03

    /OEE/CLASSIFICATION01

    /OEE/CLASSIFICATION02

    /OEE/DCELEM01

    /OEE/DCELEM02

    /OEE/DCECTX01

    /OEE/DCECTX02

    /OEE/KPI01

    /OEE/KPI02

    /OEE/MCGRP01

    /OEE/MCGRP02

    /OEE/PRDACTIVITY01

    /OEE/PRDACTIVITY02

    /OEE/PRODMODE01

    /OEE/PRODMODE02

    /OEE/RC01

    /OEE/RC02

    /OEE/SHIFT01

    /OEE/STDVALKEY_FORMULAPARAM01

    /OEE/STDVALKEY_FORMULAPARAM02

    /OEE/TIMEELEM01

    /OEE/TIMEELEM02

    /OEE/TIMEELTP01

    /OEE/TIMEELTP02

    /OEE/PLANT01

    /OEE/PLANT02

    SYNCHRON

    T006_01

    Each basic type corresponds to the list of message types above.

    Note Note

    Enter the message code

    OEE for LOIPRO01 if you want to distribute the individual capacity requirements defined in the order.

    End of the note.

    Use IDoc Type LOIWCS03 if you want to collect data for production activities like set up, processing, and tear-down.

    Cancel Processing After Syntax Error

    If selected, the IDoc Interface terminates the processing in the event that a syntax error is found

    Select the checkbox

  7. Save your entries.

  8. Repeat steps 5–7 for each listed basic type.

Maintaining a Customer Distribution Model

  1. In Customizing for Logistics - General, choose Start of the navigation path Supply Chain Planning Interfaces (SCPI) Next navigation step Production Optimization Interface (POI) Next navigation step ALE settings for POI Next navigation step Maintain customer distribution model directly End of the navigation path

  2. On the Change Distribution Model screen, choose Create model view.

  3. On the Create Model View screen, enter the following data:

    Field

    Description

    User Action and Values

    Comments

    Short text

    Short description of view of distribution model

    Enter a short meaningful description

    Technical name

    View of ALE model

    Enter a technical name

    Start date

    Identifies the start of a validity period

    Enter the start date of the validity period

    End Date

    Identifies the end of the validity period

    Enter the end date of the validity period

  4. Choose the Enter icon.

  5. On the Change Distribution Model screen, select the distribution model previously created and choose Add message type.

  6. On the Add Message Type screen, enter the following data:

    Field

    Description

    User Action and Values

    Comments

    Model view

    View of distribution model

    Enter the name of the previously created distribution model

    Sender

    Name of the logical source system for exchanging messages

    Enter the name of the system sending the IDocs

    This is usually the logical system name for the SAP client.

    Receiver

    Name of the logical target system for exchanging messages

    Enter the name of the logical system previously created

    Message Type

    Identifies different IDoc types

    Enter the message type:

    MATMAS

    LOICAL

    LOIWCS

    LOIPRO

    Each message type is added separately following the same steps.

  7. Choose the Enter icon.

  8. Repeat steps 5–7 to add each message type to the distribution model as listed above.

  9. Save your entries.