Reg: IDOC Status Info Report

Hi Experts
I am trying to posting the products/internal orders data via IDOC/ALE.
After the Data loaded into the target system,I required to display the below info:
Initial Data Load Results Report Layout:
Totals
Total number of records read:
Total number of records processed:
Total number of internal orders created
Total number of records in error
Records Created
Material XXXXXX created
Extended to Plant 9999
Extended to sales organization 9999
Characteristic xxxxxxxxxxxxxx created
Records in error
Line 12 Plant 9999 does not exist
Line 13 Sales organization 9999 does not exist
My concern here is as we were loading the data from source to target here via IDOC/ALE.So once the Idoc processed , control won't comes to the developer's view .Then how I can able to publish the above info?
As I am new to ALE/IDOCS can someone throw some light on this.
Thanks for your cooperation in advance.
Regards,
Sreeram Kumar.Madisetty

Hi
So finally you want log of updated records rite ?
Are you Using FM or stand alone program to process the IDOC ?
Standard IDOC or Custom ?
Inbound or outbound ?
For inbound if you are using standard Fm find exit for that Fm and in that u can develope the code like in report .
Finally count the number of records updated .
You are getting some errors records so pass the all error recors into internal table and count the records in that internal table ..
or
IF you are using custom fm u can directly code the requiremtn in Fm like validations .
if you are not clear please revert back and mention ur IDOC and processing Fm so that i can help you more ..

Similar Messages

Reg idoc status check

Hi i have to check the idoc status 51 or 68 how to write the code

Execute the program RC1_IDOC_SET_STATUS.
enter the Idoc number , present status , New status and execute.
Check this link
http://www.erpgenie.com/sapedi/idoc_statuses.htm
Regards

Reg:IDOC status

Hi in my scenario i had got the status using idoc_read_completely FM now have to get the idocs of status 51 0r 68 alone and proceed further.For this how to code

Execute the program RC1_IDOC_SET_STATUS.
enter the Idoc number , present status , New status and execute.
Check this link
http://www.erpgenie.com/sapedi/idoc_statuses.htm
Regards

IDOC: Status (Error/Success/information)report to Sender system

How would one send a message(error/success/information) to the sending(external) system to inform them of the statuses of the messages they've sent to our SAP system?

Hi Baumann,
you have an option called Audit reporting in which you can have the status of idoc at sender side.read the following.
Setting Up Audit Reporting
In the default behavior, after an IDoc is dispatched to a destination system, the sender does not know the state of the process on the destination system. You can configure the system, however, for cross-system reporting. You must model the ALEAUD message between the systems.
Two programs enable cross-system reporting.
1)RBDSTATE. This program is scheduled to run periodically on the destination system. It reports the status of incoming IDocs to the sending system, using the ALEAUD message and ALEAUD01 IDoc. This status information is recorded separately from IDoc status information in the audit logs.
2)RBDAUD01. This program is executed on the sending system. It analyzes the audit log and displays the output as a report.
The RBDSTATE program returns the following statuses, from the receiving to the sending system.
RBDSTATE Is Run on the Receiving System
Status of IDoc in receiving system     Status reported to sending system via ALEAUD
53 (Application document posted.)     41 (Application document created in receiving system.)
51 (Error: Application document not posted.)     Status 39 (IDoc is in the receiving system.) This status is repeated each time RBDSTATE is run, as long as the IDoc remains in status 51.
68 (Error: No further processing.)     40 (Application document not created in receiving system.)
reward points if helpful,

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

IDoc status 53 in employee replication from SAP HR

Hi experts,
We are having some problems in CRM BP creation with role employee.
We are using CRM 5.0 and SAP ECC 6.0 and we are trying to replicate employees information to CRM from HR.
After read the notes 934372, 615896, 550055, 363187, 312090 we made the next configuration steps in our systems:
R/3:
- Creation of connection port (trans. WE21)
- Creation of logical system (trans. WE20) and assignment of outbound message HRMD_ABA
- Creation of distribution model (trans. BD64) with all filters indicated in note 312090
CRM
- Creation of logical system (trans. WE20) and assignment of inbound message HRMD_ABA
- Creation of conversion between basic types HRMD_A05 and HRMD_ABA01 (trans. WE70) as described in note 312090
- Creation of conversion between message types HRMD_A and HRMD_ABA (trans. WE73) as described in note 312090
- Creation of external number range ZE from HR01200001 to HR01299999 (using PA04 in R3 we found the number range between 01200001 and 01299999)
- Creation of BP Grouping with the same name of number range (ZE) checked to be external too
- Update of table T77S0 (using SM30):
HRALX HRAC X
HRALX PBPON OFF
HRALX PBPHR ON
HRALX PBPON ON
HRALX PNUMB 3
HRALX PPROL BUP003
HRALX PSUBG ZE
PLOGI PLOGI MV
We know we should have the same value in R3 and CRM for PLOGI/PLOGI, so we created in CRM MV because that is the plan version used in R3. To create it, we just manually add a new row in table T778P and then selected it in table T77S0. Is this the correct way to create a plan version?
After these steps, in R3 we execute program RHALEINI with parameters:
- Plan version = MV
- Object type = P
- Object ID = an active employee
- Reporting period = all
- Transfer mode = Insert
- Receiving system:
Receiving partner No = DCRCLNT300 (logical system created in WE20)
Message type = HRMD_ABA
And everything looks fine in R3.
In CRM, using trans. WE05, we can see that the iDoc is created, apparently without problems with status 53 - "Applicaton document posted" but the business partner is never created.
Did we miss some configuration steps?
Should we do something more after see the iDoc in CRM to create BP?
Thanks in advance.
Alda

hi pratk bhai,
ya i have done the same setting what Ada has mentioned eariler,
and as of your suggestion to maintatin the mandatory infotype, i have even done tht,
after running RHALEINI in R3, the status is all green here.
when i run the tcode BD87 to check the Idoc status its showing fine (Error free).
now, through tcode se38 the report CRMHRALE_CENTRAL_PERSON shows all the employees as status green,,
but the partner number is not getting generated. ( i have used HRALX-PNUMB= 3 (Prefeexing the number range coming from R3)).
kindly advice me what should be done in order to generate a BP number for the replicated HR Employee.
best regards,
Madhup

IDOC status 03 but no XML generated

Hi Experts,
I am facing a problem related to idoc i.e. I am getting idoc status 03, still no XML created at the server directory.
Scenario is: A custom idoc is created with a z report which selects data & send idoc as an XML file in the server directory
IDOC (the first \ represents root as it is a unix server, 2nd \ is a saparator nd then IDOC is a folder to save XML files). Folder IDOC is having all permission(777). When i send idoc using the report is fives status 30 & after that when process it through BD87 it gives a status message 03.
I checked the partner profile, port etc. Even in port access test is OK.
I even tried putting directory as //IDOC , /IDOC but then no access possible error came. only work with
IDOC & gives status message 03.
But no idoc is reaching at the other end i.e.
IDOC.
Can anyone tell me how to fix this problem. Is the problem at SAP end of Unix end.
Regards,
Nik

Hi,
Check the Port configuration.In this case mostly problem form port configrations only.
Check Directory,Outbound file paramters in the port configuration.
Thanks,
radha.

Idoc status 53.Yet application data is not posted.

IDOC status is 53. But application data is not partially posted.iam generating 2 idocs, one for type INFREC01 and other for COND_A01. iam Generating IDOC using a fm IDOC_INBOUND_ASYNCHRONOUS. purchase info record is posted succesfully. but condition info record is not posted.
for both the idoc its shows green status-53. moreover data in EINA EINE KONH KONP is updating, but its not displayed in transaction ME13.
Kindly help me.

Hi,
Check the config stuff if you are usng the right IDoc...See partner profiles and the message types.
thanks

File -- XI -- IDoc ( IDoc Status 56)

Iam trying to post IDoc(cremas03) with File --> XI --> Idoc Scenario.
I got message processed successful in SXMB_MONI.
However on ECC5.0(R/3) I got Idoc status 56.
EDI: Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/T20CLNT400/LS//CREMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST    test flag
Procedure
Please check the inbound partner profiles.
Execute function
On IDOC Display (We02) I found following info:
Technical Short Info
Direction : 2
current status: 56
Basic type: cremas03
Message type: cremas
Partner No: T20CLNT400
On Idoc control Record:
Typeinfo tab:
Basic Type: CREMAS03
Message Type: CREMAS
Partner Tab:
Recipient
Port:   (Spaces)
Partner No: ID3CLNT550
Partner Type: LS
Sender
Port: SAPSXI
Partner No: T20CLNT400
Partner type: LS
Tech Info:
Sap rel : 640
On Partner Profiles:(WE20)
ID3CLNT550 ( in this case receiver) was defined as Logical Sytem and Inbound message type CREMAS
Would someone please guide me what to do as Iam learner of XI.
Thanks a lot

Here it is.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>400</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000046232</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPSXI</SAP:SNDPOR>
<SAP:SNDPRN>T20CLNT400</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPECC</SAP:RCVPOR>
<SAP:RCVPRN>ID3CLNT550</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>BAA624009F6311DA8AD3003048805A88</SAP:ARCKEY>
</SAP:IDocOutbound>
Following data was defined in receiver system, Client 550
Inbound parameters:( With we20)
PartnerNo: ID3CLNT550
Type: LS
Inbound parameters:
Partner Role : LS
Message Type: CREMAS
Process Code : CRE1
Trigger immediately
PartnerNo: ID3CLNT550
Partner Type: LS
Inbound parametrs:
Partner role:   <---- blank here ..does this matter ?
Message Type: CREMAS
Process Code: CRE1
Trigger immediately

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 message

HI
I have to pick IDOC status message in my report program. For this I am referring the table EDIDS. My doubt is some times the IDOC status message is storing in the field STATXT and some times the idoc status message is storing in the fields STAPA1, STAPA2, STAPA3,STAPA4. How come I know I mean from which field I need to pick status message in my report program. I am giving idoc number as input to the table EDIDS. If possible please send me the sample code to resolve this problem. I will give points.
Thanks a lot in advance.

Hi,
STAPA1, 2, 3 & 4 are the place holder values for the message..
If you have a message in SE91..like
Sales order & created.
The & will be given in the program where it displays the message.
MESSAGE s208(00) WITH vbak-vbeln.
The vbak-vbeln value will be stored in field STAPA1.
Thanks
Naren

How to handle idoc status record.

Hi expert,
We have configure custom idoc, the status of inbound custom idoc when posting by process code is 64 (Ready to posting), How we can post with status 54, have any idea ?
When I am using report RBDAPP01, it is in status 51 (Error),
How I can change the idoc status with 54 (Successful).
Please help,
Regards,
study sap

hi,
Retrigger from here
Try with tcode BD87 For Inbound IDOCS.
or BD88 for outbound IDOCs.
Refer these links
http://sap.ittoolbox.com/groups/technical-functional/sap-interfaces/idoc-status-64-1258234
http://help.sap.com/saphelp_sm32/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm
Cheers
Mohinder Singh Chauhan
Edited by: Mohinder Singh Chauhan on Jul 21, 2008 8:08 AM

Changing IDOC status

Hello
I wander how to change IDOC status. I know there is an report (or a FM) which changes it but I can not find it. Could you please hepl me?
Thank you in advance

Hi,
do you mean with a transaction BD87 ? You can modify the idoc and process it ..
regards,
Sandrine

IDoc Status Messages

Hi All, Is there any Function Module or standard report which will list out all the Status messages of an IDoc...Basically i need to capture all the segments which are in error state... In EDIDS table i am not able to link to a particular segment.
Please help me out
Thank You,
Regards,
Swaroop Patri...

HI,
<b>ALE/IDOC Status Codes/Messages</b>----
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
<b>Inbound Status Codes</b>
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
Regards
Sudheer

Reg: IDOC Status Info Report

Similar Messages

Maybe you are looking for