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.

Similar Messages

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

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

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"

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.
<b>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.</b>
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.

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

Transporting ALE Distribution Model to a Target System

Hi,
      How do I transport an ALE Distribution Model from a Development System to another target system
      While transporting, how do I ensure that in the target system, the ALE Model points to the correct partner system?
      e.g. a Dev System1 points to a Dev System2. Hence a QA System1 must point to QA System2.
        When I created the ALE Model, the system prompts for a transport request, so there must be a way to transport the same
Regards,
Aditya

Hi Aditya,
In my experiences, we always maintain manually the distribution model and partner profile in our production system due to data integrity and security reasons.
However, we always maintain the distribution model and partner profile for QA system from development system via transaction BD64.
For logical system name, you need to tranport from DEV -> QA -> PROD system.
Hope this will help.
Regards,
Ferry Lianto

ALE distribution model - restriction for incoming distributed settings

Hi, we plan to protect our ALE distribution model from user and external changes. User actions can be restricted using the B_ALE_* authorization objects, this works pretty well. However we've not found a way yet to do handle external changes. With external changes I mean the case, if someone distributes the model from a remote system to the local system. Is there an authorization to restrict that? Thanks, Andre.

Hi Andre,
in my opinion the romote system will use a rfc-connection. Behind that there is also an user (for example ZRFC with type system) in use. This user must exist in your system. His authorizations could also restricted by B_ALE*.
Regards
Bernd

ALE Distribution Models: Adding new company scenario

If a new company is added in production, what is the affect on the ALE distribution models? Like the steps which we need to take to implement this scenario.

Hi,
Change the data type to add the new fields.
Save the changed data type.
Click on the mapping and refresh the data type.
You will see the new fields appearing automatically.
Make the necessary mapping changes and activate the mapping.
While transporting, add the data type and the mapping to the change list and generate the .tpz file for transport.
Hope this will help.
Regards,
Indranil

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

Error while distributing the ALE distribution model through BD64

Hi,
I am getting the error while distributing the distribution model through BD64. The error is as follows:
"Model view DVGDVH has not been updated
Reason: the following ALE connection already exists in model view TESTMOD".
What does this means?
Regards,
Soumya.

Dear Sapera,
I faced the same problem last night.
We just manually deleted the distribution model from receiving system.
Log on to receiving system => BD64 => change/dispay => edit => delete => Save.
Once deleted log in to sender system and then select model and distribute again.
by performing this we were able to resolve this issue.
Warm regards,

How to create a data filter for BAPI used in a Distribution Model ?

I am trying to create IDOC's for a QM inspection plan via message type QPMK in ECC 6.0. When creating the new message type in the Distribution Model, it forced me to use a BAPI (MasterInspectionChar) rather that just the message as I have done in the past. In order to ensure that only IDOC's related to a specific plant and material type get sent out, I was trying to create a filter.
I am able to get into a 'Change Filter' dialog by double clicking 'No data filter set' under the node 'MasterInspectionChar.SaveReplica'. However, an attempt to highlight anything on this dialog and clicking button 'Create filter group' results in msg. 'Select node: Content-dependent parameter filtering'.
Online help led me in a different direction, one thread led me to believe I needed to create a table entry for the filter in table TBD16 via BD81 for later attachment to the BAPI in the Distribution Model. Before this, I created two Z* ALE Object Type records for plant and material type in table TBD11 via BD95 for what I thought would provide a lookup back in BD81 for creation of a new filter record, but these objects are not found. Per the help, I am also unclear as to whether I would need to set up Receiver determination or Parameter filtering, nor where to make this step in the configuration happen?
Can anyone point me back in the correct direction to get a data filter set up for this BAPI within the Distribution Model ?
Thanks - Mike

Just to clarify, what I am having trouble with is finding where exactly to plug in the name of the plant to be filtered? If using a message type such as MATMAS in a distribution model, it is very straight forward to navigate down from the 'Data filter active', and assign a value to whatever field you wish to filter via the 'List of Values'. But in this example, message type QPMK required use of the BAPI MasterInspectionChar, and therefore the different method in creating the filter.
I cannot find similar functionality when navigating the BAPI related row, for MasterInspectionChar. The 'Change Filter' dialog popup displays a row for 'Container' and then 3 more rows containing 'BAPI structure...'. Clicking the 'Attribute' checkbox on any of these rows sets 'Data filter active' as a node under the BAPI. Double clicking the 'Data filter active' brings me back into the same dialog, and selecting any row with an attempt at this point to create a filter results in the 'Select node: content-dependent parameter filtering' warning. Is this warning occuring because of missing configuration?
Thanks - Mike

ALE Distribution model view

Hello
I am setting up an ALE scenario to send idocs from system A to system B. I have a problem with the distribution model view. The model has been distributed to the receiving system with the wrong basic idoc type entered in the partner profile. I would like to know how I can change the model view and re-distribute it.
Thanks,
A.P.

Hai
Go through the following Procedure
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
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
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards
Sreeni

ALE/distribution model settings

Hi all,
We are implementing SAP HR as HR master and need to distribute HR master data to connected systems. We will transfer the data to SAP XI which distribute to connected systems according to the respective requirements.
We have two interfaces from SAP HR, one for changed data using change pointers in a near real-time fashion and one for complete records in a batch transfer using PFAL.
We have a quite complex scenario where the changes should be sent to systems A and B, while the batch transfer should be sent to systems C and D. The scheduling of the data transfer has to be done in SAP R/3, since XI only forwards the messages. In order for XI to select the correct pipeline and determine the correct receivers we had to create two different interfaces from SAP HR to XI, based on two different extensions to the HRMD_A06 Idoc.
These two interfaces are defined in two separate partner profiles in SAP, P1 and P2, each with one of the extensions as the only difference.
The problem is that real-time idocs should only be sent to P1 and batch idocs should only be sent to P2. In the distribution model you can only define the sender and receiver partner, and the message type. This information is the same for both interfaces, so all idocs that are created, containing either changes using change pointers or batch data using PFAL, are sent to both interfaces.
Is there a way to filter this, so only the correct idocs are sent to the respective interfaces?
As it is now, we have the real-time data going to interface intA and intB every time there is a change, and the batch data scheduled every night will also be sent to both intA and intB.
Any quick help or input to this is highly appreciated.
Br
Kenneth

Hi Kenneth,
Back again!!!
Pls check whether i got ur requirement
Scenario :
1.) one sending HR system
2.) one XI system
3.) four recievieng systems
    A,B for change-pointers
    C,D for batch data.
Already u have defined the following config in the SAP hr system.
message type HRMD_A
idoc type : hrmd_a06
extension1(for change-pointers) : zext1
extension2(for bacth) : zext2
Solution :
1.) whatever u have done for change-pointers is fine.
u have activated change-pointers for hrmd_a.
design a ale model only for change-pointers:
sending system : HR system
Recieving system : XI
partner profile1 :
mention
message type : HRMD_A
idoc type : hrmd_a06
        extension : ext1
Define port1
define rfc destination1.
trigger rbdmidocs for message type HRMD_A to capture change-pointers on timely basis like every 30 minutes.
BDCP table will be filled and idocs sent to XI for every 30 mins.
i hope this scenario works successfully for u as required.
2.) let us discuss abt batch data.
Define a new message type ZREAL in we81.
Define a relationship between message type,idoc type and extension.
message type :ZREAL
idoc type : hrmd_a06
extension : ext2
3.) Define ale model system.
sending system : HR system
recieving system : XI
message type : ZREAL
no need to define and activate change-pointers for message type ZREAL as it carries out only bacth data.
4.) partner profile transaction ;
partner profile1(same partner profile of change-pointers)
message type will be ZREAL.
idoc type : hrmd_a06
extension : ext2
5.) port1 will be same as change-pointers
6. rfc destination1 will be same as change-pointers.
7. schedule PFAL transaction for batch job.
it will pick up the batch data and send idocs to XI.
XI system :receiving system:
u can able to distinguish between batch data and change-pointers data by message type:
change pointers : hrmd_a
batch data : zreal
Only need to perform 2 main steps in we81,we82 for batch data.
please check the solution and let me know for any concerns.
Regards,
Senthil

Generation Partner Profiles from ALE Distribution Model

Hi ABAP/EDI experts,
I am a trainee. I am getting training from Pvt consultancy. I am working on SAP Demo systems.
I am trying t generate an IDoc using ALE method.
IN SALE window, I created two logical systems,ZVK_SS_800 and ZVK_SS_820. I assigned them to two clients 800 and 820 respectively.
In SM59 i created an RFC connection ZVK_RFC004 of type 3. Here I gave the client Number as 820. ( I'm not sure what to give)
In BD64, I created an ALE Model and added the message type MATMAS with Sending and Receiving Logical systems.
From the Environment drop down menu , selected generate partner profiles and executed with defaults checked. ( Transfer IDocs Immediatley and Trigger Immediately).
I got the following log.
Log For Partner Profile Generation:
Partner:
In Green Color
Partner ZVK_SS_800 as partner has been Created ( Sending System)
Partner ZVK_SS_820 as partner has been Created (Receiving System)
Port:
In Red Color
Port Cloud not be Created
RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
Enter the RFC destination and Restart the generation.
Please help me to fix this probelm.
Any kind of Help will be surely rewarded.
Thanks,

From SM59, you can Test your RFC Connections between Clients. I would do this from Client 800 and test the Connection to Client 820. If that checks okay, I would then try SM59 on Client 820. Check the RFC Connection from Client 820 to Client 800. Be sure you have your Logical Systems defined on Both Clients. You can also double click on your Error Message to see if there is a Long Text Available that might give you further information as what needs to be corrected. I am not an Expert in this area, but have setup several ALE Models for my Variant Configuration without any problems. If you could include your EMail Address on your Business Card I could EMail you my instructions. Your Basis person may also be able to help you based upon your Error Message.

Error executing BAPI attached to ALE Distribution Model

Similar Messages

Maybe you are looking for