ALE Distribution Lock

Hi all,
can anybody tell me what is ALE Distribution Lock ...
regards
sreedhar rusuma

Here is the documentation for ALE distribution lock
You determine whether you want an object, for example, a document, to be distributed via ALE into other systems by setting the status, for example, document status.
The indicator Distribution lock prevents an object, for example, a document, from being transported into an ALE system.
A change pointer is always set for the distribution lock during distribution even when sending within the ID PDM Solution. The system automatically creates a change indicator and a Master IDoc for distribution when you change a distribution relevant field, for example, status, for a message type, such as DOCMAS for documents.
It is possible to ignore the distribution lock when you send objects manually. In this case, the entire object is transported into the ALE system according to the distribution model.
Manual distribution is only of importance for change master records within the ID PDM system.
See also:
Change Master Record : IDoc Type ECMMAS01
Objects
You can control the ALE distribution for the following objects within ID PDM via the status:
Material
Characteristic
Class
BOM (material BOM, document structure)
Document
Object dependencies
Change master record
Activities
You can process the status for the desired objects.
1. Select in Customizing Cross Applications Components --> Distribution (ALE) -->Standard ALE Business Processes --> Logistics --> Master Data Distribution --> Integrated Distributed PDM Solution (ID PDM) --> Object status (for example, Define BOM status).
2. Process the indicator Distribution lock

Similar Messages

ALE distribution error - 0 communication IDOC

Hello,
We are getting 0 communication IDOC generated for message type DOCMAS error for ALE document distribution error. Please advice where to look for the error.
Anirudh

hi,
ani,
u check this,
If you want work items to be created when errors occur for the purpose of error handling, you need to assign the standard task TS40007915 PCROLL to a position or a workflow organizational unit.
Or
You can also distribute dependent objects manually for classes. You can use report program RCCLDIHI to distribute a complete class hierarchy including all classes characteristics, and characteristic values.
Only the message code (004 - change) is allowed for sending a document (message type DOCMAS). This function also creates the document in the target system.
You can control the sending of documents with the indicator Distribution lock. An object with this indicator in its status will not be distributed into other ALE systems.
You can set the indicator in Customizing Document Management System  Define document type  Define status. The distribution lock is read when a distribution automatically starts after a change pointer is set or for an Integrated Distributed PDM Solution (ID PDM).
You can ignore this setting by starting the distribution manually. When you set the indicator Ignore distribution lock in the initial screen, then all documents will be distributed overriding the previously set status.
You control the distribution of object links with the indicator You cannot maintain the object links via ALE and Object link unchanged in target system.
Information about object links are distributed through IDoc type DOLMAS01.
The data is transferred to the workstation application and to storage data in IDoc type DOCMAS04 if an original file exists to a document. The Remote Function Call interface protocol transfers the contents of the original file, for example text or design drawing.
You can determine whether you want originals of a certain document type to be distributed by ALE into another system under the setting Document Management System  Define document type  Define transport of originals for ALE. You can control distribution with various criteria.
You want to distribute all original files of the application WRD (Microsoft Word) for the document type R-1 (report) that are stored in vault VAULT1 (Vault for Office Applications). You do not want to distribute documents of the same document type for the application WWI (Winword 6.0).
You can process the status for the desired objects.
1. Select in Customizing Cross Applications Components  Distribution (ALE)  Standard ALE Business Processes  Logistics  Master Data Distribution  Integrated Distributed PDM Solution (ID PDM)  Object status (for example, Define BOM status).
2. Process the indicator Distribution lock
ben

How to send the spool output to the specific user during ALE distribution

Hi All
In ALE internal order Configuration done by BAPI Method SAVEREPLICA Business object BUS2075whenever user changed the internal order which is moved to the destination system because of change data setting in data element fields.
I want to know how to send the spool output of the changed internal order to the specific user during ALE distribution.
Please help me to reslove the above issue
Thanks & Regards
KRISHGUNA

Solved by myself

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 : Model view HRFI-CFP has not been updated / Rreason: Distribution model is currently being processed.

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).

Query related to filter group on matnr created in ALE distribution model

Hi All,
I have query related to filter group on matnr created in ALE distribution model.
I have created a filter group on matnr in ALE distribution model and put the value E* ( purpose is that all the material number started with E should be triggered in case of any changes in the material).But it is not working.
Can anybody suggest the solution for this i.e how to capture E* value for the material master changes and should trigger idoc using change pointer using BD21.
Thanks & Regards
Prabhat

Unfortunately, you cannot filter using wildcards or exclusions. You have to explicitly list each allowed value in its entirety.
In my opinion, the simplest solution would be to copy function MASTERIDOC_CREATE_SMD_MATMAS, modify it to handle your custom filtering and update the message type entry in transaction BD60.

Contains errors and distribution lock

Hi all,
We have a error as "contains error, distribution lock"(system status)in the status of the service confirmation. Document is in Open status and with this error any changes are not replicating to the r/3. This is the only one document with such error. All other confirmations are getting replicated to R/3. Bdoc error segment for this confirmation is "NO upload into ERP,ERP adapter is called".
How can I remove this error? Any reports available to remove? what is the cause for this issue?
Thanks In Advance

Hi,
Please try to find the relevant bdoc in SMW01 . It is probably in intermediate status or there could be an error in the bdoc.
The must be a pending outbound queue or inbound queue in SMQ1 or SMQ2 in CRM.
One reason why the order is not uploaded properly can be due to filter settings in R3AC1 for object SALESDOCUMENT.
I.e. you would not allow to download the same document to CRM and therefore the complete loop is not run ok.
Please check R3ac1 as well.
If this is sill not helping please check as well the report CRM_ODE_CHECK_CFG (as per note 490932) and check if there might be obvious settings which might block the data transfer of this order type.
Best regards
Christophe

Error executing BAPI attached to ALE Distribution Model

Hi experts,
I am executing BAPI_EXCHANGERATE_SAVEREPLICA which has been included in an ALE distribution model as I wish to replicate exchange rates from my source client to a number of remote clients.
When I execute the BAPI I get an information message back in the bapi return code as follows "one table record planned for update". Does anyone know what this means? I would have expected idocs to have been created and sent across to the target clients and for the BAPI to have been executed in the target system but nothing has happened. I have released the method (BAPI) and tried various options on the partner profile but still get the same message returned when I call the BAPI.
Any help on executing this BAPI via ALE would be much appreciated.
Thanks
Adrian

This is information message that informs you that the selected row may be updated. Then when you call BAPI_TRANSACTION_COMMIT the rows will be updated.

File2idoc:Error in ALE distribution model for SendResponse

Hi,
I'm using XI to configure a file to idoc scenario.
Now in WE19 I could see relevant data,but in WE05 it showed the error status 51,and the detail message was "Error in ALE distribution model for SendResponse".
Do I have to create a distribution model in BD64?I did this ,but failed to create.

hi,
i dont think distribution model is required for inbound case.
just check the below configuration.
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
chirag

Message type US for ALE distribution

I want to create an outbound IDOC using ALE distribution.
I have to assign Partner type as 'US' - user. Can anyone give me some input. I got the error when trying to do the same
" No partner profiles (message control) maintained
Message no. B1127 Diagnosis No IDOC partner profiles have been created for the message control for
 for application EF, condition key ZNBR and change message '' with
 partner type 'LS' and partner role ' '.
Procedure Please create the partner profiles for the logical system that should
 contain the IDOC. You can either generate them from the ALE model or
 create them manually.
Step by step will be helpfull.
Thanks

Hi Preethi,
You can use this program RBDCUS15 to generate outbound partner profile.
Also you use distribution model (t/code BD64) as well.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

ALE Distribution model customisation question.

Hi,
How essential is it to undertake the SRM ALE Distribution model config prior to making the changes to the R/3 backend tables, e.g. CRMCONSUM, CRMPAROLTP, SMOFPARSFA? The SAP SRM config guide does not indicate the whether or not the ALE config needs to be undertaken before or after the R/3 middleware config.
Please can some one clarify this.
Thank you.
Steve,

Hi Stewe
ALE Idoc Settings are required for Invoice, Good Receipt and PO Commitment.
But CRM settings are required for transfering your Business Object and Customizing object.
Both are not related each other.
regards
Muthu

Message types for ALE distribution

Hi,
I am working on SRM 7.0. I need to copy the org structure from one client to another. For that I am using the ALE distribution model. Can anyone please let me know all the message types reqired for transferring the org structure.
Thanks,
Bhakti

Hi Masa,
Thanks alot for your help. The document is quite helpful if the org structure had to be mapped from HR. But, the org structure is to be mapped from another existing ERP. Kindly suggest if there is any document for such a transfer.
Also, I have found another way to transport the org structure. Hopefully that should work. Once I am done testing for the same, I will notify.
Thanks,
Bhakti

Question regd. ALE distribution

Hi Experts,
My client has a requirement for outbound HR interface. The interface basically transfers IDocs from R/3 to XI and from XI to an ftp location A. But the client also want an option to simulate the interface. For the simulation run of the interface, it should transfer IDocs from R/3 to XI and from XI to an ftp location B. In this regard, I wanted to know if there is any elegant solution to work this issue without using different IDoc types for actual and simulation run. The ALE distribution model (R/3->XI) will be same for both the cases but I want to know if there is any simple way that XI could figure out between actual and simulation run.
Thanks
Sri

Hi,
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
Thanks
Sarada

RE: ALE distribution

Hi Experts,
My client has a requirement for outbound HR interface. The interface basically transfers IDocs from R/3 to XI and from XI to an ftp location A. But the client also want an option to simulate the interface. For the simulation run of the interface, it should transfer IDocs from R/3 to XI and from XI to an ftp location B. In this regard, I wanted to know if there is any elegant solution to work this issue without using different IDoc types for actual and simulation run. The ALE distribution model (R/3->XI) will be same for both the cases but I want to know if there is any simple way that XI could figure out between actual and simulation run.
Thanks
Sri

that's a good question.
I'm using cremas right now to transfer data from our ECC 6 box to our HR box and it's been working great for the past 3 years.
I was pulled into this implementation after their distribution model was already set up so I just assumed they needed to use that message type for some reason.
I have a call to them to verify whether they really need it or can just use cremas.

ALE distribution of HR master data to CRM - subtype CELL and MAIL

Hello,
Overview/Introduction:
we are using the ALE distribution of HR master data to CRM. The distribution has already been set up and it is running. We know that the infotype communication (0105) is especially distributing the subtypes 0010 (e-Mail) and 0020 (telephone number). This e-Mail address and the telephone number are stored in the business partner in the CRM system.
For this infotype 0105 there are also the subtypes CELL (cell phone) and MAIL (e-Mail address). Unfortunately this cell phone number and the mail address (from subtype MAIL) are not stored at the business partner in CRM.
Our request is on the one hand to store the data from subtype CELL into the field mobile number of the business partner. And on the other hand we want to store the e-mail address of subtype MAIL at the business partner instead of subtype 0010.
For some reason it seems that these requests canu2019t be setup within SAP standard.
So we found SAP note 758426 which suggests to use the BAdI HRALEX_INBOUND and the report RH_ENHANCE_BP_TEMPLATE.
Problem:
Now the problem is that the BAdI does not get called! The BAdI is active! We tried to set break points -> unfortunately did not stop! And we also implemented an endless loop in the BAdI -> even with this the system did not u2018stopu2019!?
Any ideas?
Thank you,
Roman

Hi,
First you need to create a distribution model using transaction BD64 : Edit > Model View > create.
Then you will need to maintain fields for description and technical name. In partner box you need to enter the source system (HR) and the target system (FI) in the second field. Then you need to assign a message type and filter settings if you need it. You need to create this distribution model in source system (HR).
After, still in BD64, go to environment > change partner profile or transaction WE20
Select your target system and enter the corresponding message type ( HRMD_A or HRMD_ABA depends on your scenario) with the correct customizing (receiver port, packet size, idoc type, syntax check and output mode).
Then please do the same things in your source system using WE20 for your source system and define your inbound parameters (Process code HRMD, processing by function module : use trigger immediately if it is not a production system or else trigger by background program and this case you will need to run report RBDAPP01 to process Idocs).
Once done, then go back to your model view in your source system (BD64) and go to Environment > generate partner profiles. Then please go to Edit > Model View > distribute
After all these settings done, it should work.
Please also check out documentation :
http://help.sap.com/erp2005_ehp_04/helpdata/EN/82/933b90aa9e11d6b28800508b5d5211/frameset.htm
Best Regards
Christine

ALE Distribution Lock

Similar Messages

Maybe you are looking for