IDOC Status text

Hi,
In the status table EDIDS some times the status message is storing in the field STATXT and some times it is storing in the variable STAPA1. As of now I am using the variable STATXT for fetching the status text but some cases STATXT is showing description as & & & & and STAPA1 is showing correct status text. How to use these two variables correctly. If possible please send me the code I will give points.
Thanks a lot in advance.

issue with code for idoc
interface code required........................IDOC
Extracting data from iDoc tables
Please reward points if helpful.

Similar Messages

IDoc Status "& & & &" in IDoc posting in BD87 - ALE

hi,
I am integrating two R3 servers and posting the datas from HR to cProjects server.
In Outbound I can send the IDocs and In Inbound IDocs are getting into destinations (cProjects) servers along with status "& & & &" in BD87.
Can anyone help me to know..Where the cause of problem..
Thanks in advance
Regards,
Srinivasan.R

Hi.,
In we02 its OK..
Its showing ...
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000036306 Status: IDoc ready to be transferred to application
T100 Text:     No filters , No conversion , No version change .
But., in place of BD87 I am getting status only "& &, &, &".
Regards,
Srinivasan.R

Need to change the Idoc Status based on the Text in the Idoc

Hi All,
I have developed Idoc--SOAP Sync Process Scenario Using BPM and Works Perfectly.
I have used STATUS.SYSTAT01 Idoc to capture the Response that is comming from the Webservice.
I have mapped the response Text( Success or Fail) to one of the field in the Response Idoc, this is perfect.
Requirement:
1) If the Response Idoc Field receives Success Text means the Idoc Status shld be in Green Status.
2) If the Respnse Idoc Field Receives FAIL means the Idoc Status shld be in RED Status.
How can i Do this. please suggest me......
Regards

Hi Santhosh,
YES, I have to Capture the Response from Webservice in SAP R/3 by using STATUS.SYSTAT01 Idoc.
I have mapped the response from webservice to the one of the field in the Idoc.
If this field contains Success as text means the Idoc Status in We05 shld be 53 else it shld be 56
With out changing the FM code, can we use any other process to achieve this???
@ Mario
Can u please Allobarate your views more based on my requirement
Regards

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.

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.

SM58 status text " No service for system SAPERP, client 800 in integr "

In Idoc to file scenario:
i have fallowed this blog to configure ALE settings
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I have generated one idoc successfuly from sap r/3 system.
but i didn't find any idoc in xi server.
control records are
receiver:A000000036,(RFC DESTINATION->LS_XI_100( Remote login sucessful for xi system))
      LS_XI_100
      LS
Sender: SAPERP
     LS_SAP_800
     LS
ID: Adapter specific identifiers are( LS->LS_SAP800, R/3->ERP,CLIENT,800)
so i have gone to tcode sm58 in sap r/3
   where i found the status text "No service for system SAPERP, client 800 in integr)
Please help me from this problem.
Regards,
Deviprasad.

Hi Deviparasad,
please create a techincal system and busniess system of type ABAP in XI SLD if you have already created the techincal system and busniess system then check whether client 800 is used or not if include client 800.
please reward points
Regards
Sreeram.G.Reddy

IDOC Status 68 & 51

Hi,
There is an IDOC with status 68 (Error - no further processing) , Earlier it was in status 51 with the status text "INVALID DATE' .
How to find out for which particular date field's the error is being thrown..?? what is the approach to find out the root cause of the issue.?? the IDOC is being sent to R3 through XI.
Plz give suggestions on how to tackle the issue.
Thanks in advance,
Jai

Hi ,
The idoc Status for 59 and 51 for indound idoc is....
68 Error - no further processing
51 Application document not posted
the possible solution is checkthe Partner profile for the Idoc and Port number..
and go to T_code we20 and check the Partner.and check the Syntax in the application tool bar...
then you will come to know the problem..
Regards,
Prabhudas

Any FM/methods to update idoc segments without changing idoc status

Hi All,
My requirement is a reprocessor program which fills up some fields in the idoc segment before posting. So, after updating the segments, the idoc status should remain as before.
Is there any function modules or methods to update idoc fields in segments without changing the idoc status?
I have tried the FMs EDI_DOCUMENT_OPEN_FOR_EDIT, EDI_CHANGE_DATA_SEGMENT and EDI_DOCUMENT_CLOSE_EDIT, but it changes the idoc status.
Thanks,
Arun Mohan

As for FM to do this, i don't know if there are any, but i think you can go directly to the tables with the IDOC data and change them without triggering the changes in status like FM do. Still, i am not sure this is completely true, but you could give it a try. Also, i don't know if this is the best way to do it, because of those legal/audit questions mentioned by Thomas.
Here is a sample code of a program we have to change a field in a segment of WPUUMS.
*& Report YRE00021INTPG
REPORT yre00021reppg.
TABLES: edid4 ,
        edidc ,
        mean .
* Variaveis Auxiliares
DATA: t_edidc TYPE edidc OCCURS 0 WITH HEADER LINE.
DATA: t_edid4 LIKE edid4 OCCURS 0 WITH HEADER LINE .
DATA: BEGIN OF t_docs OCCURS 0,
        docnum LIKE edidc-docnum ,
      END OF t_docs.
DATA: wa_e1wpu02 LIKE e1wpu02 .
DATA: wa_e1wpu03 LIKE e1wpu03 .
DATA: t_itedidd LIKE edi_dd40 OCCURS 0 WITH HEADER LINE ,
      t_itedidc LIKE edi_dc40 OCCURS 0 WITH HEADER LINE ,
      fw_itedidc LIKE edi_dc40 ,
      fw_itedidd LIKE edi_dc40 .
DATA: l_matnr TYPE mara-matnr,
      l_tam TYPE i.
DATA: l_idoc_number TYPE edidc-docnum.
* Ecran de selecção
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_docnum FOR edid4-docnum ,
                s_credat FOR edidc-credat DEFAULT sy-datum ,
                s_cretim FOR edidc-cretim .
PARAMETER:      p_mestyp LIKE edidc-mestyp DEFAULT 'WPUUMS' ,
                p_status LIKE edidc-status DEFAULT '51' .
*SELECTION-SCREEN SKIP.
*PARAMETER:      p_ean11 TYPE mean-ean11.
SELECTION-SCREEN : END OF BLOCK b1.
AT SELECTION-SCREEN.
IF p_status <> '51'.
    MESSAGE e001(yre) WITH 'Apenas pode modificar IDOCS com erro'.
ENDIF.
IF p_mestyp <> 'WPUUMS'.
    MESSAGE e001(yre) WITH 'Apenas pode lançar WPUUMS'.
ENDIF.
*AT SELECTION-SCREEN ON p_ean11.
* SELECT SINGLE * FROM mean WHERE
*    ean11 = p_ean11.
* IF sy-subrc <> 0.
*    MESSAGE e001(yre) WITH 'Ean não existente'.
* ENDIF.
START-OF-SELECTION.
SELECT docnum INTO TABLE t_docs FROM edidc
                     WHERE status = p_status
                     AND   mestyp = p_mestyp
                     AND   docnum IN s_docnum
                     AND   credat IN s_credat
                     AND   cretim IN s_cretim .
CHECK sy-subrc = 0 .
LOOP AT t_docs.
    CLEAR : wa_e1wpu02.
    SELECT * FROM edidc INTO TABLE t_edidc
      WHERE docnum = t_docs-docnum.
    CHECK sy-subrc = 0.
    SELECT * FROM edid4 INTO TABLE t_edid4
                  WHERE docnum = t_docs-docnum AND
                        segnam = 'E1WPU02'.
    CHECK sy-subrc = 0.
    SORT t_edid4 BY segnum.
    LOOP AT t_edid4 .
      wa_e1wpu02 = t_edid4-sdata.
      WRITE wa_e1wpu02-artnr TO l_matnr NO-ZERO.
      CONDENSE l_matnr.
*      l_tam = STRLEN( l_matnr ).
*      IF l_tam <= 6.
        SELECT SINGLE ean11 INTO wa_e1wpu02-artnr FROM ytre00004 WHERE
          codcurto = l_matnr.
        IF sy-subrc = 0.
          WRITE : /1 'Código ', l_matnr, ' alterado para ', wa_e1wpu02-artnr.
        ELSE.
          WRITE : /1 'Código ', l_matnr, ' não encontrado na tabela de conversão'.
          CONTINUE.
        ENDIF.
*        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
*          EXPORTING
*            input = p_ean11
*          IMPORTING
*            output = wa_e1wpu02-artnr.
*      ENDIF.
      UPDATE edid4 SET   sdata   = wa_e1wpu02
                   WHERE docnum = t_edid4-docnum
                   AND   counter = t_edid4-counter
                   AND   segnum = t_edid4-segnum .
      IF sy-subrc <> 0 .
        ROLLBACK WORK .
        WRITE: / t_edid4-docnum .
      ELSE.
        COMMIT WORK.
      ENDIF.
    ENDLOOP.
ENDLOOP.
END-OF-SELECTION.

IDoc status 51 - LSMW for Creating Purchasing Info Records

Dear All,
My req is to create a Conversion for Purchasing Info Records. LSMW's IDoc method is used to develop this conversion wherein Message Type "INFREC" and Basic Type "INFRECMASS01" are being used.
In the 14th step (Start IDoc Processing), I 'am getting the IDoc status "51" and Status Text "Application document not posted". If I double click on respective IDoc number, I got its Control record, Data records, and Status records; in the status records I can see "51" in Red color with the message "Function module not allowed: IDOC_INPUT_INFREC". If I double click on this it asks me to check the process code...
Request you guys to resolve the issue....
Solution will b rewarded.. Thanks in advance....

I shouldnot use basic type INFREC01 instead of NFRECMASS01.
'coz Within the FM there is a check for basic type like:
check idoc type
if f_idoc_control-idoctp c_idoctp_infrec01. " INFREC01
raise wrong_function_called.
endif.
Even one can go to WE57 and see the basic Type INFREC01 assigned to the FM IDOC_INPUT_INFREC, hence one shud use this basic type...

IDoc status 51 - LSMW for Creating Purchasing Info Records using IDoc meth

Dear All,
My req is to create a Conversion for Purchasing Info Records. LSMW's IDoc method is used to develop this conversion wherein Message Type "INFREC" and Basic Type "INFRECMASS01" are being used.
In the 14th step (Start IDoc Processing), I 'am getting the IDoc status "51" and Status Text "Application document not posted". If I double click on respective IDoc number, I got its Control record, Data records, and Status records; in the status records I can see "51" in Red color with the message "Function module not allowed: IDOC_INPUT_INFREC". If I double click on this it asks me to check the process code...
Request you guys to resolve the issue....
Solution will b rewarded.. Thanks in advance....

U should use basic type INFREC01 instead of NFRECMASS01.
Within the FM there is a check for basic type like:
check idoc type
    if f_idoc_control-idoctp <> c_idoctp_infrec01. " INFREC01
      raise wrong_function_called.
    endif.
Edited by: Joyjit Ghosh on Sep 15, 2008 4:57 PM

Problem in idoc status

Hi Abapers,
In our project some of the invoice idocs are not posted into SAP..but all the segment's data are uploaded into the respective structures..but still the staus is in 51 only..i can't find the reason behind this..can u give me solution for this?

Hi,
You can find the error reason when you open the status records and double click on the 51 status text box.
Check what was error thrown there and then correct the same and reprocess the idoc again, then it will get through.
Thanks,
Mahesh.

I/B Idoc Status 56 - Reason Required

Hi,
We have a PI system and R/3 System. PI sending some idoc to R/3. In this case Idoc is failing and giving status message as 56. Can any one tell me reason why it is giving error like.
Error messages are like this:
Status Text:- IDoc: 0000000001230201 Status: IDoc with errors added
T001 Text :- EDI: Partner profile not active
Please let me know in which system do i need to the changes and how can i do these changes.
I am new to this concept.
Thanks,
Sekhar.J

Hi Sekhar,
From PI perspective everything is fine, you were able to create an IDOC structure and push it to R/3 system and there is also successfully created but it has failed with the error 56. It is due to invalid partner profile, check the transaction WE20 whether a partner profile has been created for that partner or not, if it is created then whether the message type is configured for that partner or not.
The error is basically due to invalid partner profile and you need to correct that in WE20 transaction, once you correct that then you can reprocess the idoc through BD87 transaction.
Thanks,
Mahesh.

Status Text 000

Hello
I tried an Idoc. It doesn't reach XI. It does not appear in SXMB_MONI. In SM58, I see status text 000. What does that mean ?
However when I go to WEO2 I see Current Status as 03.
What should I do and how woiuld I proceed ?
Midhun

Hello Ravi
When I double click on it, I get this : : 000
I don't find anything more
I went to SM59, RFC Destination from QAS of XI, then did a Utilities -> Test -> Authorization Test
I got this as a result.
Logon Cancel
Error Details Name or Password is incorrect (repeat logon)
So there is an Error with SM 59 that I created to ECC from XI.
Midhun

A new IDOC status - ex. 80

Is it possible to create a new IDOC status code? we want to capture some of the intermediate processing messages in the IDOC status log. ex. "status 80 - BDC x done" -> "Status 80 order created" -> "Status 53 order has been imported".
I couldn't find anything under SALE but did saw couple of tables that list out status numbers and associated texts w/ it. I thought I would be able to add in a new status number - code, but 'new entries' is not an option.
Thanks in advance.

Yes, you have an option to create new status messages. I have done this before.
Please try running the area menu WEDI from your SAP easy acess screen.
You will find an option to create new status.
Let me know if you need more details.
Regards
Sabu

IDOC status at 30, but in we05 it is 03

Hello Gurus!!
My program generates an IDOC and as soon as the idoc is generated it the status is 03 then i have todo something else.
Within the program when i am cheking the status is 30 but actually in transaction we05 the status is 03.
I have cheked the partner profiles and transfer_idocs_immeadiately has already been selected.
I have already gone thru the forum but no valid solution was given,
There is no need to change any ALE configurations / port configurations because everything just work fine. It is only that within the program i am not able to catch the status 03. the proram is not waiting untill the idoc status is 03. it is capturing only the status 30.
Is there any thing that i can do within the program? should i capture the idoc number and then check the idoc status from EDID4?
Please answer o this questions ASAP.
Regards.

Initially when you create the outbound idocs then status is 30. then you have to run the program RSEOUT00 to process the idoc then after the processing the status changes to 03.
But the Program RSEOUT00 is optional. In the partner profile (WE20) If you select the option 'Collect Idocs', then you have to schedule the program RSEOUT00 to process the Idocs otherwise if you have choose the option 'Transfer idoc immediately', you don't need to do anything.
Thanks,
Srinivas

IDOC Status text

Similar Messages

Maybe you are looking for