Inbound idoc error message

Hello support team,
I am developing a report in which i have to give a select option "date" when i entered the date in this select-option then after executing , the corresponding idoc type, idoc date, idoc number , idoc receiving site and idoc message that appers in Wper is shown.
all the field are from EDIDC, EDID4, EDIDS tables except idoc message.
Please suggest me from which table i found the message field .
EX:
site: 017
idoc number : 6346213
idoc type WPUWBW
idoc date: 07.04.2010
Idoc message: "Delivery completed" indicator cannot be set for item 00018 .
Thanks and Regards,
Preeti thakur

Hi digvijya,
Its an Retail idoc and started with 'W'. These fields has not sufficient use for me. i tried it already.
see this example. i need to fetch this type of error message " Base unit of measure PC or article 000000000002014037 unknown ". please suggest now.
0000000027
idoc type: WPUWBW Goods movements
idoc number: 1760035             idoc date: 07.04.2010
idoc message: Base unit of measure PC or article 000000000002014037
Regards,
Preeti

Similar Messages

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Inbound IDOC error 51 Application Document not posted

Inbound IDOC error 51: Item: 002 Goods/Service number not entered So application document not posted.
Please help me out

hi
check whether service number is available in the idoc if not check the field mapping

Inbound IDoc w/message ORDERS - issues with error processing

We are using inbound IDoc ORDERS05 with message type ORDERS to create the sales orders in SAP. In WE20 we have the following settings:
- partner type LS (= Sales Org VKORG)
- process code ORDE
- trigger by background program
- post-processing agent of type US (user) with a user ID.
We create IDocs through an ABAP program and use RBDAPP01 to post the IDocs. When there is an application error in the IDoc posting we expect the designated user to receive a workflow item in the SAP Inbox, but for some reason this is not happening.
I did some research and went through all the possible settings for workflow, task, etc. and everything seems to be set up correctly. When debugging RBDAPP01 I have noticed that it calls FM APPLICATION_IDOC_POST_IMMEDIAT, which, in turn, calls IDOC_START_INBOUND. If IDOC_START_INBOUND returns SY-SUBRC = 1 then the workflow item is sent correctly to the designated user, exactly as we want. But for some reason it returns 0 (I changed it to 1 in the debugger).
It seems that IDOC_START_INBOUND reads TEDE2 records (TEVE2-EVCODE = ORDE) and sy-subrc = 1 is only possible when EDIVR2 is 1,2,3 or 4. In our case TEDE2-EDIVR2 = 6. It seems that TEDE2 is maintained in the transaction WE42. However, I tried to change the settings there but it affects the IDoc processing in whole (IDoc gets some odd status and doesn't get processed as before). I've also tried to use process code ORDE_BY_WORKFLOW in WE20 with the same "success".
What do we need to do to get a workflow item for the errors that happen in the application layer when IDoc is posted? Is it even possible with this message type?
Any ideas would be appreciated.

Hi,
Can you please share how do you overcome the problem, so that it can be helpful for others.

Inbound IDOC error :51 Passed with out Message Type to ALE Layer

Hi,
I am struct wtih the inbound IDOC scenario ..XI able to send IDOC but at ECC side it is in 51 red status and the error message is
"IDOC passed without Message type to ALE Layer"
Do I need to pass these segment values in Message Mapping? I didnt mapped any MESTYP,SNDPOR,SNDPRT and so on.. disabled these fields...
Could any one light on this issue?
Thanks
Rajeev

>
rajeev raj wrote:
> Hi,
>
> I am passing values in MM as below:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ZPORDCR01>
> <IDOC BEGIN="Constant">
> <EDI_DC40 SEMENT="Constant">
> <TABNAM>Constant</TABNAM>
> <DIRECT>Constant</DIRECT>
> <IDOCTYP>ZOrders</IDOCTYP>
> <CIMTYP>Constant</CIMTYP>
> <MESTYP>Z_Orders</MESTYP>
> <SNDPOR>B0009</SNDPOR>
> <SNDPRT>LS</SNDPRT>
> <SNDPFC>LS</SNDPFC>
> <SNDPRN>PD_100</SNDPRN>
> <RCVPOR>DEV</RCVPOR>
> <RCVPRT>LS</RCVPRT>
> <RCVPRN>Dev10</RCVPRN>
> <REFINT>GB</REFINT>
> <REFGRP>MTI</REFGRP>
> <REFMES></REFMES>
> <ARCKEY>20090909</ARCKEY>
> </EDI_DC40>
> <E1PORDCR SEGMENT="Constant">
>
> I am forwarding these values in MM... IDOC is successfully reaching in ECC but with 51 error in red... Logical system, post and message types are avaliable in Control record of the IDOC which received wiht errors in ECC.
>
> Thnaks
> Rajeev
Fill the TABNAME as EDI_DC40 and Direct as 2 (represents the inbound direction) and resend the idoc and check
Rajesh

Scheduling agreement inbound idoc error.

Hi Experts,
I am creating an Scheduling Agreement with DELFOR02 inbound idoc, while creation the Scheduling Agreement system is giving error regarding Scheduling Agreement not found. In fact I have create the Scheduling agreement by T-code VA31. And I check the table VLPKM, there are relevant record stored.
Then I maintain the view V_T663A to not check everything when inbound idoc recevie. and tried agan in t-code BD87. the system give me another message Make an entry in all required fields.
How can I handle these error messages?
Thanks..
Regards....

Does any one has ideas for that?
Thanks.

INVOICE EDI Inbound IDOC error

Hi,
We have implemented Support pack SAP_APPL SAPKH47027. And now we get
the Following error in IDOC inbound processing message type INVOIC during intercompany billing to post vendor invoices.
Error message: 'Field BSEG-BSCHL (1) (is not an input field)'.
I find that this is due to the OSS note: 960639 that has come along
with this Support pack.
Also SAP has mentioned a corection note to this problem. OSS note:
1032469.
But this Note 1032469 is not clear.
It is mentioned that..
"You explicitly enter the tax amounts in the IDoc
You can enter the tax information either at item level in
segment E1EDP04 or in header segment E1EDK04."
Is SAP suggesting to enter the TAx amounts (E1EDP04-MWSBT)?
And shud the coding be done during the Inbound processing function
module:
IDOC_INPUT_INVOIC_FI or during the outbound processing RSNASTED
(EDI_PROCESSING). We use SAP standard functionality.
Can anybody please explain what SAP has suggested to do techincally.
Regards,
Midhun.

Hi,
I checked both OSS note 960639 & 1032469. I neither find anything in first note ( 960639 ) which could cause this probem nor in the second note ( 1032469 ) which solve this problem. The only way to check is by doing what note 1032469 is saying.
One more thing you can do is debug the code, put the break-pointe message statement and findout where this error message is coming. Then you can check the code to find out the reason for this.
Can you also check if you are getting the same message when you try to enter same data directly in SAP using FB01 or whatever the relavent transaction is.
Regards,
RS

Inbound IDOC error while processing Invoice

Hi All,
I received the following error while processing an Invoice on an inbound IDOC:
Field BSEG-MEINS - does not exist in the screen SAPMF05A 0300
Message no. 00349
Diagnosis
The specified field does not exist on the screen
Procedure
Check your batch input data
Any assistance will be greatly appreciated.
Thanks, Inno

Hi
Please check which G/L Accounts were involved and verify that the Field BSEG-MEINS was set to 'optional' in Transaction OB14. The correct Field Status Variant
for the Company Code can be viewed with Transaction OBY6 and the Field
Status Group for G/L Account can be found with Transaction FS00 under
the Create/bank/inter Tab. This should eliminate the Error 00 349.
Regards
Javier

TS30000020 - IDOC error message

Hi All,
In our production system, we had some workflows got stuck up with SWF_RUN 609 error message. So i tried using SWPC
transcation to resume those workflows. I worked fine. But some did not show up in SWPC and so i used SAP_WAPI_ADM_WORKFLOW_RESUME Fm to resume, it also didnt work. So i searched through sdn and some other sites and found out the standard report "RSWWERRE - Report for restarting workitems with temporary errors", and tried that. My workflows got resumed. But over 2500 new workflow with TS30000020 and description "EDI: Incorrect status for inbound IDoc" got triggered without any agents and it went all users. Iam not aware of IDOC. Can anyone suggest why this has happened and how should i overcome this?
Regards,
Kevin.
Edited by: kevin.jk on Jul 27, 2011 7:54 AM

Hello,
RSWWERRE is normally scheduled to run periodically (usually every 20 mins) to handle temporary errors.
I'm not sure about how these IDOC workflows got started. If they're not necessary then you can logically delete them.
If you look in the IDOC workflows, when does it sya they started? Recently?
regards
Rick Bakker
hanabi technology

Inbound idoc error in the source system

HI,experts
I manually configurate the idoc type ,message type ,etc between the BW system and r/3 source system when the automatic program encouters errors. And the communication between BW and source sysyem seems ok since the source system is activated successfully in BW side.
But when I check the inbound the idoc in source system after i triggerred a full load for the datasource 0FI_GL_4,an error occurs in the inbound process in R/3. There is no control information in the idoc which message type is RSRQST.
how can i figure this issue out ?could anyone help me ?

HI,ALL
Thanks for your replies and documents.
Now I find the problems lies in the error connection between R/3 and BW. IF the autoconfiguration is completelly correct , the table RSBASIDOC in both system should be added one record.But now when the source system is activated successfully ,the table in R/3 side has no entry while the BW side has one entry .juding from this ,there is no BW system connected to the R/3 ,which is proved when I fill the setup table for LO datasource an error message shows that there's no BW system is connected to the OLTP system.
How can i figure this issue out ?If I want to do an automatic configuration ,what shall I do ?

Custom inbound Idoc error handling/ Workflow

Dear Experts,
I have a requirement where in I created a custom inbound idoc, but now i need to handle the errors in the workflow and notify the users thru workflow on an error.
Can some one please provide me a step by step guide on how to create a organizational unit, position and assign users to the position... and any other steps that need to be configured to notify the user on the error.
I'm pretty new to all these organizational uints and workflow related stuff. Any step by step would really be helpful.
Thanks for your time.
-Amit.
Moderator message: sorry, these forums cannot replace proper training, if there is step by step guides out there, then please use the search functions.
Edited by: Thomas Zloch on Oct 31, 2010 11:50 AM

Vittal,
1. If your requirement is for a SAP Standard Basic Message type and a Z extension: Then you simply have to find out the 'Standard Task' associated with basic type. You shouldn't worry about extensions. The standard task will be triggered at input error.
2. If your requirement is for a Z basic type i.e. you have created a customer IDOC for a custom processing: There are many dependencies on how you can achieve this. Firstly, you need to know how you're are processing this Z_IDOC. Are you using a standard FM or custom workflow or custom FM? There should be some triggering event within the processing of this Z_IDOC which will raise a certain flag when the error you want to capture happens (or when there is a generic error). You can configure this event in binding objects to trigger a workflow task. If you take a look at any standard tasks, you'll get an idea how the triggering event happens.
Once the workflow task (you can use custom task or use a standard task i.e. by triggering a standard event within the IDOC processing program) is triggered, you can either send it to SAP inbox, e-mail, trigger another processing etc. This is altogether another story.
So bottomline: For custom IDOC processing, you need to trigger an event when error happens. This can be a custom event or a standard event. This event should be linked to a task (custom/standard - check in SWETYPV). Bind all of these in PFTC. Once the task is triggered, you can do whatever you want to do with it.

Invoic inbound IDOC error.Please help!

Hello:
When I posted AP document by IDOC triggerred by output RD04 in billing document, this inbound idoc always failed with error message:The transaction was terminated by the user.
My message type is INVOIC.
Do you know why this error happened?
Thanks

message is "You are not authorized to use Transaction FB01".So I am wondering if the error message "The transaction was terminated by the user" is also caused by authorization problem.
It seems yes. Why dont you try with proper authorization?
Reddy

EDI IDOC error message

Dear Team,
may I kindly ask you to help me with regard to an error message I am getting for inbound idoc message type INVOIC.
The message is "Field format is incorrect" and 'Field content is incorrect". Segment E1EDS01.
I have tried various ways of fixing this but havent succeeded yet.
Has anybody encountered this problem and how has one fixed it.
Thanks

Hi Dany,
First identify which field value in that segment is throwing the error.
For this, first see which all fields are filled in the error IDOC now.
Then clear all values, and fill same value in one field at at time, and see if IDOC goes into error.
Once you identify which field is having wrong format, you can check in detail.
Regards,
Nisha Vengal.

MRESCR01 inbound IDOC error: "Object type 'TRANSID ' has no relationship '

Hello,
I am trying to get an inbound IDOC from XI to a SAP R/3 System.
It's an extended idoc (MRESCR01) for create orders.
The error at /we02 in the inbound system is:
Object type 'TRANSID ', key '0A1F032A59B345D027B002DE ', log.system ' ' has no relationship 'OUTTID '
Message no. RL007
Diagnosis
All the roles used in relationships of type 'OUTTID' should be found for object type 'TRANSID' with key '0A1F032A59B345D027B002DE' in logical system ''.
System Response
No such roles were found.
Further information:
XI process message succesfully, with the Z segments extended information. But, at the WE02, only one of the 3 extended segments arrives to SAP R/3.
Thanks a lot for your help, best regards

thanks shridar and michal for response.
these solution solved the problem of the segments. now the 5 arrives to SAP R/3.
but i keep getting the error and IDOC is not processed:
IDOC STAT = Status 51
Object type 'TRANSID ', key '0A1F032A59B345D03A7A0A26 ', log.system ' ' has no relationship 'OUTTID '
Message no. RL007
Diagnosis
All the roles used in relationships of type 'OUTTID' should be found for object type 'TRANSID' with key '0A1F032A59B345D03A7A0A26' in logical system ''.
System Response
No such roles were found.
Thanks and best regards,

Workitem not triggered for Inbound IDOC Error (ORDERS05)

Hi,
The work item is triggered for the Syntax Error in the Idoc (EDI: Partner profile Not Available).
But, as per my requirement i need to get the idoc error status (as Workitem) , any help regarding the resolution of this issue is highly appreciated.
Regards,
Rusidar S.

Hi Uwe,
Many thanks for your response, well i did run the report name that you said me.. when i executed that report i got a workitem as "ALARM Message from Active IDoc Monitoring" and workitem for EDI syntax errors"EDI: Partner profile inbound not available"
But my objective remains unsolved.. i need the error status of idoc to be generated, do u have any idea or solutions, kindly share it as its the 3rd day that am still into the same task....
Regards,
Rusidar S.

Inbound idoc error message

Similar Messages

Maybe you are looking for