Skip to Content

SAP Purchase Order IDOC Message Type ORDERS in Different Logical Systems

Hello All,

We already have ORDERS Message type triggerred for a particular condition record. There is Logical System setup for this in BD64. ( E.g. LS1).This Message is generated to external Sysem for one Plant. This setup is working fine and don't want to touech any setting in this setup.

Now we have requirement of generaring the IDOC for Purchase order for another plant. So we created new Logical System in BD64 ( E.g. LS2 ) and different condition record and are using same message type which is ORDERS.

We also added Filter of Plant in BD59 and added Filter Group in BD64 in LS1 as well as LS2.

But now the Condition record is not working for Any Plant. It is Giving Message No B1138 saying "Too Many Recipients in ALE".

Can anybody suggest if they have been through similar situation.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jul 30, 2020 at 07:24 AM

    Hello gaurav thakkar

    First of all it's message B1130 "Too many recipients found for message type & in the ALE model" not B1138.

    Look at the long text of the message, which is quite self explanatory:

    Short Text

    Too many recipients found for message type & in the ALE model

    Diagnosis

    In the ALE distribution customer model several recipient systems for IDOCs with message type and filter object type '' with value '' have been modeled from this system, but only one recipient system is allowed.

    Procedure

    Please change the ALE distribution customer model so that it allows only one recipient system for the message from this system.

    Clearly your ALE distribution model including filters specifies more than one recipient of the ORDERS message.

    You said that you had implemented filtering by plants in the ALE distribution model. However notice that plant is on the item level of a purchase order, not on the header level. Therefore such filter will not prevent ORDERS message from being created even if the plant on PO item doesn't much the filter. See note 2693492 - Material is still sent out via transaction code BD10 though object does not match ALE filter condition for a detailed explanation.

    Thus you have two options:

    1. Either define ALE distribution model filter that refers to a header level field of a PO e.g. purchasing organization or purchasing group or
    2. Define a new ALE message e.g. ZORDERS1, maintain it in the ALE distribution model and link the message to your output condition type in partner profile (transaction WE20).

    Best regards

    Dominik Tylczynski

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 30, 2020 at 05:34 PM

    Hello Dominik,

    Thanks for your reply.

    We cannot define different Message Type. We want to use Same Message Type across Object. There are lot of enhancement written with respect to segment type.

    With regards to your first Option, we tried filter at Header Level field Like Purchase Org and order Type. But it is still the same message.

    I noticed the Message is displayed as Below

    Message B1130..

    In the ALE distribution customer model several recipient systems for IDOCs with message type ORDERS and filter object type 'LIFNR' with value XXXXX have been modeled from this system, but only one recipient system is allowed.

    I have not specified any Filter with reference to LIFNR for ZORDERS in BD59.. But Still it is giving same message.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.