Hierarchy

⤷

⤷

IMG Activity
ID | SCPI_OALE_PARTPRO | Maintain partner profile |
Transaction Code | (empty) | |
Created on | 19981230 | |
Customizing Attributes | SCPI_OALE_PARTPRO | Maintain partner profile |
Customizing Activity | SCPI_OALE_PARTPRO | Maintain partner profile |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SCPI_OALE_PARTPRO |
For ALE communication to take place, the partners must be defined with inbound or outbound parameters.
Requirements
- The logical systems must be known to the system. A number range must be maintained for the ports.
- For outbound processing the receiving ports must be assigned:
- Sending and Receiving Systems
- Systems in Network
- Asynchronous processing
- Assign ports.
Activities
- Execute the function. Enter the number of the logical system as the partner number (e.g. K11MAND005).
- Use LS (logical system) as the partner type. In the scenario "Sales and distribution" you can also use the partner types "LI" and "KU", with the appropriate customer or vendor number.
- Choose the menu path Partner -> Create.
- Enter details in the "Partner class" and "Partner status" fields.
- The inbound or outbound parameters must be created according to the direction in which communication takes place. Refer to F1 help and the application help.
Further notes
For BAPIs you use the BAPI Browser to determine the message type.
We recommend that you send several IDocs by tRFC (field: "Packet size" for the outbound options of a message type), because a work flow is started for each tRFC.
In outbound processing, collecting and sending IDocs in packets, rather than than immediately dispatching them, considerably reduces system load. You can schedule the dispatch of IDoc packets in the background:
- Modeling and Implementing ALE Business Processes
- Partner Profiles and Time of Processing
- Schedule IDoc Dispatch in Packets.
Standard Settings for POI
- Partner number: <external logical system>
- Partner type: LS
- Classification
- Partner class: LOI (for example)
- Partner status: A
- -> Outbound parameters
Each of the message types of the customer distribution model must be assigned to the partner profile. Enter the receiver port, package size, output model, and IDoc type in the detail screen of the receiver port. You must also define whether the IDocs should be sent immediately, or if they should be collected first.
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SCPI_OALE_PARTPRO | 0 | HLA0009816 | Production Optimization Interface (POI) |
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 |
EDIPARTNER | T - Individual transaction object | WE20 | 0000000005 | WF-EDI: Partner profiles |
History
Last changed by/on | SAP | 19981230 |
SAP Release Created in |