Show TOC

Background documentationSAP NetWeaver Instance for SAP MII

 

On this screen, you provide information used to configure the SAP NetWeaver instance where SAP MII and SAPMEINT are deployed.

Fields

The following table describes fields requiring explanation:

Field

Description

Protocol

Choose the transport protocol to be used for message communication by SAPMEINT. Currently, only the HTTP protocol is supported by SAPMEINT.

Usage in Configuration

  • SAP ME

    The Transport URLs for the following SAP ME Outbound Collaboration directives are configured with the protocol specified in this screen:

    • ERP_SCRAP_BACKFLUSHING

    • ERP_SCRAP_CONFIRMATION

    • ERP_YIELD_BACKFLUSHING

    • ERP_YIELD_CONFIRMATION

    • ERP_CONTAINER_CLOSED_CONFIRMATION

    • ERP_CONTAINER_CLOSED_BACKFLUSHING

    • ERP_INV_CLEAR_RESERVATION

    • ERP_EQUIPMENT_STATUS_CHANGE

    • ERP_EQUIPMENT_USAGE

    • ERP_SO_COMPLETE

    • ERP_QUALITY_NOTIFICATION

    • ERP_STORAGE_LOC_MOVE

    • ERP_DIRECT_LABOR_CONFIRMATION

    To review this configuration, log on to SAP ME and verify in Collaboration Directive Maintenance (see Collaboration Directive Maintenance).

    To view the service extension points and their activity description details for a quality inspection lot, log on to SAP ME and verify by entering the following on the Service Extension Maintenance screen:

    • DataCollectionService in the Service field

    • LogSfcDcGroups in the Method field

  • SAPMEINT

    SAP ME Host URL in Supported SAP ME Plants is configured with the specified protocol. You can verify this configuration in Supported SAP ME Plants by choosing Start of the navigation path SAP ME ERP Integration Next navigation step SAPMEINT Configuration Next navigation step Supported SAP ME Plants End of the navigation path in SAP MII Dashboard menu.

  • SAP NetWeaver

    The SAP NetWeaver system property webservice.EndPointUrlPrefix is configured with the specified protocol for the xapps~me~integration~ear application. You can verify this configuration in SAP NetWeaver Administrator by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Java System Properties Next navigation step Applications End of the navigation path.

  • SAP ERP

    Not applicable

  • SAP MII

    Not applicable

Recommendation

  • Default

    HTTP

  • Impact of Change from the Default

    Not applicable

Host

Enter the name of a valid host of the SAP NetWeaver instance where SAP MII and SAPMEINT are deployed. In the case of a clustered environment, make sure the host URL is configured with the host name of the central SAP NetWeaver instance.

Usage in Configuration

  • SAP ME

    The Transport URLs for the following SAP ME Outbound Collaboration directives are configured with the protocol specified in this screen:

    • ERP_SCRAP_BACKFLUSHING

    • ERP_SCRAP_CONFIRMATION

    • ERP_YIELD_BACKFLUSHING

    • ERP_YIELD_CONFIRMATION

    • ERP_CONTAINER_CLOSED_CONFIRMATION

    • ERP_CONTAINER_CLOSED_BACKFLUSHING

    • ERP_INV_CLEAR_RESERVATION

    • ERP_EQUIPMENT_STATUS_CHANGE

    • ERP_EQUIPMENT_USAGE

    • ERP_SO_COMPLETE

    • ERP_QUALITY_NOTIFICATION

    • ERP_STORAGE_LOC_MOVE

    • ERP_DIRECT_LABOR_CONFIRMATION

    To review this configuration, log on to SAP ME and verify in Collaboration Directive Maintenance (see Collaboration Directive Maintenance).

    To view the service extension points and their activity description details for a quality inspection lot, log on to SAP ME and verify by entering the following on the Service Extension Maintenance screen:

    • DataCollectionService in the Service field

    • LogSfcDcGroups in the Method field

  • SAPMEINT

    The host name of the SAP NetWeaver instance where SAP MII and SAPMEINT are deployed and running.

  • SAP NetWeaver

    The SAP NetWeaver system property webservice.EndPointUrlPrefix is configured with the specified host for the xapps~me~integration~ear application. You can verify this configuration in SAP NetWeaver Administrator by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Java System Properties Next navigation step Applications End of the navigation path.

  • SAP ERP

    Not applicable

  • SAP MII

    The host name of the SAP NetWeaver instance where SAP MII and SAPMEINT are deployed and running.

Recommendation

Name of a valid host of the SAP NetWeaver instance where SAP MII and SAPMEINT are deployed. In the case of a clustered environment, make sure the host URL is configured with the host name of the central SAP NetWeaver instance.

  • Default

    By default, this field is populated with the host name of the server where the configuration template SAPMEINTCTC is being executed.

  • Impact of Change from the Default

    Do not change the value from the default unless this field needs to be configured with the central SAP NetWeaver instance in a clustered environment.

Port

Enter the port number of the SAP NetWeaver instance where SAP MII and SAPMEINT are deployed. In the case of a clustered environment, make sure the host URL is configured with the port number of the central SAP NetWeaver instance.

Usage in Configuration

  • SAP ME

    The Transport URLs for the following SAP ME Outbound Collaboration directives are configured with the protocol specified in this screen:

    • ERP_SCRAP_BACKFLUSHING

    • ERP_SCRAP_CONFIRMATION

    • ERP_YIELD_BACKFLUSHING

    • ERP_YIELD_CONFIRMATION

    • ERP_CONTAINER_CLOSED_CONFIRMATION

    • ERP_CONTAINER_CLOSED_BACKFLUSHING

    • ERP_INV_CLEAR_RESERVATION

    • ERP_EQUIPMENT_STATUS_CHANGE

    • ERP_EQUIPMENT_USAGE

    • ERP_SO_COMPLETE

    • ERP_QUALITY_NOTIFICATION

    • ERP_STORAGE_LOC_MOVE

    • ERP_DIRECT_LABOR_CONFIRMATION

    To review this configuration, log on to SAP ME and verify in Collaboration Directive Maintenance (see Collaboration Directive Maintenance).

    To view the service extension points and their activity description details for a quality inspection lot, log on to SAP ME and verify by entering the following on the Service Extension Maintenance screen:

    • DataCollectionService in the Service field

    • LogSfcDcGroups in the Method field

  • SAPMEINT

    The port number of the SAP NetWeaver instance where SAP MII and SAPMEINT are deployed and running.

  • SAP NetWeaver

    The SAP NetWeaver system property webservice.EndPointUrlPrefix is configured with the specified port for the xapps~me~integration~ear application. You can verify this configuration in SAP NetWeaver Administrator by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Java System Properties Next navigation step Applications End of the navigation path.

  • SAP ERP

    Not applicable

  • SAP MII

    The port number of the SAP NetWeaver instance where SAP MII and SAPMEINT are deployed and running.

Recommendation

Should be set to the valid port number of the SAP NetWeaver instance where SAP MII and SAPMEINT are deployed. In the case of a clustered environment, make sure the host URL is configured with the port number of the central SAP NetWeaver instance.

  • Default

    By default, this field is populated with the port number of the server where the configuration template SAPMEINTCTC is being executed.

  • Impact of Change from the Default

    Do not change the value from the default unless this field needs to be configured with the central SAP NetWeaver instance in a clustered environment.

MESYS Password

Enter the password associated with the MESYS user. This user will be used for all communication between SAPMEINT and SAP ME.

Usage in Configuration

  • SAP ME

    The MESYS user is created with the password specified. To review this configuration, log on to SAP ME and verify in User Maintenance (see User Maintenance).

    During this process, SAPMEINTCTC creates the SYSTEM user group and assigns the MESYS user to this group (see User Group Maintenance). The SYSTEM user group will not have permission to execute any of the SAP ME activities. The MESYS user and SYSTEM user group are created in SAP ME only to authenticate Web service requests coming to SAP ME.

  • SAPMEINT

    Not applicable

  • SAP NetWeaver

    The MESYS user is created in the SAP NetWeaver instance(s) where SAPMEINT and SAP ME are deployed and running. This user is assigned with the following roles by default in SAP NetWeaver: Role_SAPMEINT and all roles with the prefix SAP_XMII_. You can verify this configuration in SAP NetWeaver Administrator by choosing Start of the navigation path Configuration Next navigation step Security Next navigation step Identity Management End of the navigation path.

    Note Note

    SAP ME could be running in a different SAP NetWeaver instance than the SAP NetWeaver instance where SAPMEINT is running. In this case, the MESYS user is created in both of these instances.

    End of the note.

    The SAP NetWeaver system property webservice.Password is configured with the specified password for the xapps~me~integration~ear application. You can verify this configuration in SAP NetWeaver Administrator by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Java System Properties Next navigation step Applications End of the navigation path.

  • SAP ERP

    Not applicable

  • SAP MII

    The credential SAPMEINT_ME_AUTH is created in SAP MII Credential Editor with the user MESYS and the password specified on the screen. You can verify this configuration in Credential Editor by choosing Start of the navigation path Security Services Next navigation step Credential Editor End of the navigation path in SAP MII Dashboard menu.

    The following scheduler jobs in SAP MII are configured with the user MESYS and the password specified on the screen:

    • MessageDispatcher

    • QueueMessageCleaner

    You can verify these configurations by choosing Start of the navigation path System Management Next navigation step Schedule Editor End of the navigation path in SAP MII Dashboard menu.

    Recommendation

    For more information about configuring a user in SAP NetWeaver, see User Management of the Application Server Java.

    • Default

      Not applicable

    • Impact of Change from the Default

      Not applicable

XMIIIDOC Listener

This field is pre-populated with the list of message (IDoc) listeners configured in SAP NetWeaver Administrator. Choose the IDoc listener from the drop-down list for the plant that is being configured to receive IDocs from SAP ERP.

Usage in Configuration

  • SAP ME

    Not applicable

  • SAPMEINT

    Not applicable

  • SAP NetWeaver

    One of the IDoc listeners configured in SAP NetWeaver Administrator is used to receive IDocs from SAP ERP for the plant being configured. You can review this configuration in SAP NetWeaver Administrator by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

  • SAP ERP

    Not applicable

  • SAP MII

    One of the message listeners configured in SAP MII is used to receive IDocs from SAP ERP for the plant being configured. You can verify this configuration by choosing Start of the navigation path Message Services Next navigation step Message Listeners End of the navigation path in SAP MII Dashboard menu.

    SAPMEINTCTC creates the SAP JCo connector with the name <XMIIDoc Listener>_SAP_JCO is SAP MII. You can verify this configuration by choosing Start of the navigation path Data Services Next navigation step System Connection Editor End of the navigation path in SAP MII Dashboard menu.

Recommendation

None

  • Default

    The field is defaulted to the first value in the drop-down list.

  • Impact of Change from the Default

    None

SAP ERP Connection Information XMIIIDOC Listener

Program ID

Enter a valid, registered RFC Server Program ID existing in SAP ERP.

Usage in Configuration

  • SAP ME

    Not applicable

  • SAPMEINT

    Not applicable

  • SAP NetWeaver

    IDoc (message) listener is configured in SAP NetWeaver with provided Program ID. You can verify this configuration in SAP NetWeaver Administrator by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

  • SAP ERP

    An existing RFC Program ID in SAP ERP; you can verify it SAP ERP by using the transaction SM59 for the TCP/IP connection configured for transferring IDocs to the SAP XMIIIDOC Listener which has been assigned the RFC Program ID specified on the screen. For more information, see Define RFC destination in Customizing for Logistics - General under Start of the navigation path Supply Chain Planning Interfaces (SCPI) Next navigation step Production Optimization Interface (POI) Next navigation step ALE settings for POI End of the navigation path.

  • SAP MII

    Not applicable

Recommendation

This is an existing RFC Program ID in SAP ERP.

  • Default

    None

  • Impact of Change from the Default

    Not applicable

Server

Enter a valid host name for the SAP ERP which needs to be integrated with SAP ME.

Usage in Configuration

  • SAP ME

    Not applicable

  • SAPMEINT

    Not applicable

  • SAP NetWeaver

    IDoc (message) listener is configured in SAP NetWeaver with the provided host name of the ERP server. You can verify this configuration by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

  • SAP ERP

    This is the host name of the server where SAP ERP is running.

  • SAP MII

    The SAP JCo connector is created in SAP MII with the Server specified on this screen. You can verify this configuration by choosing Start of the navigation path Data Services Next navigation step System Connection Editor End of the navigation path in SAP MII Dashboard menu.

Recommendation

This is the host name of the server where SAP ERP is running.

  • Default

    None

  • Impact of Change from the Default

    Not applicable

User

Enter a valid user name for ALE communication between SAP ERP and SAP NetWeaver.

Usage in Configuration

  • SAP ME

    Not applicable

  • SAPMEINT

    Not applicable

  • SAP NetWeaver

    IDoc (message) listener is configured in SAP NetWeaver with the provided ALE user. You can verify this configuration by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

  • SAP ERP

    This is an existing system user in SAP ERP and is used only for ALE communication. For more information, see User Administration.

  • SAP MII

    The credential SAPMEINT_ALE is created in SAP MII Credential Editor with the User specified on this screen. You can verify this configuration by choosing Start of the navigation path Security Services Next navigation step Credential Editor End of the navigation path in SAP MII Dashboard menu.

Recommendation

An existing system user in SAP ERP used only for ALE communication. Make sure that this user has the necessary authorization objects configured in SAP ERP so that the user can transact between SAP ERP, SAP MII, and SAPMEINT. For more information, see Customizing for ALE for Communication with SAP ME.

  • Default

    None

  • Impact of Change from the Default

    Not applicable

Password

Enter the password for the ALE user specified for ALE communication between SAP ERP and SAP NetWeaver.

Usage in Configuration

  • SAP ME

    Not applicable

  • SAPMEINT

    Not applicable

  • SAP NetWeaver

    IDoc (message) listener is configured in SAP NetWeaver with the provided ALE user's password. You can verify this configuration by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

  • SAP ERP

    This is the password for an existing system user in SAP ERP and is used only for ALE communication.

  • SAP MII

    The credential SAPMEINT_ALE is created in SAP MII Credential Editor with the ALE user's password specified on this screen. You can verify this configuration by choosing Start of the navigation path Security Services Next navigation step Credential Editor End of the navigation path in SAP MII Dashboard menu.

Recommendation

The password for ALE system user in SAP ERP

  • Default

    None

  • Impact of Change from the Default

    Not applicable

Client

Enter an existing SAP ERP client which needs to be integrated with SAP ME for the supported plant being configured.

Usage in Configuration

  • SAP ME

    Not applicable

  • SAPMEINT

    Not applicable

  • SAP NetWeaver

    IDoc (message) listener is configured in SAP NetWeaver with the provided SAP ERP client. You can verify this configuration by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

  • SAP ERP

    This is an existing SAP ERP client.

  • SAP MII

    SAP JCo connector is created in SAP MII with the SAP ERP Client specified on this screen. You can verify this configuration by choosing Start of the navigation path Data Services Next navigation step System Connection Editor End of the navigation path in SAP MII Dashboard menu.

Recommendation

An existing SAP ERP client, which needs to be integrated with SAP ME for the supported plant being configured.

  • Default

    None

  • Impact of Change from the Default

    Not applicable

System Number

Enter an existing system number for an SAP ERP system, which needs to be integrated with SAP ME for the supported plant being configured.

Usage in Configuration

  • SAP ME

    Not applicable

  • SAPMEINT

    Not applicable

  • SAP NetWeaver

    IDoc (message) listener is configured in SAP NetWeaver with the provided SAP ERP system number. You can verify this configuration by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

  • SAP ERP

    This is a system number for an existing SAP ERP system.

  • SAP MII

    SAP JCo connector is created in SAP MII with the SAP ERP System Number specified on this screen. You can verify this configuration by choosing Start of the navigation path Data Services Next navigation step System Connection Editor End of the navigation path in SAP MII Dashboard menu.

Recommendation

An existing system number for an SAP ERP system, which needs to be integrated with SAP ME for the supported plant being configured.

  • Default

    None

  • Impact of Change from the Default

    Not applicable

Language

Enter a valid language to be used during ALE communication.

Usage in Configuration

  • SAP ME

    Not applicable

  • SAPMEINT

    Not applicable

  • SAP NetWeaver

    IDoc (message) listener is configured in SAP NetWeaver with the provided language. You can verify this configuration by choosing Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

  • SAP ERP

    This is one of the language setting configured in SAP ERP.

  • SAP MII

    SAP JCo connector is created in SAP MII with the SAP ERP Language setting specified on this screen. You can verify this configuration by choosing Start of the navigation path Data Services Next navigation step System Connection Editor End of the navigation path in SAP MII Dashboard menu.

Recommendation

One of the language settings configured in SAP ERP

  • Default

    None

  • Impact of Change from the Default

    Not applicable

Configure Integration with SAP EWM

If selected, you can configure SAP Extended Warehouse Management (EWM) and SAP ME integration.