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
In Customizing for Logistics - General, choose
.On the Change View “Logical Systems”: Overview screen, choose New Entries.
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 |
Save your entries.
In Customizing for Logistics - General, choose
.On the Configuration of RFC Connections screen, select the TCP/IP connections node and choose the Create icon.
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) |
Press Enter.
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 | For example, sapprod.visiprise.com |
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 menu |
Save your entries.
(Optional) If you configured SAP MII IDoc Listener, test the RFC connection.
In Customizing for Logistics - General, choose
On the Ports in IDoc processing screen, select the Transactional RFC node and choose the Create icon.
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.
Choose the Enter icon.
On the Ports in IDoc processing screen, enter the following data:
Field | Description | User Action and Values | Comments |
---|---|---|---|
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 |
Save your entries.
In Customizing for Logistics - General, choose
On the Partner profiles screen, create a new profile for Partner Type LS.
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 |
Save your entries.
Under the Outbound Parameters table, choose the Create Outbound Parameter icon.
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 CLFMAS BOMMAT LOIPRO LOIROU LOIPLO INVCON IORDER HRMD_A LOIWCS | |
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: MATMAS03 CLFMAS02 BOMMAT03 LOIPRO01 (configuration types A and B (see SAPMEINT: SAP ERP Configuration)) or LOIPRO02 (configuration type C) LOIROU02 (configuration types A and B) or LOIROU03 (configuration type C) LOIPLO01 INVCON02 IORDER01 HRMD_A06 LOIWCS02 | Each basic type corresponds to the list of message types above. |
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 |
Save your entries.
Repeat steps 5–7 for each listed basic type.
In Customizing for Logistics - General, choose
On the Change Distribution Model screen, choose Create model view.
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 |
Choose the Enter icon.
On the Change Distribution Model screen, select the distribution model previously created and choose Add message type.
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 CLFMAS BOMMAT LOIPRO LOIROU LOIPLO INVCON IORDER HRMD_A LOIWCS DOCMAS | Each message type is added separately following the same steps. |
Choose the Enter icon.
Repeat steps 5–7 to add each message type to the distribution model as listed above.
Save your entries.
This configuration is required to ensure that material IDocs from only specified plants with the movement types 261 (Goods issue to a production order) or 311 (Transfer posting storage location (one step)) are sent to SAP ME if you use an ERP system of the configuration type A or B (see SAPMEINT: SAP ERP Configuration). If your system is of the configuration type C , the corresponding filters are maintained in transaction DRFF of the Data Replication Framework (DRF) and filtering on ALE level is not required.
On the Change View “ALE Object Type”: Overview screen (transaction BD95) create a new entry:
Parameter | Value |
---|---|
ALE Object Type | BWART |
Table Name | MSEG |
Field Name | BWART |
Save your entries.
On the Change View "Assignment of Object Type to Message”: Overview screen (transaction BD59), assign the BWART field to the INVCON message type.
Save your entries.
On the Change Distribution Model screen (transaction BD64, edit mode), select the distribution model that you want to change and navigate to the INVCON message.
Double-click No filter set and then choose Create filter group.
On the Filter Changed screen, expand the subtree and double-click Movement Type and add the following movement types by inserting new rows:
261
311
Save your entries.
On the Filter Changed screen, double-click Plant and add your plants (sites) you want to send the inventory documents.
Save your entries.
See the following topics in SAP Library for SAP NetWeaver and SAP ERP at http://help.sap.com:
IDoc Interface/ALE
Production Optimization Interface (POI): Overview
Transfer and Distribution of Material Master Data