Process documentationSetup of Your System Landscape

 

To distribute data between systems, you must set up the system landscape appropriately. In other words, you determine which systems exchange data. Then the system knows how to send and receive data.

Process

  1. You determine the systems involved.

    Two systems are relevant for the Billing Consolidation Connector (FIN-FSCM-BC) component: the back-end system (sender) and the middleware (receiver). These two systems correspond to an SAP system and a client, and they must exist in the back-end system as logical systems. You name logical systems in Customizing for SAP NetWeaver under Start of the navigation path Application Server Next navigation step IDoc Interface / Application Link Enabling (ALE) Next navigation step Basic Settings Next navigation step Logical Systems Next navigation step Define Logical Systems End of the navigation path.

    Note Note

    The names of the systems are automatically assigned by the system administrator. If you do not find your systems here, contact your system administrator.

    If you assign a logical system a new name, you must also assign it a client. You do this in the Customizing activity Assign Logical System to Client.

    End of the note.

  2. You connect the sender system with the receiver system.

    To connect the two systems, you must create a distribution model. In the distribution model, the relationships between logical systems and message types are determined. Distribution models are used by the applications and the ALE layer to determine receivers and to control data distribution. You create distribution models and the corresponding model views in Customizing for SAP NetWeaver under Start of the navigation path Application Server Next navigation step IDoc Interface / Application Link Enabling (ALE) Next navigation step Modelling and Implementing Business Processes Next navigation step Maintain Distribution Model and Distribute Views End of the navigation path. For more information, see Creating Distribution Models and the documentation of the Customizing activity.

  3. You define the directory to which the back-end system can write the XML IDoc file before it is sent. For more information, see Determining Directory for IDoc File.

  4. You edit the partner profile. You have to include in the partner profile the partners (customers or vendors) with whom you communicate by means of IDocs. In the partner profile, you determine which message the system sends to the partner in which way, and how the system processes incoming messages. For more information, see Editing Partner Profiles.

  5. To transfer the settings to the middleware, you generate the partner profile. You generate the partner profile in Customizing for SAP NetWeaver under Start of the navigation path Application Server Next navigation step IDoc Interface / Application Link Enabling (ALE) Next navigation step Modelling and Implementing Business Processes Next navigation step Partner Profiles Next navigation step Generate Partner Profiles End of the navigation path.

Note Note

The process codes are already preconfigured in the standard delivery; you do not usually have to make any additional settings. You can recognize the process codes by the their technical key EDX... . For a complete overview, see the following list of the transactions relevant for process codes:

  • BD51 — Maintain Function Modules (Inbound)

  • WE57 — Assignment of Function Module to Application Objects

  • WE42 — Inbound Process Code

  • BD67 — Function Modules for Inbound ALE-EDI

End of the note.

More Information

SAP Billing Consolidation Connector