IDOC to IDOC Error

Hi ,
I am doing an IDOC to IDOC scenario. Idoc from source system is successfully sent to xi and xi is able to delivery the idoc to the target system. When the idoc is posted to target system the status is 64 IDoc ready to be transferred to application. When I run the RBDAPP01 report it is giving me dump. Find below the dump
Can any one throw some light on it please?
Runtime Errors GETWA_NOT_ASSIGNED
Date and Time 28.09.2007 09:28:27
 Short text
 Field symbol has not yet been assigned.
 What happened?
 Error in the ABAP Application Program
 The current ABAP program "SAPLHRALX00_INTEGRATION_PERSON" had to be terminated
 because it has
 come across a statement that unfortunately cannot be executed.
 Error analysis
 You attempted to access an unassigned field symbol
 (data segment 32785).
 This error may occur if
 - You address a typed field symbol before it has been set with
 ASSIGN
 - You address a field symbol that pointed to the line of an
 internal table that was deleted
 - You address a field symbol that was previously reset using
 UNASSIGN or that pointed to a local field that no
 longer exists
 - You address a global function interface, although the
 respective function module is not active - that is, is
 not in the list of active calls. The list of active calls
 can be taken from this short dump.
 Trigger Location of Runtime Error
 Program SAPLHRALX00_INTEGRATION_PERSON
 Include LHRALX00_INTEGRATION_PERSONF52
 Row 486
 Module type (FORM)
 Module Name IDOC_CONVERT
 Source Code Extract
 Line SourceCde
 456 add_idoc_msg ct_idoc_errors <ls_segment>-docnum <ls_segment>-segnum gc_idoc_warn
 457 'RH_ALEOX_INTG_CP_IDOC_1' 'IDOC_CONVERT/MAPPING'.
 458 CLEAR <ls_segment>-segnam.
 459 CONTINUE.
 460 ENDIF. "mapping
 461
 462 ELSEIF <ls_e1pad31>-sclas = gc_quali AND
 463 <ls_e1pad31>-otype = gc_pernr AND
 464 <ls_e1pad31>-relat = gc_q_cp_subty+1.
 465
 466 <ls_e1pad31>-otype = gc_cpers.
 467 <ls_e1pad31>-objid = <ls_mapping>-objid.
 468
 469 PERFORM idoc_convert_1001_q USING <ls_segment>
 470 CHANGING et_e1p1001_q
 471 et_refobj_q.
 472 PERFORM idoc_convert_5586 CHANGING <ls_segment>.
 473
 474 ENDIF.
 475 * -
 476 WHEN gc_e1p0000.
 477 * -
 478 PERFORM idoc_convert_pa_infty USING gc_cpers
 479 <ls_mapping>-objid
 480 '5580'
 481 space
 482 <ls_mapping>-begda
 483 'E1P5580'
 484 CHANGING <ls_segment>.
 485 * -
 >>>>> WHEN gc_e1p0001.
 487 * -
 488 APPEND <ls_segment>-sdata TO lt_segment_0001.
 489 PERFORM idoc_convert_pa_infty USING gc_cpers
 490 <ls_mapping>-objid
 491 '5581'
 492 space
 493 <ls_mapping>-begda
 494 'E1P5581'
 495 CHANGING <ls_segment>.
 496 * -
 497 WHEN gc_e1p0002.
 498 * -
 499 APPEND <ls_segment> TO lt_segment_0002.
 500 PERFORM idoc_convert_pa_infty USING gc_cpers
 501 <ls_mapping>-objid
 502 '5582'
 503 space
 504 <ls_mapping>-begda
 505 'E1P5582'
Thanks
Mohammad

Hi Mohammad
you should post in the ABAP forum, there is a quick, good answer expectable.
Regards,
Udo

Similar Messages

Error in IDOC-XI-IDOC scenario

Hi folks,
Let me explain the issue. This is an IDOC-XI-IDOC scenario. No BPMs involved. SAX parsing used to parse the IDOCs.
We had around 35000 IDOCs coming in from Brazil system, and they are all stuck in SMQ2 (Inbound queue) in XI. The first message of every queue is in SYSFAIL status, with the status text as Problems found during the EXPORT to specified keyin table.
When I try to execute the queue manually, nothing happens, but an error comes at the bottom of the screen, saying Function module does not exist or EXCEPTION raised.
I checked the dump on ST22, and it shows 130 runtime errors yesterday. The name of the runtime error is EXPORT_TABLE_UPDATE_CONFLICT.
In the what happened? part of the dump, it says Error in ABAP application program. The current ABAP program CL_XMS_PERSIST=============CP had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.
Even SXMB_MONI is not opening (for yesterdays date). When I try to open it, it hangs for a long time, and finally opens an ABAP Runtime Errors page with the runtime error titled as SNAP_NO_NEW_ENTRY and the error short text as Runtime error: Unable to write short dump
Please advise.Thanks a ton!
cheers,
Prashanth

Hello Prashanth,
First of all this is an XI issue and belongs in that forum.
The export problem is typical to situations where your XI DB is out of space/out of table space. Please check with your Basis team.
Function module does not exist or EXCEPTION raised- This message is a standard ABAP RFC message. For an RFC function call to succeed, you need the same RFC function to exist on both systems. However this is probably not the case- it is more likely that you're out of DB space as I already wrote.
Good Luck (don't forget to award points)
Ofer

Error while creating an outbound idoc using idoc type delvry02

hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leo

The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

File to idoc adapter :IDOC IS POSTED IN XI but showing error EDI partner

Hi ,
my interface is working fine but issue is that in Recver R3 system idoc is in errors status 56 (EDI partner profile not available.
I already define business system which is used to send data from XI.
My Business system name is testBsys1 for sender XI service.
In R3 i have created logical system testBsys1
and in we20 already created partner profile testBsys1
and also maintain in bound parameter.
please suggest me where is i am doing mistake.

Hi Mohit,
How is the control record of the posted Idoc made in PI? Check the Control Record of The IDoc that is posted in R3, it is not having correct information.
IF you are not making the control records in PI mapping, then in the receiver IDoc, keep apply control records from payload as checked.
Regards
Suraj

SM58 Error For IDOC to IDOC Scenario

Folks,
I am getting an error in SM58 from Sender system ( IDOC-XI-IDOC Scenario ) IDoc adapter inbound channel: Error Error when reading. The Issue is XI is not receiving any IDOCS. Does anybody know what is the problem
Thanks
Manish

Hi Renjith,
I'm facing the same problem the flow is basically form BW to BO.
When they load the data at sender side the idocs are stucked with error status 2:
"Could not find code page for receiving system" in transaction BD87.
Also when I reprocess it is successful. But its is getting stucked in SM58 with errors like:
1)Error in RFC connnection
2)ERROR REQU_D38IW3WD0XGK1DA48DM96N12J PG# 8 in BW
When I execute it throes an error saying "Function Module does not existsor EXCEPTION raised".
Also are many queues stucked in SMQ1 Outbound.
Please help. Many Thanks.

IDOC-XI-Idoc error in inbound idoc

Hi all.
   We have a Idoc-xi-idoc scenario.
   SAP R/3 - Xi - SAP CRM
   We have configure the idoc out in SAP R/3. And I use we19 to test the Orders Idoc and check the staus is ok.
   But in XI, I cannot see the Orders Idoc is sending in. However, this time I havenot configure any repository and directory.
   My question is , if I havenot configure XI repository and directory, how can I check the Idoc in error messages ? How can I know that the SAP R/3 idoc is sending to XI correctly ?

Hi Jianhong,
plz check SM58 at R/3. Assumedly the IDoc was refused by XI - because of missing Configuration in IB Directory.
Regards,
Udo

IDOCs Packaging ... What if one IDOC is in error in the packet ?

Hi all,
What will happend to the rest of the IDOC in the packet ?
Lets say, i packaged my IDOC in a bunch of 5. The first 3 IDOCs, their payload are ok. However the 4th has a bad payload and it crash in the mapping section ...
Does the first 3 IDOC (and the 5th one) will be sent and the one in error (4th one) will remain (in XI for mapping error) ?
Thank.
michel osborne

Hi chandrakanth.k,
Thank for your response. I have seen these blogs. I am not using the BPM.
I am using the IDXPW + Messages filter (sxmsfilter) to packaged the IDOCs.
I have made some tests ... wird enough ...
test #1:
idoc (1) - error
idoc (2) - valid
idoc (3) - valid
.... etc ...
test #2:
idoc (1) - valid
idoc (2) - error
idoc (3) - valid
test #3:
idoc (1) valid
idoc (2) valid
idoc (3) - valid
idoc (4) - error
In the "test #1", idoc (2) & idoc (3) are processed correctly (idoc sent to the SAP ECC backend system). Idoc (1) is stuck in XI with errror (mapping) which is OK.
In the "test #2", work the same as in test #1, idoc(1) & idoc(3) hs been delivered to the SAP ECC backend system.
However, in the "test #3"all idoc (1, 2, 3,4) are stuck in XI ... idoc(4) in error (which is ok), idoc(1) up to - idoc(3) in sxmb_moni has the racing flag .... but not delivered to the SAP ECC backend system ... they have the status: Message Schedule for outbound side ....
It seem that each time the package end with and idoc in error, the entire batch get stuck in XI .
How can i get sent them (test case #3) !!?!?
Thank in advance !

IDOC Tables with Errors Post System Refresh

Hi Everyone,
Is there any Report or other way through which one can get List of IDOC Tables with Errors Post System Refresh.
Thanks,
Regards,
- Ishan

Hi,
While selecting the Infopackage to run the INIT load, it is taking me to the ECC login screen. Once i enter my credentials, its showing a dump with the message:
Short text of error message:
No RFC authorization for user XXXXX ( RSA8 ).
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "No RFC authorization for user XXXXX ( RSA8 )."
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Please advice.
Regards
sneha

IDOC STATUS 8 error

Hai friends,
We have implemented CRM 2007 in our landscape. The data from 0CRM_SRV_PROCESS_H to 0CRM_PROH got extracted from CRM DEVELOPMENT To BW Development.
But when we try it from CRM Production to BW Production, the error message we get is as follows:
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.
However in RSA3 of the source system, the data is getting extracted.
We need to resolve this issue by today. kindly help.
Regards,
Neha Solanki

Hai,
I checked in SM37 and got the following log :
Job started
Step 001 started (program SBIE0001, variant &0000000000017, user ID ALERMOTE_BW)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0CRM_SRV_PROCESS_H
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 2000000000                              *
abap/heap_area_total.......... 2000000000                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 0 records
Result of customer enhancement: 0 records
IDOC: Info IDoc 2, IDoc No. 37230, Duration 00:00:01
IDoc: Start = 06.08.2008 10:07:44, End = 06.08.2008 10:07:45
Synchronized transmission of info IDoc 3 (0 parallel tasks)
IDOC: Info IDoc 3, IDoc No. 37231, Duration 00:00:00
IDoc: Start = 06.08.2008 10:07:47, End = 06.08.2008 10:07:47
Job finished
This means that the data is not extracted at all.
What do you think ?
Regards,
Neha Solanki

Idoc or trfc error

Hi sap bw'iets
can any one describe step-by-step process to sloving IDOC or TRFC ERROR in production support.
thank you.
regards,
kiran

hi kiran,
sometimes idocs stucks in the source system, so it shows yellow in the monitor even if every thing else is showin green. so to correct this, go to environment -> Transact RFC -> In the Source System. If the status is showing "Executing" then leave it, otherwise u can drag it to BW by selecting execute LUW (F6), by selecting the tRFC.
hope this helps.
Regards,
Purvang
Assigning Point is to say Thanks in SDN *

How to edit inbound idoc with data errors in multiple segments and reproces

Hi friends,
i have a requirement for error handling of inbound sales order(ORDERS04) without using WORKFLOW and WE19.
i have seen some function modules like edic_* ..
but my doubt is how to edit the error data(how can i identify the particular error fileds in the segments)and how to reprocess the same idoc.
Please help me...
Thanks in advance

Hi Narasimh,
Please find the following steps to edit IDOC segment after you find the error using WE02.
The example codes can be found in website
http://www.sapgenie.com/sapedi/idoc_abap.htm
STEP 1 - Open document to edit
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
       EXPORTING
            document_number               = t_docnum
       IMPORTING
            idoc_control                  = itab_edidc
       TABLES
            idoc_data                     = itab_edidd
       EXCEPTIONS
            document_foreign_lock         = 1
            document_not_exist            = 2
            document_not_open             = 3
            status_is_unable_for_changing = 4
            OTHERS                        = 5.
STEP 2 - Loop at itab_edidd and change data
LOOP AT itab_edidd WHERE segnam = 'E1EDKA1'.
e1edka1 = itab_edidd-sdata.
IF e1edka1-parvw = 'LF'.
    e1edka1-partn = t_eikto.
    itab_edidd-sdata = e1edka1.
    MODIFY itab_edidd.
    EXIT.
ENDIF.
ENDLOOP.
STEP 3 - Change data segments
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
           TABLES
                idoc_changed_data_range = itab_edidd
           EXCEPTIONS
                idoc_not_open           = 1
                data_record_not_exist   = 2
                 OTHERS                  = 3.
STEP 3a - Change control record
CALL FUNCTION 'EDI_CHANGE_CONTROL_RECORD'
       EXPORTING
            idoc_changed_control         = itab_edidc
       EXCEPTIONS
            idoc_not_open                = 1
            direction_change_not_allowed = 2
            OTHERS                       = 3.
STEP 4 - Close Idoc
Update IDoc status
CLEAR t_itab_edids40.
t_itab_edids40-docnum      = t_docnum.
t_itab_edids40-status      = '51'.
t_itab_edids40-repid       = sy-repid.
t_itab_edids40-tabnam      = 'EDI_DS'.
t_itab_edids40-mandt       = sy-mandt.
t_itab_edids40-stamqu      = 'SAP'.
t_itab_edids40-stamid      = 'B1'.
t_itab_edids40-stamno      = '999'.
t_itab_edids40-stapa1      = 'Sold to changed to '.
t_itab_edids40-stapa2      = t_new_kunnr.
t_itab_edids40-logdat      = sy-datum.
t_itab_edids40-logtim      = sy-uzeit.
APPEND t_itab_edids40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
       EXPORTING
            document_number = t_docnum
            do_commit        = 'X'
            do_update        = 'X'
            write_all_status = 'X'
       TABLES
            status_records   = t_itab_edids40
       EXCEPTIONS
            idoc_not_open    = 1
            db_error         = 2
            OTHERS           = 3.
Hope this will help.
Regards,
Ferry Lianto

Transfer(IDocs and TRFC) error when use infopackage to load data from R/3

I create an infopackage to load data from R/3, when start immediately ,there is no data transfered. The return error is :
transfer(IDocs and TRFC): Errors occurred
request IDoc: Application document not posted
Does anybody know how can correct this error?
Thanks great.

Hi Yimeng,
Check in SM58 transaction code in R/3 and see if any LUWs are stuck there. If so you can execute them manually and complete the data load.
regards,
Sumit

Transfer (Idocs and TRFC): Errors ocurred

This error occured when we are loading flatfile (trans) into transactional infocube:
Info Idoc 1: IDoc with errors addeed (in red)
Info Idoc 2: IDoc with errors addeed (in red)
Info Idoc 3: IDoc with errors addeed (in red)
Data Package 1: arrieved in BW; Processing: Selected number does not agree with transferred
Info Idoc 3: IDoc with errors addeed (in red)

What other data package errors are you getting? TRy going to a PSA first if you can...I have never tried loading a flat file to a transactional ODS directly.
/smw

IDOC - BPM - IDOC Error --no sender or receiver interface definition found

I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
Sergio

Rajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio

IDOC to IDOC Error

Similar Messages

Maybe you are looking for