04-21-2014 2:20 PM
My scenario is to send SHPORD idocs to 2 different systems based on shipping point and sales org.
For this i created filter groups in BD95 and BD59.
When i run program 'RSNAST00' for the delivery, it is failing with error
"
Message no. B1130
In the ALE distribution customer model several recipient systems for IDOCs with message type SHPORD and filter object type 'KUNNR' with value '117033' have been modeled from this system, but only one recipient system is allowed.
Please change the ALE distribution customer model so that it allows only one recipient system for the message from this system.
I created only one model view for these 2 systems, and the SHPORD message type does not exist in other models.
Appreciate your help.
Thanks
Srinivas
04-21-2014 2:57 PM
04-21-2014 3:28 PM
Thanks Harish,
I checked all the models in BD64, SHPORD message type does not exist in any other models.
Thanks
Srinivas
04-21-2014 3:50 PM
Hi Srinivas,
I don't think there would be any other issue then multiple model view. let's wait if some one has any other solution.
regards,
Harish
04-22-2014 4:19 AM
Hi Srinivas
My guess is during runtime execution, it is finding both the recipient systems that you have configured.
Have you set the filter conditions in BD64 for the two systems so that only one system is determined at any one time?
Rgds
Eng Swee
04-23-2014 12:06 PM
Precaution: Just to be sure, check table EDP13 with message type SHPORD for other model views instead of searching in BD64(easy reference).
Queries:
(1). Since filter is made on Sales Org. and Shipping point, why KUNNR is coming into picture? Are customers also maintained as filter values?
(2). At the segment level, Sales org and Shipping point are appearing at Header segment level or at Item level? To my knowledge, receiver system selection based on filter values will work if they appear at Hierarchical level 1. If not, BD64 filters are only segment filters.
05-01-2014 3:54 PM
Hi, we use next configuration to solve this:
Regards Jack
05-02-2014 9:12 PM
I'm able to resolve the issue.
Previously we defined output as ALE Medium, Now we changed to EDI Medium and added 'LS; to the partner role in the partner profile.
Thanks
Srinivas