10-13-2008 2:13 PM
Hi
We are trying to configure the ALE setup.
The data should be transferred to the application directory for the other server.
Have created the file port, but getting the Idoc error 29.
Please can u tell me the steps..
Thanks in advance!
Sushmitha
10-13-2008 2:18 PM
HI,
Status 29 seems to be a ALE Service Error.
Check your FilePort Konfiguration (authorization/space/etc).
and test it with WE19
10-13-2008 2:18 PM
HI,
Status 29 seems to be a ALE Service Error.
Check your FilePort Konfiguration (authorization/space/etc).
and test it with WE19
10-13-2008 2:21 PM
Hi
If we are using file port, then how is the connection between 2 systems done..
Please can anybody let me know the steps..
Thanks
10-13-2008 2:24 PM
Hi,
Please specify your logical system name and RFC destination as same.
so that system can generates some internal communication settings if problem persists check consistency of modelview with BDM5 tcode.
Thanks & Regards
Nagesh.Paruchuri
10-13-2008 2:47 PM
Hi
When checked through BDM5 it is not correct..
I think the configutaion steps are wrong..
Please let me know..
Thanks
10-13-2008 3:30 PM
Hi,
IDoc status 29: Missing or incorrect partner profile
To send an IDoc from the SAP system to the external system, you must define outbound parameters for the message type and all relevant partners.
For more information, see Interfaces ® External Systems ® Configure Warehouse Management ® Communication R/3 -> External System ® Maintain Partner Profile in the Implementation Guide for Warehouse Management.
If the system cannot find the partner (that is, the connected partner system) for sending the IDocs, proceed as follows:
Define the missing partner profile.
Resend all existing IDocs, which the system has not yet been able to send.
For this error, the system triggers a workflow work item for the standard task Output: Error processing with IDoc and sends a message to the inbox of the corresponding user.
You trigger subsequent sending of the IDocs that contained errors from the inbox.
On subsequent transmission, the incorrect IDoc is flagged with status 31 and copied to a new IDoc, which is enhanced with data from the partner profile and transferred to the asynchronous RFC.
Check this.
Rhea.
Edited by: rhea on Oct 13, 2008 4:52 PM
10-21-2008 5:54 PM