IDoc not visible in target R3 system

Hello
I am working on File-to-IDoc test scenario where I am sending CREMAS IDoc to R3 system (through IDoc receiver adapter). I performed all the necessary configuration which includes
RFC Dest of type R3 in both the systems
Creating ports in both the systems with port name similar to logical sys name of business system
Creating Partner profile for the above port with Inbound message type as CREMAS
When I am viewing the message in SXMB_MONI it shows successfully processed but Outbound status is still showing as "Message Scheduled on Outbound Processing". Also when I checked on the R3 side using we02, I could'nt find any IDoc over there. I checked in the trace where it states "Async processing completed OK".
Am I missing any configuration on R3 side which is not processing an IDoc?
Thanks in advance.
Regards
Rajeev

Hello
Thanks for the replies but i did configuration exactly as shown in the weblog. My RFC Destination is working fine.Also theres nothing in SM58. Also in SMQ2 "Nothing is selected" that means the message is processed successfully.
In SXMB_MONI it shows status as "Processed Successfully" but the Outbound Status is "Scheduled for Outbound processing".
In addition to this, I tried to test run (through SE37
) the FM "IDOC_INBOUND_ASYNCHRONOUS" in the receiving system with the control paramters of XI and that is creating the IDoc.
Regards
Rajeev

Similar Messages

Idoc not visible in Business system

Hello Experts,
I am trying to configure a scenario where in I am trying to use the IDoc ZCNOSE_PRICAT.PRICAT02.ZPRICAT1.
However, this IDoc is not reflected in the business system in which I am using.
I have already released the extension from the backend SAP system.
Can you please suggest what I am missing such that the extension is visible in the Business system.

Hi,
You imported the idoc structure into the ESR, under a specific SWCV.
Make sure that SWCV is linked to your Business System in the SLD.
Kind regards,
Dimitri

** File to IDoc scenario - IDoc not created in target system

Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.

Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Thanks,
Satya

IDOC not visible in IR but metadata successfully imported

Hi,
I have this wiered issue.
I want to import IDOC WPUSKR01 (cashier productivity) from BI.
But when I connect to BI system from IR to import Idoc structure, this IDOC is not visible.
But I can manually import the metadata from BI in idx2.
Now how to import this in IR?
I have imported other Idocs (like WPUBON) before and did the scenario successfully for BI.
Regards,
Anirudh Vyas.

Hi,
In BI Tcode we82 I have manually added the entries for WPUKSR01. Now Idoc is visible when importing in IR.
I have checked all the segments in we31, they are all released.
But it gives error:
Error: IDoc type WPUKSR01 contains errors (unable to read segments)
Then, I checked in R/3, there also WPUKSR01 was not there in we82. I manually added there and I was successfully able to import it in IR.
But the same thing is failing in BI. I have SAPALL permissions in all the systems.
Can I use Idoc imported from R/3 in scenario for BI?
regards,
Anirudh.

Outbound IDOC not received at the receiver system.

Hi,
Im sending an IDOC from sap to a non-sap system. During this process, from sap system it is executing successfully without any erros and the status is also '03' .
The problem is that the other system is unable to receive the IDOC sent from SAP system.
The connection is like TCP/IP and the registered server program is given as 'PROGRID' in RFC destination.
I would like to know what would be the possible cases where this IDOC is not received at the receiver system.
The configuration is perfect as per my knowledge. Just want to confirm one thing 'do i need to include any message type such as "SYNCH".
Awaiting for your solutions.
Thanks
rohith

Hi,
If the IDOC is sent successfully from the sender system then the status of the IDOC will be '03' , no matter whether the receiver has received the IDOC or not.
As per your case,
Check the Partner Profile parameters , whether the basic and extended message types are used properly.
The message type Synchron (Sync) is generally needed in Inbound IDOC side. Check whether you have added SYNCH or not.
Hope this Helps.
Regards,
Abhinab Mishra.
Experience is the name everyone gives to their mistakes.

Idoc not found in the receiving system

Hi Experts,
In the sending system idoc status is 03 (Data passed to port OK), but in the receiving system the idoc is not there. How to rectify this error?
Thanks & Regards,
Soumya.

Hi Soumya,
Check the RFC connections, becoz in the sending system once the IDOC is sent the status becomes 03 it does not check whether the IDOC has sent to the received system, if there are any errors before sending the IDOC it will not send and the status will be 01, so check the RFC connections at sending and receiving systems.......
Reward points if this helps............
Regards,
Ravi G

Inbound IDoc not getting generated in XI System

Hi all,
I have created a scenario following the given weblog:
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
The first half of this scenario is working fine and the idoc data is getting posted into the the oracle table successfully.
The business process is successfully sending the acknowledgement IDOC 'ALEAUD' to the XI server using an HTTP Receiver Channel.
The problem is that no inbound IDOC can be seen in the XI system using tcode we05.
Next the xi system has to send the same IDoc to the R/3 system. But as no IDoc is getting generated in XI, nothing gets sent to R/3.
Can anyone suggest what could be the possible error.
Pls help.
Regards,
Neetu

Hi,
You will not see that IDOC in WE05 of the XI system. You can see that only in SXMB_MONI. XI system will not store any IDOC. When it enters XI it is a XML message and it will not post any IDOC that you can see in WE05.
If you need to send the IDOC back to R/3 system, you can use BPM and send back the IDOC to R/3. If you need few details from Oracle tables that is to be sent back to R/3 then get those values from Oracle tables and fill in the same IDOC and send it back to R/3.
Try this and let me know.
Thanks,
Prakash

IDOC not visible to import to XI, but on R/3 created and released

Hi guys!
I have problem with import IDOC into my repository objects. It is not visible to import, but on the r/3 side it is created and released.. Other IDOCs are visible, but not the one I need.. The IDOC I need is custom, created few moments ago..
What could be wrong?
Thanx for answer!
Olian

Olian,
you need to release our IDOC to be visiable for XI.
goto we60 see if you can find the our ZIDOC if you dont then goto WE30 then type our IDOC then goto Edit tab on top and select set release.
if you have done this then do this
T/C Code: WE82
pass the IDOC type , message type and sap version then save.
now our output types andIDOC assigments to IDOC types are done
Regards
Sreeram.G.Reddy
Message was edited by:
Sreeram Reddy

Datasource not visible in rsa1

Hello,
my datasources are not visible in rsa1 -> source systems.
I tried replicate, check connection, repair connection, run report RSAOS_METADATA_UPLOAD, upload metadata, etc.
Now I have no clue.
In roosource datasourse is active (in sourcesystem).
Any idea?

Wow!! I loved the way it works :).
I was trying all sorts of things to find out where did my datasource go. then i stumbled upon your recommendation Yogesh. And it did work. everything appeared perfect after i logged off n then login.
Thanks a lot Yogesh.
next time when I get a weird error the first thing i'm goin to do is to log off.

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.

IDOC not reaching destination system

Hello,
I am trying to send DOCMAS type IDOC from one SAP sys to another SAP sys.The IDOC has the status 03 (The IDoc was sent to an SAP system or an external program via a transactional RFC) but i dont see the IDOC in the target sys.
Please let me know what could have gone wrong.
Thanks,
Rakesh.

Hello Rakesh More ,
First let us know how you corrected the previous error???. What was wrong?
Then talk about the next issue.
If you maintain properly the Inbound IDOC partner profile this error should not come. Make sure you have the below things set-up properly:-
1) In the inbound IDOC in the destination system there should be a partner receiver in the IDOC control data. Make sure you have maintained the partner profile for that partner and for the partner type as well.
2) For the partner make sure you have maintained the proper inbound mesaage type and process code properly.
Thanks,
Greetson
Edited by: Greetson Shunmugasundaram on Aug 1, 2011 9:47 PM

CUA roles sometimes do not match the target system

Hi,
We are using CUA on Solution manager to assign roles to our different systems. Every now and then what is in CUA does not match the target System.
I know that you can look at the idocs using WE05 and see what the root cause was, fix it and then re-assign the role.
The problem is that when you assign the role using CUA, it doesn't warn you that the transmission failed on the target system.
We just went live last week, so I am added and removing roles from many different users using SU01 and SU10 and I do not think it is a valuable use of time to sift through the idoc logs every time I make a change. Especially, since most of the time it works.
Is there a better way to monitor the Idoc logs? Can you have it send a notification (email for example) when there is an error? Is there a better process then WE05?
Thank you in advance for the help!
Neil

Neil. It was a long time I played around with CUA. But I am remembering some transaction where you had the logs. Think it is SCUL.
I searched saphelp and got the following hits for you:
http://help.sap.com/saphelp_nw70/helpdata/EN/c1/db4063fd3111d5997a00508b6b8b11/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/cc/50b43be7492354e10000000a114084/frameset.htm
Best of luck to you!
Regards Fredrik

My business system not visible

Hi all,
I created one business system using 3rd pary when I
am going to assign in "Integration Directory" it is not
coming in list. Then when I am trying to create the BS
in SLD with same name and Logical system then it is
showing "Already exits". But in SLD also not
visible...??? What will be reason. How to get my BS in
ID?
regards,
Khaja.

Hi,
It is not added in any other scenarios. When I done "Cache Notification" then I am getting this Error
"com.sap.aii.ib.server.abapcache.CacheRefreshException:
Unable to find an associated SLD element (source
element: SAP_XIIntegrationServer, [CreationClassName,
SAP_XIIntegrationServer, string, Name, is.01.apollo,
string], target element type: SAP_BusinessSystem)
Regards,
Khaja.

CCMS alert monitoring data for ORACLE is not visible in Central system

Hello,
I have installed sapccm4x agents in the CI of the Satellite System and it shows in the Central System as sucessfully registered under Agents for remote System and the RFC Connection test is also successfull. When i check in RZ20 in Central System not all the predefined monitors are visible of the Satellite System in the Central System and mainly the MTE element ORACLE. The database,CI and other instances on the Satellite System are installed on separate hardware. As said the database is installed not with the CI but a standalone.
Please let us know what needs to be configured in order to get the MTE element of ORACLE to show in the Central System.
Thanks,
Vinod Meno

Bhudev,
Thanks for the quick respose..
1.Sapccmsr agent is installed on Java standalone server and it has been sucessfully registered and running and we can grep the process to see its state as well as in the Central System i can see under ccms agents for remote systems it shows and the RFC connection test is also sucessfull.
2.Yes we are sending the data from the DB to CI first,but we also want the data visible in the Central System mainly for the MTE element Oracle.The filesystem of the Satellite Systems shows up in the Central System but i am intrested to capture the MTE element Oracle since we plan to monitor the tablespaces threhold .
I am thinking of opening an SAP message but i am trying to see if i can get some info that can give me the result.
Regards,
Vinod Menon

Solution Import Failure Message: Cannot add a Root Component 'GUID' of type 29 because it is not in the target system

Hi all,
Please refer to the error:
Root Components import: FAILURE
[2015-04-10 17:04:48.126] Process: w3wp |Organization:0937f109-45df-e411-80cf-0050560100db |Thread: 43 |Category: Exception |User: ac011cf7-ad36-405b-91cf-2155ca15efb1 |Level: Error |ReqId: d3924c06-ad4b-4d5e-a204-70f8170016e1 | CrmException..ctor
ilOffset = 0x30
at CrmException..ctor(String formattedErrorMessage, Int32 errorCode, Object[] arguments) ilOffset = 0x30
at ImportRootComponentsHandler.GetSolutionRootsCollection(Boolean throwIfMissing, Boolean skipRibbonCustomization) ilOffset = 0x209
at ImportRootComponentsHandler.ImportItem() ilOffset = 0x8
at ImportHandler.Import() ilOffset = 0x43
at RootImportHandler.ImportAndUpdateProgress(ImportHandler ih) ilOffset = 0x7
at RootImportHandler.HandleNonMetadataHandlers(String[] ImportEntities, ImportHandler& ihForCurrentPath) ilOffset = 0x33
at RootImportHandler.RunImport(String[] ImportEntities) ilOffset = 0x1D8
at ImportXml.RunImport(String[] ImportEntities) ilOffset = 0xE
at ImportXml.RunImport() ilOffset = 0x5BF
at ImportXmlService.ImportSolutionSkipCapable(Boolean overwriteUnmanagedCustomizations, Boolean publishWorkflows, Byte[] customizationFile, Guid importJobId, Boolean convertToManaged, Boolean skipProductUpdateDependencies,
ExecutionContext context) ilOffset = 0x46
at RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) ilOffset = 0xFFFFFFFF
at RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) ilOffset = 0x25
at RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) ilOffset = 0xCF
at LogicalMethodInfo.Invoke(Object target, Object[] values) ilOffset = 0x4F
at InternalOperationPlugin.Execute(IServiceProvider serviceProvider) ilOffset = 0x57
at V5PluginProxyStep.ExecuteInternal(PipelineExecutionContext context) ilOffset = 0x200
at VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context) ilOffset = 0x65
at Pipeline.Execute(PipelineExecutionContext context) ilOffset = 0x65
at MessageProcessor.Execute(PipelineExecutionContext context) ilOffset = 0x1C5
at InternalMessageDispatcher.Execute(PipelineExecutionContext context) ilOffset = 0xE4
at ExternalMessageDispatcher.ExecuteInternal(IInProcessOrganizationServiceFactory serviceFactory, IPlatformMessageDispatcherFactory dispatcherFactory, String messageName, String requestName, Int32 primaryObjectTypeCode,
Int32 secondaryObjectTypeCode, ParameterCollection fields, CorrelationToken correlationToken, CallerOriginToken originToken, UserAuth userAuth, Guid callerId, Guid transactionContextId, Int32 invocationSource, Nullable`1 requestId, Version endpointVersion)
ilOffset = 0x16E
at OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, UserAuth userAuth, Guid targetUserId,
OrganizationContext context, Boolean returnResponse, Boolean checkAdminMode) ilOffset = 0x1F1
at OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode) ilOffset
= 0x2D
at OrganizationSdkServiceInternal.Execute(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode) ilOffset = 0x26
at InprocessServiceProxy.ExecuteCore(OrganizationRequest request) ilOffset = 0x34
at PlatformCommand.XrmExecuteInternal() ilOffset = 0xF6
at ImportSolutionCommand.Execute() ilOffset = 0x20
at DataSource.ImportSolution(Byte[] customizationFile, Boolean overwriteUnmanagedCustomizations, Boolean publishWorkflows, Guid importJobId, Boolean convertToManaged, Boolean skipProductUpdateDependencies, IOrganizationContext
context) ilOffset = 0x0
at SolutionImportProcessPage.ImportSolution() ilOffset = 0x123
at SolutionImportProcessPage.ProcessRequestData() ilOffset = 0x4A
at SolutionImportProcessPage.ProcessAction(String action) ilOffset = 0x92
at AppUIPage.OnPreRender(EventArgs e) ilOffset = 0xD
at Control.PreRenderRecursiveInternal() ilOffset = 0x54
at Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) ilOffset = 0x6D3
at Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) ilOffset = 0x3C
at Page.ProcessRequest() ilOffset = 0x14
at Page.ProcessRequest(HttpContext context) ilOffset = 0x33
at CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() ilOffset = 0x18D
at HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) ilOffset = 0x15
at ApplicationStepManager.ResumeSteps(Exception error) ilOffset = 0x10A
at HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) ilOffset = 0x5C
at HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) ilOffset = 0x16A
at ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType) ilOffset = 0x4B
>Crm Exception: Message: Cannot add a Root Component 0ffbcde4-61c1-4355-aa89-aa1d7b2b8792 of type 29 because it is not in the target system., ErrorCode: -2147188705
[2015-04-10 17:04:48.126] Process: w3wp |Organization:0937f109-45df-e411-80cf-0050560100db |Thread: 43 |Category: Platform.Sql |User: ac011cf7-ad36-405b-91cf-2155ca15efb1 |Level: Info |ReqId: d3924c06-ad4b-4d5e-a204-70f8170016e1 | BusinessProcessObject.ExecuteNonQuery
ilOffset = 0x28
I am getting this coming up in the error log when I attempt to import an unmanaged solution.
After searching on google Type 29 refers to a workflow.
I go into the source system and query the database by the GUID and discover that it is actually a Business Process Flow called 'Phone to Case Process'.
I do not have this process in my target system as I deleted it.
Looks like this is one of the out of the box ones. I don't think we we have changed this one much.
What does this mean and what should I be looking for??
Anyway how do I remove this offending process from the unmanaged solution xml file and attempt to re-import it?
It doesn't look like I can generate the solution again without the offending workflow/process..

I managed to resolve this issue after looking at this thread:
https://social.microsoft.com/Forums/en-US/fddff17f-1cca-4d33-a666-60c08ad76b0c/crm-2011-import-failure?forum=crmdevelopment
Just modify both solution and customizations xml by searching for the guid and removing the root component

IDoc not visible in target R3 system

Similar Messages

Maybe you are looking for