ALe Error 29

Hi,
I am trying send Message type PICKSD, I am getting error 29 error in ALE service layer. My partner profile sounds ok. Can Anyone please tell me the possible reason.
Thanks,
Santosh

Hello,
3 main reasons which could lead to such error.
1.No partner profile (outbound parameter) could be found
(Double check your profile information)
2. Define the receivers in your distribution model for this message type PICKSD.
3. The document passed to the ALE layer is addressed to its own logical system SAP0DC4993. In such cases processing of will be interrupted to prevent an endless send loop.
Regards,
Manohar

Similar Messages

About ale error handling in workflow?

Hi,
can any one explian in detail ale error handling through workflow,its urgent for me.
Regards,
phani

Hi Srikanth,
follw the steps it will helpful u,
Pre-requisites.
It is assumed that the reader of this article has some knowledge in SAP workflow BOR objects and ALE Idoc process like process code, Partner Profile etc.
Description
Here, we will be discussing in details the Error handling of an Inbound Idoc through triggering an event, which in turn will be triggering a workflow attached to the workflow.
Steps:-
1.     Create custom BOR object with the events, Start and Stop event
2.     Create a workflow for the error handling, like generating a notification whenever an error occurred in the Inbound Idoc.
3.     Creation of Function Module and attachment with the Process Code
4.     Create the settings for the Inbound Process of the Idoc through the Process Code.
Creation of BOR objects. Go to the[http://www.****************/Tutorials/ALE/ErrorHandling/page3.htm] transaction SWO1.
Enter a name for the Object type and click CREATE button for creating the custom BOR object.
Enter the details required for creating the BOR objects...
Create the Key fields and events of the BOR object.
For creating the Key fields place the cursor on the Key fields and Click on the Create Button
Create events for triggering the workflow and stopping the workflow.
For creating the event place the cursor on the EVENTS and Click the create button like Key fields.
Create two events.
Enter the event name description etc and proceed further to create it.
Similarly create another event for ending the Workflow in the similar manner like that created earlier.
Now, Generate the BOR object through the generate button
Release the EVENTS and subsequently release the BOR object.
After the creation of BOR object
Create a workflow for the generation of notification whenever an error is reached in the Inbound Idoc.
Execute the transaction SWDD.
Click on the CREATE button for creating the workflow for error handling.
Choose the Step type to be inserted for the notification like here we are using Send Mail option for sending a mail to the user whenever any error occurred.
Activate the Workflow and test it whether it is working as per the requirement.
After the successful completion it is required to attach the workflow with the event.
Go to the Header section (Denoted by CAP).
Go to the Start Events TAB.
Enter the details of the event with which the workflow should be linked like the category, BOR object type and the event with which that should be linked.
Enter here the BOR object that has been created and give the name of event created for starting the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Generate the binding and click OK button to save the binding.
Click on Activate / deactivate button for activating the linkage.
After the successful linkage the following sign will appear on the workflow.....
This shows that the workflow has been linked to the event and it will be triggered whenever that particular event will be triggered.
After the creation and successful linkage of workflow with the event it is required it is required to generate a function module and attached it to the process code.
Go to SE37 transaction and copy a standard process code function module to a custom one. Do no delete any parameters from the function module as the SAP standard program itself is calling this.
In that function module do the required validation and whenever the validation fails set a standard parameter WORKFLOW_RESULT to 9999 from within the function module, otherwise normally proceed to set the status to 53.
After the creation of function module it is required to attach it to the process code and corresponding attached to the message type at the Partner Profile stage.
The process code is being created through the transaction WE42
Go to the change mode and click the New Entries button for creating new process code.
Enter the Process Code Name, description and choose the processing type as Processing by function module. Click on the extension button of Identification.
The details for the of the Process Code after clicking the identification button will be
Whenever idoc arrives into the Destination system then the standard SAP triggers the Process code attached to the Message type in the partner profile. The partner profile is being maintained in the transaction WE20.
Since, it is and inbound scenario so the message type and the corresponding process code will be maintained for the Inbound Parameters.
Click on Create Inbound Parameters button for creating new Inbound Message type and the corresponding message type.
Enter the process code for the corresponding message type.
Click SAVE button for saving the changes.
Whenever the IDOC arrives into the target system, it checks the partner profile and finds the corresponding process code. The process code is being linked with the function module through which the IDOC is required to be processed.
Regards,
Phani.

ALE error while posting payroll data

Hi all,
We are trying to set up payroll posting via ALE interface. We have done the following settings
1. Distribution model setup with filters on for standard bapi's
2. Partner profile setup
3. RFC destination setup
When we try to post payroll data,it was returned with the following errors
       RFC destination is not maintained for object BUS6001 and method PRECHECKPAYROLLACCOUNTASSIGN
       The account assignment objects could not be checked
       RFC destination is not maintained for object BUS6004 and method CHECK
       The G/L account could not be checked
We verified RFC destination and it is working fine. I have searched all possible links in SCN, but unable to get the solution.
Can someone help in this issue?

Hi,
Using tcode pc_payresult please check whether the off-cycle payroll is executed again in period 06-2010. If yes then try to post off-cycle payroll separately (PC00_M99_CIPE - Create Posting Run) by entering "Off-Cycle Payroll Run" parameters. May be you will get an error while posting this off-cycle payroll because this payroll is already posted. In this case you will have to reverse the existing off-cycle posting and then post off-cycle payroll again.
Once off-cycle payroll is posted, then you try to post normal monthly payroll.
I hope your problem will be solved by doing the above work out.
Regards,
Waqas Rashid

ALE Error

HI All
This is a very common error and I have searched for the solution in the earlier blogs in SDN.
My scenario is File ( Legacy ) to IDOC ( ECC) using PI. I have done all the configurations and when doing the testing I get this error in SXI_MONI.
unable to convert the sender service to an ALE logical system.
I am using a business service for the sender and a business system at the receiver. For the business system I have done the adapter specfic identifier ( compare the LS with SLD ).
After this I still get the same error. Is there any other thing that needs to be looked into. I am using a Business service (sender ) so do I need to do compare with SLD for the business service also. But if I do the same it says that the LS already exists for the business system and cannot be used again. Please advice.
I also tried using the header
Thanks
Amit

And if the problem is not resolved and your XI is <= SP10 then check:
a) go to the TCODE: SXI_CACHE and check your Receiver Agreements
b) find the one that's causing the problem and check if the header mapping is visible (if you've configured it in your BPM)
c) if not... then probably you'll need to implement OSS note: 791181 (which deals with an error caused by a header mapping)

ALE errored out with error message 127

Hi all,
       We have a process where we trigger an ALE of INVOIC type using output type in invoice document. When I saw some time back, i encontered following error message "
Object 0009543773
Output type: ALE Invoice
B1   ALE group messages   127 No partner profiles (message control) maintained
When I tried today, I am not getting this error. I didn't do any changes. I am worried that this might happen in production as well. I am curious to know why this error happened earlier and why it is not appearing now. Also, a remedy action if this happens in production.

Hi sudhakar,
can u post the solution for this problem pls.so tht it can be helpfull to us.
Regards,
Sameer

ALE Error while sending PO IDOC through EDI

Hi Experts,
                  I am sending one PO IDOC through EDI but I am getting the following error:-
                  Message no. B1130.
                  "Too many recipients found for message type ORDERS in the ALE model"
                  How can I solve this error ? Please guide me in this regards as this is an
                  important issue with urgency.
Thanks & Regards
Jitendra Gujarathi

Please check this discussion thread
Re: Too many recipients found for message type in the ALE model

ALE Error Handling Issues

Hi Experts:
For instance,
A company distribute PO to B company SO by ALE Order (ORDERS).When sales order creating,
IDOC will diaplay error message if some missing in material master ,but it shows 1 issue once only.
Suppose that there are 4 missing in material master causes sales order can not be created successfully,
is it possible IDOC shows all of error messages at the same time that make easy to trouble shooting?

Hi Jeff,
Your concern is right..we must get all the errors at once..
But this is not the right approach..SAP ALe programs written in procedural way..i.e. step by step..
its obivious that if some error in step 1 is coming then step 2 is not possible...so system also stop processing when an error occur..
In many Process codes this has done but they are very few...
so we have to go one by one error..
cheers

ALE - error in custom message type creation

HAI friends,
I am new to ALE IDOC, i am creating custom message type for custom table . i created segment, idoc, message type and executed outbound program . in outbound client, status is dispatch ok. so problem in outbound.
my problem is in inbound . i created one function module idoc_input_zmsg. In test tool for idoc processing ie. TCODE WE19, i clicked my segment and then i clicked the inbound function module button . In function module text box my own function module idoc_input_zmsg is available. but when i click ok button, i am getting the following error.
"INTERFACE FOR FUNCTION IDOC_INPUT_ZMSG IS INCORRECT".
PLS HELP ME . THANKS IN ADVANCE.
WITH REGARDS,
SENTHIL KUMAR.R

All the IDOC processings FMs should have similar interface like this.
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
Check if you have different one. Even if the name of variables is not as above you may get the error message .
Cheers

ALE error - variant LOGSYS does not exist?

In trying to setup ALE within SAP (ECC 5.0) to send a material master IDOC from the ERP to XI. I followed the ALE Quick Start guide and several other resources on the net including IDOC Cookbook and others. When I try to select transaction BD10 (Send Material Master), it returns the following error:
Variant LOGSYS does not exist
The long text is:
Variant LOGSYS does not exist
Message no. DB612
Diagnosis
You selected variant LOGSYS for program RBDSEMAT.
This variant does not exist.
Procedure
Correct the entry.
In trying to narrow down the problem, I created a minimal scenario of just sending the MATMAS IDOC from one client to another on the same system and I get the same error.
My first thought was the logical systems for the two
clients were not setup correctly, but they seem okay. I'm using the 'PRODUCTION' logical system that came with the IDES version we installed (client 811) and trying to send to a new client I setup as logical system VM1CLNT300 (client 300) on the same system.
RFC Destinations test okay, partner profiles, ports, and the distribution model seem okay.
Googling for that error message above produced nothing that I could get an answer from. Any ideas?
Thanks,
-tim

Yes, both logical systems are there. Additionally, each
client has been set to the appropriate logical system:
client 811 -> PRODUCTION logical system
client 300 -> VM1CLNT300 logical system
-tim

EREC: PFAL ALE Error

Hi,
When i do ALE of HCM data to erec system, info type 0006 and IT105 are not being copied over. I get the below error,
Object 01 ,P ,000***1 does not exist: infotype 0006 cannot be created
Message no. 5-105
Diagnosis
You have tried to create infotype 0006 for plan version 01,object type P,object ID 000****. However,the object does not exist.
PA objects exist if infotypes 0000, 0001, and 0003 have been created.
PB objects exist if infotypes 4000, 0001, and 0002 have been created.
PD objects exist if infotype 1000 has been created.
This is confusing as it's saying employee number doesn't exists hence 0006 is not copied, but it also says PA objects 0000,0001,0003 and 00002 are created. Why isn't 0006 and 105 being copied just like other basic info types?
Any help to understand the issue is much appreciated.

You need to first update 0000, 0001, then only the Object type P will be created, P means Person,
Personnel Number will be created only after 0000, and 0001 creation.
After that you can update 0006, and 0105 infotypes.
So In your IDOC first update those segments first (0000, and 0001),
then update 0006, and 0105 infotypes.
cheers
Venu

MASS, MM42(ALE) - error messages

I am updating MARA-LABOR for a number of articles in MASS. There are messages posted in the application log than pertain to checking tables and fields other than the one I have selected for update and related to sites that I do not have access to update.
I am wondering why the program is checking the site data related to the article (tables MARC, MBEW, WLK2 for example) when the table I am trying to update is not site specific.
I know that I can update the authorization profile to clean up the hard error I am getting but I would like to understand why the check is being made. I believe this has to do with ALE Master data distribution configuration but I am not sure.
Thank you.
L

There are some function modules like "KYVA_REPORT_VARIANTS_DELETE or get user variants "RM_GET_VARIANTS_4_REPORT_USER".
- is there any transaction in SAP, which delete the mass variants for reports for all users?
2- I am getting an error An Idoc without a message type was passed to the ALE layer.
I have already check file port is set up correctly and I am passing message type HROT_BRM.
This also happen in previous test, as user does not have the proper authorization, so I assign the authorization and ran it. It worked.
However, this time a user has the authorization and still the error messaging is coming. Am I missing something?

BOM Distribution : ALE Error

Hi Experts,
I'm distributing Materials and BOMs with ALE.
In the Target system, I have the following error (Application Log) :
"Local BOM cannot be changed via ALE".
Please Suggest some solution ASAP.
Regards,
Hemant.

It's a functional error, try to change your bom in destination system manualy by your own to know why you couldn't change it.
If you don't know why, you could ask to functional forum.
Christophe

Customer ALE Error (E1KNATM segment)

I am sending customer master data from one client to another within SAP using standard DEBMAS07 type Idoc.
In the receiving client IDOC fails with error message as 'Invalid date'
After detailed analysis I found that it is due to segment E1KNATM segment (Customer general data tax category) fields wrongly filled. Normally while updating tax category fields like exempted from (KNAT-EXDF) and exempted till (KNAT-EXDT) are left blank. When Idoc is generated for such customer record these fields are updated with value as 00000000 and which fails standard date validation.
Kindly suggest solution for this.
Upendra

Hi Madhu,
I am not using any external system to generate these Idoc.
This ALE is being done within two clients for same SAP system.
Here are the details to reproduce this error.
use transaction BD12
Use any customer for which there is a entry in KNAT table and fields EXDF and EXDT are blank for this entry
Trigger DEBMAS type Idoc for any other SAP client
Check for E1KNATM segment in corresponding Idocs in both sending and
receiving clients.
Fields EXDF and EXDT are updated with values 00000000 which is wrong

Processing ALE Error in Foreground?

Hi All,
I am having problem with ALE doing my trial with PO-SO ALE.
I am creating a PO in one client(800) and it should create a SO in another client(810).
I am able to do the setup. Outbound Idoc generated successfully.
Inbound Idoc was successful to some extent, but it failed after call transaction.
The error message it is telling is "Please enter all the mandatory fields"
When i referred to Arvind Nagpal, for this error message, it is telling to process the idoc in foreground and get to the point where it stuck.
But i am not sure how to process an idoc in foreground. What is the transaction to process the idoc in foreground and how to process it in foreground?
Regards
Mitesh

Hi Mitesh,
There is a little trick to this.
You do this in transaction BD87. Run the transaction and enter the selection criteria to display the idoc. Put the cursor on the idoc in the display, right click and select: Restrict and Process.
You have another selection screen which allows you to further filter the idoc list. Put any further selection criteria you need to reduce the list to one idoc. The important step now, is to uncheck "Import in background". Hit execute.
A new screen appears with the specific idoc. Go to the menu: Edit->Proces->Foreground processing.
There it is.
Occasionally the Foreground processing will be greyed out. That means that foreground processing is not supported for that Idoc status.
Hope that helps.
Brad

ALE - Error - Assign client to logical system

Hi All,
When i am working in ALE [SAP IDES]. In SALE transaction when i try to do ' Assign client to logical system' -
in the second screen 'Change View: clients details' after i give all the details, it's showing error
'An entry already exists in the same key' & the cursor is in the client field [i entered 800 as i m working in client 800],
Kindly help.

Hi,
You did create a client in SCC4.
firstly,
1. did you create a logical system via BD54 and then did you assign that logical system to this newly created client ?
2. did you perform a local client copy to put data into this new client from an old or from a standard client like 000 ?
If you didn't perform above two things, then please do.
Hope it works!!
Regards,
Amruta

ALE error : Maintenance systems not identical

Hi All,
I just configured the ALE settings to send material from client 250 to 214 on the same ECC. When I try to distribute the model I get the error "Maintenance systems are not identical."
What could be the fix for this?

Hi Sakthi,
Refer these links:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/sapR3%2528Idocs%2529ToXI--Steps+Summarized
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Steps to be followed are:
1. Create a Logical system for the sender SAP system and the receiving XI system using Transaction - u2018SALEu2019:
2. Assign Client to the Sender Logical System
3. Create RFC destination of type u20183u2019 for SAP XI system using transaction u2013 SM59 note: Make sure that the name of the RFC destination and Logical system for SAP XI is the same.
4. Create a Distribution Model through u2018SALEu2019 transaction. Create a Distribution Model by selecting u2018Create Model Viewu2019.
5. For the model view created above, add the message type of the idoc that you wish to send using this model view. Select u2018Add Message Typeu2019 option and then specify the sender logical system and the receiver logical system.
6. Generate the partner profiles by selecting the navigation path from the main menu, Environment --> Generate Partner profiles
7. From the main screen navigate through the menu option, EDIT --> MODEL VIEW --> DISTRIBUTE. Upon receiving the message, it means the distribution is successful.
8. Go to transaction BD10 to send a material out of IDES
9. Go to transaction WE02/WE05 to check the status of the IDOC in the sendign system.
Hope this helps
Regards,
Nithiyanandam

ALe Error 29

Similar Messages

Maybe you are looking for