Show TOC

Background documentationConfiguration of Standard SAPMEINT Interfaces Locate this document in the navigation structure

 

The following documentation describes how to make corrections and modifications to the Standard SAPMEINT interfaces manually.

The Standard SAPMEINT interfaces are installed and configured using the SAPMEINTCTC configuration wizard. For more information, see SAP ME 6.0 Installation Guide available at   http://service.sap.com/instguides   SAP Business Suite Applications   SAP Manufacturing   SAP Manufacturing Execution 6.0  .

Deploying JDBC Driver

For information on deploying the JDBC driver, see SAP ME 6.0 Installation Guide.

Configuring Datasources in SAP NetWeaver Java AS

SAPMEINTCTC creates two datasources, SAPMEINT and SAPMEWIP. These datasources are used by the SAPMEINT interfaces.

Datasource

Datasource Alias

Description

SAPMEINT

jts/SAPMEINT

Used to do CRUD operations on SAPMEINT database

SAPMEWIP

jts/SAPMEWIP

Used to read data from SAP ME WIP database

To modify the datasource configurations, proceed as follows:

  1. Log on to SAP NetWeaver Administrator using the following URL: http://<host>:<port>/nwa.

  2. Choose   Configuration Management   Infrastructure   Application Resources  .

  3. Search for SAPMEINT or SAPMEWIP as the Resource Name.

  4. Select the desired datasource and make the necessary modifications on the following datasource properties:

A datasource for the MS SQL Server database is configured as follows:

Parameters

Field

Example Value

Driver Name

SAPMEINT_SQL

SQL Engine

Vendor SQL

Isolation level

Default

JDBC Version

2.0 (with XA support)

Object Factory

DataSource Type

ConnectionPool DataSource

CPDS Class Name

com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource
Connection Pooling Parameters

Field

Example Value

Initial Connections

10

Maximum Connections

25

Maximum Time to Wait for Connection

120
Additional Parameters

Field

Example Value

URL

Default instance:

jdbc:sqlserver://PROTEUS:1433

Name instance:

jdbc:sqlserver://PROTEUS\SAPME:1433

Password

******

User

qa_nwsapme52wip

databaseName

SAPMEWIP

serverName

PROTEUS

A datasource for the Oracle database is configured as follows:

Parameters

Field

Example Value

Driver Name

SAPMEINT_ORA_10_2

SQL Engine

Vendor SQL

Isolation Level

Default

JDBC Version

2.0 (with XA support)

Object Factory

DataSource Type

ConnectionPool DataSource

CPDS Class Name

oracle.jdbc.pool.OracleConnectionPoolDataSource
Connection Pooling Parameters

Field

Example Value

Initial Connections

10

Maximum Connections

25

Maximum Time to Wait for Connection

120
Additional Parameters

Field

Example Value

URL

jdbc:oracle:thin:@ PROTEUS:1527: SAPME

Password

******

User

qa_nwsapme52wip

After creating the datasources, make sure that the SAPMEWIP and SAPMEINT datasources are running and in a Fully Available state.

For more information about configuring datasources, see Application Resources Management in SAP Library for SAP NetWeaver.

Configuring SAPMEWIP Data Server in SAP MII

  1. In the SAP MII main menu, choose   Data Services   Data Servers  .

  2. Select Datasource and choose SAPMEWIP.

  3. Make the desired modifications:

    Field

    Value

    Name

    SAPMEWIP

    Connector

    Datasource

    ConnectorType

    SQL

    Datasource

    jdbc/jts/SAPMEWIP

    Enabled

    Selected

    DatePrefix

    '

    DateSuffix

    '

    DaysRetention

    7

    Description

    SAPMEWIP

    InternalDateFormat

    MM/dd/yyyy HH:mm:ss

    MaxRetryCount

    5

    RetryInterval

    60000

    Server Package

    com.sap.xmii.Illuminator.connectors.IDBC

    Note Note

    If the database is Oracle, use the following parameter values:

    DatePrefix: TO_DATE('

    DateSuffix: ','MM/DD/YYYY HH24:MI:SS')

    End of the note.

  4. Save your entries.

  5. Choose Status to verify connectivity to the SAPMEWIP.

    The status must be Running.

Configuring SAPMEINT Data Server in SAP MII

Note Note

You can use one database to store both SAP ME and SAPMEINT data if needed. For more information, see SAP Note 1409811Information published on SAP site — SAP ME System Landscape Recommendations.

End of the note.

  1. On the SAP MII main menu, choose   Data Services   Data Servers   .

  2. Select Datasource and choose SAPMEINT.

  3. Make the desired modifications:

    Field

    Value

    Name

    SAPMEINT

    Connector

    Datasource

    ConnectorType

    SQL

    Datasource

    jdbc/jts/SAPMEINT

    Enabled

    Selected

    DatePrefix

    '

    DateSuffix

    '

    DaysRetention

    7

    Description

    SAPMEINT

    InitCommand

    InternalDateFormat

    MM-dd-yyyy HH:mm:ss

    MaxRetryCount

    5

    RetryInterval

    60000

    Server Package

    com.sap.xmii.Illuminator.connectors.IDBC

    Note Note

    If the database is Oracle, use the following parameter values:

    DatePrefix: TO_DATE('

    DateSuffix: ','MM/DD/YYYY HH24:MI:SS')

    End of the note.

  4. Save your entries.

  5. Choose Status to verify connectivity to the SAPMEINT.

    The status must be Running.

Configuring MESYS User in SAP NetWeaver

SAPMEINTCTC creates the MESYS user in SAP NetWeaver where SAPMEINT and SAP ME are deployed. In the case of a single server environment where SAP ME and SAP MII are deployed on the same server, the MESYS user is created only on this server. If SAPMEINT and SAP ME are deployed on separate servers, SAPMEINTCTC creates the MESYS user on both servers.

This user is used for any SAP ME Web Service calls. For more information about configuring a user in SAP NetWeaver, see Identity Management.

Configuring Credentials in SAP MII
Credential for SAP ME Web Service Calls

SAPMEINTCTC creates the credential SAPMEINT_ME_AUTH in SAP MII. To modify the password for the credential, proceed as follows:

  1. On the SAP MII main menu, choose   Security Services   Credential Editor  .

  2. Choose the credential SAPMEINT_ME_AUTH.

  3. Enter a new password for the MESYS NetWeaver user.

  4. Confirm the password.

  5. Save your entries.

Note Note

Make sure that the password for the MESYS user is also modified in SAP NetWeaver server where SAP ME is deployed.

End of the note.

Recommendation Recommendation

We recommend that you do not change the user name (MESYS) for this credential.

End of the recommendation.
Credential for BAPI Calls to SAP ERP

SAPMEINTCTC creates the credential SAPMEINT_ALE in SAP MII. To modify this credential, proceed as follows:

  1. On the SAP MII main menu, choose   Security Services   Credential Editor  .

  2. Choose the credential SAPMEINT_ALE.

  3. Enter the desired user name.

  4. Enter a new password for the user.

  5. Confirm the password.

  6. Save your entries.

Configuring Role_SAPMEINT Role in SAP NetWeaver

SAPMEINTCTC creates the role Role_SAPMEINT in SAP NetWeaver where SAP MII and SAPMEINT are deployed and running.

For more information about configuring roles, see Administration of Users and Roles.

Configuring SAP ERP ALE

You need to configure SAP ERP to send IDocs to the SAP MII server. This involves the following procedures:

  1. Creating a logical system for the SAP MII server within SAP ERP

  2. Creating a TCP/IP RFC destination to the SAP MII server

  3. Testing the connectivity of the RFC destination to the SAP MII server

  4. Creating a port

  5. Creating a partner profile configured for the following IDoc types:

    • MATMAS03

    • CLFMAS02

    • BOMMAT03

    • LOIROU02 (LOIROU03 for ERP configuration type C; see SAPMEINT: SAP ERP Configuration)

    • LOIPRO01 (LOIPRO02 for ERP configuration type C)

    • LOIPLO01

    • INVCON02

    • IORDER01

    • HRMD_A06

    • LOIWCS02

  6. Creating a distribution model

For more information, see Customizing for ALE for Communication with SAP ME.

Configuring Message Listener

SAPMEINTCTC creates the message (IDoc) listener in SAP NetWeaver to receive notifications of IDocs from SAP ERP server and download the IDoc. To make modifications to the Message Listener configuration, proceed as follows:

  1. Log on to SAP NetWeaver Administrator using the following URL: http://<host>:<port>/nwa.

  2. Choose   Configuration Management   Infrastructure   Application Resources  .

  3. Select Resource Adapters from the dropdown list.

  4. Select the resource configured by SAPMEINTCTC, such as XMIIIDOC01, that you want to modify in the table.

  5. Choose Properties tab in the bottom window.

  6. Edit the properties to match your SAP ERP server.

  7. Save your entries.

Example Example

Field

Example Value

ProgramID

XMII_RHEA

MaxReaderThreadCount

1

SAPClient

210

UserName

ALE_USER — a valid SAP ERP user to perform ALE communication

Password

******

Language

EN

ServerName

sapdev.sap.com

PortNumber

03

BindingKey

XMIIIDOC — use the default value

For more information, see Customizing for ALE for Communication with SAP ME.

End of the example.

After configuring the resource, make sure that this configuration works by doing the following:

  1. Check that the resource is in a running and Fully Available state.

  2. In the SAP MII menu, expand Message Services and choose Message Listener.

  3. Select the message listener configured by SAPMEINTCTC, such as XMIIIDOC01and choose Update.

  4. Choose Status.

    The following message appears: Server Connected.

Configuring Processing Rules

SAPMEINTCTC creates the processing rules in SAP MII Message Services. Processing rules specify how incoming IDocs are processed by SAP MII based on message type. SAPMEINTCTC creates the following rules:

  • <Name of the IDoc Listener>_MATMAS

    Message type for material

  • <Name of the IDoc Listener>_BOMMAT

    Message type for BOM

  • <Name of the IDoc Listener>_LOIROU

    Message type for routing

  • <Name of the IDoc Listener>_LOIPRO

    Message type for production order

  • <Name of the IDoc Listener>_LOIPLO

    Message type for planned order

  • <Name of the IDoc Listener>_INVCON

    Message type for floor stock receipt

  • <Name of the IDoc Listener>_IORDER

    Message type for planned maintenance order or service order

  • <Name of the IDoc Listener>_CLFMAS

    Message type for material classification

  • <Name of the IDoc Listener>_HRMD_A

    Message type for user

  • <Name of the IDoc Listener>_LOIWCS

    Message type for resource or work center

To modify the configurations for these processing rules, proceed as follows:

  1. In the SAP MII main menu, expand Message Services and choose Processing Rule Editor.

  2. Select the processing rule that you want to modify.

  3. Make the desired modifications.

  4. Save your entries.

Note Note

For optimal performance, use the following Message Processing Rules parameter values for all message types:

Persist Transaction: ONERROR

Log Level: ERROR

End of the note.
Configuring <Name of the IDoc Listener>_MATMAS Processing Rule

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Rule Name

<Name of the IDoc Listener>_MATMAS

Description

<Name of the IDoc Listener>_MATMAS

Server Name

Name of the IDoc Listener

Message Name

MATMAS

Message Type

IDoc

Processing Rule

Transaction

Transaction

Visiprise/ERPShopFloorIntegration/services/SyncDOCService

Transaction Parameters

DOC

Enter ReceivedMessageXML in the Value column for this parameter. You can select the checkbox next to the document parameter to insert.
Configuring <Name of the IDoc Listener>_BOMMAT Processing Rule

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Rule Name

<Name of the IDoc Listener>_BOMMAT

Description

<Name of the IDoc Listener>_BOMMAT

Server Name

Name of the IDoc Listener

Message Name

BOMMAT

Message Type

IDoc

Processing Rule

Transaction

Transaction

Visiprise/ERPShopFloorIntegration/services/SyncDOCService

Transaction Parameters

DOC

Enter ReceivedMessageXML in the Value column for this parameter. You can select the checkbox next to the document parameter to insert.
Configuring <Name of the IDoc Listener>_LOIROU Processing Rule

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Rule Name

<Name of the IDoc Listener>_LOIROU

Description

<Name of the IDoc Listener>_LOIROU

Server Name

Name of the IDoc Listener

Message Name

LOIROU

Message Type

IDoc

Processing Rule

Transaction

Transaction

Visiprise/ERPShopFloorIntegration/services/SyncDOCService

Transaction Parameters

DOC

Enter ReceivedMessageXML in the Value column for this parameter. You can select the checkbox next to the document parameter to insert.
Configuring <Name of the IDoc Listener>_LOIPRO Processing Rule

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Rule Name

<Name of the IDoc Listener>_LOIPRO

Description

<Name of the IDoc Listener>_LOIPRO

Server Name

Name of the IDoc Listener

Message Name

LOIPRO

Message Type

IDoc

Processing Rule

Transaction

Transaction

Visiprise/ERPShopFloorIntegration/services/SyncDOCService

Transaction Parameters

DOC

Enter ReceivedMessageXML in the Value column for this parameter. You can select the checkbox next to the document parameter to insert.
Configuring <Name of the IDoc Listener>_LOIPLO Processing Rule

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Rule Name

<Name of the IDoc Listener>_LOIPLO

Description

<Name of the IDoc Listener>_LOIPLO

Server Name

Name of the IDoc Listener

Message Name

LOIPLO

Message Type

IDoc

Processing Rule

Transaction

Transaction

Visiprise/ERPShopFloorIntegration/services/SyncDOCService

Transaction Parameters

DOC

Enter ReceivedMessageXML in the Value column for this parameter. You can select the checkbox next to the document parameter to insert.
Configuring <Name of the IDoc Listener>_INVCON Processing Rule

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Rule Name

<Name of the IDoc Listener>_INVCON

Description

<Name of the IDoc Listener>_INVCON

Server Name

Name of the IDoc Listener

Message Name

INVCON

Message Type

IDoc

Processing Rule

Transaction

Transaction

Visiprise/ERPShopFloorIntegration/services/SyncDOCService

Transaction Parameters

DOC

Enter ReceivedMessageXML in the Value column for this parameter. You can select the checkbox next to the document parameter to insert.
Configuring <Name of the IDoc Listener>_IORDER Processing Rule

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Rule Name

<Name of the IDoc Listener>_IORDER

Description

<Name of the IDoc Listener>_IORDER

Server Name

Name of the IDoc Listener

Message Name

IORDER

Message Type

IDoc

Processing Rule

Transaction

Transaction

Visiprise/ERPShopFloorIntegration/services/SyncDOCService

Transaction Parameters

DOC

Enter ReceivedMessageXML in the Value column for this parameter. You can select the checkbox next to the document parameter to insert.
Configuring <Name of the IDoc Listener>_CLFMAS Processing Rule

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Rule Name

<Name of the IDoc Listener>_CLFMAS

Description

<Name of the IDoc Listener>_CLFMAS

Server Name

Name of the IDoc Listener

Message Name

CLFMAS

Message Type

IDoc

Processing Rule

Transaction

Transaction

Visiprise/ERPShopFloorIntegration/services/SyncDOCService

Transaction Parameters

DOC

Enter ReceivedMessageXML in the Value column for this parameter. You can select the checkbox next to the document parameter to insert.
Configuring <Name of the IDoc Listener>_HRMD_A Processing Rule

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Rule Name

<Name of the IDoc Listener>_HRMD_A

Description

<Name of the IDoc Listener>_HRMD_A

Server Name

Name of the IDoc Listener

Message Name

HRMD_A

Message Type

IDoc

Processing Rule

Transaction

Transaction

Visiprise/ERPShopFloorIntegration/services/SyncDOCService

Transaction Parameters

DOC

Enter ReceivedMessageXML in the Value column for this parameter. You can select the checkbox next to the document parameter to insert.
Configuring <Name of the IDoc Listener>_LOIWCS Processing Rule

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Rule Name

<Name of the IDoc Listener>_LOIWCS

Description

<Name of the IDoc Listener>_LOIWCS

Server Name

Name of the IDoc Listener

Message Name

LOIWCS

Message Type

IDoc

Processing Rule

Transaction

Transaction

Visiprise/ERPShopFloorIntegration/services/SyncDOCService

Transaction Parameters

DOC

Enter ReceivedMessageXML in the Value column for this parameter. You can select the checkbox next to the document parameter to insert.
Configuring the SAP ERP Server Connection

SAPMEINTCTC configures the SAP ERP server connection in SAP MII to make BAPI calls to SAP ERP. SAPMEINTCTC creates the SAP ERP server connection with the following naming convention <Name of the IDoc Listener>_SAP_JCO, where <Name of the IDoc Listener> is the IDoc Listener configured by SAPMEINTCTC. To modify the configuration, proceed as follows:

  1. On the SAP MII main menu, expand Data Services and choose System Connection Editor.

  2. Choose Connect Type JCO.

  3. Choose New.

  4. Select the desired SAP ERP server.

    You can modify the following properties:

    Field

    Value

    Name

    <Name of the IDoc Listener>_SAP_JCO

    Server

    <Your SAP ERP server host name>

    Client

    <Your SAP ERP client for production>

    System

    <Your SAP ERP system number>

    Pool Size

    <Pool size for your JCo resource>

    Language

    EN

  5. Save your entries.

Configuring SAPMEINT MII Web Services in SAP NetWeaver Java AS

SAPMEINTCTC configures the SAP NetWeaver system properties for the SAP MII transactions Web services to work. To modify this configuration, proceed as follows:

  1. Log on to SAP NetWeaver Administrator console using the following URL: http://<host>:<port>/nwa.

  2. Choose   Configuration Management   Infrastructure   Java System Properties   Applications  .

  3. On the Applications tab page, search for the xapps~me~integration~ear application.

    You can edit the following properties:

    Name

    Custom Value

    webservice.authenticationMechanismType

    SAPMEINTCTC configuration defaults this value to 1 and this value should not be modified.

    webservice.UserName

    <SAP NetWeaver User who has the Role_SAPMEINT role assigned to access SAP MII transactions and Web services>

    SAPMEINTCTC configuration defaults this value to the user MESYS.

    webservice.Password

    <User password>

    webservice.EndPointUrlPrefix

    The default value:

    http://localhost:50000/XMII/SOAPRunner

    SAPMEINTCTC configures this value using the server name and port of the SAP MII server.

  4. Save your entries.

Configuring SAPMEINT GUI Applications to Role_SAPMEINT Role

SAPMEINTCTC configures navigation links for SAPMEINT GUI applications in SAP MII. To verify this configuration, proceed as follows:

  1. On the SAP MII main menu, choose   Navigation Services   Navigation  .

  2. Make sure Role is selected in the Select Role or User dropdown list.

  3. Select Role_SAPMEINT in the Account Name dropdown list.

    The navigation items appear in the navigation tree for this role.

Configuring SAPMEINT Workflow

To configure SAPMEINT workflow, you need to log on as the user with the Role_SAPMEINT role assigned.

SAPMEINT Global Configuration

SAPMEINTCTC configures SAPMEINT Global Configuration properties with the values provided during the SAPMEINTCTC configuration process. To modify this configuration, proceed as follows:

  1. In the SAP MII Dashboard menu, choose   SAP ME ERP Integration   Administration   Global Configuration  .

    You can modify the following global configuration properties:

    Property

    Description

    Example Value

    SAPMEINT_ME_Application_Context

    The Web context root for SAP ME application

    /manufacturing

    SAPMEINT_ME_Host

    Host name of SAP ME server

    vmserv1, vmserv.acme.com

    SAPMEINT_ME_Port

    Server port on which SAP ME listens for all HTTP requests

    50000

    SAPMEINT_ME_User

    SAP ME user

    MESYS

    SAPMEINT_DB_Vendor

    Database vendor for the SAPMEINT data source

    ORACLE, SQLSERVER

    SAPMEINT_OEE_Max_Buckets

    The number of times to display the buckets in the OEE Report

    12

    SAPMEINT_RETRY_RETENTION_PERIOD

    Defines the retention period in minutes for a message to be retried after a system error

    30

    SAPMEINT_CORRELATION_RETENTION_PERIOD

    Defines the retention period in minutes for a message when a message is waiting for more documents to arrive and be correlated

    10

    SAPMEINT_CustomerMessageDiscriminatorTxn

    See Note below

    SAPMEINTCTC defaults this parameter to an empty value.

    SAPMEINT_PartnerMessageDiscriminatorTxn

    See Note below

    SAPMEINTCTC defaults this parameter to an empty value.

    Note Note

    The Message Discriminator transaction is responsible for building a valid identifier typeId (DOC_TYPE) for each incoming message to SAPMEINT. SAPMEINT uses this typeId to determine the workflow associated with this message.

    Prior to SAPMEINT 5.2 SP05, customers had to configure their discriminator transaction via the same global configuration parameter since there was no specific global configuration parameter for partner or customer exit points. Therefore, when migration happens, the customized partner or customer transaction were replaced by the standard discriminator transaction and the custom configuration was lost. To correct this, partner and customer exit points were added where customers can plug in their custom discriminator transaction. These transactions will not be overwritten by the base configuration.

    SAPMEINT comes with pre-built standard discrimination logic to determine the typeId of a message.

    If you want to customize this logic, you can configure your discrimination logic using the following Global Configuration properties:

    • SAPMEINT_CustomerMessageDiscriminatorTxn

    • SAPMEINT_PartnerMessageDiscriminatorTxn

    The SAPMEINT system checks if SAPMEINT_CustomerMessageDiscriminatorTxn has been configured. If it has been configured, the system executes the transaction. Otherwise the system executes the transaction defined in SAPMEINT_PartnerMessageDiscriminatorTxn if it has been configured.

    If the value for the output parameter ”type” of these transactions is not empty, SAPMEINT uses this value as the typeId for the message. If the value returned from these transactions is empty, the standard SAPMEINT discrimination logic executes and attempts to find the typeId of the message.

    End of the note.

  2. Save your entries.

Workflow Parameters

SAPMEINTCTC configures SAPMEINT workflows with default values. These default values work for most of the scenarios. If any of the workflow parameters need to be changed, proceed as follows:

  1. In the SAP MII Dashboard menu, choose   SAP ME ERP Integration   Administration   SAPMEINT Workflow Configuration  .

  2. Retrieve the workflow parameter for the desired interface by choosing the Type ID.

  3. Make the necessary modifications.

  4. Save your entries.

Configuring the SAP MII Schedulers

SAPMEINTCTC configures the SAP MII Schedulers to process queued messages in SAPMEINT. To modify this configuration, proceed as follows:

  1. In the SAP MII main menu, choose   System Management   Schedule Editor  .

  2. Select the desired scheduler.

  3. Modify the desired properties

    Note Note

    For optimal performance, use the following Message Processing Rules parameter values for all message types:

    Persist Transaction: ONERROR

    Log Level: ERROR

    End of the note.
    MessageDispatcher Properties

    Field

    Value

    Name

    MessageDispatcher

    Description

    Dispatcher for queued SAPMEINT messages

    Enabled

    Selected

    Transaction

    Visiprise/ERPShopFloorIntegration/frame/dispatchers/simpleDispatcher/SimpleMessageDispatcher

    User

    A valid SAP MII user who has permission to run the Scheduler

    Password

    The password for the SAP MII user

    Parameters

    numberOfMessagaes

    The number of queued messages to be processed for this scheduler task run. SAPMEINTCTC defaults this parameter with a value of 50.

    Pattern

    Your pattern
    MessageEnqueuer Properties

    Field

    Value

    Name

    MessageEnqueuer

    Description

    Dispatcher to enqueue SAP ME outbound messages from the Outbound ME Messages queue into the Integration Message Queue for processing by the Message Dispatcher scheduler job

    Enabled

    Selected

    Transaction

    Visiprise/ERPShopFloorIntegration/SAPMEMessageEnqueuer/SAPMEMessageEnqueuingDispatcher

    User

    A valid SAP MII user who has permission to run the Scheduler

    Password

    The password for the SAP MII user

    Parameters

    deleteAfterQueuing

    Controls if the queued message is deleted after being processed. SAPMEINTCTC defaults this parameter with a value of true

    numberOfMessagaes

    The number of queued messages to be processed for this scheduler task run. SAPMEINTCTC defaults this parameter with a value of 200.

    Pattern

    Your pattern
    QueueMessageCleaner Properties

    Field

    Value

    Name

    QueueMessageCleaner

    Description

    Dispatcher to delete the old SAPMEINT messages

    Enabled

    Selected

    Transaction

    Visiprise/ERPShopFloorIntegration/MessagePurging/MessageCleaner

    User

    A valid SAP MII user who has permission to run the Scheduler

    Password

    The password for the SAP MII user

    Parameters

    messageRetentionPeriod

    The number of hours the messages will be kept in the system after they are received into SAPMEINT. SAPMEINTCTC defaults this parameter with a value of 24.

    Pattern

    Your pattern

  4. Save your entries.

Configuring SAP ME

See SAP ME Configuration for SAP ME ERP Integration.

Configuring Supported SAP ME Plants

SAPMEINTCTC configures supported SAP ME sites that correspond to SAP ERP plants during the SAPMEINTCTC execution. To modify this configuration, proceed as follows:

  1. On the SAP MII Dashboard menu, choose   SAP ME ERP Integration   Administration   Supported SAP ME Plants  .

  2. On the Supported SAP ME Plants screen, choose the SAP ME site (plant) to modify.

    You can modify the following properties:

    Field

    Example Value

    Plant Language

    E – This value should match the language field in the IDocs.

    Note Note

    The language field for MATMAS and LOIWCS can be found in SPRAS and the language field for DOCMAS can be found in LANGU.

    End of the note.

    SAP ERP Server

    <Name of the IDoc Listener>_SAP_JCO

    SAP ME Host URL

    http://<host>:<port>

    SAP ERP Server TimeZone

    US/Eastern

    SAP ME Server TimeZone

    US/Eastern
Configuring SAP ME Web Services

SAPMEINTCTC configures SAP ME web services during the SAPMEINTCTC execution. To modify these configurations, proceed as follows:

  1. Log on to SAP NetWeaver Administrator Console using the following URL: http://<AS Java hos namet>:<port number>/nwa.

  2. Choose   SOA Management   Application and Scenario Communication   Single Service Administration  .

  3. Search for the following web services:

    • AlarmProcessingIn

    • ERPBOMProcessingIn

    • ErpItemProcessingIn

    • NextNumberProcessingIn

    • OperationProcessingIn

    • ErpProductionProcessingIn

    • ErpRouterProcessingIn

    • ProductionProcessingIn

    • ProductionOrderProcessingIn

    • ERPShoporderProcessingIn

    • ItemCustomData

    • ERPUserProcessingIn

    • ServiceOrderProcessingIn

    • ResourceProcessingIn

    • WorkCenterProcessingIn

  4. Select each port type, for example AlarmProcessingIn.

  5. In the bottom window, select associated ServicePort, for example ProductionAlarmServicePort.

  6. Choose the Security tab.

  7. Choose Edit.

  8. Select the Transport protocol.

  9. Check the UserID/Password under HTTP Authentication.

  10. Save your entries.

  11. Repeat the steps above for each port.

Clearing SAP MII Transaction Cache

As a final step after the configuration of SAPMEINT, clear the transaction cache by executing the following URL:

http://<host>:<port>/XMII/Illuminator?Service=BLSManager&Mode=ClearCache&Type=Transaction