IDOC DELINS Error with Ehp5

Dear experts,
We just have upgraded to Ehp5 and found an issue with standard IDOC segment. In segment E1EDP10 the following 3 fields are missing.
IDNKD_EXTERNAL
IDNKD_VERSION
IDNKD_GUID
As per OSS note 1175343, i supposed to do the following.
Enhance the segment E1EDP10 in transaction WE31:
a) Menu: Segment -> Add version
At the end of the segment, add the following fields:
Field name        Data element
IDNKD_EXTERNAL    MGV_IDNKD_EXTERNAL
IDNKD_VERSION     MGV_IDNKD_VERSION
IDNKD_GUID        MGV_IDNKD_GUID
A new version is created.
b) Release the new version: Return to the initial screen of transaction WE31 (choose "Back").
just to give some more information, we have version 002 before upgrading to Ehp5 and all the fields exist but after upgrading that version is missing.
When i try to add version to the segment, i am getting the following error.
Name range violation : Name E1EDP10 not permitted in CUSTOMER system
Message no. EA269
Diagnosis
An attempt was made to change segment E1EDP10.
System Response
This is not allowed in the current system.
Please guide me to get around with the errors in adding a new version and 3 new fields to it.
Thanks in Advance..
Rajesh.

Hi ,
The Userclone Idoc message type creates users with different roles in receiving systems.
The User data is centrally maintained in teh Sender system from which it is distributed across to various systems.
Transaction SU01 is used to check the Users .
Probably accoring to the error mentioned Users are not created in teh receiving system.Check with Tcode SU01(sender and receiver) and try resending teh Users once again .
Furthermore you may refer these links whcih may be helpful :
http://www.saptechies.com/setting-up-central-user-administration/
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a00a2105-cb48-2a10-26a3-93bb81f3135d
Regards,
Radhika.

Similar Messages

IDoc- userclone05 error with reference user

Hi Guru's
An idoc is in error. message type - userclone , basic type is userclone05.
error - ref user rcf_cand_int does not exist.
the central user is serve ZE2 clnt 050 from where user roles are replicated or users are created in other sstems.
idoc is in server ZS1.
Now can anybody tell me how to check whether this idoc wa creating a user or doing something else.
Regards
Manu
Edited by: Julius Bussche on Feb 6, 2009 3:05 PM
Please use meaningfull subject titles

Hi ,
The Userclone Idoc message type creates users with different roles in receiving systems.
The User data is centrally maintained in teh Sender system from which it is distributed across to various systems.
Transaction SU01 is used to check the Users .
Probably accoring to the error mentioned Users are not created in teh receiving system.Check with Tcode SU01(sender and receiver) and try resending teh Users once again .
Furthermore you may refer these links whcih may be helpful :
http://www.saptechies.com/setting-up-central-user-administration/
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a00a2105-cb48-2a10-26a3-93bb81f3135d
Regards,
Radhika.

File to IDOC scenario : Error with mapping due to Context handling

Hi Experts.
I have a file to IDOC scenario which need your advice.
Source File structure as follows:
Control_Header     <1:1>
Invoice_Header     <1:unbounded)
Invoice_Line          <1:unbounded)
Trailer                    <1:1>
Payload as follows capture from SXMB_MONI
- <Control_Header>
        <Key>999</Key>
        <TransactionID>RCTV</TransactionID>
</Control_Header>
- <Invoice_Header>
    <Key>000</Key>
    <BusinessUnit>HDB05</BusinessUnit>
    <InvoiceNo>64471</InvoiceNo>
</Invoice_Header>
- <Invoice_Line>
      <Key>001</Key>
      <UnitPrice>7.00000</UnitPrice>
      <Quantity>1.0000</Quantity>
      <GSTAmount>0.49</GSTAmount>
      <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Invoice_Line>
      <Key>001</Key>
      <UnitPrice>8.00000</UnitPrice>
      <Quantity>1.0000</Quantity>
      <GSTAmount>0.56</GSTAmount>
      <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Invoice_Header>
      <Key>000</Key>
     <BusinessUnit>HDB21</BusinessUnit>
     <InvoiceNo>6Y0575</InvoiceNo>
</Invoice_Header>
- <Invoice_Line>
    <Key>001</Key>
    <UnitPrice>49.50000</UnitPrice>
    <Quantity>1.0000</Quantity>
    <GSTAmount>3.47</GSTAmount>
    <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Trailer>
     <Key>TRL</Key>
     <TransactionID>RCTV</TransactionID>
     <TotalFeedLine>96</TotalFeedLine>
     <HashTotalValue>212.00</HashTotalValue>
</Trailer>
</ns:MT_EINVOICE>
Mapping as follow:
                                               IDOC
<Control_Header>   ->    <Control_Header>
<Invoice_Header>   --> <Header_Invoice>
<Invoice_Line>      --->        removeContext --> <Line_Invoice>       this is the child node of <Header_Invoice>
<Trailer>               -
>    <Trailer>
The result of the using the above Payload get the following result which not wht I seek
<Control_Header>
<Header_Invoice>
      <Line_Invoice>
      <Line_Invoice>
     <Line_Invoice>   *** This belong to the Invoice_Line of the second <Header_Invoice> at the payload
<Header_Invoice>
     <Line_Invoice>   *** THis segment is empty
<Trailer>
I required the Line_Invoice to belong to the child of the second <Header_Invoice>, I have tried using
removecontext with splitVaue and collaspeContext but to no avail.
May I know what is my mistake on the mapping of the Invoice_Line to Line_Invoice>
Rgds
FNG

Hello,
There should be something that could correlate the Invoice_Header/Key and Invoice_Line/Key. In your example, both are the same for the first and data set. If the sample looks like the one below, it is possible to sort things by correlating the Invoice_Header key and Invoice_Line key
<Invoice_Header>
<Key>000<Key>
</Invoice_Header>
<Invoice_Line>
<Key>000<Key>
</Invoice_Line>
<Invoice_Line>
<Key>000<Key>
</Invoice_Line>
<Invoice_Header>
<Key>001<Key>
</Invoice_Header>
<Invoice_Line>
<Key>001<Key>
</Invoice_Line>
An example mapping could look like this
For Header
Invoice_Header --> Header_Invoice
For Line
/InvoiceLine/Key --> removeContext --> splitByValue:valueChanged --> Invoice_Line
The subfields of the invoice line would also follow a similar logic, you just need to use formatByExample --> splitByValue:eachValue so that the context levels are the same.
Hope this helps,
Mark

IDOC posting error with dollar values

Hello,
We have recently started posting general ledger transactions via IDOC. We just noticed that a few of the idocs reflect a status 53 however did not create postings. When drilling into the message, it says that there were not valid line items. (meaning lines with 0 dollar value). However all of the records had valid dollar values. I have found a few notes that adress this as an issue in 46B, however we are on 4.7 and all of the suggested code fixes have been implemented already. Has anyone seen this happen?
-Jeff

1. Please check that the process code in the inbound partner profile is correct.
2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.
3. If this is also the case, then the function module and the application object type are not permitted for the logical message type, message variant, message function and basis type that are contained in the IDoc control record. You should check whether the correct values have been assigned to these fields in the control record. If they do have the correct values, then the assignment to the function module and the application object type needs to be maintained.
BR,
Alok

Idoc INVOIC - error Tax entry not possible in this item - Message no. FF724

Hello,
I have an idoc in error with the following error message.
In the idoc type INVOIC
Segment E1EDK04:
MWSKZ     N1     VAT indicator
MSATZ     19.000     VAT rate
MWSBT     20.52     Value added tax amount
In OBCD
Partn.Type PartnerNo Tax type Tax rate Cty Tx
LI         FNISL     N1       19.000       V2
Input tax N6 is defined in the system with rate 19.000%
Direction         2     Inbox
Current status    51
Basic type        INVOIC01
Extension
Message type      INVOIC
Partner No.       FNISL
Partn.Type        LI
Tax entry not possible in this item
Message no. FF724
Diagnosis
You can not enter a tax amount in this item since, due to the posting amount entered and the tax code, a total tax amount of zero has been calculated.
This could either be due to the fact that the tax code has been defined with a value of 0%, or because the posting amount entered (that is, the tax base) is too small.
Example:
With a tax rate of 15%, a tax amount greater than zero will only be achieved with a base amount greater than 0.04. With values of 0.03 and less, it is therefore not possible to enter a tax amount.
Procedure
Only enter tax amounts in conjunction with tax codes for which a percentage rate not equal to zero has been defined. Make sure that in documents with several G/L account items you enter the total tax amount in an item with a sufficiently high posting amount.
do you have an idea to solve it?
Regards
Arnaud

Message no. FF724
Check note 681538
thanks
G. Lakshmipathi

IDOC Syntax Error E0072 with status 26 after upgrade to ECC6.0

Hi
We have upgraded SAP R/3 from 4.6C to ECC6.0. After upgrade, when we create PO and output EDI, we are seeing this IDOC syntax error E0072 for Mandatory Segment E1EDK01. In 4.6C it was working fine with no issues, only after upgrade this problem started. It says E1EDK01 is missing which is mandatory. We are using basic type ORDERS01 with no extensions. When we see WE30 it looks fine, WE20 settings looks fine.
Order of the segments got scrambled in upgraded version. First segment is E1EDP19001, this is supposed to be under E1EDP01 segment. There are two E1EDP19001 segments created but there were no sub segments to E1EDP01.
Any help in this regard is highly appreciated.
Thanks
Pandiri

User Exit activation and fixing the issue in user exit fixed this issue.

IDOC is posting with Errors in File to IDOC scenario

Hi,
I did the File to IDOC scenario for CREMAS . IDOC is posting with Errors .. i.e. in the status record it was showing 56- EDI: Partner profile inbound not available ..
If I manually process that IDOC in WE19 , then it was processing successfully.. and in the we19 it was showing Inbound Processing : Port Not Maintained but even though manually it was posting fine...
any ideas regarding this will be appriciated.....
Regards
Babu

Please check whether you had done the following assuming your doing File to Idoc
Settings in your Business service for the receiving system
Please specify the RFC detination, SAP System and Client of the Receiving System in the adapter specific detials.
Settings in R/3
WE20 - Add the partner profile for the particular message type cremas and process code.
Your statement
" and that same logical system name had given as Message Specific Attributes in the Sender Business Sevice parameters in I.D "
Please do mention R/3 Details in the receiver business service or system.
Thnz

Payment requests created from In-House Cash - error with PAYEXT IDOC

Hello -
I am getting getting a '51' error with my inboud PAYEXT IDOC and the payment request cannot be created and the IDOC error is : Error creating the payment requests - no valid payment method available.
I have checked the Route process config in IHC and it looks good (or I think so). I then checked the IHC config: Set Up of payment request for inbound IDOC in FI and am wondering about the Processing Parameters set up. In this config, I see 2 payment methods field (Payment Method for This Payment) and (List of the Payment Methods to be Considered).   Can somebody tell me what's the difference between these two fields and since my payment method is not in the List of PM to be considered, could that be causing my erorr?
Any guidance would greatly be appreciated.
Thanks
Becky

Hi Odaiah
I am in ECC 5.0 and when I view IMG activity IHC_VC_INB_CUST, there's a field called:
Payment Method for This Payment(Payment method used to settle open items)
and another field called List of the Payment Methods to be Considered.
The invoice was paid via payment method 'W' and in our system, we are using IHC to make payments on behalf. So after running F110 for payment method 'W', the IDOC gets created and sent to IHC to process. IHC will then create the payment request (IDOC PAYEXT) which will then get process by F111. Since the IDOC is failing, the payment request is not getting created.   You mentioned to get an ABAPer to throw in debug, I would love to but does not know the program that this process is running through. I tried putting it in debug from WE02 (IDOC processing) but with no success.
Becky

IDoc to Soap, with BPM - Permanent error in BPE inbound processing

Hi Experts,
IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
How to rectify this any issue???
Thanks-
sk

Hi,
The inbound processing encountered a permanent error and the queue therefore stopped.
The error message "Permanent error in BPE inbound processing" may be caused by the following:
- At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
Refer to the help in Note 1082099
- The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
- Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful.

IDOC Error with STATUS 51

HI,
I has a JMS-XI-IDOC Scenario where i has used BPM to get the response from RFC wehre the RFC input is the message from JMS.
The Response Message from RFC is mapped to IDOC .The Scenario is working and the IDOC is getting created in SAP System Iam getting the Error with Status = 51 and the required field LIFNR not found.
Request you to please provide the suggestion whether i need to make any settings to resolve this.
Thanks & Regards,
Y.Raj.

Hi !
Status 51 in most cases is because of lock occured in R3, you can check the kind of error in BD87. If it is a lock error then you can directly say process all
also check in the last page of this URL
http://help.sap.com/saphelp_nw04/helpdata/en/d4/0d67e4d85511d2a6080060087832f8/frameset.htm
Thanks
Edited by: Abhishek Agrahari on Sep 22, 2008 9:54 AM

Status Code 56; Idoc is added with errors

file 2 idoc :
i am getting error 56(idoc is added with errors).
data was picked successfully from legacy system and sent to xi.. sxmb_moni shows success but in target r/3 weo5 shows error 56......plz anyone give me answer//

answered

Idoc delins problem

we are having problem with the idoc delins.
we are using fm idoc_input_delins.
The error we are getting is that "make an entry in
all required fields".
we checked all the segments but all the fileds are filled.
i tried it in bd87 then i got the log as...
190027 51 51 Application document not posted No batch input data for screen SAPMSSY3 0131

Hi Madan,
This error occured due to the BREAK-POINT.
Please remove all the break-points and run the application, then you dont get the error.
Best regards,
raam

IDOC is created with status 51( application document not posted)

Hi experts
iam working on File-IDOC scenario, when i test the process the XML message is created with no errors and
but the IDOC is created with status 51( application document not posted)
the details error shows:
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA01.
previously i used same test data that time it was working fine,
please tell me how can i fix the issue.
regards
vasavi

Key in your Idoc number in BD87, execute
select the error message and then follow the menu path :
EDIT --> restrict and process (Select)
In the next screen UNCHECK the Bkgd Processing and execute
Now EDIT --> Process --> foreground from error or in foreground mode.
This will lead you the screen where it errored out.
Thx
PSR

IDOC AAE error:IDOC_ERROR_PARSE_FAILURE

Hello Gurus,
I am facing following error in IDOC AAE channel scenario is SOAP to IDOC we are using Integrated configuration.I have mapped all the attributes in the IDOC to 1 and date formats are fine.On Analsys i found for the IDOC Field MENGE is not accepting Decimal values when the value 868.000 is passed IDOC AAE is failing with following error.
When i pass with out decimal like 868 Idoc is posting successfully.
using connection
File_http://sap.com/xi/XI/System failed, due to:
com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to
idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException
occurred while parsing IDocXML for type :state=READING_FIELD_VALUE_TAG,
charPosition=441, lineNumber=1, columnNumber=442" tabIndex=0
ti="0" lsdata="{0:'Transmitting the message to endpoint using
connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException:
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE:
An IDocConversionException occurred while parsing IDocXML for type
:\nstate=READING_FIELD_VALUE_TAG, charPosition=441, lineNumber=1,
columnNumber=442',7:true}" ct="TV"
bMarkedAsFocussed="true" bResetTabIndex="true"Transmitting
the message to endpoint <local> using connection
File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException:
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE:
An IDocConversionException occurred while parsing IDocXML for type
<Z2MAK075IDOC>:
state=READING_FIELD_VALUE_TAG, charPosition=441, lineNumber=1, columnNumber=442
I have explored through forum but i didnt find exact solution how decimal values can be handled in IDOC AAE .Please through some light on the issue any help is higly apprecaited.
Regards
Praveen Maareddy

Hi Praveen
Looks like it will not allow dot(.) or comma(,) .
Check this
A numc field will not allow you to post values like '.' or ',' to it. You need to get rid of the decimal point/comma. You can do that by multiplying the value by 100 or 1000... depending on your decimal places. Then it is possible to post that values to a numc field. A numc does allow only the numeric characters from 0 to 9. If this is not what you want (because you are dealing with an characteristic) you need to use a char infoobject or you need to use a keyfigure.
Problem with conversion char to numc in transference rules
You can change the data type of MENGE like below
result TYPE p LENGTH 8 DECIMALS 3.

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML

Hello Rescue Team,
I am facing the following error :\
16.06.2014 23:22:42.164
Error
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.166
Error
MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Exception caught by adapter framework: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
and the payload transferred is as attached in the attachment below.
I have refered various blogs, however I am still not able to understand how to get the exact location of the error location..According to me, the value that is giving trouble is OTH in <BSARK> however I have checked the permitted values for BSARK on ECC and OTH is maintained.
Can you please help how I can resolve this error.
Thanks
Saurabh

Hi Guys,
This is solved..I corrected the date format of the ZZTIME segment from 1157 to 115700.
Thanks
Saurabh

IDOC DELINS Error with Ehp5

Similar Messages

Maybe you are looking for