SAP ABAP IMG Activity SIMG_CFMENU_PDR_WE20 (Maintain Partner Profile Manually)
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_WE20 Maintain Partner Profile Manually  
Transaction Code S_ALN_01001091   (empty) 
Created on 20020214    
Customizing Attributes SIMG_CFMENU_PDR_WE20   Maintain Partner Profile Manually 
Customizing Activity SIMG_CFMENU_PDR_WE20   Maintain Partner Profile Manually 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENU_PDR_WE20    

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

  1. Execute the function. Enter the number of the logical system as the partner number (e.g. K11MAND005).
  2. 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.
  3. Choose the menu path Partner -> Create.
  4. Enter details in the "Partner class" and "Partner status" fields.
  5. 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.

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_WE20 0 HLB0009011 O ALN0000162  
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 Partner Profiles 
History
Last changed by/on SAP  20020214 
SAP Release Created in 110