Configuring SAP ME Outbound Collaboration 
SAPMEINTCTC configures collaboration directives to specify Web service URL for operation confirmation, scrap confirmation, yield confirmation, clearing inventory reservation, equipment usage, and equipment status change.
In Collaboration Directive Maintenance, review transport parameters for the following directives:
Directive |
Value |
|---|---|
ERP_SCRAP_BACKFLUSHING |
|
ERP_SCRAP_CONFIRMATION |
|
ERP_YIELD_BACKFLUSHING |
|
ERP_YIELD_CONFIRMATION |
|
ERP_CONTAINER_CLOSED_CONFIRMATION |
|
ERP_CONTAINER_CLOSED_BACKFLUSHING |
|
ERP_EQUIPMENT_STATUS_CHANGE |
|
ERP_EQUIPMENT_USAGE |
|
ERP_INV_CLEAR_RESERVATION |
|
ERP_RMA_COMPLETE |
|
ERP_QUALITY_NOTIFICATION |
|
Directive |
Value |
|---|---|
ERP_SCRAP_BACKFLUSHING |
The above URL calls an SAP MII transaction which correlates the Scrap Backflushing messages. If message needs to be processed immediately without correlation, the collaboration directive can be configured to use the following transport URL:
End of the note. |
ERP_SCRAP_CONFIRMATION |
The above URL calls an SAP MII transaction which correlates the Scrap Confirmation messages. If message needs to be processed immediately without correlation, the collaboration directive can be configured to use the following transport URL:
End of the note. |
ERP_YIELD_BACKFLUSHING |
The above URL calls an SAP MII transaction which correlates the Yield Backflushing messages. If message needs to be processed immediately without correlation, the collaboration directive can be configured to use the following transport URL:
End of the note. |
ERP_YIELD_CONFIRMATION |
The above URL calls an SAP MII transaction which correlates the Yield Confirmation messages. If message needs to be processed immediately without correlation, the collaboration directive can be configured to use the following transport URL:
End of the note. |
ERP_CONTAINER_CLOSED_CONFIRMATION |
The above URL calls an SAP MII transaction which correlates the Yield Confirmation messages. If message needs to be processed immediately without correlation, the collaboration directive can be configured to use the following transport URL:
End of the note. |
ERP_CONTAINER_CLOSED_BACKFLUSHING |
The above URL calls an SAP MII transaction which correlates the Yield Backflushing messages. If message needs to be processed immediately without correlation, the collaboration directive can be configured to use the following transport URL:
End of the note. |
ERP_EQUIPMENT_STATUS_CHANGE |
|
ERP_EQUIPMENT_USAGE |
|
ERP_INV_CLEAR_RESERVATION |
|
ERP_RMA_COMPLETE |
|
ERP_QUALITY_NOTIFICATION |
|
For more information, see Collaboration Directive Maintenance.
In Collaboration Link Maintenance, ensure that the following collaboration links are set up as follows:
Link |
Trigger Action |
Directive |
|---|---|---|
ERP Scrap Backflushing |
COLLABORATION_ERP_SCRAP_BACKFLUSHING |
ERP_SCRAP_BACKFLUSHING |
ERP Scrap Confirmation |
COLLABORATION_ERP_SCRAP_CONFIRMATION |
ERP_SCRAP_CONFIRMATION |
ERP Yield Backflushing |
COLLABORATION_ERP_YIELD_BACKFLUSHING |
ERP_YIELD_BACKFLUSHING |
ERP Yield Confirmation |
COLLABORATION_ERP_YIELD_CONFIRMATION |
ERP_YIELD_CONFIRMATION |
ERP Container Closed Confirmation |
COLLABORATION_ERP_CONTAINER_CLOSED_CNFRM |
ERP_CONTAINER_CLOSED_CONFIRMATION |
ERP Container Closed Backflushing |
COLLABORATION_ERP_CONTAINER_CLOSED_BCKFL |
ERP_CONTAINER_CLOSED_BACKFLUSHING |
ERP Clear Inventory Reservation |
COLLABORATION_ERP_INV_CLEAR_RESERVATION |
ERP_INV_CLEAR_RESERVATION |
ERP Equipment Status Change |
COLLABORATION_EQUIPMENT_STATUS_CHANGE |
ERP_EQUIPMENT_STATUS_CHANGE |
ERP Equipment Usage |
COLLABORATION_ERP_EQUIPMENT_USAGE |
ERP_EQUIPMENT_USAGE |
ERP RMA Order Complete |
COLLABORATION_SHOPORDER_COMPLETE |
ERP_RMA_COMPLETE |
ERP Nonconformance Logged |
COLLABORATION_NC_LOG |
ERP_QUALITY_NOTIFICATION |
Point |
Trigger Action |
Directive |
|---|---|---|
ERP Scrap Backflushing |
COLLABORATION_ERP_SCRAP_BACKFLUSHING |
ERP_SCRAP_BACKFLUSHING |
ERP Scrap Confirmation |
COLLABORATION_ERP_SCRAP_CONFIRMATION |
ERP_SCRAP_CONFIRMATION |
ERP Yield Backflushing |
COLLABORATION_ERP_YIELD_BACKFLUSHING |
ERP_YIELD_BACKFLUSHING |
ERP Yield Confirmation |
COLLABORATION_ERP_YIELD_CONFIRMATION |
ERP_YIELD_CONFIRMATION |
ERP Container Closed Confirmation |
COLLABORATION_ERP_CONTAINER_CLOSED_CNFRM |
ERP_CONTAINER_CLOSED_CONFIRMATION |
ERP Container Closed Backflushing |
COLLABORATION_ERP_CONTAINER_CLOSED_BCKFL |
ERP_CONTAINER_CLOSED_BACKFLUSHING |
ERP Clear Inventory Reservation |
COLLABORATION_ERP_INV_CLEAR_RESERVATION |
ERP_INV_CLEAR_RESERVATION |
ERP Equipment Status Change |
COLLABORATION_EQUIPMENT_STATUS_CHANGE |
ERP_EQUIPMENT_STATUS_CHANGE |
ERP Equipment Usage |
COLLABORATION_ERP_EQUIPMENT_USAGE |
ERP_EQUIPMENT_USAGE |
ERP RMA Order Complete |
COLLABORATION_SHOPORDER_COMPLETE |
ERP_RMA_COMPLETE |
ERP Nonconformance Logged |
COLLABORATION_NC_LOG |
ERP_QUALITY_NOTIFICATION |
Note
The input parameters passed to Outbound Service transactions using URL parameters can be set with different values than what is specified in default. For example, if there is no need to save request and response XML during the message processing for the messages generated from ERP_EQUIPMENT_USAGE and we also would like to set a different retry limit value, we could do it by setting the transport parameter like:
operation=equipmentUsage;url=http://<MIIhost>:<port>/XMII/Runner?Transaction=SAPMEIntLite/SAPMEIntegration/services/Outbound/EquipmentUsage/EquipmentUsageService&InputParameter=document&saveRequestAndResponse=true&retryLimit=3&OutputParameter=ResponseMessage&Session=false
For more information, see Collaboration Link Maintenance and Collaboration Log Report.