IDOCs in trfc with status text as error

Hi,
I have IDOCs in trfc queue with status text as 'The ABAP/4 Open SQL array insert results in duplicate database records'.
How to reach this error point and rectify the same.
Regards,
Sheetal

Hi Sheetal,
Please refer the link,
Successfully posted IDOC from XI but not reflected in Receiver R/3 system
Best Regards.
Reward points if it is useful.

Similar Messages

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

No session found with status "New" or "Error"

Hi,
I put the statement after the CLOSE GROUP to process the BDC automatically:
SUBMIT RSBDCSUB AND RETURN
 EXPORTING LIST TO MEMORY
 WITH MAPPE = SESSION.
 WITH VON = SY-DATUM
 WITH BIS = L_NEXT_DAY
 WITH Z_VERARB = 'X'
 WITH FEHLER = ' '.
And when I ran it I got an error that says
No session found with status "New" or "Error"
When I go to SM35, I see the session in the 'New' tab. How can I get this to process completely without manual intervention or first thing first no error from running the program?
Thanks,
Will

Hi Rob,
I will try the COMMIT. I think because I processing mutltiple GS01 transaction in one program.
Hi Sudheer,
I am actually usinng the INCLUDE that was given to me when I did the recording. Here is the complete code from the include.
***INCLUDE BDCRECX1.
for programs doing a data transfer by creating a batch-input session
and
for programs doing a data transfer by CALL TRANSACTION USING
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS SESSION RADIOBUTTON GROUP CTU. "create session
SELECTION-SCREEN COMMENT 3(20) TEXT-S07 FOR FIELD SESSION.
selection-screen position 45.
PARAMETERS CTU RADIOBUTTON GROUP CTU. "call transaction
SELECTION-SCREEN COMMENT 48(20) TEXT-S08 FOR FIELD CTU.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) TEXT-S01 FOR FIELD GROUP.
selection-screen position 25.
PARAMETERS GROUP(12). "group name of session
SELECTION-SCREEN COMMENT 48(20) TEXT-S05 FOR FIELD CTUMODE.
selection-screen position 70.
PARAMETERS CTUMODE LIKE CTU_PARAMS-DISMODE DEFAULT 'N'.
 "A: show all dynpros
 "E: show dynpro on error only
 "N: do not display dynpro
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) TEXT-S02 FOR FIELD USER.
selection-screen position 25.
PARAMETERS: USER(12) DEFAULT SY-UNAME. "user for session in batch
SELECTION-SCREEN COMMENT 48(20) TEXT-S06 FOR FIELD CUPDATE.
selection-screen position 70.
PARAMETERS CUPDATE LIKE CTU_PARAMS-UPDMODE DEFAULT 'L'.
 "S: synchronously
 "A: asynchronously
 "L: local
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) TEXT-S03 FOR FIELD KEEP.
selection-screen position 25.
PARAMETERS: KEEP AS CHECKBOX. "' ' = delete session if finished
 "'X' = keep session if finished
SELECTION-SCREEN COMMENT 48(20) TEXT-S09 FOR FIELD E_GROUP.
selection-screen position 70.
parameters E_GROUP(12). "group name of error-session
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) TEXT-S04 FOR FIELD HOLDDATE.
selection-screen position 25.
PARAMETERS: HOLDDATE LIKE SY-DATUM.
SELECTION-SCREEN COMMENT 51(17) TEXT-S02 FOR FIELD E_USER.
selection-screen position 70.
PARAMETERS: E_USER(12) DEFAULT SY-UNAME. "user for error-session
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 51(17) TEXT-S03 FOR FIELD E_KEEP.
selection-screen position 70.
PARAMETERS: E_KEEP AS CHECKBOX. "' ' = delete session if finished
 "'X' = keep session if finished
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 51(17) TEXT-S04 FOR FIELD E_HDATE.
selection-screen position 70.
PARAMETERS: E_HDATE LIKE SY-DATUM.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(33) TEXT-S10 FOR FIELD NODATA.
PARAMETERS: NODATA DEFAULT '/' LOWER CASE. "nodata
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(33) FOR FIELD SMALLLOG.
PARAMETERS: SMALLLOG as checkbox. "' ' = log all transactions
 "'X' = no transaction logging
SELECTION-SCREEN END OF LINE.
data definition
 Batchinputdata of single transaction
DATA: BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
 messages of call transaction
DATA: MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
 error session opened (' ' or 'X')
DATA: E_GROUP_OPENED.
 message texts
TABLES: T100.
at selection screen *
AT SELECTION-SCREEN.
group and user must be filled for create session
IF SESSION = 'X' AND
 GROUP = SPACE OR USER = SPACE.
 MESSAGE E613(MS).
ENDIF.
open dataset *
FORM OPEN_DATASET USING P_DATASET.
OPEN DATASET P_DATASET
 FOR INPUT IN TEXT MODE
 ENCODING DEFAULT.
IF SY-SUBRC <> 0.
 WRITE: / TEXT-E00, SY-SUBRC.
 STOP.
ENDIF.
ENDFORM.
close dataset *
FORM CLOSE_DATASET USING P_DATASET.
CLOSE DATASET P_DATASET.
ENDFORM.
create batchinput session *
(not for call transaction using...) *
FORM OPEN_GROUP.
IF SESSION = 'X'.
 SKIP.
 WRITE: /(20) 'Create group'(I01), GROUP.
 SKIP.
open batchinput group
 CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING CLIENT = SY-MANDT
 GROUP = GROUP
 USER = USER
 KEEP = KEEP
 HOLDDATE = HOLDDATE.
 WRITE: /(30) 'BDC_OPEN_GROUP'(I02),
 (12) 'returncode:'(I05),
 SY-SUBRC.
ENDIF.
ENDFORM.
end batchinput session *
(call transaction using...: error session) *
FORM CLOSE_GROUP.
IF SESSION = 'X'.
close batchinput group
 CALL FUNCTION 'BDC_CLOSE_GROUP'.
 WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),
 (12) 'returncode:'(I05),
 SY-SUBRC.
ELSE.
 IF E_GROUP_OPENED = 'X'.
 CALL FUNCTION 'BDC_CLOSE_GROUP'.
 WRITE: /.
 WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).
 E_GROUP_OPENED = ' '.
 ENDIF.
ENDIF.
ENDFORM.
 Start new transaction according to parameters *
FORM BDC_TRANSACTION USING TCODE.
DATA: L_MSTRING(480).
DATA: L_SUBRC LIKE SY-SUBRC.
batch input session
IF SESSION = 'X'.
 CALL FUNCTION 'BDC_INSERT'
 EXPORTING TCODE = TCODE
 TABLES DYNPROTAB = BDCDATA.
 IF SMALLLOG <> 'X'.
 WRITE: / 'BDC_INSERT'(I03),
 TCODE,
 'returncode:'(I05),
 SY-SUBRC,
 'RECORD:',
 SY-INDEX.
 ENDIF.
call transaction using
ELSE.
 REFRESH MESSTAB.
 CALL TRANSACTION TCODE USING BDCDATA
 MODE CTUMODE
 UPDATE CUPDATE
 MESSAGES INTO MESSTAB.
 L_SUBRC = SY-SUBRC.
 IF SMALLLOG <> 'X'.
 WRITE: / 'CALL_TRANSACTION',
 TCODE,
 'returncode:'(I05),
 L_SUBRC,
 'RECORD:',
 SY-INDEX.
 LOOP AT MESSTAB.
 SELECT SINGLE * FROM T100 WHERE SPRSL = MESSTAB-MSGSPRA
 AND ARBGB = MESSTAB-MSGID
 AND MSGNR = MESSTAB-MSGNR.
 IF SY-SUBRC = 0.
 L_MSTRING = T100-TEXT.
 IF L_MSTRING CS '&1'.
 REPLACE '&1' WITH MESSTAB-MSGV1 INTO L_MSTRING.
 REPLACE '&2' WITH MESSTAB-MSGV2 INTO L_MSTRING.
 REPLACE '&3' WITH MESSTAB-MSGV3 INTO L_MSTRING.
 REPLACE '&4' WITH MESSTAB-MSGV4 INTO L_MSTRING.
 ELSE.
 REPLACE '&' WITH MESSTAB-MSGV1 INTO L_MSTRING.
 REPLACE '&' WITH MESSTAB-MSGV2 INTO L_MSTRING.
 REPLACE '&' WITH MESSTAB-MSGV3 INTO L_MSTRING.
 REPLACE '&' WITH MESSTAB-MSGV4 INTO L_MSTRING.
 ENDIF.
 CONDENSE L_MSTRING.
 WRITE: / MESSTAB-MSGTYP, L_MSTRING(250).
 ELSE.
 WRITE: / MESSTAB.
 ENDIF.
 ENDLOOP.
 SKIP.
 ENDIF.
Erzeugen fehlermappe ************************************************
 IF L_SUBRC <> 0 AND E_GROUP <> SPACE.
 IF E_GROUP_OPENED = ' '.
 CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING CLIENT = SY-MANDT
 GROUP = E_GROUP
 USER = E_USER
 KEEP = E_KEEP
 HOLDDATE = E_HDATE.
 E_GROUP_OPENED = 'X'.
 ENDIF.
 CALL FUNCTION 'BDC_INSERT'
 EXPORTING TCODE = TCODE
 TABLES DYNPROTAB = BDCDATA.
 ENDIF.
ENDIF.
REFRESH BDCDATA.
ENDFORM.
 Start new screen *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.
 Insert field *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL <> NODATA.
 CLEAR BDCDATA.
 BDCDATA-FNAM = FNAM.
 BDCDATA-FVAL = FVAL.
 APPEND BDCDATA.
ENDIF.
ENDFORM.
Thanks
Will
I awarded points to everyone. Thanks so much.
Message was edited by:
 Will Ferrell

Sharepoint 2013 webDAV PROPPATCH fails with status code 409 error every time when trying to set custom property.

Sharepoint 2013 webDAV PROPPATCH fails with status code 409 error every time, when trying to set custom property.
anyone have any idea

Hi
Stumbled upon the resolution myself. The Bean Area item needs to be set to Visible=Yes in the property palette for the bean within Forms Builder, and also the implementation class also in the bean's properties must match exactly the package & class name specified in the PJC (my full implementation class string had to be set to oracle.forms.demos.runApplication).
As this bean has no user interface component, and since the Visible property has to be set to Yes, to avoid having a random square shape for the bean sitting on the form's canvas, I also set the Width and Height properties for the bean to 0.001. This does show a very small dot on the form, but that will be acceptable.
So in summary there has been a change for PJC / Bean Areas between 6i and 10g Forms, in 6i you could have the Bean Item to be set Visible=No, and the SET_CUSTOM_ PROPERTY built-in would work, however in 10g Forms the Bean Item must be set to Visible=Yes for the SET_CUSTOM_PROPERTY built-in to work.
Daryl

IDOC Posting To XI Failed With Status Text "::000" in SM58

Hello Gurus
Can u please suggest me how to overcome the problem with Custom Idocs while trying to send from SAP R/3 to SAP PI(XI).
The status text is displaying as "::000" with no other details, in SM58 of the sender system i.e. SAP R/3.
The Idocs status in the sender system is showing as 03 with the message "Idoc sent to sap system" in transaction BD87.
So I am getting confused where I missed the configuration.
Please suggest how I can troubleshoot the above.
<<Text removed>>
Regards,
Rk.K
Thanks in advance .
Edited by: Matt on Jun 24, 2011 9:58 AM

Thanks a lot for your support.
I have tried all the suggested solutions......but my problem was not solved.
The Metadata should be automatically created when the IDOCS successfully received by the XI server.
If it is not created then we should clear the SLD Cache in XI and try to create a new Metadata by giving the Custom IDOC Name and Port.
Even I tried with a Standard Idoc ORDERS05 , but I failed to do so.
After doing the above step I am getting the Information pop-up message "I::000".
Regarding RFC, I have created 2 users in both the systems with the same name(ALEREMOTE) of type "System".But,I am unable to Remote Login from XI to R/3 whereas the vice -versa is successful.
Are there any chances for this being the reason for failure of Idoc processing?
Such information message"I::000" is completely inexplainable.
Kindly, suggest a solution for it.
Thanks.

Inbound Idocs Got struck with status 75

Hi All,
My idocs Got struck in qrfc with status 75 ,Could any body tell why they r struck with status ,even though my partner Profile setting is set to Trigger Immedeatly
Appreciate your Replies..
Thanks,
Madhu

Dude, use Search button:
Re: Customer creation in R/3 from PI data using IDOCs

Segment mising in IDOC for outbound with status 3

Hi ,
Segment mising for IDOC for outbound and IDOC status in 03 . What could be the possible reason for segment missing ?
Edited by: Raghavendra Balegar on Jan 11, 2010 8:26 AM

how do you create the IDOC?
which IDOC?
what segment?

PO is getting created but showing error is address with status of IDoc - 51

Hi Experts,
I am using IDoc type - PORDCR103
Process code - copy of IDOC_INPUT_PORDCR1 (Function Module)
After processing through WE19 it is generating an IDoc number with status - 51 showing error in Address , But it is creating a PO.
My requirement is In status -51 It should not create PO.
Inside IDOC_INPUT_PORDCR1 a Bapi 'BAPI_PO_CREATE1' is used for creating PO. Here In RETURN parameter of BAPI a Row is comming with Message type - E. Some other messages are also there of type 'S' and 'W'.
After processing , PO is getting created with staus - 51.
Please help me .
Thanks
Susanta
Edited by: Susanta22 on Oct 11, 2011 12:29 PM

Hi,
in ur code ur filling the idoc data rcord, control record ryt ..before u append data to idoc data , u r also validating and u might be doing in loop for appening the idoc data.
if there is any error in idoc then it won't distribute the data, it will be in error status only..u can only see the data in WE02. Then u can also change the data in WE02 and redistirbute it via BD87.
if u have any conerns let me know
Regards,
Nagaraj

Idoc are posting to ECC with Status 64

Hi All,
We are receiving IDOC with status 64 from PI.
We used tried by changing the options in partner profiles
--> Trigger by Background program
The inbound IDoc is processed in the background. In this case, make sure, that the report RBDAPP01 is scheduled in the transaction SM37 as a regular job with the correct variant to process all IDoc´s, which have this processing option maintained.
--> Trigger immediately
When using this setting, it is important to have sufficient resources for the immediate processing of the inbound IDoc´s. One dialog work process must be available for every single IDoc.
If this dialog work process is not available, the IDoc cannot be processed and stays in status 64.
I reffered the notes
555229 ‘IDocs hang in status 64 for tRFC with immediate processing’
734576 ‘IDocs retain status 64, but should be processed immediately’
1055679 ‘IDoc-tRFC inbound with immediate processing may not work’
Still the idocs are in 64 status, every time im re-processing them manually. even after re-processing some of them are going to 51 or 54.
Please help me.
Regards
Bhargava Krishna

Hello,
Can you please explain your issue is with "Trigger by Background program" or "Trigger immediately"?
For Trigger immediately, if there is no free dialog work process available than IDocs are posted with status 64.
For Trigger by Background program, Background job RBDAPP01 will process IDocs depending on variant you define to select & process IDocs(i.e., IDoc Status = 64).
It is always recommended to use "Trigger by Background program" for high volume interface which has large number of IDocs.
Help on RBDAPP01
Regards,
Sameer

Event when logistic invoice gets in the sys. through EDI with status cod 03

Hello Gurus,
I am trying to find the event that gets triggered when an incoming EDI logistics invoice gets posted/created in system with status code 3 (error status). I know that I can go to transaction SWELS to find the event using event trace.
The problem is I cannot create such a test scenario manually i.e logistic invoice in the system with status code 03. So I was woneding if someone cal tell me if it would be event
incominginvoice.created or incominginvoice.posted in business object BUS2081 when the logixtics invoice gets crated/posted with status code 03.
Thanks.
Regards,
Rajesh.

Hi Rajesh,
The events triggered when an IDOC goes into error are associated with the inbound process code.
Have a look in transaction BD67 for your process code, e.g. INVM under the IDOC section you will see the object and events that are invoked when any error occurs.
Is that what you are after?
Darren

Adalnctl failed to start with status 127

OS:red hat as4
ebs: 11.5.9
now my system can be started,but the adalnctl failed to start with status 127.
the error message is about lsnrctl which saied that lsnrctl: command not found.
but when i start the lsnrctl with oracle owner,the lsnrctl was started immediately.
however,i found that,the lsnrctl was conected to the port 1521,the adalnctl to the port 1626.
please help me to see it!
the cdalnctl log was this:
LSNRCTL for Linux: Version 9.2.0.3.0 - Production on 20-MAY-2009 17:03:27
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=TCP)(Host=ebstest)(Port=1626))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Linux Error: 111: Connection refused
Starting listener process APPS_PROD.
LSNRCTL for Linux: Version 9.2.0.3.0 - Production on 20-MAY-2009 17:03:27
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Starting /u01/oradata/prodora/8.0.6/bin/tnslsnr: please wait...
TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
TNS-00515: Connect failed because target host or object does not exist
Linux Error: 2: No such file or directory
adalnctl.sh: exiting with status 1
Checking status for listener process APPS_PROD.
adalnctl.sh: exiting with status 1
./adalnctl.sh: line 126: lsnrctl: command not found
Starting listener process APPS_PROD.
./adalnctl.sh: line 137: lsnrctl: command not found
adalnctl.sh: exiting with status 127
Checking status for listener process APPS_PROD.
adalnctl.sh: exiting with status 1

oh maybe i found it
i have more than one listener.ora
[root@ebstest /]# find -name listener.ora
./u01/oradata/prodora/iAS/hs/admin/listener.ora
./u01/oradata/prodora/iAS/network/admin/samples/listener.ora
./u01/oradata/prodora/8.0.6/network/admin/samples/listener.ora
./u01/oradata/prodora/8.0.6/network/admin/PROD_ebstest/listener.ora
./u01/oradata/proddb/9.2.0/network/admin/samples/listener.ora
./u01/oradata/proddb/9.2.0/network/admin/PROD_ebstest/listener.ora
./u01/oradata/proddb/9.2.0/appsutil/out/PROD_ebstest/01010106/listener.ora
./u01/oradata/proddb/9.2.0/appsutil/out/PROD_ebstest/01010108/listener.ora
./u01/oradata/proddb/9.2.0/appsutil/out/PROD_ebstest/01010121/listener.ora
and the other listener.ora was about port 1626
[root@ebstest /]# cat ./u01/oradata/prodora/8.0.6/network/admin/PROD_ebstest/listener.ora
# $Header: admk80ln_ux.sql 115.13 2003/04/03 08:05:06 skghosh noship $
# LISTENER.ORA For Oracle Applications
# This file is automatically generated
APPS_PROD =
(ADDRESS_LIST =
(ADDRESS= (PROTOCOL= TCP)(Host= ebstest)(Port= 1626))
SID_LIST_APPS_PROD =
(SID_LIST =
( SID_DESC = ( SID_NAME = FNDSM_PROD )
( ORACLE_HOME = /u01/oradata/prodora/8.0.6 )
( PROGRAM = /u01/oradata/prodappl/fnd/11.5.0/bin/FNDSM )
( envs='MYAPPSORA=/u01/oradata/prodappl/APPSPROD_ebstest.env,PATH=/usr/bin:/usr/ccs/bin:/bin,FNDSM_SCRIPT=/u01/oradata/prodcomn/admin/scripts/PROD_ebstest/gsmstart.sh' )
( SID_DESC = ( SID_NAME = FNDFS )
( ORACLE_HOME = /u01/oradata/prodora/8.0.6 )
( PROGRAM = /u01/oradata/prodappl/fnd/11.5.0/bin/FNDFS )
( envs='EPC_DISABLED=TRUE,NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1,LD_LIBRARY_PATH=/usr/dt/lib:/usr/openwin/lib:/u01/oradata/prodora/8.0.6/lib,SHLIB_PATH=/usr/lib:/usr/dt/lib:/usr/openwin/lib:/u01/oradata/prodora/8.0.6/lib,LIBPATH=/usr/dt/lib:/usr/openwin/lib:/u01/oradata/prodora/8.0.6/lib,APPLFSTT=PROD,APPLFSWD=/u01/oradata/prodappl/admin' )
STARTUP_WAIT_TIME_APPS_PROD = 0
CONNECT_TIMEOUT_APPS_PROD = 10
TRACE_LEVEL_APPS_PROD = OFF
LOG_DIRECTORY_APPS_PROD = /u01/oradata/prodora/8.0.6/network/admin
LOG_FILE_APPS_PROD = APPS_PROD
TRACE_DIRECTORY_APPS_PROD = /u01/oradata/prodora/8.0.6/network/admin
TRACE_FILE_APPS_PROD = APPS_PROD

Error in idoc with status 20 "Error triggering EDI Subsystem"

Dear All,
I have query related to IDOC Status 20.
I am tirggering IDOC with standard t-code from IS-Retail system. I have created two ports a) TRFC port and b)File port .
We are having sending and receiveing application on two different OS i.e one XI on Windows and IS Retail on AIX(Unix). I am not able to send idoc to another system. I am getting these IDOC status in WE05 (STATUS 01 , 30 , 03 , 20 )
Keeping the above fatcs in mind could you please tell me how to remove the error with status 20 "Error triggering EDI Subsystem".

Hi prabhat,
You should have checked the automatic triggering possible at the file port level and the partner profile setting could be 'start subsytem'.
Go to WE21 and do the access test for the file port.
Once you done and find no issues then go to SM59 and test the connection for the RFC destination assigned to the ports.Possibly it has to do with the RFC destination.
Other reasons could be yours is a test client and got refreshed recently.so the production client settings might be causing this error.Check with your basis to get it working.
other reason could be the logical system assigned to the client should be having production client's name.
Check these.
I am sure you should be able to solve this issue.
Thank you.
regards,
karun.M

ERROR IN IDOC WITH STATUS 51

Hello Experts,
I am facing a connectivity issue B/w Dev server
i am getting data into BI dev from ECC dev.
but when i am running the infopack the IDOC error status appearing in ECC dev with status 51 with error message text Incomplete control parameter for commmunication with the BW system appearing
please suggest where to maintain the parameter and how to transfer data

earlier it was working fine than after that our basis guy did client copy activity on ECC Dev client and after that its not working.
if i run infopack it shows 0 records and request turns red with below error
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
when i am checking in WE02 the idocs are showing STATUS 51
now i have activated Source system and i am authorised for all transactions
but still facing the problemm

5 IDOC with status 29 Error in ALE service

hi there,
im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
IDOC Status Outbox:
IDOC failure between 13/07/2008 to 14/07/2009
1 IDOC with status 02 Error passing data to port
5 IDOC with status 29 Error in ALE service
IDOC Status InBox:
88 IDOC with status 51 Application document not posted
regards
raju

Hi,
Check this thread.
DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Regards.

Inbund IDOC error: Status records with status 51 after status 53

Hi all,
I'm looking to resolve an issue related to posting an inbound IDOC. when I process inbound IDOC created from report prg I'm getting a status message: "Status records with status 51 after 53" .
Functionality: I'm creating an IDOC from flat file and processing it to post Customer master data into SAP. During this process creation of IDOC is successful but when I'm changing the existing data record (customer master data) IDOC is throwing this error.
Changing data: For changing existing data I'm passing KUNNR field and overwriting the remaining data. Even though the idoc status is 51 the changed data is getting posted in to SAP. Here my concern is to see IDOC status as 53.
Regards,
Ganesh.
Edited by: Ganesh Sunkara on Aug 1, 2009 3:45 AM

Hi all,
I solved this issue by myself. There is an error in the user exit code.
regards,
Ganesh.

IDOCs in trfc with status text as error

Similar Messages

Maybe you are looking for