Document RFC Error in DEBMAS IDoc?

Hi Experts,
we use RFC to transfer DEBMAS-Idocs to a JCo-System.
Is it possible to set an Outgoing Idoc to a red/error state if the RFC transfer fails?
Thanks in advance & best regards,
Alex

Hi,
>>>Is it possible to set an Outgoing Idoc to a red/error state if the RFC transfer fails?
sure it's possible - the IDOC is called ALEAUD and it can tell you the status of the IDOCs in ERP (red etc.)
Regards,
Michal Krawczyk

Similar Messages

RFC Error:The BW IDoc type ZSBA011 is not the same as the source system

Hi Experts,
RSA1Source System (Context Menu) Check
I am getting the below error
The BW IDoc type ZSBA011 is not the same as the source system IDoc type ZSBD012 
What might happened wrong.When i checked with my Basis Consultant who is new to job,Replied every this is ok with regeards to RFC.
Where should i check to correct the error
Thanks

Hi,
Did you do a system copy for BW ?
Try a restore (rightclick on your source system) in most cases this will solve the problem.
If not check the notes below:
184322 Procedure after DB copy of BW source systems
886102 System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
325470 Activities after client copy in BW source systems
325525 Copying and renaming systems in a BW environment
184754 Procedure after BW database copy
184447 Building a BW-system landscape
184971 Notes on BW source system connections
140276 Error in source system assignment
524554 Storing destinations in the BW environment
538052 Maintenance of Myself destination in BW
Regards, Patrick Rieken
Message was edited by:
 Patrick Rieken - BI-Formance B.V.

RFC error in idoc to file scenario in PI 7.0

Hi Experts,
I am getting a RFC error message like this below
:u201D RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_XI_SEND_MAIL in remote system (RfcClient[RFC_REJECTION_MAIL]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.u201D
Here Z_XI_SEND_MAIL is a customised function module which is calling some classes. This function module is responsible for sending emails to a group of people. This function module is working fine in acceptance server and development server but throwing exception in production. Thus the users are unable to receive emails. There has been no code changes in the function module. Idocs are being triggrred from sap r/3 system into XI, then being processed by a BPM, finally RFC (Z_XI_SEND_MAIL ) is being called to send email messages. SXMB_MONI is showing that the email message is being send to the RFC properly but communication channel is showing the above mentioned error.
Please suggest me what might be the reason of such errors?
Regards
Anupam

Hello,
Have you tested the production data in your acceptance system or development system for the interface?
Is it working fine??
It seems that the function module is generating exception, which could be due to data.
-Rahul

Error when generating IDoc from MC document - workitem to all the SAP users

A workflow item with the subject of Error when generating IDoc from MC document is sent to all the SAP users' inbox. Is it possible to stop the generation of this work item? If that is not possible, can we limit sending the work item to a specific user/agent instead of all the users in the system?
It appears that these work item or error message are generated when one of the developers reopen the POs and add line items. Moreover, during that time the procurement team blocked the IDOCs from going out to the vendors when changing and resaving the POs. Therefore, we need stop the generation of error message/work item when the IDOCs generation blocked.

Please check Rule 70000141which is the default rule for this task. Inside this rule a FM is attcahed which is reading table EDO13 and EDPP1 where agent is retrieved Probably this table entries are not maintained. This Workflow is getting triggered from Message cOntrol I think.
Please check this link for
http://help.sap.com/saphelp_47x200/helpdata/en/c5/e4aec8453d11d189430000e829fbbd/frameset.htm
Reward points if useful and close thread if resolved

Error when generating IDoc from MC document

Hi,
Our Workflow administrator is getting the following error in his inbox daily for a particular IDOC type.
Error when generating IDoc from MC document
Please let me know how to disable this message.
Regards
Elini.P

Hi experts,
i got the error msg when generating idoc from mc document
this error msg goes to all sap users inbox,how to resolve this problem
pl give me solutions
regards
kumar

Error when posting debmas idoc

i have test run the debmas idoc, when iexecute it i got an an error ' NO BATCH INPUT FOR SAPMF02D 0340 SCREEN' is displayed.. please help me..i have used debmas06 as basic type

Hi,
usually this is due to a field which is either in display only, either suppressed in the online transaction XD01 or XD02.
Try to figure out which field is the one by looking at the data in the idoc in comparison to the fields ready for input in the online transaction.
Alternatively, you can try to process the idoc using the idoc test tool transaction WE19.
Process it using function module IDOC_INPUT_DEBITOR and process the customer master data transaction in order that it jumps online at the first error.
This should help to investigate.
For the fields settings transaction look into OVT0 and OB20
BR
Alain

How To Track the Errors For LSMW Idoc

Hello Expert
While working on Material Master Idoc getting an error message
Error 51 Application not posted
Details: IDoc included in IDoc packet containing an error: transfer it separately
How do i tackle this
Thanks

Hi,
I hope idoc is failing because of problem with the application data. Its not because of RFC. You told that you were getting 51, it means inbound idoc...if its problem with RFC, before creation of idoc itself it should be there...but now idoc created successfully and tried to post / create application document. there it was failing.
Can you give details some thing like, which inbound FM you are using to post the idoc & idoc type.
Regards,
DJ
reward, if its useful

Error: EDI: Error while assigning IDoc number

Hi Everybody,
using XI 3.0 on Linux 64 bit SLES9 with Oracle I got some probleme sending messages from mq series to sap:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>EDI: Error while assigning IDoc number</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: EDI: Error while assigning IDoc number</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What is missing here?
Kind regards,
Michael

Hi Jayakrishnan,
thanks a lot for your answer.
SM59 is working finde. In IDX1 I got the the correct RFC destination entered and a double click works fine also.
The other way around R3 -> XI -> mq series is working fine. Here we are trying mq -> XI -> R3 and it stops sending from XI to R/3.
How to check the IDOC type?
Regards,
Michael

Error while generating IDOC

hi! Friends
Using IDOC I'm transferring the data from one server to another. While Creating RFC to generate an IDOC " are not mutually convertible
Bellow are the steps followed,
1. Declared the Segment parameters as ZSACL_KANBAN     LIKE     EDIDD in Tables section of Function Module
2. Since I'm transferring the records which has been customized for our org. i have created a structure similar to the structure defined in the Segment
3. after fetching the Data from the database assigned the Segment name and Data to the Table defined in the Function module
    zkanban-segnam = 'ZSEG_KANBAN'.
    zkanban-sdata = wa_finaldata.
    append zkanban.
but it throws error as wa_finaldata and zkanban are not mutually convertible.
but if i pass only one column IDOC is generating, but i want to pass 10 columns
how to define according to the Data Segment.
Regards
Kv

hi! Thanks for your reply.
Now I'm able to 10 columns into SDATA but there are mismatch in field size while uploading.
Tried by removing (or) including the preceding zeros for the field but then the data are merging up.
how to concatenate the 10 different columns with the constant field size.
Regards
Kv

ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

Hi,
I got this error in FIle-IDOC scenario.
ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
Is there any other suggestions?

Hi aarthi,
I suggest u chk all d settings dat u hav done..
Steps for ALE settings:-
Steps for XI
Step 1)
 Goto SM59.
 Create new RFC destination of type 3(Abap connection).
 Give a suitable name and description.
 Give the Ip address of the R3 system.
 Give the system number.
 Give the gateway host name and gateway service (3300 + system number).
 Go to the logon security tab.
 Give the lang, client, username and password.
 Test connection and remote logon.
Step 2)
 Goto IDX1.
 Create a new port.
 Give the port name.
 Give the client number for the R3 system.
 Select the created Rfc Destination.
Step 3)
 Goto IDX2
 Create a new Meta data.
 Give the Idoc type.
 Select the created port.
Steps for R3.
Step 1)
 Goto SM59.
 Create new RFC destination of type 3(Abap connection).
 Give a suitable name and description.
 Give the Ip address of the XI system.
 Give the system number.
 Give the gateway host name and gateway service (3300 + system number).
 Go to the logon security tab.
 Give the lang, client, username and password.
 Test connection and remote logon.
Step 2)
 Goto WE21.
 Create a port under transactional RFC.(R3->XI)
 Designate the RFC destination created in prev step.
Step 3)
 Goto SALE.
 Basic settings->Logical Systems->Define logical system.
 Create two logical systems(one for XI and the other for R3)
 Basic settings->Logical Systems->Assign logical system.
 Assign the R3 logical system to respective client.
Step 4)
 Goto WE20.
 Partner type LS.
 Create two partner profile(one for XI the other for R3).
 Give the outbound or inbound message type based on the direction.
Step 5)
 Not mandatory.
 Goto BD64.
 Click on Create model view.
 Add message type.
Step 6)
 Goto WE19
 Give the basic type and execute.
 fill in the required fields.
 Goto IDOC->edit control records.
 Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
 Click outbound processing.
Step 7)
 Go to SM58
 if there are any messages then there is some error in execution.
 Goto WE02.
 Check the status of the IDOC.
 Goto WE47.
 TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
reward points if helpful...
MenoN

Error when updating Idocs in Source System - Urgent

Hi Team,
When i was loading the data from SAP R/3 to BW, i was facing the error "Error when updating Idocs in Source System" (0 From 0 Records).
When i check in the Environment>Transaction RFC->In the Source System, it was displaying the error--
" Import container contains errors (are any obligato) in the Function Module: IDOC_ERROR_WORKFLOW_START_R".
Can any one please help me to solve this error.
This is am Urgent requirement for me to deliver.
Thanks & Best Regards,
Venkata.

Hello VenkaTa,
How r u ?
The workflow settings are not proper it seems. Ask the BASIS people to correct the Work Flow Settings. Then try Updating the IDOCs manually.
Also check the Inbound and outbound IDOCs in the Source system. The outbound should contain some warnings or errors.
Best Regards....
Sankar Kumar
+91 98403 47141

Re : How to Error Handling In Idoc /ALE.

Hi This is Arief ,
I tranfer the Data Through ALE from One Client To Other Client some of Data not Posted ......how check other client wither Data Posted or not ....
How to error Handling In IDocs.....pls Help me.......
Kind Regards
Arief .S

Hi
The exception handling for idocs
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm
Exception handling in File to IDoc Scenario
For RFCs
Re: Passing SAP Exceptions to a sync SOAP Call
Error Handling when using RFC
Exception Handling while Calling RFC - BPM
handle exceptions in remote function modules

Adobe document service error: SOAP Runtime Exception

Hello,
I am trying to test an Adobe Form created using the ABAP workbench SFP transaction, and getting the following error.
Adobe document services error: SOAP Runtime Exception: CSoapExceptionTransport : (100101)
These are the steps I am using.
1. Call SFP transaction and select an ADOBE Form.
2. Function key F8 to test
3. Select the Output device and do "Print Preview"
Our configuration is : WAS 6.40 SP11 and corresponding ADS level. We used the standard SAP ADS configuration guide to setup.
Thanks in advance for any reply.
Regards,
PK

Hi PK
it looks like you have a problem with either your Adobe document services or your RFC configuration. In the current ADS Configuration Guide in the SAP Service Marketplace, you find a configuration quick test in chapter 3.4. The results should tell you if this is the issue.
There are 2 tests you can run:
A. Checking the User and Password
This is a small test where you can check that your entries for user, security role, and passwords are correct.
Procedure:
1. Enter the following URL in your web browser:
http://<server>:<port>/AdobeDocumentServices/Config
where <server> is the name of the J2EE engine where the Adobe document services are installed and <port> is the port of the J2EE engine.
Note that the entries in the URL are case-sensitive.
2. The web page of the web service AdobeDocumentServices is displayed. Choose Test.
3. Choose rpdata(test.) .
4. Choose the Send button without entering any parameters.
5. Enter the same user name and password as given in the configuration steps earlier.
6. Choose Submit.
If the configuration is correct, you get the information about the Version number in the response area.
If the configuration settings are not correct, the page does not change and Submit still appears.
B. Checking the ABAP Connection
This is a small test for checking the RFC destination you have created.
Procedure
1. Log on to your SAP system.
2. Call transaction SE38
3. Enter the name of the test report: FP_PDF_TEST_OO.
4. Choose Execute (F8)
If the configuration is correct, you get the Version Information.
If the configuration is not correct, you get a dialog box with fields for user and password. Check your configuration settings and also the entries you made when creating the ABAP connection.
Hope this helps.
Kind regards,
Markus Meisl
SAP NetWeaver Product Management

ALE distribution error - 0 communication IDOC

Hello,
We are getting 0 communication IDOC generated for message type DOCMAS error for ALE document distribution error. Please advice where to look for the error.
Anirudh

hi,
ani,
u check this,
If you want work items to be created when errors occur for the purpose of error handling, you need to assign the standard task TS40007915 PCROLL to a position or a workflow organizational unit.
Or
You can also distribute dependent objects manually for classes. You can use report program RCCLDIHI to distribute a complete class hierarchy including all classes characteristics, and characteristic values.
Only the message code (004 - change) is allowed for sending a document (message type DOCMAS). This function also creates the document in the target system.
You can control the sending of documents with the indicator Distribution lock. An object with this indicator in its status will not be distributed into other ALE systems.
You can set the indicator in Customizing Document Management System  Define document type  Define status. The distribution lock is read when a distribution automatically starts after a change pointer is set or for an Integrated Distributed PDM Solution (ID PDM).
You can ignore this setting by starting the distribution manually. When you set the indicator Ignore distribution lock in the initial screen, then all documents will be distributed overriding the previously set status.
You control the distribution of object links with the indicator You cannot maintain the object links via ALE and Object link unchanged in target system.
Information about object links are distributed through IDoc type DOLMAS01.
The data is transferred to the workstation application and to storage data in IDoc type DOCMAS04 if an original file exists to a document. The Remote Function Call interface protocol transfers the contents of the original file, for example text or design drawing.
You can determine whether you want originals of a certain document type to be distributed by ALE into another system under the setting Document Management System  Define document type  Define transport of originals for ALE. You can control distribution with various criteria.
You want to distribute all original files of the application WRD (Microsoft Word) for the document type R-1 (report) that are stored in vault VAULT1 (Vault for Office Applications). You do not want to distribute documents of the same document type for the application WWI (Winword 6.0).
You can process the status for the desired objects.
1. Select in Customizing Cross Applications Components  Distribution (ALE)  Standard ALE Business Processes  Logistics  Master Data Distribution  Integrated Distributed PDM Solution (ID PDM)  Object status (for example, Define BOM status).
2. Process the indicator Distribution lock
ben

Error in Transfer (IDOC and TRFC )

Hi experts
I am getting the error in Transfer (IDOC and TRFC ) Info IDoc 1 : Sent not arrived : Error posting data to port" when I am trying to Upload data by executing an infopackage.
Pl. advice.
Thankls in advance
Dinesh Sharma

Hi Dinesh,
This latest error code E0 266 & is really a Basis one (BC-MID-ALE); not BW.
If the error occurs all the time then please do the following.
Firstly, please ensure that the relavant RFC destination is set up as per SAP Note 613389. The use of a logon language is a must.
Secondly, please also add the value of SCP2 as well as SCP5 to the role of the RFC user as per Note 784381 (SCP2 isn't mentioned in the note but please add it anyway) - This should resolve your issue.
If you only see this error sometimes, then set the flag in tcode OYEA as per Note 784381.
Hope this helps,
Colum

Document RFC Error in DEBMAS IDoc?

Similar Messages

Maybe you are looking for