Inbound IDOC Failing

HI All,
We are upgrading our 4.6C system to ECC6.We have EDI interface.We are sending and receiving IDOCs through Webmethods.
We are testing inbound IDOCs.IDOC (ORDERS03) got generated in webmethods properly, but it got reached ECC6 system with error message 51.
IDOC in ECC6 system didn't created properly.All data segments didn't filled with data.
Can you please tell me, why it got happened?Do we need to change any setting in terms of port defenitions, RFC destinations?
Kindly let me know.It is urgent.
Regards,
Srinivas.

Hi Ramya,
Thanks for your response.
In Biz Talk schema is designed for 700 release idoc.Whereas our system is upgraded to 731 release.
Hotfix is for Biz Talk. Can't we implement any solution in SAP side.
Thanks,
Gowrinath.

Similar Messages

Mails whenevr an inbound idoc fails

Hi Experts,
Is there any way I can trigger mails whenevr an inbound idoc fails to update in r3.With reference to workflow etc
Regards,
Arnab

Hello Arnab
On SAP release >= 6.20 you have the standard report RSEIDOCA available which can be scheduled in background.
Unfortunately SAP did not provide an e-mail notification mechanism for this report but only workflow. For our company I created a ZRSEIDOCA report having this e-mail function. For more details please refer to
ALE Error Message Handling
e-mailing: How to sent out an email to the Managers OUTLOOK express account
Regards
Uwe

Triggering a mail when ever a perticular inbound IDOC fails

Hi Experts,
Is there any way I can trigger mails whenevr an inbound idoc fails to update in r3.With reference to workflow etc
Regards,
Arnab

hi,
i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
regards,
pankaj singh

Inbound idoc failing to reach SAP system.

Hi All,
We are upgrading our SAP system from release 700 to 730. Post upgrade we have identified that idocs which are supposed to reach SAP as inbound are failing in Biz Talk with below message.
Error details: Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDT37003GRP IDOCTYP: SHPMNT03 Release: 700 CIMTYP: . Ensure that your message xml validates against the operation schema.
This happening for only one inbound idoc which is using SHPMNT03 idoc.Whereas other inbound idoc which is using /AFS/ORDERS05 idoc is reaching SAP without any issues. I am bit confused why this is happening for idoc SHPMNT03.
Please let me know your thoughts.
Thanks,
Gowrinath.

Hi Ramya,
Thanks for your response.
In Biz Talk schema is designed for 700 release idoc.Whereas our system is upgraded to 731 release.
Hotfix is for Biz Talk. Can't we implement any solution in SAP side.
Thanks,
Gowrinath.

Send mail to a specific user group when an Inbound Idoc processing fails

I am using standard Message type DEBMAS, but the process code is customed (say ZDEBM as the function module is customed). Can you tell me what configurations are required to activate the error notification message to a user when the inbound idoc fails?

hi,
i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
regards,
pankaj singh

Inbound IDOC for Invoice failing at segment-E1EDK28- Incorrect BankAccNumbe

Hi SDNers,
We have EDI - Invoice/Invoice Processing.
Inbound Idoc failing at segment E1EDk28.
This is because in segment E1EDK28 ,
1. The field ACNUM has the value for Bank Account Number as N111111A.
2. This is incorrect.
3. This field should have had the value for account number as 0000N111111A.
4. But for some reason the pre-zerou2019s are removed .
5. When we check the process code IDOC_INPUT_INVOIC_FI, and IDOC_INPUT_INVOIC_MM, and the table LFBK the value is saved as 0000N111111A.
But why in IDOC it is getting seen as N111111A?
Please guide as to where i need to look for the solution or fix.
Where should i look for the fix for this issue.
Regards,
SuryaD.
Edited by: SuryaD on Nov 24, 2009 7:01 PM
Edited by: SuryaD on Nov 25, 2009 9:21 AM

Hi Navitha,
Thanks for your response.
I had checked the exits to see if the field ACNUM is changed anywhere while debugging.
It wasn't getting changed anywhere.
In fact the user and the ticket creator had the assumption that the Vendor Bank Account number (in case of the Inter company billing) is maintained in vendor master (XK03) or LFBK or KNBK.
the y thought IDOC is picking the ACNUM from one of the above three place.
They were checking the Bank account number from the above 3 places and since here it was maintained as 0000N111111A while in IDOC it was showing as N1111111A they had all this confusion.
In fact the IDOC segment E1EDK28 picks the ACNUM from SPRO->Financial Accounting-> Banking->home bank.
Here we checked and found that the Bank Account Number was maintained as N1111111A and we changed it to 0000N1111111A and the IDOc segment E1EDK28 picked it correctly.
Issue got resolved.
Thanks for your input.
Regards,
SuryaD.
Edited by: SuryaD on Nov 25, 2009 10:29 PM

Inbound idoc ordsp fm:IDOC_OUTPUT_ORDRSP

my problem is that idoc fails when it comes in as a response of ORDCHG when user changes the delivery date in PO outbound idoc triggers with message type ORDCHG. Vendor sends the response as a confirmation of order via inbound idoc message type ORDRSP. it fails at that movement and gives an error ME 790(material number differ from .............) it is comparing the value of segment E1EDP19 qualifier 001 field IDTNR with ekpo-matnr &ekpo-ematn.
NOTE: there is value in segment and it is correct value. but when inbound idoc fails it is taking blank value in fekpo and comparing with ekpo-matnr &ekpo-ematn and giving an error ME 790
and when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully
one more thing i noticed in all failed idoc that segment E1EDK02 qualifier 002 not got populated which contains vendor acknowledgement number.
but when we reprocess it in WE19 without doing any changes it posted sucessfully.
thanks in advance.

You say that "when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully". What about if you reprocess the same iDoc via BD87 ? If you are using the same Function Module, this shouldn't happen, unless you have some very specific userexit code around the user or transaction type.
Cheers, Paul.

Creating Work Flow Item for inbound Idocs

Hi experts,
I'm just trying to create a work item in sap inbox when inbound idoc fails and gets the status 51 .Documentation says no need for any extra setup,it works with standard SAP tasks & Idoc system process codes which are all preconfigured.
I'm assiginig a user id in the partner profile.I do get a work item when there is syntax error in the inbound idoc segments(like wrong sequence of segments...), but not when idoc fails,due to idoc errors.Am i missing something.Users want a workitem when it fails,so they can reprocee/edit etc.Please help.
Thanks in advance,
Rajj

Thanks for the response.I know this task and i could see a event triggered in the event log,but no work item created in my inbox.What should i do to get the work item in my inbox.should i change this task or assign this to some thing else.
Thanks,
Rajj

Handling of Error(s) for Inbound IDOCs

Hi Gurus,
I have an requirement where we need to handle and correct the error if inbound IDOC fails. This inbound will be for Account Document posting.
Please let me know how to handle this issue.
Thanks in advance.
Regards,
Gajanan

<b>Hi,
smells like workflow task.
DI Information
Message type
INVOIC
IDOC type
INVOIC01, INVOIC02
X12 transaction set
810
Edifact message type
INVOIC
Workflow in case of error
TS 0000 8056</b>
Executable program
IDOC_INPUT_INVOIC_FI
Regards,
Clemens

When idoc failes for inbound sales orders then how to trigger a mail notifi

Hi All,
When idoc failes for inbound sales orders in SAP then i would like to send an email notificaiton to particular user id. Could you please let me know the settings for this requirement.
Thanks in advance..

Closing thread as there are no replies

Creation of Sales Order and Service Contract from Inbound IDOC

Hi Experts,
My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
Thanks in Advance.
Regards,
Priyabrata

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

Inbound idoc for updating delivery date of purchase order

Hi All,
Our vendor sends a delivery file consisting of delivery date and quantity(could be partial) for line items of a purchase order.
I need to update the Purchase order line item with the delivery date and quantity sent from the Vendor. It should add a new confirmation line with custom confirmation category in the confirmation tab of the line item in the Purchase order.
Each time we get a delivery file we need to add a new confirmation line in the confirmation tab of the purchase order line item.
How can I get this working using inbound idoc processing? Which Idoc type should I use to solve my issue. Will ORDERSP work for my scenario?
Thank you,
Sonali.

>
sonali ashi wrote:
> We have all EDI set up done for ORDERSP idoc in our system. Problem when I use this idoc type by default system is always adding confirmation catgeory 'AB' but we want our custom category to be added instead of 'AB'.
> Edited by: sonali ashi on Dec 23, 2010 9:47 PM
Confirmation category used for order acknowledgement is define in configuation. You can change that from AB to your custom condition and EDI should pickup that.
SPRO->Material Management->Purchasing->Confirmation->Define Internal Confirmation Category
>
sonali ashi wrote:
> I have also noticed that 'AB' confirmation accepts only full quantity order acknowledgement through Idoc processing.
> Manually I can add a "AB" confirmation for partial quantity but in the idoc processing it fails.
> Edited by: sonali ashi on Dec 23, 2010 9:47 PM
Check tolerance limit defined for confirmation category in 'Conformation Control' Node in SPRO at same level as above.
Regards,
Pawan.

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

Item text not getting copied into sales order from inbound Idoc

Hi All,
I have a scenario where in we get the sales order created through a inbound 850 idoc .
The trading partner sends the sales order information which gets through GENTRAN and gets posted as inbound idoc in SAP .
The problem here is that ,there are segments with values for item text in the idoc ,but the item text is not getting carried over to the sales order which is getting created because of this idoc.
There is no problem with the header text and it is present both at the idoc as well as the sales order level.
I have checked the configuration for text determination and everything looks fine .
Please let me know has anyone come across a scenario like this .This is important as our EDI is getting failed when an outbound 810 is sent from SAP for the simple reason that there is no item text .
Thanks
Sridhar

Hello Sridhar
Do you have access to the genuine 850 EDI message? Does it contain the item texts? If so then there is probably a problem with the (XSLT) mapping EDI 850 -> ORDERS.ORDERS05 IDoc.
Are you able to test the mapping independent of the EDI transmission? This way you could nail down the problem.
Regards
Uwe

Inbound idoc for orders05 to create sales order

Hi all,
I am creating a sales order through idoc (ORDERS05). I am getting a flat file, which is being converted into idoc from XI side and i need to add certain things and validate inside the function module IDOC_INPUT_OREDERS. I am using the exit call customer function '002' (EXIT_SAPLVEDA_002) in it.
My confusion is regarding the population of control records. If some validation fails, i need to set current status as 51. Which field i need to update in this exit in order to achieve this. What are the other control fields that i need to update for an inbound idoc please specify.
Also, i have another doubt, what is the use of DXBDCDATA in that exit. Do i need to do any BDC related work in inbound idocs.
I am new to inbound idoc scenario. But havn't found enough tutorial related to standard idoc generation..
thanks

Hi,
I think, you should fill the validation errors in EXIT_SAPLVEDA_011 (SD EDI Incoming Orders: Final Processing of Internal Error Tables) which subsequently update the status records of IDOC. Check line NO 56 of function module "IDOC_INPUT_ORDERS".
Regards
Vinod

Inbound IDOC Failing

Similar Messages

Maybe you are looking for