Error: EDI: Error while assigning IDoc number

Hi Everybody,
using XI 3.0 on Linux 64 bit SLES9 with Oracle I got some probleme sending messages from mq series to sap:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>EDI: Error while assigning IDoc number</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: EDI: Error while assigning IDoc number</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What is missing here?
Kind regards,
Michael

Hi Jayakrishnan,
thanks a lot for your answer.
SM59 is working finde. In IDX1 I got the the correct RFC destination entered and a double click works fine also.
The other way around R3 -> XI -> mq series is working fine. Here we are trying mq -> XI -> R3 and it stops sending from XI to R/3.
How to check the IDOC type?
Regards,
Michael

Similar Messages

Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number

Hi,
I'm attempting to create a simple interface which converts cutomer data from a flat file and loads it into a SAP enterprise system as an DEBMAS06 IDoc type. I am getting the error message Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number in the XI message monitor.
Has anyone come accross this error before and if so, what is the resolution???
Thanks, in advance,
Pete

Hi Peter,
did you fixed it?
How did you?
got the same problem
Kind regards,
Michael

Error when testing the standard idoc number of type PORDCH

while i was testing the idoc message type PORDCH in we02,i have got an error message type saying as
the following below are the steps which i have done in testing the idoc
WE02
Enter Idoc 705556 and execute
Opened status record.
Looked at the error under status 51. it says
An error has occurred assigning data (E1BPMEPOITEM )
Message no. B1527
Diagnosis
To call a BAPI the IDoc data must first be assigned to the relevant BAPI interface parameters.
An error has occurred when carrying out this operation, possibly due to an incorrect data type or data format in the segment E1BPMEPOITEM.
Procedure
Check that the data types in the IDoc data record matches the data types in the BAPI parameter.
You can reproduce the same error with BD87
Enter Idoc number and execute.
Drill down to the error (debug) and click process.
sap has shown the following error message in one of the status record when i tested using transactions bd87 and we02.
so wat must i do ,can i implement the SAP Note 731418 - ALE interfaces for PORDCR1 and PORDCH
are not up-to-date or is there any alternate way
will be waiting for quick and good response
bye.
Regards.
Varma Mandapati

Hi Seeta Ram,
try to reprocess the idoc using the Program
Program RBDMANI2 for status 51 ..
Read the below document for the Possible error
Processing in the Application Layer
The posting function module either calls a standard
SAP transaction, using the call transaction command
for posting the document, or invokes a direct input function module.
The results of the execution are passed back via the function
module's output parameters. If posting is successful, an application
document is created. The IDoc gets a status code of 53 (Application document posted).
If errors occur, the IDoc gets a status code of 51 (Application document not posted).
Regrads,
Prabhudas
Edited by: Prabhu Das on Apr 17, 2009 11:22 PM
Edited by: Prabhu Das on Apr 17, 2009 11:23 PM

Getting error in B2B while processing Revison Number EDI

Hi Guru's
The EDI file being sent to us by our partener has following ISA/GS header
ISA*00* *00* *12*8283234100 *01*041158668 *081103*1315*U*00200*000271883*0*P*>
GS*OG*8283234100*9099751019*20081103*1315*271883*T*004010UCS
We have setup the B2B with reviosin as 04010. For the development phase we were testing with removing the UCS from the header and processing the file
i.e our header looks like
ISA*00* *00* *12*8283234100 *01*041158668 *081103*1315*U*00200*000271883*0*P*>
GS*OG*8283234100*9099751019*20081103*1315*271883*T*004010
Our partner can't truncate the 004010UCS as 004010 and will continue sending the file with GS header having revision as 004010UCS. Issue is when we send the file having 004010UCS transaction gets failed as it doesnt matches the doc revision. Error from the log is
2009.02.05 at 03:57:29:109: Thread-35: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupVersionNumber, val = [004010]
2009.02.05 at 03:57:29:109: Thread-35: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [004010UCS]
2009.02.05 at 03:57:29:109: Thread-35: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Value and doc parameter don't match
due to which I see the following error
2009.02.05 at 03:57:29:121: Thread-35: B2B - (DEBUG) iAudit report :
Error Brief :
5082: XEngine error - Guideline look-up failed.
and
<![CDATA[Machine Info: (soaappcrp1.dpi.com)
Validation of Group parameters failed. Please verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in B2B:
null ]]>
I tried changing the values from current value 004010 to 004010UCS in DC and Business action but still the issue persists. Can you please let me know where else do I need to change the values so that there is no need to modify the file before sending.
Any pointers will be highly appreciated.
Regards
Sahil

Hi Prasanna,
Thanks very much for the reply. But we are genrating the ECS file without ISA/GS headers. If we generate the ECS with ISA/GS header then we will get the following error
<errorDescription>
<![CDATA[Machine Info: (soaappcrp1.dpi.com)
Segment ISA(Interchange Control Header) at guideline position (N/A) is missing. This segment's standard option is Mandatory.{br}{br}This segment was expected after:{br}{tab}Segment Count: 0{br}{tab}Character: 837 ]]>
</errorDescription>
Please refer to our post on forum
Error B2B Segment ISA at guideline position missing
Any thoughts how can we do this.
Regards
Sahil

Getting error code 37 while sending IDOC via WE19

Hello experts,
I am facing a very unlikely error which is preventing me from testing my scenario.
I dont have XI quality server and hence I am using my development server as both dev and quality. Hence I need to connect both dev and quality SAP R/3 system to my XI dev system. While I have done all the configurations in my XI and both SAP R/3 systems, its giving me error when i am trying to send IDOC from quality system.
In quality R/3 i have done the following:
1) Created RFC for my XI dev server
2) Created port for this RFC
3) Created partner profile adding all required IDOCS in the outbound parameters
4) Created distribution channel for all the idocs
In XI dev system i have done the following:
1) Created RFC for both dev and quality of R/3
2) Created port for both the RFCs
3) Maintained the IDOC metadata for both the ports
Now when I am pusing IDOC via dev of r/3 (we19) is working fine but when I am doing the same from quality of r/3 its giving me status code of idoc as 37 that says "An error was identified in the control record while adding an IDoc. The sender port SAPQTY_510 is invalid."
But I have created this sender port SAPQTY_510 in my XI dev system and have also maintained the idoc metadata. I dont know why this error is coming.
Can anyone please point out what mistake i have done or if i missed sometig as I am trying to connect 2 r/3 systems to one XI system.
Its really urgent hence your help will be highly apreciated.
Thanks,
Yash

hi yash,
where you created SAPQTY_510 ,it should be created in R/3 Quality RFC destinations.
In XI DEV create port like SAPxxx WHERE xxx is SID of quality system.
actually we are getting confused.
i guess you used same name SAPQTY_510 in quality R/3 and XI DEV .
In error it says sender port SAPQTY_510 is invalid mean port of Source not XI DEV(receiver).
just try to use some other name say SAPXXX_QUA and confirm the error.
when IDOC is sent to XI DEV ,port of XIDEV SAPQTY_510 has nothing to play any role .
just check whether rfc destination of sender port (QUALITY R/3)you used is of type 3.
so please check at which port error is coming.
Thanks & Regards,
Rama Krishna
Edited by: rama krishna talluri on Mar 5, 2008 10:02 AM

Error Mssg: FI673 while assigning company code to FM area

Hi,
I have multiple company codes and only one company code (A) is assigned to FM area and another company code (B) is not assigned to FM area but some transactions have already been posted in dev client, I got the following error message while trying to assign the company code B to the same FM area.
"You must not change assignment to company code B
Diagnosis:
There is already actual data for FM area, which is assigned to company code B"
Please note that I have already deleted the FI transactions for company B thru t-code OBR1 but unable to delete the CO transactions as multiple company codes assigned to one CO area.
Please let me know how to overcome this issue of assigning the company code B to FM area.
Thanks
VS

Hi,
check SAPNET note 1502436 maybe its helpful.
Best regards, Christian

Error in gl while assigning po

hi Friends..
good morning..
need help..
while generating PO-service , and assigning gl account and cost center (mkc1590 ) an error was encountered..
" 459000 for 18.06.2009 as a cost element in controlling area 1000"
regards,
rashmi

Hi Rashmi,
If it is already a cost element, you can check the dates for which it is created.
Thanks,
- Mahak

Error on WebMetods while calling IDOC Adapter

Folks ,
I am facing a problem calling IDOC adapter from WebMethod, I have all the configuration in ID and IDX1 .
This is the error:
<i><b>com.sap.mw.jco.JCO$Exception: No Service for system QUANTUM1, client 902 in Integration Directory</b></i>
Regards,
Manish

Hi,
did you create it exactly as specified:
http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/content.htm
for QUANTUM1 and 902?
I'm not sure what the ID of the system if the system
is not the SAP...
maybe you can just post the idoc via http adapter?
REgards,
michal

Error While assigning points

I am getting the following error for the past 2 days, while assigning point and closing the tread.
An error has occured while assigning points. Please refresh the thread view and try again
a®

I think we are facing this problem from almost last 4 days.
Even the display of forum points looks 0 which doesn't look good.
Hope somebody from the technical team is working on it and try to
close the same at the earliest.

Error while assigning the Position through Hiring

Dear all,
I am getting error "Time constraint" while assigning a newly created Position.
it says "Position cannot be assigned to two employees".
However when I checked through PO13 no person is assigned to that position.
so please suggest.
Regards,
Krishna.

Hi Krishna,
Please check first only one org unit is assigned to positon. Check in PP01 if the position has any A008 relationship.
The time constraint set up for relationships between persons and positions (subtype A008) only allows you to assign one position to on person at a time.
Set the time constraint for relationships between person and position (subtype A008) to 3.
Check the time constraints of the object type through table T77ZR.
Regards,
Supriya

Process AGREEMENT_CREATED not assigned to number type in version AGREEMENT_

HI:
Create a contract, error:
Process AGREEMENT_CREATED not assigned to number type in version AGREEMENT_CREATED .
Everyone, please help me.
Thank you!
Sarah

hello Sarah,
Is it a SRM standard system or activated PPS also. Which version of SRM are you on.
The error message you are getting during contract creation, because the numbering type is not correctly defined.
might be you need to look into this customization.
Cross-Application Basic Settings--> Configurable Item Numbering --> Define Configurable Item Numbering Scheme

Error:- How to assign Partner Number (KU) in R3 System [Idoc(KU) to File]

Hi ,
In Idoc to file Scenario (KU to LS), how to assign Partner numbe (KU) in R3 Sender system.
I m getting below error:-
No partner profile (outbound parameter) could be found using the following key:
Do the needful.
thanks
Anshul

Yes, I have the partner profile maintained in we20 of type KU
In We19, it is showing error:-
No partner profile (outbound parameter) could be found
For Example- For Logical system it is possible through SALE

Error while assigning dates to associative array of date type

Hi All,
I am facing the issue while assigning dates to associative array of date type:
Oracle Version:
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE    10.2.0.1.0      Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
Stored procedure i am trying to write is as following
create or replace procedure jp1 (
p_start_date date default trunc(sysdate,'MM')
, p_end_date date default trunc(sysdate)
is
l_no_of_days number;
type t_date_id is table of date
index by pls_integer;
l_date_id_arr t_date_id;
begin
l_no_of_days := p_end_date - p_start_date;
for i in 0
.. l_no_of_days - 1
loop
    l_date_id_arr := p_start_date + i;
    dbms_output.put_line(p_start_date + i);
end loop;
end;
I am getting error at line 14 while compiling this. and the error message is as following:
Errors for PROCEDURE JP1:
LINE/COL ERROR
14/5     PL/SQL: Statement ignored
14/22    PLS-00382: expression is of wrong type
So while investigating this i tried to output the value of (p_start_date + i) using dbms_output.put_line and the output is date itself.
create or replace procedure jp1 (
p_start_date date default trunc(sysdate,'MM')
, p_end_date date default trunc(sysdate)
is
l_no_of_days number;
type t_date_id is table of date
index by pls_integer;
l_date_id_arr t_date_id;
begin
l_no_of_days := p_end_date - p_start_date;
for i in 0 .. l_no_of_days-1
loop
    --l_date_id_arr := p_start_date + i;
    dbms_output.put_line(p_start_date + i);
end loop;
end;
output of the
exec jp1
is as following:
01-DEC-13
02-DEC-13
03-DEC-13
04-DEC-13
05-DEC-13
06-DEC-13
07-DEC-13
08-DEC-13
09-DEC-13
10-DEC-13
11-DEC-13
12-DEC-13
13-DEC-13
14-DEC-13
15-DEC-13
16-DEC-13
17-DEC-13
18-DEC-13
I see the output as date itself. so why it is throwing error while assigning the same to associative array of date type.
I tried to google also for the same but to no avail.
Any help in this regard is appreciated or any pointer some other thread on internet or in this forum.
Thanks in advance
Jagdeep Sangwan

Read about associative arrays :
create or replace procedure jp1 (
p_start_date date default trunc(sysdate,'MM')
, p_end_date date default trunc(sysdate)
) is
l_no_of_days number;
type t_date_id is table of date
index by pls_integer;
l_date_id_arr t_date_id;
begin
l_no_of_days := p_end_date - p_start_date;
for i in 0..l_no_of_days - 1
loop
    l_date_id_arr(i) := p_start_date + i;
    dbms_output.put_line(p_start_date + i);
end loop;
end;
Ramin Hashimzade

Error while Reading Idocs from ECC 6.0 to Sun IDM .

Hi Gurus,
We have a scenerio where we have to update the Sun IDM Server with all the changes in HR Data happening in ECC.
For that... we have
1. Created a Logical System for Sun IDM server, Port, RFC Connection (TCP/IP).
2. Assigned Partner Profiles, Distribution Model etc. for msg. type HRMD_A ;
3. We have created a Communications User used by the IDM server to connect to ECC.
Idocs are created daily and are in status 03 - Data passed to Port OK !
and on the In Sun Identity manager 8.0 we have created SAP resource adapter for ECC 6.0,
after giving resource parameters our test connection is successful.
We also changed edit synchronisation policy for the same but when we start synchronisation in IDM, it is unable to read any idocs although Idocs are generated in SAP .
Log file gives the message as "Incoming IDoc list request containing 0 documents"
We also have one more error ;
some times while doing a connection test : JCO.Server could not find server function 'åäåä¹'
while most of the times the connection is successful.
Please suggest .

Hi Gurus,
The error got resolved .
The changes in the settings i did :
SAP SIDE : Made the RFC Connection Unicode.
IDM SIDE : Checked on the "SAP Server Unicode" checkbox; while doing the HR Activ Synch Settings.
This Resolved the error.
regards
Vaibhav

Error while processing Idoc - Urgent!

Hi all,
I am getting the following error while processing the IDOC :
"Application Document not posted "
Status = 51
Error Details :
" V51VP - item was not found - process cancelled ".
Any ideas, what's wrong?
Please Help.
Regards,

Hi,
U might be not passing any item value to idoc which might be necessary...wat u can do is
goto WE19 TCODE,give the error idoc number and press execute button,now in the next screen CLICK ON INBOUND FUNCTION MODULE in the application tool bar,now give the FM NAME which triggers teh idoc,check the check box IN DEBUG MODE and radio button IN FOREGROUND....Now it will take to inside of the FM ,now debug and see where it caught the error..
Regards,
Nagaraj

Error: EDI: Error while assigning IDoc number

Similar Messages

Maybe you are looking for