Hierarchy
⤷ LO-SCI-AIN (Application Component) Auto-ID Backend Integration
⤷ AID-BI (Package) Auto-ID Backend Integration
IMG Activity
ID | SIMG_ABIPRTNRPRFL | Maintain Partner Profiles |
Transaction Code | S_ALN_01002380 | (empty) |
Created on | 20031104 | |
Customizing Attributes | SIMG_ABIPRTNRPRFL | Maintain Partner Profiles |
Customizing Activity | SIMG_ABIPRTNRPRFL | Maintain Partner Profiles |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_LOSCIAIDPARTNER |
Use
In this IMG activity, you define partner profiles for each of the predefined logical systems, with the message types as either inbound or outbound parameters. This enables ALE communication to take place.
For more information, see IMG activity Maintain Partner Profile Manually (in Customizing for Application Link Enabling).
Requirements
You have defined the following:
- Auto-ID infrastructure systems and XI system as logical systems in IMG activity Define Logical System.
- A receiving port for the XI system in IMG activity Define Port.
Standard settings
Activities
For the standard implementation, do the following:
Define Partner Profile for Each Auto-ID Infrastructure System
Ensure that you do the following when defining the partner profile for each auto-ID infrastructure system:
- Define the partner type as LS (Logical System).
- Enter the following message types as outbound parameters:
- AIDMATMAS
- AIDNRMSG
- ARTMAS
- Enter the following message types as inbound parameters:
- AIDARCMSG
- AIDOPMSG
- AIDRQMSG
- In the Process code field of the Inbound options tab, enter ABI_AIDN_IN.
Define Partner Profile for XI System
Ensure that you do the following when defining the partner profile for the XI system:
- Define the partner type as LS (Logical System).
- Enter the following message types as outbound parameters:
- AIDMATMAS
- AIDNRMSG
- AIDOPMSG
- ARTMAS
- For each message type, enter the port that you defined in IMG activity Define Port in the Receiver port field (Outbound Options tab).
- Enter the following basic IDoc types (Outbound Options tab) for each message type as follows:
Message Type IDoc Type
AIDMATMAS MATMAS01
AIDNRMSG AIDNR01
AIDOPMSG AIDOP01
ARTMAS ARTMAS01
- Enter the predefined output types in the Message Control tab for message type AIDOPMSG. If you are using the output types provided with the auto-ID infrastructure, enter the following values:
Application Message type Process code
E1 AUB0 ABI_AIDN_OUT
E1 SU10 ABI_AIDN_OUT
E1 AUU1 ABI_AIDN_OUT
V2 ALB0 ABI_AIDN_OUT
V2 APL1 ABI_AIDN_OUT
V2 APL2 ABI_AIDN_OUT
V2 SL10 ABI_AIDN_OUT
Example
Business Attributes
ASAP Roadmap ID | 255 | Create Interfaces |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
WE20_1 | T - Individual transaction object | WE20 | Maintain Partner Profiles |
History
Last changed by/on | SAP | 20031231 |
SAP Release Created in | 500 |