Add message to iDoc status

I created Z_ functional module for inbound Sales Order iDoc processing.
I want to add my own warning message to iDoc status:
    CLEAR idoc_status.
    idoc_status-docnum = idoc_contrl-docnum.
    idoc_status-status = '64'.
    idoc_status-msgty = 'W'.
    idoc_status-msgid = 'ZMSERIES'.
    idoc_status-msgno = '005'.
    APPEND idoc_status.
When i test in Test Tool WE19 using button "Inbound functional module" message successfully added to iDoc (WE02).
When i click "Standard inbound" - there is no my message in iDoc status.
Maybe i should use another status number? Instead of '64'?

I dont think you should change status number, but i ask you to check it once with proper configuration settings

Similar Messages

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

Idoc Status 53 but Applicaton document not posted message type PORDCR

Hi,
Need your help. I am using message type PORDCR and Basic type PORDCR04 to create Purchase order through inbound Idocs. I am getting correct status '53' Application document posted along with the new Purchase order number. When I am trying to see it in EKKO / or ME23N I could not see this purchase order.
Can anyone please let me know what could be the possible reason for document is not getting posted in in database but Idoc status is correct.?
Thanks in advance.
Regards,
Deepak

check SM13 and ST22 to see if there are any errors there

Inbound Processing of iDoc Status Message

Silly me - I thought this would be simple ...
I am currently changing our bank interface from a customized ABAP solution to use more standard SAP utilities (particularly iDocs). I have the configuration set up to use the PAYEXT message type sending PEXR2002 iDocs to a file port. Our bank is receiving these documents and is returning an iDoc status message containing the status of each payment iDoc that they received from us.
My problem is that I can't figure out how to get these status iDocs to update the status of the corresponding PEXR2002 iDoc.
I am trying to execute an RFC interface to apply these status messages to my system using the following OS command:
D:\usr\sap\VPR\SYS\exe\uc\NTAMD64\startrfc.exe -3 -d RT2 -u xxxxxx -p xxxxxx -c 220 -h SPR32K36 -s 00 -F EDI_STATUS_INCOMING -E PORT=ZFI_INT003
The error message that I receive when this is run is:
RFC Call/Exception: SYSTEM_FAILURE
Group             Error Group 104
Key                RFC_ERROR_SYSTEM_FAILURE
Message        Status record 1 is invalid (TABNAM: 'EDI_DC40')
The port (ZFI_INT003) is the file port that is configured for the outbound file. in WE20, this port has the "Status File" tab set to use the logical file name where the status file is being stored on the server. the startrfc command is connecting to the SAP system and opening the status file. I'm not sure where I'm going wrong here.
Can someone please help get me pointed in the right direction? I've obviously missed something here.
Thanks,
Glen

Hi,
call function modules:
EDI_DOCUMENT_OPEN_FOR_PROCESS
   EDI_DOCUMENT_STATUS_SET
   EDI_DOCUMENT_CLOSE_PROCESS
kind regards,
HP

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

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,
ALE/IDOC Status Codes/Messages----
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
Inbound Status Codes
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

Remove Idoc Status Message

Hi,
Is there any way we could remove the IDoc status message after IDoc posted successfully? I have created the customized idoc status and want to remove the standard message since it is overlapping message.
Any helps is very much appreciated.
Thanks.
regards,
Faread

Hi,
IDOC systat01 can be used to change
the IDOC status very easily
(you put the idoc number and new idoc status basically)
http://help.sap.com/saphelp_46c/helpdata/EN/75/4b3c1cd14811d289810000e8216438/content.htm
REgards,
Vasanth

Add new User Awareness Status Messages(Collboration)... :)

Hello All,
I want to add new user availability status messages (which are related to Awareness Status Selector in Collaboration).
When an user enables the Collaboration Launch Pad, the user can enable on:
i> Auto Detect Status
ii> Not Available
I would like to add essages like "Be Right Back", "In Meeting", etc....just like we have in Yahoo Messenger.
I found the par file which is respensible for such Collboration feaures & its:
"com.sap.netweaver.coll.shared.ui.par"
but when I opened the par file to check the details...noticed that all is in the portalapp.xml file.
Cannot understand where can i add new messages....
Please help...
Awaiting Reply.
Thanks and Warm Regards,
Ritu R Hunjan
Note: Please excuse me for posting this in EP Development Content and not KMC Forum section.
Message was edited by: Ritu Hunjan

Reinstalling isn't a drastic measure w/Snow Leopard. It just replaces all OS components with new and uncorrupted ones and Apple's basic apps, such as TextEdit, Mail, Safari, and Terminal. That eliminates any mucked up ones. Once you assure yourself that the problem's solved, make a bootable backup/clone or Time Machine backup and update via Software Update. Let us know how it turns out.

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, Tracking in SAP PI/PO Single Stack

Hi All,
My PO version: 7.4, SP4. I am not sure my questions below are still a limitation in current PI/PO single stack systems, and hence requesting your help for the same.
1) Is there a way we can track outbound idocs in SAP PI/PO single stack similar to PI abap stack IDX5? ( Note:- I couldn't find any option in IDOC monitoring in single stack SAP PO 7.4, SP4)
2) IDOC status is always 0 in SAP PO 7.4 single stack IDOC monitoring. I am not sure if this status is just specific to my PO system. Any setting needs to be applied?
ps: Please post only relevant answers/solutions
Thanks,
Praveen Gujjeti
Message was edited by: Praveen Gujjeti

Hi All,
As per SAP help: Comparison of IDoc Adapter (IE) and IDoc Adapter (AAE) - SAP NetWeaver PI Reference Documentation - SAP Library idoc status and tracking not supported in current PO versions. May be SAP will add this feature in upcoming PO versions
Auditing, Monitoring ,and Tracing Functions
Attribute/Feature
IDoc Adapter (IE)
IDoc Adapter (AAE)
ALE Audit
Supported
Supported
IDoc tracing
Supported (transaction IDX5)
Not supported
IDoc monitoring
Transaction IDX5
Integration with channel monitor and message monitor (as part of Advanced Adapter Engine monitor)
Status tracking -SYSTAT
(analysis and further processing of messages that have not been processed)
Not supported
Not supported
RFC monitoring
Supported
Not supported
Message persistence in the IDoc adapter
Supported
Message correlation information can be stored in IDoc adapter.
Not supported.
Message is persisted in messaging system with correlation data persisted in adapter.
Regards,
Praveen Gujjeti

IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

Hi All,
I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
Error Detail :
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
This error can have several reasons:
The segment ZPROSEG is assigned to a group whose header segment does not occur.
The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type PROACT01 (extension PROACTEX).
Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
Below is the Details of the Steps which I have followed:
1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
Here when I run syntax check warning appears "No predecessors exist". I am not sure if its okay!!
3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
DATA segnam(27).
READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
IF sy-subrc NE 0.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
APPEND dedidd.
ENDLOOP.
ENDIF.
Finally ran transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
Looking forward for your reply.
Many thanks in advance.

Hello,
Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
lv_index = sy-tabix. " <<--
ADD 1 TO lv_index. " <<--
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
*APPEND dedidd.
INSERT dedidd INDEX lv_index. " <<---
ENDLOOP.
Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

Error Inbound IDoc - Status 51

Hi,
i am new in working with SAP and I am trying to integrate an inbound IDoc type WPUBON via WE19 transaction, l solved all the issues related with ports and partner profiles(they were the first errors). But when I want to check if the process has been done well with the WE05 transaction I get two error messages, both of them with status 51:
The transactions for intermediate document 0000000000052247 could not be written
Message no. /POSDW/INPUT004
Document flow: Error reading model data of object relationship se
Message no. /POSDW/CORE028
Diagnosis
Error reading model data of object relationship se
System Response
The document links could not be updated.
Procedure
Contact your system administrator.
Procedure for System Administration
Check the format of the document links transferred to the POS Workbench.
Thank you very much in advance!!
Best regards,
Ander
Edited by: AAnder on Nov 3, 2010 11:46 AM

General process for a correct IDOC infrastructure is:
Create RFC destination --> SM59 (You can point to local machine for tests)
Create RFC port to process IDOC --> WE21 with the RFC create before
Create FILE port to process IDOC --> WE21
Create LOGICAL SYSTEM (BD54) --> IDOC2FILE
Define partner in WE20 with partner type "LS" --> WE20 ... add message
RECEIVER port ( created in WE21 )
FROM WE19 GENERAte IDOC with LOCAL SYSTEM as sender And FILE PORT as receiver
WE19 is FOR TEST...
tell me if you can understand, sorry for my english ....

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

Set idoc status

Dear experts,
i have an idoc which i work with. My Problem is:
how can i set the idoc status to 51 and mark it as corrupted ?
or how can i let the system mark it like this if it is not possible to do it myself ?
Thanks a lot and best regards
René

Presumably, the 51 status has been triggered by some error condition in your process code. That error condition should have a message associated with it. You should have a table or structure that stores these messages and then at the end of your processing, add those messages to the IDOC_STATUS table. You can also add messages for status 53 (such as the document numbers that you have created), status 68, or any other status value. Look at examples of standard process code and you'll see what I mean but here are a few code snippets:
Conditional error message:
    GV_IDOC_ERROR_FLAG = 'X'.
    GV_STATUS          = C_IDOC_STATUS_51.
    MESSAGE E199(ZCORP) WITH GS_DEL-VBELN INTO GV_MESSAGE.
    PERFORM F9999_ADD_MESSAGE.
Setting the status, adding the messages to the IDOC in a subroutine at the end of processing:
CLEAR IDOC_STATUS.
LOOP AT GT_MESSAGES INTO GS_MESSAGES.
    IDOC_STATUS-DOCNUM = P_DOCNUM.
    IDOC_STATUS-STATUS = GV_STATUS.
    IDOC_STATUS-MSGTY = GS_MESSAGES-MSGTY.
    IDOC_STATUS-MSGID = GS_MESSAGES-MSGID.
    IDOC_STATUS-MSGNO = GS_MESSAGES-MSGNO.
    IDOC_STATUS-MSGV1 = GS_MESSAGES-MSGV1.
    IDOC_STATUS-MSGV2 = GS_MESSAGES-MSGV2.
    IDOC_STATUS-MSGV3 = GS_MESSAGES-MSGV3.
    IDOC_STATUS-MSGV4 = GS_MESSAGES-MSGV4.
    APPEND IDOC_STATUS.
    CLEAR IDOC_STATUS.
ENDLOOP.
IF SY-SUBRC NE 0.
    IDOC_STATUS-DOCNUM = P_DOCNUM.
    IDOC_STATUS-STATUS = GV_STATUS.
    APPEND IDOC_STATUS.
    CLEAR IDOC_STATUS.
ENDIF.

Outbound IDoc status set as 31

Hi Friends,
I am working on the outbound IDoc interface IDOC_OUTPUT_ORDRSP. I modify/add few segments based on the business conditions using the user-exit EXIT_SAPLVEDC_003 (ZXVEDU15). According to the business need, I have to set the IDoc status record as 31. Now IDoc is being created with status record as 30. Is there any way to set the status record with status 31 within the scope of this IDoc interface IDOC_OUTPUT_ORDRSP.
Pls let me know if any user exit for this same purpose. If not possible to set status explain me the reason for that.
Thanks
Hari

Hi,
You can use this standard program RC1_IDOC_SET_STATUS to change IDoc status 30 to another status.
If the program does't exits then try this ...
DATA: L_EDIDC_TAB LIKE EDIDC OCCURS 1 WITH HEADER LINE,
 L_IDOC_STATUS_TAB LIKE BDIDOCSTAT OCCURS 1 WITH HEADERLINE,
 L_IDOC_CONTROL LIKE EDIDC.
 L_IDOC_STATUS_TAB-DOCNUM = <your IDoc number>.
 L_IDOC_STATUS_TAB-STATUS = '68'.
 APPEND L_IDOC_STATUS_TAB.
 CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
 EXPORTING
 IDOC_NUMBER = L_EDIDC_TAB-DOCNUM
 IMPORTING
 IDOC_CONTROL = L_IDOC_CONTROL
 TABLES
 IDOC_STATUS = L_IDOC_STATUS_TAB
 EXCEPTIONS
 IDOC_FOREIGN_LOCK = 1
 IDOC_NOT_FOUND = 2
 IDOC_STATUS_RECORDS_EMPTY = 3
 IDOC_STATUS_INVALID = 4
 DB_ERROR = 5
 OTHERS = 6.
Reward points
Regards
Message was edited by:
 skk

Add message to iDoc status

Similar Messages

Maybe you are looking for