Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
PLM-PPM-RPL (Application Component) Product Data Replication⤷
CRWB (Package) Replication Workbench
IMG Activity
| ID | SIMG_CFMENU_PDR_BD82 | Generate Partner Profiles |
| Transaction Code | S_ALN_01001092 | (empty) |
| Created on | 20020214 | |
| Customizing Attributes | SIMG_CFMENU_PDR_BD82 | Generate Partner Profiles |
| Customizing Activity | SIMG_CFMENU_PDR_BD82 | Generate Partner Profiles |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENU_PDR_BD82 |
With this function, you can define the partner profiles for all outbound and inbound messages based on the information in the distribution model.
After you have defined and distributed the distribution model, you have to do the same in every local system.
Requirements
- The distribution model must be defined.
- The distribution model must be distributed.
- RFC destinations must be assigned.
- To ensure that the responsible employees are informed, if a processing error occurs, you must make settings in: Error handling -> Create organizational units and assign standard tasks.
Activities
- Execute the function.
- Enter the outbound processing mode and the packet size.
If you are working with a generated BAPI-ALE interface and you want to set the IDoc packet size for packet processing, the BAPI must be able to handle packet processing and the interface must have been generated with the option Packet processing allowed. - Enter the inbound processing mode.
Functions of the report:
- Outbound messages, no ports yet available:
- For every receiving system, you must create an RFC destination with exactly the same name as the logical system to which the message has to be sent.
- Outbound messages, ports are available:
- If a message has already been defined for a receiver system, then the port set up for the new messages is used instead. Otherwise, the function generates an outbound port.
- The report records and displays settings that have been defined incorrectly.
Further notes
If you want to make changes, you can do this manually. For details see the following section.
A non-enhanced IDoc type is always used to generate a message type.
If a non-enhanced IDoc type is not assigned to a message type, nothing is generated for this message type.
The partner profiles for the message type of the BAPI/IDoc interface are generated for BAPIs maintained in the distribution model.
Recommendation
Specify the outbound processing mode (background, immediately)that is most suitable for most scenarios. Please note that background dispatch places a much smaller load on the system than the immediate dispatch of every IDoc.
Notes on the Transport
The partner profiles are not generated automatically as a part of the Transport and Correction system. Therefore they must be generated manually on all systems.
Use
Requirements
Standard settings
Activities
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 |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENU_PDR_BD82 | 0 | ALN0000162 O HLB0100224 |
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 |
| BD82 | T - Individual transaction object | BD82 | Generate Partner Profiles |
History
| Last changed by/on | SAP | 20030708 |
| SAP Release Created in | 110 |
