Tracking Idoc status in target system from XI

Hi
We have done File to IDOC Scenario succesfully i.e HR
data from file has been mapped to HR Idoc(HRMD_A06) .
Now when Idoc is posted to R/3 , SXMB_MONI shows
successful status(Idoc posted successfully) .
But when we check in R/3 in WE05 transaction ,though
the idoc is present but it shows status 51/52
with message "Idoc could not be posted" /"IDOC not
fully posted" .
In this case how can we track in XI whether the Idoc
is properly posted in the target system(i.e R/3) .
Since XI only shows that Idoc was successfully sent
irrespective of the status in R/3 .
Please suggest as we are new to XI .
Regards,
Shikha

Hi
Thanks for the guide.
we are not sure of the steps to configure it in R/3
system so that it sends the acknowledgement back to XI
system.
When we tried to configure it as per the guide , for
test purposes we executed the program RBDSTATE but it
gave message "No parties are interested in the selected
data" .
Please guide us on this .
Thanks
Shikha
Message was edited by: Shikha Jain

Similar Messages

How to check the status of an IDoc in the Target system

Hi Experts,
we are using a self-made program to send Material and BOMs from Client A to Client B into the same ERP System.
How can I check the status of an IDoc in the Target Client B (like BD87 - ALE Monitor) ?
If you have some examples or Function, please give me the information.
Rewards if helpful.
Regards,
David

Hi David
As mentioned in the earlier reply you can check your status with tcodes:-BD87,WE02,WE05.What i guess from your querry is the staus of your idoc whether posted or not in target client B.Check in the target client for the message type which you are using (since its an program that means you must be using an customised idoc type or standard) .You might have maintained Basic type tcode:-WE30.Give in your messagetype,Basictype,Created at and executed using tcode :- BD87.The prerequisites are you need to create an Partner Profile(WE20) .For this you need to create to provide in your message type and Process code(we41,we42,we57).If you have to create an process code for customised one(se37) .You need to actuivate the idoc inbound processing .If you are using a file in your file make it sure the port is being maintained for the same to chek for unicode format in tcode :-WE21 (check or uncheck).
For standard BOM i recon you are using message type :-BOMMAT and Processing code as:-BOMM.Its always advisible that instead of using an whole abap program you need to have an ETL tool that would take care of the extraction of data provided your client do have existing Legacy system in its place since it would be much faster and easier.
Regards
Somnath

IDOC status to sender system

I configured IDoc within 2 clients in same server, when I send IDoc to receiver it is giving 03 (success) but in receiving system IDoc gives error 51 as some data is not maintained, i am using "Z" function module for inbound IDoc
question - how to send that same error message to the sender

Hi Ankush ,
question - how to send that same error message to the sender?
I have done the same requirement . Please find the below Procedure
-> before ending of the Custom function module check whether Idoc is Success or not .
   IF (error)
LOOP AT idoc_status INTO wa_idoc_status
                      WHERE   docnum = idoc_data-docnum . "Loop the Idoc Status table
l_i = 0.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
   id              = wa_idoc_status-msgid
   lang            = '-D'
   no              = wa_idoc_status-msgno
   v1              = wa_idoc_status-msgv1
   v2              = wa_idoc_status-msgv2
   v3              = wa_idoc_status-msgv3
   v4              = wa_idoc_status-msgv4
IMPORTING
   msg             = l_msg
EXCEPTIONS
   not_found       = 1
   OTHERS          = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
l_i = l_i + 1.
CASE l_i .
    WHEN c_1.
      MOVE l_msg TO   wa_zf40-error_msg1.
    WHEN c_2.
      MOVE l_msg TO   wa_zf40-error_msg2.
    WHEN c_3.
      MOVE   l_msg TO   wa_zf40-error_msg3.
    WHEN c_4.
      MOVE l_msg   TO   wa_zf40-error_msg4.
    WHEN c_5.
      MOVE   l_msg TO   wa_zf40-error_msg5.
ENDCASE.
ENDLOOP.
->Now create a Ztable to make the error descrptions.(Matian some Key fields to identify the Idoc .
->After this create   a RFC to read the entries .
I hope this helps to you.Please let me know if u have any query.
Rgds
Sree M
Edited by: Sree Merugu on Mar 27, 2008 6:22 PM

How to get status of target system battery level

Hi,
I want to get the current battery percentage on the target system with labview. Does anyone have DLL that I can use, or can someone please help me. The target system connected to the Host system running labVIEW via TCP/IP.
thanks,
John

The DLL is Windows only though....
What target are we talking about? Is it a RT Desktop? A Windows Laptop?
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Set WBS status in Project System from CRM Status

Hi Gurus
I am figuring out a solution for how to influence WBS element status in Project Systems in ECC from the campaign/Marketing plan status in CRM. Has anyone done it before or is there any BADI for it.
Your help is greatly appreciated.
Regards
-MP

Your yourself answered your question.
"Can we create our own list of system status"
"Our own" status creation and maintenance feature within SAP in called "User Status".
Please follow link below to have additional information regarding system status.
link: [http://help.sap.com/saphelp_erp60/helpdata/en/a9/8a853488601e33e10000009b38f83b/frameset.htm]

Idoc status 51 while loading from R/3 to PSA

hi experts,
I am loading from R/3 to BW (fiar data), the request is in yellow status and running for long time and showing zero(0) records.
i have checked that some of the idocs are not posted.
when i try to push through BD87 still the status is showing 51 only.
can you plz giv solution for this.
regards
venuscm

Hi,
Maybe this is due to bugs in the TRFC programs that are solved with the
attached notes:
1280898,,IDoc hangs when it is to be sent immediately with
1338739 RFC calls in the wrong system
1377863 max no of gateways exceeded
Also please refer to the following note for additional info:
1250813 SAPLARFC uses all dialog work processes
1403974 Determining the maximum connections in transactione error
I hope it helps you.
Regards,
Fran.

IDoc: Status: Application document not posted

Hi Friends,
       I am New to ALE/IDOC. Based on the ALE_QUICKSTART documentation. I have tried to send material from one client to other client. (within system) To do that
I have created two logical systems and assigned them to corresponding clients.
Created a RFC destination and assigned logical systems.
Created Distribution model in sending client.
Created partner profile in both clients.
Created Material and send to receiving system using BD10 tcode.
I checked Idoc status in Sending system, Idoc status is 03-Data is passed to port OK, status 30-Idoc ready for dispatch and status 01- Idoc generated.
But in receving system (Inbound Idoc)- I got status- 51-Application document not posted and Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT.
I also checked partner profiles in both systmes- both r same.
Kindly tell me what went wrong and what should i do.
Pl.provide answers pertain to this problem only.
Thanks in advance,
S.Senthil

Hi Chris,
        Thanks for ur reply. I am not using is-retail and I have Generated MATMAS idoc in sending system.
      Kindly provide me answer.
Thanks in advance,
s.senthil kumar

How to send IDOC Status confirmation

HI,
I would like to know an STANDARD way of sending the IDOC status to XI system.
The scenario is as follows:
INVOIC01 reception: EDI -> XI/PI -> SAP
(using WE20 EDI partners LI)
I need to send the IDOC INVOIC01 status back to XI/PI.
The RBDSTATE program just works with LS partners.
Any idea to solve that?
Please remember that just using the SAP standard functionalities. Not developing any kind of "Z" program.
Thanks a lot!
Demétrius

Hi,
Even though the acknowledgment is sent by your vendor it is going to come to your XI system, so from the XI system you send the status idoc and then post in SAP.
Your XI system can be registered as an Logical system to your SAP system and your problem is solved.
Thansk,
Mahesh.

How to create empty text file on target system for empty source text file

Hi All,
I have an issue in handling empty file in the Text (FCC) to Text (FCC) file scenario. Interface picks text file and delivers on target system as text file. I have used FCC in both sender and receiver CCs.
Interface is working fine if the source file is not empty. If the source text file is empty (zero Bytes), interface has to delivery an empty text file on target system. I have setup empty file handling options correctly on both CCs.
But when I tried with an empty file I am getting the error message 'Parsing an empty source. Root element expected!'.
Could you please suggest me what I need to do to create an empty text file on target system from empty source text file?
Thanks in Advance....
Regards
Sreeni

>
Sreenivasulu Reddy jonnavarapu wrote:
> Hi All,
>
> I have an issue in handling empty file in the Text (FCC) to Text (FCC) file scenario. Interface picks text file and delivers on target system as text file. I have used FCC in both sender and receiver CCs.
> Interface is working fine if the source file is not empty. If the source text file is empty (zero Bytes), interface has to delivery an empty text file on target system. I have setup empty file handling options correctly on both CCs.
>
> But when I tried with an empty file I am getting the error message 'Parsing an empty source. Root element expected!'.
>
> Could you please suggest me what I need to do to create an empty text file on target system from empty source text file?
>
> Thanks in Advance....
>
> Regards
> Sreeni
the problem is that when there is an empty file there is no XML for parsing available. Hence in case you are using a mapping it will fail.
What ideally you should do is to have a module that will check if the file is empty and if so write out an XML as you want with no values in the content/fields.
Or the next choice would be to have a java mapping to handle this requirement. I guess that on an empty file the java mapping will go to an exception which you can handle to write out your logic/processing

IDOC status on 03 but not recieved on target system

Hi,
We are recieving inbound idoc from external system and processing Inbound IDOC on SAP system, after processing inbound idoc on SAP we are sending status outbound idoc to external system.
The above functionality was working fine before upgradation.
after upgradation we have recreated RFC (TCP/IP) connection, updated at port level and also configured the new SAP system details ( sid, Hostname, service programsname...) on external system correctly.
Now we are recieving inbound idoc from external system on upgraded system,after processing inbound idoc details on SAP system, generating outbound idoc from SAP and it reaching the outbound prot sucessfully on 03 status with green light.
But external system is not recieving the IDOC. How to find why idoc is not reaching external system even though it is sucessfully passed at outbound port level with green light status 03.
We have also checked the SM58 for TRFC entries but we didn't identified any entries on SM58. Please help us on this issue
Thanks,
Raju

Hi Raju,
As mentioned by The specified item was not found., the one common problem for the IDocs not being sent might be a missing COMMIT WORK. I.e. when using the standard SAP API's for sending outbound IDocs, SAP actually creates the IDoc and registers an update function for sending the IDoc out. So without the COMMIT WORK, the IDoc usually exists on the database (implicit or database commmits), is in status 03, but hasn't been sent out and cannot be found in the outbound RFC queue (because SAP never tried to send it).
If you're convinced that a COMMIT WORK is happening (and after trying to send the outbound IDoc) then I'd try the following: Replace the used RFC destination (or re-define it temporarily) with one that points to the same system from where you're sending. If you don't see the IDocs as inbound IDocs or in the outbound RFC queue, the sending never happens. (Ok, might be a moot point if you completely trust your external system, but usually it's good to even rule out the most unlikely causes - if it's simple.)
So if this didn't help, maybe you can provide some further insight into how you're creating/sending the outbound IDocs. This could help us in trying to get some answer, but for a starter the COMMIT WORK mentioned by The specified item was not found. is in my opinion the best candidate.
Cheers, harald
p.s.: Even if you're using ALE, I don't think it could be due to anything in your distribution model as mentioned by The specified item was not found.. If you wouldn't have setup the distribution model, the SAP API's should create a master IDoc in memory and then no communication IDocs (since there's no recipients or due to filtering) and thus there should be no outbound IDocs on the database.

Idocs are unable to transfer from R3 to PI system, IDOC status is 03

Hello Gurus,
Idocs are unable to transfer from R3 to PI system, IDOC status is 03
in sm58 getting below error
RFC are working fine
"EDISDEF: Port SAPCEP segment defn Z2SH_DESCR000 in IDoc type MATMAS03 CIM"
Regrds
vamsi

Hi,
I am also facing same problem, Can any one suggest me what is the issue..

SAP Idocs -How to handle response from target system

Hi,
I am working on a scenario in which I will send Idocs asynchronously from SAP thro a SOAP adapter to a webservice deployed on the target system.
After the Idoc data is posted in the target system,the target system will send the acknowledgement for the receipt(basically response message).How to handle this scenario?
SAP Idoc( outbound asynchronous)---> SAP XI3.0(soap adapter) ---> Target system(inbound synchronous)
Do I need to go for BPM to handle this situation?
Is there any alterantive to BPM.
If any of the forum members who have worked on the similar scenario could help me in finding a better solution,I will be thankful to them.
Thanks,
Leo

Hi Udo,
Thanks for the info.My scenario is like this.
SAP R/3 Idoc -> SAP XI 3.0 <-> Webservice in the target system.
The webservice in the target system will receive the Idoc as a request messsage and send a response message synchronously.
Since Idoc is sent asynchronously( I believe Idocs sent from SAP are always asynchronous),there is no Proxy waiting in SAP R/3 to receive the response message from the target system.
If I go for BPM for the above scenario,will the BPM steps look like the following.
1)Receive Idoc from SAP.
2)Send Idoc sysnchronously to webservice
3)Receive the response from the webservice synchronously.
4.Post the response message to a proxy which can handle it further in SAP R/3.
Please note that my knowledge in BPM is limited and correct me if I am wrong.
Thanks in advance
S.Banukumar

IDoc Status 02 ( Could not find code page for receiving system )

Hi All,
I am getting Idoc status 02 when I am trying to send IDocs from ECC to PI system ( Production ).
Error description.
Could not find code page for receiving system
Message no. E0266
Diagnosis
For the logical destination PIP001, you want to determine the code page in which the data is sent with RFC. However, this is not currently possible, and the IDoc cannot yet be dispatched.
Procedure for System Administration
Possible causes are:
1. The entry no longer exists in the table of logical destinations.
2. The target system could not be accessed at runtime.
3. The logon language is not installed in the target system.
4. In the destination system, no logon language is maintained
Please help.
Thanks - Vinay.

Hi Vinay,
Status 02 occurs when data is not passed to port suceessfully. Check the RFC desination is working fine and your able to connect to target system and also check correct port is assigned.
Regards,
Vinod.

Not been able to export data from FDQM to target system

Hi,
Am not been able to export data from FDQM to my target system which is Hyperion Enterprise 6.4
I have imported, Validated the mapping but as soon as i click on export after creation of the export file the system throws an error as "*Error: Arguments are of the wrong type, are out of acceptable range, or are in conflict with one* *another*". Also am pasting the error log down below
** Begin Enterprise Adapter Runtime Error Log Entry [2009-08-20-16:10:27] **
ERROR:
Code.............. 10230
Description....... Data Load Errors.
Enterprise API Return Code: ALREADY_LOCKED_RO-.
Procedure......... clsHPDataManipulation.fDBLoad
Component......... upsHE6xG4A
Version........... 100
Thread............ 6028
IDENTIFICATION:
User.............. administrator
Computer Name..... HYPERION
ENTERPRISE CONNECTION:
App Name.......... GCIP_S
Connect Status.... Connection Open
GLOBALS:
Zero-For-No....... True
INI File Path..... C:\WINDOWS\HypEnt.ini
NameCat.txt Path.. C:\Hyperion\FDM\GCIP\Outbox\Logs\NameCat.txt
NameCat Entity....
NameCat Category..
NameCat Exists.... False
Any suggestions any one, what should i do

Hello,
Is it possible that the entity that you are loading to in Enterprise is locked? It appears that it may be per the below error. You can only load to unlocked intersections, so I would start by checking the catagory and entity combination for being locked.
Regards
JF

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

Tracking Idoc status in target system from XI

Similar Messages

Maybe you are looking for