To add condition on which distribution model MATMAS should be sent

Hello All,
I have to send MATMAS Idoc to XI. But in R/3 there 2 distribution models created one for XI and other for some R/# system.
I have created a custom report of MASTERIDOC_CREATE_SMD_MATMAS to handle specific conditions. Now I want to send to distribute this IDoc only to XI sytem and not to the other R/3 system.
Where can I add this condition.
Thanks in advance..
Shabari

hai..
MDD1     Advance for MDD0
MDD2     Adv.frm prev.per.for MDD0
MDD3     Advance MDD2 paid back
MDD5     Arrears w. balance recov.
MDD6     Recovery for MDD5(IT15)
MDD7     Balance & IT15 entry
MDD8     Deduction for MDD7
MDD9     Total deducted via MDD8

Similar Messages

How to add BAPI in ALE-distribution model?

HI all,
I have to send The post goods issue through ALE-IDOC, this have to create the Goods Receipt in the receiving side.
I came to know that the message type for this is MBGMCR , when i am trying to add this in the distribution model , it is prompting an error message that this message type belongs to BAPI.
So , to send the required data , i have to add the BAPI.
Please help me clearly on how to add this and what are the steps involved in distributing data through BAPI ?
Thanks,
Vamshi

In we20
process code will be BAPI and setting will be same as in other process codes
in bd64 i have example..
TCode BD64
Add ADRMAS in Distribution Model u2018TestERDToEXDu2019 as follow:
Click on u2018Add BAPIu2019 Buton.
Give Object Name as AddressOrg
Give Method Name as SaveReplica
You will get a entry as follows
Edited by: Madan Gopal Sharma on Jul 1, 2008 9:02 AM
Edited by: Madan Gopal Sharma on Jul 1, 2008 9:04 AM

When to add message type to distribution model

hi
i am bit confused on when to add a custom/std message type to distribution model. what are the conditions. is that always necessary to add the message type to distribution model.
thanks

[http://sap.ittoolbox.com/groups/technical-functional/sap-interfaces/add-message-type-in-ale-distribution-model-1192885]
[http://docs.sun.com/app/docs/doc/820-5014/ggcpd?a=view]
[http://publib.boulder.ibm.com/infocenter/wtxdoc/v8r2m0/index.jsp?topic=/com.ibm.websphere.dtx.packsapxi.doc/tasks/t_pack_sapxi_Create_a_Destination_Model_BD64.htm]

Adding a Filter in a distribution model

Hi Experts,
I need to add few fields in my IDOC segments as a filter in distribution model.
and i need to set certain values to these fields.
Can anyone plesae tell me step by step procedure how to add the filter in distribution model?
Regards,
Ashish

Hii..Ashish..
These are the Steps to Implement Data Filtering in ALE.
Filter Objects: These are the Fields based on which you define The Conditon.
For eg: Matnr, Mtart...
1. Create a Filter Object (If it is not available for ur Requirement)
   Tcode: BD59
   New Entries:
   ALE Filter Object type : MBRSH (Industry Sector)
   Segment type : E1MARAM
   Segment field : MBRSH
   Save.
2. Link the ALE Filter Object type to the Table field in DDIC
    Tcode: BD95
    New Enries:
    ALE Filter Object type : MBRSH (Industry Sector)
    Table Name : MARA
    Table field : MBRSH
    Save
3. Creating Data filtering using this Filter Object type
    Tcode: BD64.
    Expand ur Model view.
    Under the Message Type MATMAS
    Double click on No Data filter / Data filter Active.
    Create a Filter Group.
    It will list out all the Filter Objects of the Message type:
    (you should find the New filter Object type)
   Double Click on the Filter Object type MBRSH .
   Assign the Filter values
   Save.
<b>Reward if Helpful</b>

Need of distribution model in IDOC triggering

Hi,
I have one question dat is it necessary to maintain distibution model in BD64 for outbound IDOCs or only maintaining partner profile in WE20 is mandatory.
I have seen some cases in which distribution model is not maintained.
Please let me know the cases in which we maintain distribution model
Thanks in advance.

hi,
The distribution model describes the ALE message flow between logical systems u2013 that is, it determines which messages are distributed to which logical systems.
For example, you can make distribution dependent on conditions that you define as filters in the ALE distribution model.
please refer this blogs for more info:
Data Ditribution Model BD64 config
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a610f507d11d18ee90000e8366fc2/frameset.htm
thanks ,

Error while generating Distribution Model in ERP to EWM

I am trying to generate new distribution Model from ERP to EWM for my warehouse.
In system one distribution Model already exists for another warehouse. Below error encountered.

Hi Suraj,
Thanks for the answer
Yes i was using the Wrong Distribution Model , I should have selected EWM , but i was giving some new name as i thought that was required. Hence message came.
I did with EWM distribution Model and all worked well.
Thanks
Inder

ADD BAPI in distribution model

Hello everybody,
Can you please expalin use of ADD BAPI button given in BD64/distribution model.
Please explain with an example.
I tried to to serach on inetrnet about ADD BUTTON.But not much information available niether ADD BAPI was explained in me training.
Thanks.

Hi Jitu,
gr8 to se ur reply.
I think ur suggesting custom idoc for accounting.
Though we need not use MASTER_IDOC_DISTRIBUTE.
We can still create custom idoc using BDBG.
Just need to instanciate BO-
CALL FUNCTION 'SWO_CREATE'
EXPORTING
    objtype           = 'ZBUS6035_A'           "My z- BO ,Here we can use standard BO
    objname           = 'ZBUS6035_A'         "Custom method
IMPORTING
    object            = l_objhnd
EXCEPTIONS
    no_remote_objects = 1
    OTHERS            = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
break-point.
pass data to container for bapi
SWC_GET_ELEMENT lt_cont 'Date1' DATE1.
fire BAPI
CALL FUNCTION 'SWO_INVOKE'
EXPORTING
ACCESS = 'C'
object = l_objhnd
verb = 'ZBUS60351_A'
PERSISTENT = ' '
IMPORTING
return = l_return
VERB =
MODE_ID =
TABLES
container = lt_cont.
My problem is resolved now.Icould use ADD BAPI for IDOC triggere.
Thanks everybody for kind help.
Edited by: Sanjay_lnt on Feb 1, 2011 11:35 AM
Edited by: Sanjay_lnt on Feb 1, 2011 11:37 AM

Error in IDOC Distribution Model

HI all ;
Please Help me in this Issue!!
am working with standard IDOC Using MATMAS (Material Master Transfer)
LS_800 - Outbound.
LR_810 - Inbound.
--> BD54.
--> SCC4.
-->SM59.
-->WE21.
-->WE20.
--> WE20 ( in inbound side) Clear Up to this level.
After that the Problem in Distributing the Model,,,,
In Bd64 t-code Distribution Model.
while Generating the Partner Profiles in BD64 ;
its giving the blank message like below.
No message has been defined for the selection conditions in the model.
when we distribute(in BD64) 2 Errors (red) Like Below;
RFC destination for Syncronous Communication (Message type SYNCH)
Partner Profile LS LR_810 SYNCH does Not Exits.
Generate Partner Profile.
or Specify outbound partner Profile for message type SYNCH
RFC destination for Syncronous Communication (Message type SYNCH)
Partner Profile LS LS_810 SYNCH does Not Exits
Generate Partner Profile.
or Specify outbound partner Profile for message type SYNCH
Thannks;
Upender.

In Bd64 t-code Distribution Model.
create the model view ,
add message type Matmas to it.
-> select the model view
->environment-> generate partner profiles
In Partner Profiles u hv to maintain the Outbound parameters in Both LS_800 &
LR_810 .
in receiver port, double click & make sure that the rfc destination assigned connects successfully..
Regards.

How to restrict the idoc creation based on the distribution model

Hi all,
I want to create the idocs for certain material types only, for this i configured Distribution model and set the filter for material types.
If the delivery is created with the material type which is not in the filter means,
Idoc is creating for that Delivery with header segments only and restricting Item level segments.
it is coming to XI and failing in mapping every time.
I do not want to generate the whole idoc itself. Am i missing any thing??
Regards
Edited by: Suman gupta on Jun 10, 2010 11:13 PM

Hi Mike,
>>config in PI in the routing condition - if no lines exits don't send the message to the mapping/receiver
If no lines exists we can restrict don't send to receiver, but how can we restrict dont send to mapping??
It comes to mapping and failing in PI MONI.
Is there any way that i can restrict the Idoc generation itself in ECC ??
Regards

Material Master Change Pointers/Distribution Model - any suggestions?

Dear All,
Hope everyone is doing good.. I have been trying to come up with a solution for the below issue, but didn't get any further. Your help is highly appreciated.
Initial Design:
Couple of years before we had a plant 123 and plant 456 where we need to send the materials. So we had specified these plants in Distribution Model and things worked fine.
First Problem
During testing what we have found out was, if some one changes MARA level, IDOC is being created but it's not being sent out of SAP system because the IDOC doesn't have 123 and 456 plants which the distribution model filtered it out and no data got sent to SAP PI.
Solution implemented:
After doing lot of analysis and research we have implemented solution as per the blog The specified item was not found.
Today's problem
There are couple of more plants we were supposed to send the data 789 and 678. The problem is if some one did a mass change on plant 456, the above solution implemented takes all the data(not the deltas) and pushing it out. Even though the change is only on 456 plant, we were unnecessarily sending the data to 789, 678 which is causing lot of problems.
Now we realize we shouldn't have gone with the solution mentioned above, because it's not applicable in my scenario.
Does anyone handled this kind of scenarios in the past, if so can you please shed some lights?
Thanks,
Raj

Hi Raj,
As per my experience what you had already implemented, that is absolutely correct. I don't think there is any alternative to send the data as a whole (I understood if you are not sending the Plant data, how the middle ware filter them).
Now your requirement is if you make some mass changes in the materials which are extended different plants other than 456 plant, we have to restrict them. To restrict the outbound Idocs for MATMAS. you can use the Filter option in BD64 (Distribution Model). Here after creating the Filter Group, you can edit LOV for Plants.
Once your mass changes transmission is over, you can remove this.
Hope this will work, at least you can give a try...............

R/3 to XI (Idoc to File): Do we need to maintain distribution model in R/3?

Hi All,
I have a very basic question regarding Distribution model.
My scenario is IDOC-->File ( SAP R/3 --> XI). So all I am trying to do is send the IDOC frrom R/3 to XI. ( Within XI I am going to do an FTP to the 3rd party file server)
I have created a distribution model, but was wondering if I really need to create one as message is going from R/3 to XI and not from R/3 to another R/3.
Please help let me know If I need to distribute this model to XI or to SAP production sytem or I do not need to duistribute at all for this scenario.
Thanks
Shirin

Hi,
if you create partner profiles and port via t.code.
i hope, it's not required to maintain Distribution model.
please check the below points.
Configuration Steps for Idoc to File Scenario.
This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
To Configure the IDOC TO FILE SCENARIO, SETTINGS IN SAP-XI
STEP 1:ALE SETTINGS IN SAP-XI
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) ALE SETTINGS TO POST IDOC OUT OF SAP-R/3 ***********************************************************************
a) Create RFC Destination using T.code in SM59.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item u2018Generate Partner Profilesu2019
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> u2018Distributeu2019 to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
warm regards
mahesh.

ALE distribution model - one message type to more than one recipient

Hello colleagues,
currently I'm working on an integration project between one SAP system and an e-shop system. The communication is established through IDOCs ( both inbound and outbound ). There is another system ( POS ) which is already integrated
with SAP via IDOCs also.
   Now I'm facing the following problem regarding distribution of transactional IDOCs ( orders, deliveries, etc. ): when assigning one message type ( for example DESADV - Delivery: Shipping notification ) to more than one external system in ALE distribution model I receive a message alerting that one message type can be send to only one recipient.
The distribution model is as follows:
Model Views
   SAP to POS
      SAPDEV ( the SAP system )
         POS ( the external POS system )
            DESADV
   SAP to E-SHOP
      SAPDEV ( the SAP system )
         E-SHOP ( the external e-shop system )
            DESADV
   Well, the system message is clear and I did the obvious: create a complete copy to the original message type and than assign it to the E-SHOP system ( the original message type is already used in integration between SAP and POS ).
As you can see I have found a workaround already but I think that it comes natural to SAP to communicate with other systems and to exchange same kind of documents to those systems and I can't believe that there isn't a standard solution for situation like this.
FYI I'm working on SAP ECC 6.0
Thanks in advance.
Wish you nice day and successful week ,
Vladimir

I believe when ePrint server has received the email, it made the necessary settings and configured the job for printing and then it went for "Reply All" option. So here it cannot send the print job to your personal email ID and the error came up.
The only option I can think of is add the printer email ID to your email contact list and give it a name like MyPrinter so you can remember easily , just like email contacts are added in Outlook.
Mark this post as answered so that others can find it useful.
Say "Thanks" by clicking the Kudos Star in the post that helped you.
Please mark the post that solves your problem as "Accepted Solution"

ALE Distribution Model

Hi,
I've created an ALE distribution model to process the interface concerning Set Up HR and Accounting. Initialy we make it all and distribute it to the receiving system (FI) and it seems to be ok. After that the funcional team generate some movements and the IDOC's were generated but they were not sent to the FI system. We've a look at tRFC and an error concerning user or password invalid appears, so i define again the user comunication and after a few adjustments to the model view we distribute it again to the FI system. When i execute it the following message appears : <b>Model view HRFI-CFP has not been updated / Rreason: Distribution model is currently being processed.
</b>
Next step we delete the model view and created it again but the same error still remains.
Can anyone help me ???
Thanks is advance.
JMMatos

Hi
Distribution Model A model that describes the ALE message flow between logical systems.
Applications and the ALE distribution service layer use the model to determine receivers and to control the data distribution. The relationships between logical systems, message types, BAPIs and filters are defined in the distribution model.
Ex: The screen shot depicts customer distribution mode ALE_TRNG_Mar07.
Sender Logical System EC1CLNT800
Receiver Logical System SALES
Message Type CREMAS
No filter conditions defined.
This configuration step allows the installation of core ALE features on which data transfer activity will be based.
In the distribution model you can specify the messages to be sent to a given logical system. You can also define the conditions for the content and dispatch of messages in the filters.
The distribution model consists of one or more views that you can define
After creating the distribution model the model needs to be distributed to the receiver system.
Partner profiles need to be generated in both sender and receiver systems using transaction BD82 (automatically) or WE20 (manually).

Problem with IDoc filtering in the distribution model

Hello Experts,
We are using a distribution model in which we have set filters as like the following
Filter Group 1
Plant : XYZ
Sales Org: SAP1
As far as the documentation says this Condition should work with AND logic between Plant and Sales Org
(i.e ~ Plant XYZ and SO SAP1 ) but the IDoc gets created even if any one of the condition is met(looks like working in OR logic).
How to achieve the AND filtering between the different objects.
Would appreciate your kind help.
Thanks in advance.
RGds,
Vasanth.

> Jakub ~ Yes I checked the generated IDocs(classified pertaining to my Model)for my model alone and that's where we are facing this problem
So that's the filtering problem.
I would check in which segments are the "filtering objects" located (BD59) and whether it is a mandatory segment. If it is a mandatory segment - IDoc should not be created. If it is an optional segment - this segment and its subsegmets will be filtered out - but IDoc will be created.
> ~ Do we need to apply some SAP Notes to avoid this problem ?
> But why the filter should behave in OR fashion ? I do not understand.
I believe that Sachin meant that the logic is:
Filter Group1 OR Filter Group 2 OR ... Filter Group N
Filter Group 1 Object 1 AND Filter Group 1 Object 1 ... AND Filter Group 1 Object M
Filter Group 1 Object 1 Value 1 OR Filter Group 1 Object 1 Value 2 OR ... Filter Group 1 Object 1 Value L
regards,
Jakub

Interaction between Distribution model, partner profile, etc.

Hello,
I am a newbie in the SAP world, and I am a little bit lost in the behavior of the Outbound Processing (the send of an IDoc to an external non-SAP system).
Actually my question is how the following components interact during an outbound process :
- RFC Destination
- Logical Port
- Logical System
- Partner Profile
- Distribution Model
- SAP Gateway
- IDOC Repository
- ALE Service
Currently, the only thing I think I have really understood is that the RFC Destination allows to hide to SAP the Program ID of the registered external server...
Thanks a lot
Sebastien

For each logical system and each basic message type (for example, LOIBOM), a unique message type has to be defined by reducing the original one (for example, MYBOM).
If you reduce a message type, only the obligatory fields are automatically selected. You must select those segments and fields you want to have transferred. Fields that have not been selected for transfer always contain the value "/".
Maintain partner profile
Each of the message types of the customer distribution model (see above) must be assigned to the partner profile. Enter the receiver port (see above), package size, output mode and IDoc type in the detail screen of the receiver port. You must also define whether the IDocs should be sent immediately, or if they should be collected first.
Maintain customer distribution model directly
First define a customer model for a logical R/3 system. The displayed list shows which logical system is the sender and all the possible receiving systems that have been defined. "Create message type" defines which logical system receives information from the logical R/3 system.
When maintaining the customer distribution model, you usually add all (reduced) message types that should be sent from the R/3 system to the external system.

To add condition on which distribution model MATMAS should be sent

Similar Messages

Maybe you are looking for