Error while posting the IDoc for Customer Invoice.

hi,
I m posting Customer Invoice through LSMW using IDocs.
Basic type is FIDCCP02 and message is FIDCC2.
While posting the Idoc I m getting error as:
'Document or line item does not exist for invoice reference'.
I m not getting the error why it is asking for invoice reference because
in FB01 it is not asking for any reference or anything.
Even in f-22 also it is not asking for the same.
In Idoc all the item level values are coming prorperly.
If anybody worked on such issues then please reply.
-Thanx.
-Umesh

Hi,
Where you able to resolve your issue, I would appreciate if you can share the solution.
Thanks

Similar Messages

  • Error while posting the IDOC. Status message '56'

    Hi,
    I have a requirement where I will post an IDOC which inturn will split the original IDOC into child IDOCs based on the store value.
    I am trying to post the IDOC in WE19. So, the Original IDOC is posted successfully with status '53'. Whereas, the child IDOCS finished with error. The status of the message is '56' and the error says 'EDI: Partner profile not available'. Could someone tell me what could be the reason for this..?
    Actually, the IDOC was created by the Functional Consultant. So, should the partner profile creation also done by them or do we need to do anything to solve this problem.? Could someone answer me this question. Thanks in advance.
    Best Regards,
    Paddu.

    It looks like the control data for the child segment is not getting populated. you have to find the code which populated the control data and see if it is doing what it should.

  • Error while posting the  Idoc 'Update error, transaction VA01'

    Hi Gurus,
    When an inbound Idoc for sales order is trying  to post we  are  getting the  error 'Update error, transaction VA01'.
    Aslo following  are the  details of  the error:
    Update error, transaction VA01
    Message no. 00377
    Diagnosis
    An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
    during a synchronous update.
    The error was caused by the transaction VA01.
    Update information
    Return code:        009
    Text       :        Error during insert table FPLTC (RC= 1, Key= )
    Procedure
    Pleas analyse your Batch-Input data.
    You can also examine your posting data using the transaction SM13.
    Can somebody let  me  know  what would  be  the cause.
    Also the  we are  trying  to post the  Idoc with a Id which is  having  maximum Authorization.

    Hi,
    Where you able to resolve your issue, I would appreciate if you can share the solution.
    Thanks

  • Error while posting the ID for Validation

    Hello Experts,
                 We are running a report from a ECC 6.0 server which connects to the PI server via RFC connection defined through RFC Adapter on the PI server. This Pi server then connects to the web server for validation and then returns the status as true or false. But while executing the report on the ECC 6.0 server we are getting the error as " Sender Agreement not found:lookup of binding via CPA-cache failed for Adapter type RFC, AdapterNS http://sap.com/xi/XI/Sy". The connection test for the RFC from the ECC 6.0 server is fine and okay.
    When we get this error we keep trying to validate the ID twicw and third time the transaction happens sucessfully. How do we overcome this error? While creating the communication channel for this scenario on the PI server the * has been removed from the Party field as suggested in one of the blogs in this forum. But in our case the problem still persists even after removing the * in the party field in the Communication channel of the scenario. Kindly suggest the remedy for this problem.
    Thanks
    Best Regards
    PI team

    Hi,
        You could have an issue because the RFC definition has changed and the cache is out-of-synch
    1) Reimport and activate the RFC.
    2) Restart the RFC Adapter service in the Visual Administrator. This will flush the metadata cache in case the RFC has changed.
    If this doesn't work, verify that your Sender Agreement is setup correctly
    1) A common mistake is to create a Message Interface in the IR (Design) for RFC and IDoc senders and point the sender agreement to this Message Interface which won't work. The Sender Agreement should be setup as follows:
    Service: SAP Business System
    Interface: RFC name
    Namespace: urn:sap-com:document:sap:rfc:functions
    please go through below threads,
    senderAgreement not found - PLEASE read
    Error: Sender agreement not found, lookup of binding via CPA-CACHE failed.
    regards,
    ganesh.

  • Error while posting Idoc for customer invoice.

    hi,
    I m posting Customer Invoice through LSMW using IDocs.
    Basic type is FIDCCP02 and message is FIDCC2.
    While posting the Idoc I m getting error as:
    'Document or line item does not exist for invoice reference'.
    I m not getting the error why it is asking for invoice reference because
    in FB01 it is not asking for any reference or anything.
    In Idoc all the item level values are coming prorperly.
    If anybody worked on such issues then please reply.
    -Thanx.
    -Umesh

    Hi Umesh,
    Try posting customer invoice through TCode - F-22. There it may be asking for reference number. Generally we post customer invoice by F-22 not from FB01.
    If you are getting error you can add reference field in your LSMW it may be mandatory in F-22.
    Ashven

  • Error while posting the CREMAS03 Idoc

    Hi
    I a getting the Error while posting CREMAS03 idoc from File
    The ERROR: Status 65 ,Error in ALE Servics: Cross Company code does not exits..
    but when i cheked with the functional guys , the comany code exits..
    Any one have any idea
    SV

    Hey,
        seems you have given wrong enteries for logical system in sale or in WE20(patrner profile)
    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)
         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 6)
         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.
    Step 7)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    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.

  • Error while compiling the composite through custom ant script

    Hi,
    I am getting the following error while compiling the composite through custom built ant scripts which are intern call the ant-sca-package.xml. And the composite is created by upgrading the 10g bpels. But the same composite is successfully compiling from Jdeveloper (11.1.1.4).
    oad of wsdl "oramds:/soa/shared/workflow/NotificationService.wsdl" failed
    oracle.fabric.common.FabricException: Error in getting XML input stream: oramds:/soa/shared/workflow/NotificationService.wsdl: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/soa/shared/workflow/NotificationService.wsdl does not exist.
         at oracle.fabric.common.metadata.MetadataManagerImpl.getInputStreamFromAbsoluteURL(MetadataManagerImpl.java:280)
         at oracle.integration.platform.common.MDSMetadataManagerImpl.getInputStreamFromAbsoluteURL(MDSMetadataManagerImpl.java:555)
         at oracle.fabric.common.metadata.MetadataManagerImpl.getDocumentAsInputStream(MetadataManagerImpl.java:159)
         at oracle.integration.platform.common.MDSMetadataManagerImpl.getDocumentAsInputStream(MDSMetadataManagerImpl.java:417)
         at oracle.fabric.common.wsdl.WSDLManager.loadWSDL(WSDLManager.java:241)
         at oracle.fabric.common.wsdl.WSDLManager.loadWSDL(WSDLManager.java:304)
         at oracle.soa.scac.ValidateComposite.loadWSDLs(ValidateComposite.java:934)
         at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:491)
         at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
         at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)
    Caused by: java.io.IOException: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/soa/shared/workflow/NotificationService.wsdl does not exist.
         at oracle.mds.internal.net.AbstractOraMDSURLConnection.getPDocStream(AbstractOraMDSURLConnection.java:388)
         at oracle.mds.internal.net.AbstractOraMDSURLConnection.getInputStream(AbstractOraMDSURLConnection.java:176)
         at oracle.mds.internal.net.OraMDSURLConnection.getInputStream(OraMDSURLConnection.java:67)
         at java.net.URL.openStream(URL.java:1010)
         at oracle.fabric.common.metadata.MetadataManagerImpl.getInputStreamFromAbsoluteURL(MetadataManagerImpl.java:276)
         ... 9 more
    Caused by: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/soa/shared/workflow/NotificationService.wsdl does not exist.
         at oracle.mds.internal.net.AbstractOraMDSURLConnection.getPDocStream(AbstractOraMDSURLConnection.java:339)
    And in the following blog, its recommended to check for the adf-config.xml. But when upgrading the bpels from 10g to 11.1.1.4, I don't see any such file created by Jdeveloper.
    http://orasoa.blogspot.com/2010/08/ant-and-mds-composite-compile-error.html
    Not sure if I am missing some properties to add in by custom script while compiling.
    Thanks
    Sree
    Edited by: Sree on Jul 4, 2011 7:25 AM

    Hi Hussain,
    Thanks for the reply.
    Were you able to compile the form at the client side successfully?
    1) Were you able to compile the form at the client side successfully?:
    Ans: Yes, I was able to compile the form successfully at client side.
    2) Are you logged in as applmgr user? Have you sourced the application env file before compiling the form?
    Ans: No, I have not logged by applmgr user, i am using my own login. Yes I have sourced the application env file before compiling the form
    3) What does "echo $FORMS_PATH" return?
    Ans: echo $FORMS_PATH on server gives this path
    /u01/app/EBS00/apps/apps_st/appl/au/12.0.0/resource:/u01/app/EBS00/apps/apps_st/appl/au/12.0.0/resource/stub
    Can you please advise?
    Thanks,

  • Error while executing the Job for Objects :null  Batch Risk Analysis

    Hi All,
    We've recently upgraded Virsa to version  5.3_14 .  I'm encountering a problem when executing the Batch Risk Analysis job for users, roles and profiles.  The job does not complete for some objects and it seems to be sporadic and shows this error: -
    Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null                                                                               
    I've attached the log for your review.
    Thanks in advance for your help.                                                                               
    Linda Lewis                                                                               
    Feb 9, 2011 1:47:53 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
    FINEST: ObjAuthMatcher constructed: 4ms, #singles=2141, #ranges=0, #super=0
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
    WARNING:  Job ID:395 : Failed to run Risk Analysis
    java.lang.StringIndexOutOfBoundsException at java.lang.String.substring(String.java:1019)
    at com.virsa.cc.xsys.util.RuleLoader.getPermRule(RuleLoader.java:573)
    at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1609)
    at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:321)
    at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1166)
    at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1464)
    at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:560)
    at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:363)
    at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
    at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
    at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
    at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
    at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(AccessController.java:207)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
    FINEST: Lock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
    FINEST: Unlock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
    WARNING: Error: while executing BatchRiskAnalysis for JobId=395 and object(s):ABROWN: Skipping error to continue with next object: null Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
    FINEST: --- @@@@@@@@@@@ Updating the Job History -
    2@@Msg is Error while executing the Job for Object(s) :ABROWN:null
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
    INFO: -
    Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
    FINEST: Lock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
    FINEST: Unlock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
    INFO: --- BKG User Permission Analysis (System: P20:020) completed ---  elapsed time: 4522 ms
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
    Edited by: Linda Lewis on Feb 9, 2011 9:08 PM

    Hi,
    Was a solution found for this error?
    Thanks,
    Glen

  • Error while posting Inbound Idocs-"EDI: Partner profile not available"

    Hi,
    I am getting the error "EDI: Partner profile not available" Status -56 while creating inboud Idocs.
    I have done the following steps so far
    1.Created IDOC basic Type and Message Type. (Custom)
    2. Created process code to process the IDOC.
    3. Use the FM IDOC_INBOUND_WRITE_TO_DB to create the inbound IDOC.
    4. Use the FM IDOC_START_INBOUND to process the IDOC.
        Is ther anything else that i have to do inorder to post the idoc sucessfully.
    Thanks in advance
    -Nishant
    Edited by: nishant patel on Nov 13, 2009 10:35 AM
    Edited by: nishant patel on Nov 13, 2009 10:41 AM

    Hi,
    Check in WE20 if the partner profile is configured for the idoc type and the message type. That might be the cause of the error.
    Also make sure the same partner profile details are sent to the control record. Partner profile details are stored in the table EDP13.
    Hope this helps
    Regards
    Shiva

  • Error while posting the parked document in ECC 6.0

    Hello ABAPers,
    After upgrade from R/3 4.6c to ECC 6.0, when we try to post the parked documents ,It calls FM :POSTING_INTERFACE_DOCUMENT".
    Inside it a call transaction is done using FBVB which throws error while posting for more than 4 withholding tax types.
    Error : Field WITH_DIALG-WT_BASE(5) does not exist in the screen SAPLFWTD 0100.
    On running BDC in foreground mode ,Error is happening when the withholding dialog opens and screen seems to be small to input all the tax codes i.e it shows only 4-5 rows and hence only 4 tax types passes to the screen and remaining is left out and error is thrown. This results in document not getting posted.
    But in 4.6 c a bigger screen pops up and no error is thrwon.
    We are not able to check FBVB directly, since it does'nt allow Direct call to this transaction.
    We have checked lots of thread and notes ,But nothing seems to be relevant or helpful in our case.
    Could you please help us in resolving this issue/ let us know if any configuration/ screen variant change is required?
    Thanks!
    Regards,
    M M Jaffer.

    Hello Nabheet ,
    It is a standard code. We are calling the FM  'PRELIMINIARY_POSTING_POST_ALL'  for posting the parked document. The FM calls internally another FM 'POSTING_INTERFACE_DOCUMENT'. This calls the transaction FBVB where we get the above error.
    Thanks.

  • ERROR  WHILE POSTING  THE STOCK  OF MATERIAL

    Dear experts
    while  posting  the stock  of  material  iam  getting  the error  'number ranges for transevent type WA in year 2011 does not exist.
    what  transaction  should  be  used  .
    Thanks & Regards.
    Erfan.

    Dear,
    First of all please go to T-code FBKP, click on Document Type, double click on document Type "WA" and check what is the value in Number Range.
    For Example there it is 01, then got to FBN1, enter company code and give  give 01 and against this maintain number.
    Hope this helps!!!
    Br,Vivek

  • Error while posting the payroll results to accounts

    Dear all,
    Im facing a issue while posting the payroll results to the accounts in T.code PC00_M99_CIPE,
    The error log says...
    Inconsistence in payroll results (tables V0/RT)
    Diagnosis:
    An inconsistency results has been found during the evaluation of the payroll results. No referenced entry has been found in table V0.
    Can anybody suggest me wat i hav to do...
    Thanks & regards
    Gopinath.Balakrishnan

    Hi
    Check whether the user is having the authorisation for the t.code PC_PAYRESULT or PC00_M40-PAYRESULT.
    Because some times HR user will run the payroll and FI user will do the postings. If FI user is doing the postings, in general he will not have the authorisation for HR T.codes, then system will give such kind of errors.
    If not check the paryoll results and control record.
    Thanks & Regards
    Bharathi

  • Error While posting the Budget Update(BPUP)

    We are getting an error message u201CError when saving the Budget Updateu201D while posting the Budget Update (BPUP). I have filed all mandatory requirements in the transaction.
    I couldnu2019t able to find out reason for this error message. Please help me on this.

    Hi,
    Where you able to resolve your issue, I would appreciate if you can share the solution.
    Thanks

  • Error while posting the Goods Receipt

    Hi Friends,
    I am having an issue while posting the Goods Receipt.
    I am getting the error "Balance not zero: 1.000,00- debit: 0,00 credit: 1.000,00". I am using the Purchase Order with Account Assignment category P and K. When ever I used the account assignment category, I am getting this type of error. I have checked the configuration and every thing is OK. System is not able to debit the G/L account which is mentioned in the Purchase Order, hence the problem. However, I think system is able to get the G/L account (to Credit the amount) from Automatic Account determination.
    Would like to know if any one come across similar type of problem and resolved it.
    We have recently upgraded the system from 4.7 to ECC 6.0.
    Apprciate the help.
    Thank you,
    Prakash

    Hi
    Thank you for the reply.
    I have checked what you have mentioned. While creating PO it is determining the G/L account automatically through the assignments in OBYC. Even then I am getting the error while doing the Goods Receipt.
    Any one is having any idea?
    Thank you,
    Prakash
    Edited by: Prakash KM on Dec 17, 2010 6:26 PM

  • Error in posting the Idoc....

    Hi Experts,
         When I post the Idoc from the external system to the SAP,I am getting the
    error as application document not posted and status code as 52.so what I need
    to do to overcome this error,please help me over this issue.
    Regards,
    Kiran.

    Hi,
    you have to check the idoc in debugg mode and pull it out the reason why i has 52 and you know how to debug inbound - go to we19 and here give any existing idoc no and press F8 and enter into screen, in that select 'INBOUND FUNCTION MODULE' select give ur standard F.M name and select the background mode.
    or thre way is  goto BD87 make the correct the error idoc manually.
    --Use Tcode BD87 to check for IDocs that are not been processed and reactivate.
    u can find here if any data wrong or missing.
    <b>Reward if useful</b>
    Regards,
    Vijay

Maybe you are looking for