Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
There are going to be some situations where we need more granularity for selecting idocs to process. For example, we have a bunch of ORDERS05 idocs to process. However, the project team does not want to process each other's ORDERS05 idocs in some cases.
We don't see how the parameter screen for RBDAPP01 can allow us to choose at a more granular level what Idocs to process when they are all coming from the same partner.
Can someone offer us some ideas or references on how to select a group of idocs based on more criteria than just the message type and partner so that we can select just the group of ORDERS05 idocs that we really want to process rather than processing all ORDERS05 idocs in the queue?
RBDAPP01 has a Message Variant parameter which can be utilized to filter same-name message types for processing. This can be the "Message Code" set on the Partner Profile. Thanks!
RBDAPP01 has a Message Variant parameter which can be utilized to filter same-name message types for processing. This can be the "Message Code" set on the Partner Profile. Thanks!
You can setup inbound partners with separate message function based on the source system logical system and you can use the same message function along with message type and partner while processing Idocs using the program 'RBDAPP01'.
Thanks for the reply. I am not a developer and I am not familiar with the message functions, but we will take your suggestion and look into it. If it works, we will post an update
RBDAPP01 has a Message Variant parameter which can be utilized to filter same-name message types for processing. This can be the "Message Code" set on the Partner Profile. Thanks!
Bluesky
