Urgent: IDOC Error

Hi SDN's,
We are getting error
"system setting does not allow in changing object Idoc XXXXX."
How to resolve it.
It is a bit urgent..
Please help us..
Thanks in advance...
Regards,
Rahul

so what exactly are you trying to change. The content, the structure, or what? The basic Idoc type itself?
If it is an already existing (inbound / outbound) Idoc with actual IDoc number?

Similar Messages

Urgent IDOC Error : No description transferred

Hello
I am trying to load an IDOC for Material Master
Using MATMAS 05
Getting a error 51 Application not posted
When check its details it says No description transferred
There is no long text for this error
Your response is greatly appreciated
Thanks

1) You are creating outbound or inbound.
Error 51 is for inbound. Just to make sure.
I think you are doing some abnormal process that's why you didn't see any message.
Thanks,
Narayan

Hi Ragarding....Idocs Errors, ODS Functionality

Hi Gurus
Pls Urgent
Can U explain the --> Idoc Errors....and how to solve
                          ---> Ods( Whether functionality...Addition / Subtraction)
                          ---> Ticket Procedure and how do maitain this
                          ---> how many views can be created in generic Extraction
pls do the needful
regds
Pandu

HI,
ODS : has overrite functioanlity where info cube has additive fucntioanlity.
So, every time we shud recommend ODS in between datasource and Infocube.
Another imp point is , if the datasource is not supporting delta fucntionality, how do we handle the situation? right.
So use ODS, from the datasource load the data till ODS and as ODS contains changelog with 0recordmode with before and after images, we can perform the delta functinality to the Cube.
Ticket procedure:
See, we have third party ticketing tools like Gremedy, clarify, lotus notes etc.
Ticket means- defect or issue in the data or application or technical object.
So user raises the ticket and it wil assigned to concerned technical resource by the helpdesk and based on the priority of the issue, technical peopel should resolve the issue or ticket with in the SLA(Service level aggrerment).
Views : View is nothing but a image of the tables.
So we can call up multiple tables in a view for generic extraction.
Hope this info helps.
Thanks,Ramoji.

Urgent,showing error while running form..pls,help...

Hi,
I have created my own view named GP_NUIF_V and have also successfully established a Database connection,using FWK_TBX_TUTORIAL.I have developed a personal page in Oracle9i JDeveloper ,which is to fetch particular details from my view and show it .. but whenever I run my form I am continuously getting this type of error..pls,help me out ,as my project delivery is nearing..for this I am not been able to head on to registering the form..I have checked from Pl/Sql developer that my query is just running fine as I wanted it to be..I have also changed the FNDNAM in the .dbc file to my view name but it is giving me the same error..please,look at my error and suggest all other ways in how I can solve my problem ,as early as possible..
Error Page
Exception Details.
oracle.apps.fnd.framework.OAException: oracle.adf.mds.exception.MDSRuntimeException
     at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:888)
     at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(OAPageErrorHandler.java:1064)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1794)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:463)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:384)
     at OA.jspService(OA.jsp:40)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:727)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:306)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:767)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:259)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:106)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
     at java.lang.Thread.run(Thread.java:534)
## Detail 0 ##
oracle.adf.mds.exception.MDSRuntimeException
     at oracle.adf.mds.internal.MUnResolvedState.resolveState(MUnResolvedState.java:193)
     at oracle.adf.mds.internal.ElementData.resolveState(ElementData.java:509)
     at oracle.adf.mds.internal.ElementData.getUntransAttrVal(ElementData.java:922)
     at oracle.adf.mds.internal.ElementData.getAttrVal(ElementData.java:835)
     at oracle.adf.mds.internal.ElementData.getAttributeValue(ElementData.java:260)
     at oracle.adf.mds.internal.Cache.getAttribute(Cache.java:237)
     at oracle.adf.mds.internal.MetadataManagerBase.getAttributeValueInternal(MetadataManagerBase.java:1069)
     at oracle.adf.mds.internal.MElementImpl.getAttrValueOrExpression(MElementImpl.java:620)
     at oracle.adf.mds.internal.MElementImpl.getAttributeValue(MElementImpl.java:230)
     at oracle.adf.mds.MElement.getLocalRef(MElement.java:291)
     at oracle.apps.fnd.framework.webui.JRADWebBeanMetaData.getUINodeName(JRADWebBeanMetaData.java:1812)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.addAkChildren(OAWebBeanContainerHelper.java:223)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:197)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:123)
     at oracle.apps.fnd.framework.webui.OARowLayoutHelper.setMetaDataProperties(OARowLayoutHelper.java:74)
     at oracle.apps.fnd.framework.webui.OARowLayoutHelper.createWebBean(OARowLayoutHelper.java:53)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanUsingHelper(OAWebBeanFactoryImpl.java:1046)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanFromCustomTables(OAWebBeanFactoryImpl.java:782)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBean(OAWebBeanFactoryImpl.java:469)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBean(OAWebBeanFactoryImpl.java:460)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.addAkChildren(OAWebBeanContainerHelper.java:229)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:197)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:123)
     at oracle.apps.fnd.framework.webui.OAContentContainerHelper.setMetaDataProperties(OAContentContainerHelper.java:74)
     at oracle.apps.fnd.framework.webui.OAContentContainerHelper.createWebBean(OAContentContainerHelper.java:55)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanUsingHelper(OAWebBeanFactoryImpl.java:1046)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanFromCustomTables(OAWebBeanFactoryImpl.java:782)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBean(OAWebBeanFactoryImpl.java:469)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBean(OAWebBeanFactoryImpl.java:460)
     at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.addAkChildren(OAPageLayoutHelper.java:657)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:197)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:123)
     at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.setMetaDataProperties(OAPageLayoutHelper.java:243)
     at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.createWebBean(OAPageLayoutHelper.java:194)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanUsingHelper(OAWebBeanFactoryImpl.java:1046)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanFromCustomTables(OAWebBeanFactoryImpl.java:993)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBean(OAWebBeanFactoryImpl.java:902)
     at oracle.apps.fnd.framework.webui.OAPageBean.createRootWebBean(OAPageBean.java:3966)
     at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:1962)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1562)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:463)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:384)
     at OA.jspService(OA.jsp:40)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:727)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:306)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:767)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:259)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:106)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
     at java.lang.Thread.run(Thread.java:534)
oracle.adf.mds.exception.MDSRuntimeException
     at oracle.adf.mds.internal.MUnResolvedState.resolveState(MUnResolvedState.java:193)
     at oracle.adf.mds.internal.ElementData.resolveState(ElementData.java:509)
     at oracle.adf.mds.internal.ElementData.getUntransAttrVal(ElementData.java:922)
     at oracle.adf.mds.internal.ElementData.getAttrVal(ElementData.java:835)
     at oracle.adf.mds.internal.ElementData.getAttributeValue(ElementData.java:260)
     at oracle.adf.mds.internal.Cache.getAttribute(Cache.java:237)
     at oracle.adf.mds.internal.MetadataManagerBase.getAttributeValueInternal(MetadataManagerBase.java:1069)
     at oracle.adf.mds.internal.MElementImpl.getAttrValueOrExpression(MElementImpl.java:620)
     at oracle.adf.mds.internal.MElementImpl.getAttributeValue(MElementImpl.java:230)
     at oracle.adf.mds.MElement.getLocalRef(MElement.java:291)
     at oracle.apps.fnd.framework.webui.JRADWebBeanMetaData.getUINodeName(JRADWebBeanMetaData.java:1812)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.addAkChildren(OAWebBeanContainerHelper.java:223)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:197)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:123)
     at oracle.apps.fnd.framework.webui.OARowLayoutHelper.setMetaDataProperties(OARowLayoutHelper.java:74)
     at oracle.apps.fnd.framework.webui.OARowLayoutHelper.createWebBean(OARowLayoutHelper.java:53)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanUsingHelper(OAWebBeanFactoryImpl.java:1046)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanFromCustomTables(OAWebBeanFactoryImpl.java:782)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBean(OAWebBeanFactoryImpl.java:469)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBean(OAWebBeanFactoryImpl.java:460)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.addAkChildren(OAWebBeanContainerHelper.java:229)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:197)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:123)
     at oracle.apps.fnd.framework.webui.OAContentContainerHelper.setMetaDataProperties(OAContentContainerHelper.java:74)
     at oracle.apps.fnd.framework.webui.OAContentContainerHelper.createWebBean(OAContentContainerHelper.java:55)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanUsingHelper(OAWebBeanFactoryImpl.java:1046)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanFromCustomTables(OAWebBeanFactoryImpl.java:782)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBean(OAWebBeanFactoryImpl.java:469)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBean(OAWebBeanFactoryImpl.java:460)
     at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.addAkChildren(OAPageLayoutHelper.java:657)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:197)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.setMetaDataProperties(OAWebBeanContainerHelper.java:123)
     at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.setMetaDataProperties(OAPageLayoutHelper.java:243)
     at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.createWebBean(OAPageLayoutHelper.java:194)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanUsingHelper(OAWebBeanFactoryImpl.java:1046)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBeanFromCustomTables(OAWebBeanFactoryImpl.java:993)
     at oracle.apps.fnd.framework.webui.OAWebBeanFactoryImpl.createWebBean(OAWebBeanFactoryImpl.java:902)
     at oracle.apps.fnd.framework.webui.OAPageBean.createRootWebBean(OAPageBean.java:3966)
     at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:1962)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1562)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:463)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:384)
     at OA.jspService(OA.jsp:40)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:727)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:306)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:767)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:259)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:106)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
     at java.lang.Thread.run(Thread.java:534)

Don't put reposts. Follow the issue at one place Re: Urgent,showing error while running form..pls,help...
--Shiv

IDoc error In case of ERS procedure, please enter terms of payment

Hi,
I tried to use BAPI_PO_CREATE1 to post purchase order. However, I encountered this error.
IDoc error In case of ERS procedure, please enter terms of payment
I passed the payment term in IDOC PORDCH. Segment E1BPMEPOHEADER-PMTTRMS has value filled out. This value is passed into the BAPI correctly but for some reasons, it got cleared out in the BAPI. Any ideas or suggestions would be greatly appreciated.
Thanks

Check
BAPI_PO_CREATE1 - E 06 436 In case of account assignment

IDoc Errors in ECC

Hi Experts,
what kind of IDoc Errors can occur in ECC for the scenario :
ECC sending PO to Ariba(E-commerce hub, using third party adapter) and in receiving back Order confirmation from it.
Thank you,
MK

Hi,
This depends on the design and landscape and also Disaster Recovery or High Availability Plan.
some hints:
1. Connection Problem: Because of timeout , unavailability of the Receiver system.
2. Data Problem may cause you the error in IDoC posting [ probably functional/Business Team should look into this]
3. User ID and Password Maintenance - it may hit sometimes
4. If any pre-requisite process is required to process this IDoC, then problem in the pre-requisite process will lead the problem
these all kind of problems you may face..
Rgds , Moorthy

Urgent IDOC - EXIT_SAPLLMDE_002 not getting triggered.

I am doing an inbound idoc on message type WMMXY goods movement.
The idoc is sucessfully getting posted when tested through we19.
But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
I have activated the exit functional module, the project in CMOD is also activated.
Some one pls help me .. if u have its document pls post it to me.

Hi,
Please refer to this documentation of user-exit; may be of some help for you.
You can use this user exit to influence the processing of IDOCs of the
message type WMMBXY (goods movements) that are sent to SAP from external
systems via the MM-MOB or WM-LSR interfaces. You can also access
customer-specific processing in this case.
Call transaction and other important requirements
The user exit is performed in the function module that processes the
IDOCs of the message type WMMBXY, after the IDOC is withdrawn and
checked but before direct processing in the application has been
initiated. (That is, the data for the goods movement has already been
determined and edited, but the function module for updating this has not
yet been accessed. The standard function module for processing the
message type WMMBXY is called L_IDOC_INPUT_WMMBXY. The IDOC is processed
in an update task, which means that the source code is also executed in
the update.
If an error arises, then messages should not be issued since processing
is being carried out in the background and the result of processing must
always be returned to the ALE interface. For this reason language
elements such as MESSAGE, COMMIT WORK, LEAVE and the like should not be
used. If errors that should be passed on to the ALE interface or that
affect the result of processing are found in the user exit, you should
also use the user exit MWMIDI07(EXIT_SAPLLMDE_001) since it alone can be
used to take your errors into account (see documentation of the user
exit).
Parameters and options
The user exit in the program is the function module EXIT_SAPLLMDE_002.
In order to be able to use it, you must first create Include zxlidu10
and activate the enhancement by means of transaction CMOD. As
parameters, you can use the following data:
o   Goods movement data already determined from the received IDOC:
    -   Transaction code that is given along with the application
        function module (see interface description (import parameter
        X_TCODE).
    -   Indicator: post only if all items o.k. (import parameter X_XALLP
        ). This indicator must be set by default, to enable IDOC error
        processing.
    -   Indicator: Reset all tables (as primary call) (import parameter
        X_XALLR). This indicator is not set by default to enable the
        processing of several IDOCs. Normally you will not change these
        two indicators.
        -   Goods movement items table (table parameter T_IMSEG)
    o   Received IDOC data:
        -   IDOC control record (import parameter I_IDOC_CONTROL)
        -   IDOC data records (table parameter T_IDOC_DATA)
    This user exit can be used to:
    o   Influence the determined data for the goods movements. All data can
        be changed in this case.
    o   Analyze and process data that is transferred using customer-specific
        segments.
    o   Access additional activities.
    Examples
    A number of potential applications are described below.
A number of potential applications are described below.
o   You want to inform a user by mail when the goods movements of
     certain vendors or customers take place.
o   You want to start your own label printout, for example at goods
     receipt.
o   You want to update your own tables, for example statistical data.
o   You want to analyze a missing parts table at goods receipt and
     redirect the goods receipt correspondingly.
Reward points if helpful.
Regards,
Pankaj Sharma

IDoc Error 51 - Make Entry in All Required Fields

hi,
I am using a scenario where an idoc is being posted into an R/3 system from a legacy application. For some reason I keep getting Idoc error 51 (Document not posted).
Once I drill down further, the specific error states "Make entry in all required fields". Have checked to make sure all mandatory fields have been mapped and proper constant values have been specified.
But cannot seem to get rid of the problem. Could anybody help out in determining how else to troubleshoot this and identify the possible cause?
thx,
Manpreet

Manpreet,
What IDoc Type you are trying to post ? One way is debugging the inbound function module using WE19. The second option is talking to a functional consultantor who worked, what fields are needed for that particular IDoc.
I wouldn't care much about whether the IDoc is posted or not because, it is the ABAP ALE/EDI consultant's job to do that. The only way XI Developer is concerned is when it is not posting, ABAPer would tell what's missing.
Hope this info helps.
regards
SKM

File to IDOC - Error Inbound -56

Hi,
I am doing file to Idoc. (CREMAS01).. My scenario in
RWB is successful. But in R/3 it is shwoing IDOC
error :"EDI: Partner profile inbound not available".
I created Partner Profile in R/3(logical name of BS-
sender file). Still is shwoing Error.
Regards,
Mukharji
Message was edited by: Mukharji T

Hi Mukharji,
I hereunder give you the step by step procedure for File to IDOC scenario. Cross check whether you have done all these:-
SLD
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Hope this helps you.
Regards.
Praveen

Incoming IDOC Error "No batch input data from the screen SAPMV45A 4001"

Hello ,
The Incoming IDOC with Message type 'ORDERS' is triggering the error message "No batch input data from the screen SAPMV45A 4001" with message no 00344 . There is an SAP note 785000 to handle this type of error message which has been already implemented. Still we are encountering few IDOC error's at the time of sales order creation. The IDOC reaches status 51 throwing the error which is again reprocessed through BD87 .
We are unable to replicate the similar scenerio in Development & Testing systems as it works fine.
Can any one kindly advise how to eliminate the error "No batch input data from the screen SAPMV45A 4001" message at the time of Incoming IDOC processing.
Thanks in advance.
Best Regards
Sateesh

Dear Sateesh
Check this link where the same topic was discussed
[ VA01/VA02: batch-input error in IDoc processing|http://www.sapfans.com/forums/viewtopic.php?f=21&t=313032]
thanks
G. Lakshmipathi

IDOC error while receiving

Hi Friends,
In my scenario, I have to receive P.O. message from partner in to my R/3 system.
I am using PI 7.1
When partner is sending me message I am getting error , "Only asynchronous processing supported for IDoc adapter outbound processg" in SXMB_MONI
I tried to find solution on sdn, and I got 2 related foroum,
Idoc Error
Re: No receiver could be determined. (File to Idoc)
But from this also I am not sure hw can i solve this error.
Please Suggest.
Thanks & Regards,
Brijesh Soni

Hi
For Error Only asynchronous processing supported for IDoc adapter outbound
IDOC adapter support asynchronous only,
Check Quality of Service in your sender adapter. Should be EO or EOIO, not BE.
This thread had same problem and resolved :
Re: No receiver could be determined. (File to Idoc)
In Your case QOS is BE. Plz check in your CC if and BE is by default..
If you use BE, HTTP expects a Response back and as IDOC does not support BE, you go the earlier error.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
Regards
Abhishek
Edited by: Abhishek Agrahari on Jan 21, 2009 3:14 PM

Thousands of IDOC Errors

Hi there,
I have recently configured workflow using SWU3 - Now suddenly there are about 10 000 new work items in everyones inbox - All related to IDOC errors.
I have made sure that the workflow administrator is set to a specific user, and in WE46, the IDOC administrator is also set.
Most of the wor-items are back-dated to about a year ago, way before the workflow was configured.
Firstly, why are all these appearing now?
Secondly, how can I get rid of them, or at least isolate them into only one persons inbox?
This is on our test system, so there is no need to investigate any idoc errors...

This is happening because you have made some program run in background while configuring SWU3 most probably the deadline program.
You can get rid of them by checking the Workflow Log and then investigating from where agents are getting determined and accordingly changing the agents to a particular user Id.
Reward points if useful

IDOC Error V1 042 - Sales document X is currently being processed by user X

Hello Experts,
I am using the IS-Retail solution of SAP and I am facing a IDOC Error which keeps the IDOC in Status 51. I traced the Error Message and it was V1 042. I am using an Inbound IDOC 'SHP_OBDLV_CREATE_STO01' to create the STOs (Deliveries) using the POs and there is a locking issue of the PO giving error message 'Sales document XXX is currently being processed by user XXX'.
I have created a backgroung job using a program to post the STOs using IDOCs that picks up multiple files from Application Server and processes them one by one. Now when 2 or more files use the same PO then this error occus.
I added a couple of minutes of wait time between the file processing but that did not help.
Please let me know if you have faces same situation and what solution did you apply.
Regards,
PS

Hopefully you have fixed this by now, but for anyone else who might be looking at this problem. We had this problem and we had the 2 programs check to see if the other was already runing. If so the program would submit itself for a number of minutes, different for both programs, and then exit. We also, and just before this, checked to make sure that there were not 2 of the running programs running and if so to exit. This was necessary because re-scheduling could put a program in conflict with itself. I hope that this may help someone. We used the join V_OP and searched for the program name, not the job name.
Kevin

IDOC error in production server

Hi everyone,
I'm getting this error, when users trigger an Idoc:
Error while writing IDoc to file
Message no. EA084
Diagnosis
The IDoc was to be written to file
cocca3301\interface\output_idocs\1120549.txt
That was not possible because no authorization for writing to this file.
Procedure
Please inform your system administration.
Anyone has seen this before? in development and quality servers didn't happen this...
Thanks in advance. Helpful answers will be rewarded.

Not at all, I was talking with basis administrators about this problem for a long time. I'm pretty sure that it's all about folder permission. I think it's a matter of system, not SAP. But they said that's not the problem... I'm not 100% confident with that answer.
But, in order to keep idocs running, i found program RBDAGAIN, that reprocess the failed idocs. I put it into a job every 30 minutes. That solves my problem "temporary", until i solve the real problem.
I advice you to talk with your system administrator and/or basis, and check the group permission for the folder you are trying to put your files. If it works, please let me know.

Missing IDoc and recurring IDoc errors

Hi,
I would like to ask for a help or any ideas on below case.
We encountered almost everyday a number of generated IDoc errors and the number increases everyday. All of these IDocs has Status "51" (application document not posted) and description "EDI: IDoc 63120 does not exist, please check data".
This IDoc errors does not happen before. It only started when the IDoc 63120 was missing and we can't find it already. We don't know why this is missing and we really need to get rid of these recurring IDoc errors whcih increases almost everyday.
Your response will be helpful in solving my problem.
Thanks in advance!

Hi Juan Francisco Zurita Duque
KNREF : Customer description of partner (plant, storage location)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 040, Offset : 0906. external length : 000030
Use
Sold-to party number sent in by the customer in delivery schedules.
Use
The system uses this number to automatically determine the ship-to party.
Every thing good for ORDRE05 IN ECC6.0
Check your config settign related to Message type and idoc type.....once again.....
RR

Urgent: IDOC Error

Similar Messages

Maybe you are looking for