Show TOC

Background documentationCustomizing for ALE Audit (Optional)

 

You can configure your client and hub systems so that your client systems send confirmation of replicated materials back to the MDG hub. Use the following steps to set up this confirmation process.

In the client system make the following settings:

  1. Select Distribution Model

    1. Run transaction BD64 and choose Change/Display.

    2. Select the distribution model you created above and choose Add Message Type.

    3. In the Add Message Type screen enter the following:

      • In the Sender field, enter the logical system from which the acknowledgement is sent (The client system).

      • In the Receiver field, enter the logical system to which the acknowledgement is sent (The hub system).

      • In the Message Type field, enter ALEAUD.

    4. Choose Ok.

  2. Select Partner Profile

    1. Run transaction SALE and choose Start of the navigation path Modeling and Implementing Business Processes Next navigation step Partner Profiles Next navigation step Generate Partner Profiles End of the navigation path. Alternatively, run transaction BD82 (Generate Partner Profiles).

    2. Select the distribution model and in the Partner System field, enter the hub logical system name.

    3. Enter the ALE-User (the default value is ALEREMOTE) and the following values.

      Field

      Value

      Version

      3

      PackSize

      100

      Output Mode

      Transfer IDoc Immediately

      Inb. Parameters: Processing

      Trigger Immediately

    4. Click on the Execute button. The log for partner profile generation appears showing the new sender and receiver systems

    5. To verify your settings, run transaction WE20 and from the Partner Profiles menu, choose Partner Type LS. Verify that Partner type LS is the logical destination system.

    6. In the detail screen, the message type, ALEAUD must appear.

    7. In the Inbound Options tab, in the Process Code field enter AUD2.

    8. Select the Cancel Processing After Syntax Error checkbox.

    9. In the Processing by Function Module section, select the Trigger Immediately radio button.

    10. Choose Save.

    11. Run transaction BD64. Select the model view and select Start of the navigation path Edit Next navigation step Model View Next navigation step Distribute End of the navigation path. Select the Hub system and click OK.

In the hub system make the following settings:

  1. Distribution Model

    1. Run transaction BD64 and check that the same Distribution Model View with partner profile was created.

  2. Partner Profile

    1. Run transaction WE20 and check that the partner profile with logical name of the receiver system (Hub system) exists below the Partner Type LS folder.

    2. Select Receiver Logical System (Hub system) and choose Change.

    3. Choose Create Outbound Parameter.

    4. In the Message Type field enter ALEAUD.

    5. In the Outbound Options tab, in Receiver Port field, enter the logical system name for the client from which the status information is to be received.

    6. In the Output Mode list, select Transfer IDoc Immediately.

    7. In the Basic Type field enter ALEAUD01.

    8. Select the Cancel Processing After Syntax Error checkbox.

    9. Choose Save.

  3. Configure DRF Customizing

    1. Run transaction DRFIMG.

    2. Navigate to Start of the navigation path Data Replication Next navigation step Define Custom Settings for Data Replication Next navigation step Define Technical Settings for Business Systems End of the navigation path.

    3. Select the receiver system (Hub system) and double-click on Define Bus. Systems, BOs, Communication Channel.

    4. Enter the business object type 194 and choose OK.

    5. Select the checkbox Upd.KM.

    6. Choose Save.

Note Note

The inbound IDoc in the target system always accepts the material number sent in the IDoc, independent of the number range settings for the material type. Without additional coding it is not possible to force the target systems to create new material numbers. You can do this coding in enhancement spot ES_SAPLMV02 in function module IDOC_INPUT_MATMAS01.

End of the note.