Idoc Failing With IDOC_INPUT_ALEAUD

hi
Trying to post an idoc from XI to R/3 system. The message has succesfully come into XI, but in R/3 system it is showing with error "Function module not allowed: IDOC_INPUT_ALEAUD"
Could someone help.
thx,
Pradip

hi Pradip,
If you send and receiving are both SAP system you can configure the IDoc ack. This quide will help you do the same
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Regards
Ramesh P

Similar Messages

IDoc failed with the error massaeg "Instance of object type could not be ch

Hi All
I am getting IDoc failed with the error massaeg "Instance of object type could not be changed"
Message type :PORDCR
Basic type : PORDCR05
Message no. BAPI003
Status : 51
All POs are get uploaded in SAP during Cut over activities only.
Please suggest on this.It will be a great help.
Thanks
Ajit

Hi
After uploading POs into SAP we are changing quantity and value in PO in Legacy system, and for this all IDocs are failed, subsequently these changes are not triggering to ECC.
Please help
Thanks
Ajit

Idoc failed with status 51 for Warning/Information messages

Hi All,
We are trying to create some Sales Orders with the help of Idocs. We are facing some problem as mentioned below.
1.There are some warning messages/information messages written in standard Sales Order User Exit USEREXIT_SAVE_DOCUMENT_PREPARE
2.As soon as the Idoc processing reaches any of these messages, it considers them as ERROR message and Idoc fails with the status as 51 which is not expected.
3.Also, I see that the Sales Order is saved with the data that has been passed in the Idoc.
Is this the standard behavior ?? (Or) Is there any EDI related configuration setting which can be used to suppress these kind of messages in Idoc Processing ??
Any help on this would be highly appreciated.
Thanks,
Babu Kilari

if your IDOC has status 51 then it is not posted, hence your sales order cannot be created from this IDOC. of course this error behaviour can be originated by the user exit.
please read OSS note Note 747631 - Some tips when testing idoc_input_orders

Inbound BOMMAT idocs failing with MSG BOM 023

We're taking in BOMMAT idocs into an ECC6.0 system from an external system and I have some failed idocs with message BOM 023 - local BOM <material> <plant> <alternative> cannot be changed via ALE.
We're doing create and change functions - this one is a change with MSGFN = 005
There are no multiple BOMS, alternative 1 the only 1.
I haven't been able to find any sensible explanation for this message and I haven't seen it before . Can anyone throw any light on it?
Thanks,
Jonathan

Hi Jonathan,
You are trying to change a BOM on SAP that was not initially transfered-created via the interface. Instead it was firstly created manually on SAP. For this reason you get the message for local BOM that cannot be changed via ALE. You can also confirm this also by the ALE indicator on BOM header (field STKO-ALEKZ for the given BOM).
Br,
Petros

IDOC Failed - Error massage Deficit of PU IR quantity

Hi
I am getting IDoc failed with erros massage "Deficit of PU IR quantity "
What could be the reason.pleaseadvice.
Thanks
Ajit K Barik

You need to provide more detail e.g. IDoc type, message number etc. Look at the data in the IDoc and try posting a document based on this. Usually you will get the same error and understand why you are getting it.

Email on Idoc Failure with Status 56 64 68 69 70

We have standard inbound idoc processing for Basic Type : DELVRY01 and Message Type : DESADV using the function module IDOC_INPUT_DESADV1.
We currently have a requirement to send an email, when any of these type of Idocs fail with status 56, 64, 68, 69 and 70.
Where would be best place to provide this solution to send an email to a particular user when the Idoc fails with the above status?

Hello Saleem,
One approach would be to consider workflow based on object type IDOCAPPL. The start condition for the workflow could be the triggering of the event errorProcessCompleted. You could filter further by status and your message type (DESADV ) to only start the workflow for the errors that you mentioned. The workflow could then send an email.
You will need to verify the details for your own scenario.
Good luck,
Greg Kern

RSEOUT00 failing with "Could not write IDoc to file" TPRI_DEF table

Outbound Idoc processing fail with the following error:
Could not write IDoc to file
Message no. EA299
Diagnosis
The system could not convert data from the data record 000027.
Procedure
Check the port definition of the receiver port.
You can use the "Continue despite conversion error" option to write the IDoc to the file from transaction BD87 with replacement characters.
Short dump indicate that there is a some junk character in th e TPRI_DEF for program SAPLSPRI that it is unable to convert.
I have set the flag on the we21 port to "continue despite conversion error" and that seem to help, but I would like to figure out how to fix the junk characters from coming through from the TPRI_DEF table.
This is what shows up in the short dump after RSEOUT00 is run.
TPRI_DEF                                   / /       : :     00002932
    010GV21            \0\0\0\0\x0006āȂ耀㐱〲\0\0嬇\0ሟ鴂푎眩\x0802儔잏퉓
I do not see any entries for area "GV" in the table, there is one for "GF". which has no user assigned to it and it is of key version 21.
I am not sure if the table is supposed to have an entry with no user assigned?
thank you for looking at this issue .

HI Jurgen,
we have the same issue, chinese charecter is in PO text header. so facing error. If we click unicode format then it works fine as my testing in development.
I just want to knom what is the impact if i clicked directly unicode format ?( with refernce to your reply above " have you set the Unicode format flag directly above in WE21?" )
I doc is going from SAP sytem - (PO information )
Pls adivce..
waiting for your reply..
Thanks in advance

SAP_XI_IDOC/IDOCXmlToFlatConvertor fails with Enhanced Idoc

Hi All ,
We have used the PI conversion module SAP_XI_IDOC/IDOCXmlToFlatConvertor in a number of Idoc-To-FlatFile scenarios and it is working fine.
However recently we tried to use it in a scenario where the target file structure is that of an enhanced Idoc.
In this case, the receiver channel (where the module is configured) fails with the error message, Idoc metadata not available in ECC.
We have tried the following:
1) Checked NWA connection for RFC Destination and JCA connection factory : Working fine.
2) Loading Enhanced IDoc in IDX2: Working Fine.
3) Change the receiver agreement to point to a Standard IDoc instead: Working fine.
Have any of you been facing the same issue and/or could you guide us to a possible solution.
Thanks,
Abid Ali

Hi Ali,
We are also facing exactly the same issue with a custom IDoc while converting on the receiver side.
It is actually interesting that the module "SAP_XI_IDOC/IDOCFlatToXmlConvertor" works fine for the very same idoc and fails to recongize the metadata information while converting from Xml to Flat.
Did you have any luck in getting this resolved?If so,can you please provide the details.
Thanks
Narendra

IDOC is Getting Fail with - 56 Status EDI Partner profile not available

Hi,
I am trying to Post invoice Data into IDOC on ECC Side.
My Scenario is File u2013 XI u2013 ECC(IDOC).
But It is Getting Fail with 56 Status u201C EDI: Partner profile not available u201C
On Control record I am getting this
Port                      BLANKKKKKKKKKK
Partner Number              CLNTDEC110      Logical system for Client
Partn.Type       LS                    Logical system
Function                                  BLANKKKKKKKKKK
Port                            SAPDPI
Partner number             CLNTSAMPLE
Partn.Type                      LS         Logical system
Partner Role                   BLANKKKKKKKKKK
My configurations are Like this :----
On ECC Side MY SID is DEC
On ECC side I have two logical system in CLNTDPI100 for PI
                         CLNTDEC110 for ECC.
I have Partner profile on ECC system on CLNTDPI100 logical system    - we20
Added message type in inbound side of partner Profile (INVOIC-INVOIC02)
ON SAP PI/ XI System MY SID is DPI
IDX 1 has Port name SAPDEC
On Message mapping EDI_DC40 is mapping with constants with below given value
<INVOIC02>
   <IDOC BEGIN="">
      <EDI_DC40 SEGMENT="">
         <TABNAM> </TABNAM>
         <DIRECT>2</DIRECT>
         <IDOCTYP> </IDOCTYP>
         <MESTYP>INVOIC</MESTYP>
         <SNDPOR>SAPDPI</SNDPOR>
         <SNDPRT>LS</SNDPRT>
         <SNDPRN>CLNTDPI100</SNDPRN>
         <RCVPOR>SAPDEC</RCVPOR>
         <RCVPRT>LS</RCVPRT>
         <RCVPRN>CLNTDEC110</RCVPRN>
      </EDI_DC40>
Regards
PS

Check the following :
in We 02 which partner number is displayed just in the posted IDOC -> 2nd coloum in the IDOC list .and verify if the
same you have in Partner profile. Actually this details comes from ECC business system's logical system name which you give in SLD.
in we 19 - take the error iDOC numner and open the IDOC ->click on the first line -> check entries as you mentioned
above sender port should be PI port not empty.you need to check the partner profiles properly
follow these steps
1. create a RFC destination of tyoe H for Pi system- 2. create a Port and assigen the RFC destination to it
3 create logical system for PI BD54 PICLNT001 say , 4 with the same name create a partner profile in We20
    in parter profile maintain the inbbound message parameters and add the PI port as receiver port in it .Give the basic type also .
now
for sender details in ur case PI : u have port (defined in PI IDX1),patner number (LS defined in ECC PICLNT001), parter type LS.
for receiver you have port defined (as above), partner number the logical system for ECC system.
in we 19 ,, edit the control record as above and go to the tab inbound processing and test the internal posting
it should work fine. in the adapte specific attribuet for receiver ECC system , maitain the same LS name , if any wrong entry is
there then change the LS in sld to poing to correct LS/
refer this
http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/technology/sap/26/
Regards,
Srinivas

Automated error email notification when outbound IDOC fails

Hi,
The requirement is that whenever the outbound IDOC of message type PAYEXT, basic type PEXR2002, fails, then email has to be trigerred to a group id.
I had suggested to write a report program that runs as a job. If the IDOC goes to error status then mail will be sent from this report. Client prefers it to be done through workflow.
There is a standard process code for outbound IDOC failure handling EDIO (we40). standard task 7989 has been assigned to this process code. I dont want to modify this standard task as I am not sure of impact.
Terminating event for this task is 'ERRORPROCESSCOMPLETD'.
I have developed the workflow that has trigerring event 'ERRORPROCESSCOMPLETD' and bound with the IDOC number. This will send mail to the group id with the IDOC details
Now issue is that, I am not sure if standard process EDIO will be trigerred automatically, or should we configure anywhere. Since this is standard outbound IDOC, I am not able to add the process code in partner profile.
Please give your inputs or any other alternate solution to send mail through workflow when outbound IDOC fails.
Thanks in advance.

Hi,
I guess in your outbound partner profile for PAYEXT. you need to add process code EDIO in message control TAb. WHich will cause to trigger the workflow which will send the notification.

Confirmation Idoc failed

Hi
The Idoc related to Goods confirmation has got failed with error "Account xxxxx requires Trading partner", we checked the trading partner settings of the relavent GL account, it was not maintained. But for those Idocs which were sucessful also there was no Trading partner defined. Please advise ASAP.
Regards / Shekhar

Hi
Which SRM and R/3 versions are you using ? Which Support pack ?
When are you getting this error ?
<b>Please go through the OSS Notes below -></b>
Note 356665 - BAPI BAPI_GOODSMVT_CREATE: Add. import parameters
<u>Related Notes</u>
833603 - EDI: Goods receipt for stock transport order
398801 - Missing import parameters for BAPI BAPI_GOODSMVT_CREATE
388601 - Follow-up processing for GR/SE confirmation is not possible
375570 - No inventory transfer posting of decentralized WMS
358454 - Redesign: Delivery document flow for goods movement
339567 - MIGO: Unloading point/goods recipient not copied
Do let me know.
Regards
- Atul

Attempt to process file failed with Exception in XML Parser-format problem

Hi all,
Iam getting an unusual error in the J2EE stack in XI.
And the message is:
006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)' 2006-11-30 17:31:07 Error Exception caught by adapter framework: null 2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
My scenerio iam posting IDOC to a flat file with content conversion in the receiver side,the mapping got executed successfully and in the audit log i found that the error was after the 'Start converting XML document content to plain text'.
This means that error occured during content conversion of XML to the prescribed file format.
Can anyone suggest any better approach using which we may trace the junk data in IDoc. Manual adhoc approach could take time and is error prone.
Thanks in advance...
karun

Hi Bhavesh,
Thanks for the early reply. I checked the mapping and everything is fine and the output is also in valid XML format.
The audit log shows that the mapping got executed successfully and the error is after the step 'Start converting XML document content to plain text '. Is there any constraint in the file adapter regarding the message size for parsing.
2006-11-30 17:30:50 Success Transfer: "BIN" mode, size 2912595 bytes, character encoding -
2006-11-30 17:30:50 Success Start converting XML document content to plain text
2006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)'
2006-11-30 17:31:07 Error Exception caught by adapter framework: null
2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2006-11-30 17:31:07 Success The asynchronous message was successfully scheduled to be delivered at Thu Nov 30 17:36:07 GMT 2006.
2006-11-30 17:31:07 Success The message status set to WAIT.
2006-11-30 17:31:08 Success Acknowledgement creation triggered for type: SystemErrorAck
2006-11-30 17:31:08 Success Acknowledgement sent successfully for type: SystemErrorAck
2006-11-30 17:36:08 Success Retrying to deliver message to the application. Retry: 1

Info IDoc received with status 8 in BI but Data available in source system

Hello Experts,
I am loading Budget Period (attributes) into PSA in BI.
Budget Period data Loading Issue : No data available while loading. But source system ie ECC has data in that data source
Data source: 0PU_BDGTID_ATTR
This is full load.
I checked that whether I am making any mistake during data selection. I could not find any issue. Message while loading data into PSA (Yellow Traffic light)
No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Already looked this thread and googled also.
Re: IDoc received with status 8.
Check points:
sm58 - NO issue
BD87 in ECC (RSINFO Idoc status: 03) -sucessful
BD87 in BI (RSINFO Idoc status : 53)
ST22 - NO issue
sm37 - Job is successful (I could see Idoc no in ECC source system in Job log)
I am not sure if I am missing any thing.
Thanks
Rana

Hi all,
I've got exactly the same issue with several extractors. I'm inialising the Master Data in a all new system, in the Quality the loads succeeded but in Prod it failed.
For instance with the basic DataSource "0FUNCT_LOC_TEXT", I've made the following test:
RS3 (R/3) - > 0 data
ST22 -> no short dump
WE05 (Idoc) - > everything is ok
I reactivated the Datasource in R/3 (RSA5) and then deleted it and replicated it in BW but the same issue occured.
Any ideas?
Thanks
jak

RFC Lookup's in message mapping fail with RuntimeException for no reason

Hi guys,
We have developed interfaces that execute a lot of RFC's from Message Mapping, by making use of RFC Lookup API.
In ID, in the corresponding RFC Receiver Communication Channel we have set the number of maximum connections to 100.
However, when a big number of Idocs with lots of items is sent to XI some messages fail in XI because mapping fails with a runtime exception that is not correct, since there is a return value found from the execution of the RFC function. And when I am testing the mapping in Test mode of XI IR, the mapping is executed successfully.
Do you think that by increasing the maximum number of connections in Communication Channel, it will take effect?
Evaggelos

Hi Evaggelos,
DECREASE, may be til 10.
Regards,
Udo

BPM where if a Idoc fails i need to resend it

hi all
I need to have a BPM where if a Idoc fails i need to resend it ..on the receiver side i m having a SOAP Adapter...
How can i do it...?
thanx
with regards
shivanjali

Hi Michal
The receiver application is just returning an error message (e.g. locked) and expecting XI or ALE to deal with it.
Do we have to use BPM like for certain errors we re-submit message a number of times with a delay, and for others we raise an alert. any alternative for BPM by ALE ?
With Regards
Shivanjali

Idoc Failing With IDOC_INPUT_ALEAUD

Similar Messages

Maybe you are looking for