Configuration of High Performance SAPMEINT Interfaces 
The following documentation describes how to make corrections and modifications to the High Performance SAPMEINT interfaces manually.
The High Performance SAPMEINT interfaces are installed and configured using the SAPMEINTCTC configuration wizard. For more information, see SAP ME 5.2 Installation Guide available at .
Note
Contact your SAP ME consultant concerning the usage of the High Performance interfaces. Due to the continuing performance improvement and architectural advantages of the Standard interfaces, the High Performance interfaces will not be supported in future releases.
See Configuring Datasources in SAP NetWeaver Java AS in Configuration of Standard SAPMEINT Interfaces.
See Configuring SAPMEWIP Data Server in SAP MII in Configuration of Standard SAPMEINT Interfaces.
See Configuring SAPMEINT Data Server in SAP MII in Configuration of Standard SAPMEINT Interfaces.
See Configuring MESYS User in SAP NetWeaver in Configuration of Standard SAPMEINT Interfaces.
See Configuring Credentials in SAP MII in Configuration of Standard SAPMEINT Interfaces.
See Configuring Role_SAPMEINT Role in SAP NetWeaver in Configuration of Standard SAPMEINT Interfaces.
See Configuring SAP ERP ALE in Configuration of Standard SAPMEINT Interfaces.
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:
Log on to SAP NetWeaver Administrator using the following URL: http://<host>:<port>/nwa.
Choose .
Select Resource Adapters from the dropdown list.
Select the resource configured by SAPMEINTCTC, such as XMIIIDOC01, that you want to modify in the table.
Choose Properties tab in the bottom window.
Edit the properties to match your SAP ERP server.
Save your entries.
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.
After configuring the resource, make sure that this configuration works by doing the following:
Check that the resource is running and in a Fully Available state.
On the SAP MII menu, expand Message Services and choose Message Listener.
Select the message listener configured by SAPMEINTCTC, such asXMIIIDOC01, and choose Update.
Choose Status.
The following message appears: Server Connected.
Processing rules specify how incoming IDocs are processed by SAP MII based on message type. SAPMEINTCTC creates the following rules in SAP MII Message Services:
<Name of the IDoc Listener>_MATMAS03
Message type for material
<Name of the IDoc Listener>_BOMMAT03
Message type for BOM
<Name of the IDoc Listener>_LOIROU02
Message type for routing
<Name of the IDoc Listener>_LOIPRO01
Message type for production order
<Name of the IDoc Listener>_LOIPLO01
Message type for planned order
<Name of the IDoc Listener>_INVCON02
Message type for inventory receipt
<Name of the IDoc Listener>_IORDER01
Message type for planned maintenance order or service order
<Name of the IDoc Listener>_CLFMAS02
Message type for material classification
<Name of the IDoc Listener>_HRMD_A06
Message type for user
<Name of the IDoc Listener>_LOIWCS02
Message type for resource or work center.
To modify the configurations for these processing rules, proceed as follows:
On the SAP MII main menu, expand Message Services and choose Processing Rule Editor.
Select the processing rule that you want to modify.
Make the desired modifications.
Save your entries.
Note
For optimal performance, use the following Message Processing Rules parameter values for all message types:
Persist Transaction: ONERROR
Log Level: ERROR
SAPMEINTCTC configures this processing rule with the following values:
Field |
Value |
|---|---|
Rule Name |
<Name of the IDoc Listener>_MATMAS03 |
Description |
<Name of the IDoc Listener>_MATMAS03 |
Server Name |
Name of the IDoc Listener |
Message Name |
MATMAS |
Message Type |
IDoc |
Processing Rule |
Transaction |
Transaction |
SAPMEIntLite/SAPMEIntegration/services/Inbound/Material/MaterialSplitService |
Transaction Parameters |
|
SAPMEINTCTC configures this processing rule with the following values:
Field |
Value |
|---|---|
Rule Name |
<Name of the IDoc Listener>_BOMMAT03 |
Description |
<Name of the IDoc Listener>_BOMMAT03 |
Server Name |
Name of the IDoc Listener |
Message Name |
BOMMAT |
Message Type |
IDoc |
Processing Rule |
Transaction |
Transaction |
SAPMEIntLite/SAPMEIntegration/services/Inbound/BOM/BOMService |
Transaction Parameters |
|
SAPMEINTCTC configures this processing rule with the following values:
Field |
Value |
|---|---|
Rule Name |
<Name of the IDoc Listener>_LOIROU02 |
Description |
<Name of the IDoc Listener>_LOIROU02 |
Server Name |
Name of the IDoc Listener |
Message Name |
LOIROU |
Message Type |
IDoc |
Processing Rule |
Transaction |
Transaction |
SAPMEIntLite/SAPMEIntegration/services/Inbound/Routing/RoutingService |
Transaction Parameters |
|
SAPMEINTCTC configures this processing rule with the following values:
Field |
Value |
|---|---|
Rule Name |
<Name of the IDoc Listener>_LOIPRO01 |
Description |
<Name of the IDoc Listener>_LOIPRO01 |
Server Name |
Name of the IDoc Listener |
Message Name |
LOIPRO |
Message Type |
IDoc |
Processing Rule |
Transaction |
Transaction |
SAPMEIntLite/SAPMEIntegration/services/Inbound/ProductionOrder/ProductionOrderService |
Transaction Parameters |
|
SAPMEINTCTC configures this processing rule with the following values:
Field |
Value |
|---|---|
Rule Name |
<Name of the IDoc Listener>_LOIPLO01 |
Description |
<Name of the IDoc Listener>_LOIPLO01 |
Server Name |
Name of the IDoc Listener |
Message Name |
LOIPLO |
Message Type |
IDoc |
Processing Rule |
Transaction |
Transaction |
SAPMEIntLite/SAPMEIntegration/services/Inbound/PlannedOrder/PlannedOrderService |
Transaction Parameters |
|
SAPMEINTCTC configures this processing rule with the following values:
Field |
Value |
|---|---|
Rule Name |
<Name of the IDoc Listener>_INVCON02 |
Description |
<Name of the IDoc Listener>_INVCON02 |
Server Name |
Name of the IDoc Listener |
Message Name |
INVCON |
Message Type |
IDoc |
Processing Rule |
Transaction |
Transaction |
SAPMEIntLite/SAPMEIntegration/services/Inbound/InventoryReceipt/InvReceiptService |
Transaction Parameters |
|
SAPMEINTCTC configures this processing rule with the following values:
Field |
Value |
|---|---|
Rule Name |
<Name of the IDoc Listener>_IORDER01 |
Description |
<Name of the IDoc Listener>_IORDER01 |
Server Name |
Name of the IDoc Listener |
Message Name |
IORDER |
Message Type |
IDoc |
Processing Rule |
Transaction |
Transaction |
SAPMEIntLite/SAPMEIntegration/services/Inbound/IORDER/OrderDiscriminatorService |
Transaction Parameters |
|
SAPMEINTCTC configures this processing rule with the following values:
Field |
Value |
|---|---|
Rule Name |
<Name of the IDoc Listener>_CLFMAS02 |
Description |
<Name of the IDoc Listener>_CLFMAS02 |
Server Name |
Name of the IDoc Listener |
Message Name |
CLFMAS |
Message Type |
IDoc |
Processing Rule |
Transaction |
Transaction |
SAPMEIntLite/SAPMEIntegration/services/Inbound/Classification/MatCustData/MatCustDataSplitService |
Transaction Parameters |
|
SAPMEINTCTC configures this processing rule with the following values:
Field |
Value |
|---|---|
Rule Name |
<Name of the IDoc Listener>_HRMD_A06 |
Description |
<Name of the IDoc Listener>_HRMD_A06 |
Server Name |
Name of the IDoc Listener |
Message Name |
HRMD_A |
Message Type |
IDoc |
Processing Rule |
Transaction |
Transaction |
SAPMEIntLite/SAPMEIntegration/services/Inbound/User/UserSplitService |
Transaction Parameters |
|
SAPMEINTCTC configures this processing rule with the following values:
Field |
Value |
|---|---|
Rule Name |
<Name of the IDoc Listener>_LOIWCS02 |
Description |
<Name of the IDoc Listener>_LOIWCS02 |
Server Name |
Name of the IDoc Listener |
Message Name |
LOIWCS |
Message Type |
IDoc |
Processing Rule |
Transaction |
Transaction |
SAPMEIntLite/SAPMEIntegration/services/Inbound/LOIWCS/LOIWCSDiscriminator |
Transaction Parameters |
|
See Configuring the SAP ERP Server Connection in Configuration of Standard SAPMEINT Interfaces.
SAPMEINTCTC configures the E-mail Server connection in SAP MII to generate E-mail notifications. To modify this configuration, proceed as follows:
On the SAP MII main menu, choose .
Select the MAIL connect type.
Choose the E-mail server SAPMEINT_EMAIL_SERVER.
You can modify the following properties:
Field |
Value |
|---|---|
Server |
<Your E-mail server> |
Port |
<E-mail server port> |
Connection Timeout |
60 |
Read Timeout |
60 |
Protocol |
<Your E-mail protocol> |
Note
The server name must be SAPMEINT_EMAIL_SERVER and should not be modified.
Save your entries.
SAPMEINTCTC configures E-mail address in SAP MII Shared Memory to receive E-mail notifications. To modify the E-mail address, proceed as follows:
On the SAP MII main menu, choose .
Edit the EmailNotificationEmailTo property for the SAPMEIntLite project by choosing the Edit icon.
Enter the E-mail address in the popup window.
Choose OK to save the address.
SAPMEINTCTC configures the mapping details of the quality notification request in SAP MII Shared Memory. It configures the following fields in the mapping using the values supplied during the configuration process:
NOTIF_TYPE
CODE
PRIORITY
CATALOGUE
CODE_GROUP
To modify the existing values, proceed as follows:
On the SAP MII main menu, choose .
Edit the qualityNotificationRequestTransform property for the SAPMEIntLite project by choosing the Edit icon.
Enter the desired values for the above mapping fields.
Choose OK to save your entries.
See Configuring SAPMEINT MII Web Services in SAP NetWeaver Java AS in Configuration of Standard SAPMEINT Interfaces.
See Configuring SAPMEINT GUI Applications to Role_SAPMEINT Role in Configuration of Standard SAPMEINT Interfaces.
SAPMEINTCTC configures SAPMEINT Global Configuration properties with the values provided during the SAPMEINTCTC configuration process. To modify this configuration, proceed as follows:
On the SAP MII Dashboard menu, choose and choose Global Configuration.
You can modify the following properties:
Property |
Description |
Examples |
|---|---|---|
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_OEE_Max_Buckets |
The number of times to display the buckets in the OEE Report |
12 |
SAPMEINT_DB_Vendor |
The database vendor for the SAPMEINT datasource |
ORACLE,SQLSERVER |
SAPMEINT_ME_User |
SAP ME user |
MESYS |
Save your entries.
SAPMEINTCTC configures the SAP MII Schedulers to process queued messages in SAPMEINT. To modify this configuration, proceed as follows:
On the SAP MII main menu, choose .
Select the desired scheduler.
Modify the desired properties:
Note
For optimal performance, use the following property values for all the scheduling processes:
Persist Transaction: ONERROR
Log Level: ERROR
Field |
Value |
|---|---|
Name |
SAPMEIntQueueDispatcher |
Description |
Dispatcher for queued SAPMEINT messages |
Enabled |
Selected |
Transaction |
|
User |
A valid SAP MII user who has enough 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 |
Field |
Value |
|---|---|
Name |
SAPMEIntQueueMessageCleaner |
Description |
Dispatcher to delete the old SAPMEINT messages |
Enabled |
Selected |
Transaction |
|
User |
A valid SAP MII user who has enough 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 |
Field |
Value |
|---|---|
Name |
ScrapBackflushingCorrelationDispatcher |
Description |
Dispatcher to correlate Scrap Backflushing messages |
Enabled |
Selected |
Transaction |
|
User |
A valid SAP MII user who has permission sufficient to run the Scheduler |
Password |
The password for the SAP MII user |
Parameters |
If the numberOfDocuments = 10 and waitTimeInSec=300, SAPMEINT waits for 10 documents with the same correlation key to arrive into the SAPMEINT queue. If 10 documents with the same correlation key arrived into the SAPMEINT queue before 300 seconds, it merges these 10 documents. If 10 documents with the same correlation key did not reach SAPMEINT queue before 300 seconds, SAPMEINT merges any documents with the same correlation key that are in the queue. End of the note. |
Pattern |
Your pattern |
Field |
Value |
|---|---|
Name |
YieldBackflushingCorrelationDispatcher |
Description |
Dispatcher to correlate Yield Backflushing messages |
Enabled |
Selected |
Transaction |
|
User |
A valid SAP MII user who has permission to run the Scheduler |
Password |
The password for the SAP MII user |
Parameters |
If the numberOfDocuments = 10 and waitTimeInSec=300, SAPMEINT waits for 10 documents with the same correlation key to arrive into the SAPMEINT queue. If 10 documents with the same correlation key arrived into the SAPMEINT queue before 300 seconds, it merges these 10 documents. If 10 documents with the same correlation key did not reach SAPMEINT queue before 300 seconds, SAPMEINT merges any documents with the same correlation key that are in the queue. End of the note. |
Pattern |
Your pattern |
Field |
Value |
|---|---|
Name |
ScrapConfirmationCorrelationDispatcher |
Description |
Dispatcher to correlate Scrap Confirmation messages |
Enabled |
Selected |
Transaction |
|
User |
A valid SAP MII user who has permission sufficient to run the Scheduler |
Password |
The password for the SAP MII user |
Parameters |
If the numberOfDocuments = 10 and waitTimeInSec=300, SAPMEINT waits for 10 documents with the same correlation key to arrive into the SAPMEINT queue. If 10 documents with the same correlation key arrived into the SAPMEINT queue before 300 seconds, it merges these 10 documents. If 10 documents with the same correlation key did not reach SAPMEINT queue before 300 seconds, SAPMEINT merges any documents with the same correlation key that are in the queue. End of the note. |
Pattern |
Your pattern |
Field |
Value |
|---|---|
Name |
YieldConfirmationCorrelationDispatcher |
Description |
Dispatcher to correlate Yield Confirmation messages |
Enabled |
Selected |
Transaction |
|
User |
A valid SAP MII user who has permission sufficient to run the Scheduler |
Password |
The password for the SAP MII user |
Parameters |
If the numberOfDocuments = 10 and waitTimeInSec=300, SAPMEINT waits for 10 documents with the same correlation key to arrive into the SAPMEINT queue. If 10 documents with the same correlation key arrived into the SAPMEINT queue before 300 seconds, it merges these 10 documents. If 10 documents with the same correlation key did not reach SAPMEINT queue before 300 seconds, SAPMEINT merges any documents with the same correlation key that are in the queue. End of the note. |
Pattern |
Your pattern |
Save your entries.
See Configuring Supported SAP ME Plants in Configuration of Standard SAPMEINT Interfaces.
See Configuring SAP ME Web Services in Configuration of Standard SAPMEINT Interfaces.
See Clearing SAP MII Transaction Cache in Configuration of Standard SAPMEINT Interfaces.