Recurring Documents Error

Dear Friends:
Uisng T.code F.14, Creating posting Documents from Recurring Documents, I entered data for Co.Code,Doc.No,F.Year,
and settlement period as 01.01.2007 to 31.01.2007.
User name:XXXX.
I am getting the error as mentioned below.
Session 2000_RENT was not created
Message no. FB202
Diagnosis
You have started the report SAPF120.
System response
No recurring document could be selected which would have corresponded to the selection criteria you specified.
The session 2000_RENT was therefore not created.
Procedure
Check your entry or change your existing selection criteria.
How to overcoem the problem.Please advise.
Regards
MSReddy

Hi,
U r getting error when ur executing jobs.
here u r running recurring documents through f.14
first go and check FB03(recurring document diosplay)for what is u r recurring document executing date.
And also go and check f.15 for next recurring document entry data. from that u can run f.14. now u r jobs will generate.
Here recurring document means reaccuring documents this is for regular payments Ex: rent or insurance payments .So at the time of recurring document creation they will mention the first run date and last run date .
So if this is first run means u have to mention first run date. otherwise go and check the f.15 there we can get next run date.
So u mention that date and run the transaction f.14.

Similar Messages

  • Error while entering sample and recurring documents

    Hi
        Hi Iam trying to enter sample and recurring documents.I have given number ranges of X1 and X2 under company code,but  still giving that no number range assigned under company code.Plz help me on this issue.
    Thank you.

    Hi Shilpa,
    Go to T-code: FBN1
    and enter your company code : XXXX
    Check for current year number range  has been maintained
    Best Regards
    Ashish Jain

  • 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

  • Recurring document on transaction code F.14

    Hi All,
    I got problem with this user complaining on the recurring document when she try to execute on the above transaction code. At first she create few documents with success then when she try to do the next step, which is to create posting documents from recurring documents, the error occurred. with the message:
    Session FEB09 was not created.
    Message No. FB202
    Diagnosis
    You have started the report SAPF120
    System Response
    No recurring document could be selected which would have corresponded to the selection criteria you specified. The session FEB09 was therefore not created.
    Plz help and assist me to solve this issue. appreciate ur help. Thanx in advance.

    Hi,
    Use transaction O7E6 and create your own variant and then set up using transaction FB00.
    Award points if helpful.
    Sadie Gajanand

  • Unable to create AAM,or Recurring Document/Sample document

    Hi,
    I am not able to create AAM,or Recurring Document/Sample document, it comes up with a ABAP runtime error, dont know what to do,
    Can some one Advise?
    Regards,
    Raj

    Hi,
    It depends on what kind of message in the ABAP runtime error. But I would suggest you to look at the variant whether they are available or not, for example the recurring document, check in O7E3.
    regards,

  • Recurring Document Analysis report

    Hi!
    we have created some recurring documents using transaction code FBD1. After executing F.14, how can we know whether all recurring documents are created are posted? while executing batch input session, there may be some errors in recurring documents due to which posting cannot happen.
    my client is asking the report where recurring document number and corresponding accounting document posted in that spcific period? is there any report?
    regs,
    ramesh

    Hi Ramesh.
    Please follow the below steps to extract the report with accounting document numbers with their corresopnding recurring document numbers.
    Use T code: FB03
    1. Give the parameters (ex: CoCd, Fiscal year, doc type, posting date/ entry date ec.,), then select the execution button (F8).
    2. System will popup the list of accounting posted documents, go to change layout tab (Ctrl+F8) and find the recurring doc from hidden colums then press enter button.
    3. Now you will see the total list of accounting posted documents with their corresponding recurring setup documents.
    Regards,
    Srinivas

  • Cannot open document (Error: INF)

    We have migrated reports from version Business Objects 6.5.1 to Business Objects XI 3.1 SP2. We have been receiving sporadic 'Cannot open document (Error: INF)' now and again whenever you open Desktop Intelligence reports using Infoview. Have any other users come across this issue using BOXI 3.1 SP2. I do not believe that this issue occurred on SP1.
    This error is very frustrating.
    I have browsed various forums and implemented changes which have had no effect whatsoever including the SAP Marketplace.
    We are also receiving SetPrompts Failed errors. When a report is opened in Infoview and you refresh a report, a blank dialog appears with a red cross. if you refresh the report again then the SetPrompts Failed error appears. I have evene made changes according to article 1364437 based on this error and this has not resolved the issue.
    Regards
    Dipendra

    We're on BOXI3.1 SP2 aswell and we have had the same sporadic issue - Cannot open document for Deski reports. This is causing some serious concern amongst our users over system stability.
    You can recreate the situation by shutting down the InputFileRepository server and you get the same message. I've noticed that when this happens there is a mesage in the fcproc log file 'm_repFileMgr.Download failed'
    My theory is that there may be some congestion in linking between the desktopintelligence server and the inputfilerepository. In addition, we had some logging on the fileserver and at the time of the error there was no mention of the report that failed or any error. We contacted SAP about this but did not get a satisfactory response. There were some heavily utilised DESKi reports which we managed to convert to Webi to take the load off and we also dropped the timeout to 20 minutes (not brilliant but it did mean that if we got the message the users wouldn't have to wait too long before it was resolved in case they couldn't get hold of IT).
    I also upped the parameter for Maximum Retries for File Access in case it was having problems getting the file.
    The result of this was that the error appeared to go away... until yesterday!!!
    Any further insights welcome.

  • "...not a valid Photoshop document" error when opening Mac cc file on PC

    I get a "Could not complete your request because it is not a valid Photoshop document." error message whenever I try to open up a PSD file created on a Mac using Photoshop CC on my PC using CC. Other people have been able to open the file from the same location, so the files aren't corrupted. Anyone know how to fix this?

    I know this thread is a bit old, but I wanted to share my experience and solution in case anyone else runs into this.
    The other day, I spent many hours editing some photos for a client. I saved them all and closed Photoshop. When I tried to open the .PSDs, they all came up with this "Not a valid Photoshop document" error. I was freaking out. I could see the thunmbnails and previews with the MacOS Finder and could see the images just fine in Lightroom, but couldn't open them in Photoshop CC.
    Finally, I remembered that these were NOT supposed to be .psd files! They were supposed to be TIFFs. What happened was, when I edited them from within Lightroom into Photoshop, they opened as TIFFs. However, when I did "save as", I wanted to name them similarly to some other files I had. I clicked on one of the existing files to copy the file name in the Save As dialog to make it easier to name the new file I was saving, but I didn't realize it was changing the file extention from ".tif" to ".psd" as well. The older MacOS (version 9 and earlier) didn't rely on file extensions fo identifying file types, so it didn't hit me right away that this would be the problem. When I changed the incorrect .psd file extension to .tiff, the files opened in Photoshop just fine.
    SO... if you run into this "Not a valid Photoshop document" error, try figuring out if it's actually another file type (.jpg, .tif, .png, etc) by either getting the file info from another program or just experimenting with different file extensions. Chances are good that your file isn't actually corrupt, but just named improperly!

  • Background scheduling of recurring document postings

    Hi Freinds,
    I have 3 recurring entries every month, Lets say 1 should rum on 1st of everymonth, 2nd one should run on 4th of every month and 3rd entry on 10th. I hve created 3 recurring docs in FBD1.
    Instead of go ro F.14 and create batch job every month. I would like to scehdule a background job for the whole fiscal year. So that every month all 3 docs automatically gets posted.
    Anyone give me step by step process of scheduling background job.
    thanks in advance..
      Venkat

    hi
    kindly note the steps below:
    1)     Create a recurring document giving the start date and end date, directing the system to post the entries at the end of a period (monthly, bi-monthly, quarterly, semi annually, annually, etc).
    2)     Determinants would be the transaction should recur regularly and have the same values across the horizon of recurrence. Again the posting period in which the entry can be posted should be open.
    3)     Post the entries as on a particular posting date by running a batch process for all the recurring document templates created.
    Create Recurring entries document template u2013 FBD1
    Execute Recurring entry program u2013 F.14
    Recurring entries list u2013 F.15
    regards
    eashwar

  • Load the document in Firefox (click gmail "Documents") error: The page isn't redirecting properly. Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

    load document in Firefox (clicking gmail "Documents", error: "The page isn't redirecting properly. Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

    Clear the cache and the cookies from sites that cause problems.
    "Clear the Cache":
    * Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
    "Remove Cookies" from sites causing problems:
    * Tools > Options > Privacy > Cookies: "Show Cookies"
    * http://kb.mozillazine.org/The_page_is_not_redirecting_properly

  • Cannot open document (Error: INF) / Session is closed (Error: INF )

    SAP BO XI3.1
    last time I face this one but suddenly disappear during testing, now we once again face this issue. As all users are member of group 'EveryOne' if we add any user membership to administrator group / master group this error resolved for this user.but that is not proper solutions, so far i m unable to find the rights which is lacking to all user for these report which are available in each user infoview and causing these errors while viewing.
    Open Document error message:
    While viewing Web Intelligence reports
    [Session is closed (Error: INF )|http://yfrog.com/0cwebirightsp|Session is closed (Error: INF )]
    While viewing Desktop Intelligence reports
    [Cannot open document (Error: INF )|http://yfrog.com/mjdeskirightsp|Cannot open document (Error: INF )]

    You might need to give read rights to the folder and category this report belongs to???
    If the problem is fixed when the user who is viweing is an administrator, this means there is insufficient privileges for the other users.

  • Recurring document - FBD1 with incorrect due-date calculation for AP

    Hi Gurus,
    in our ECC 6.0 system we are creating with F.14 FI-documents (SAPF120) based on recurring documents (created with FBD1) for various purposes (e.g. Recurring entries for IC-business).
    Therefore it's important that the system provides in the final processing of the recurring documents the correct net-due-date in the AP-document based on the document date and the payment term included in the AP-masterdata (LFB1-ZTERM).
    Problem:
    The processed FI-document contains the correct payment term but the calculated net-due-date with regards to the document date (BKPF-BLDAT) isn't correct. A Dummy-Update of the FI-document with FB02 on field BSEG-ZTERM provides finally the correct net due date but this a not recommended solution.
    Any ideas how to solve that issue???
    Thanks for replies.
    BR, Bernd

    Hi Vishnu,
    the defined payment term is
    fix day: 15
    additional month: 1.
    Default for baseline date is posting date
    Therefore the expectation is that net due date is calculated for posting date
    e.g. : 01.02.2012 to 15.03.2012.
    The line item after processing in FI-document shows :
    Posting Date : 01.02.2012
    Bline Date:   01.02.2012
    Days/percent: 35
    Net due date: 07.03.2012 (dd.mm.yyyy)
    That's wrong according to my understanding of the payment term definition.
    BR, Bernd

  • Large XML Document Error

    We are using Oracle's XSQL servlet engine 9.0.2.0.0A to query an Oracle Database using xsql:include-owa. This xsql document uses a custom serializer to write the resulting XML to a file on the webserver. We have run into a problem with writing XML documents larger than approximatly 7MB. The file is written but just contains a Malformed XML Document error. We have tried tracking down the problem and it seems to be occuring before the custom serializer is given control of the document. Attached below is the xsql document and the Java source of our serializer if it would be of any help.
    -Eric Dalquist
    <?xml version="1.0"?>
    <?xml-stylesheet type="text/xsl" href="simple_transform_xml.xsl" serializer="XMLWriter"?>
    <BASE_TAG connection="XXXXXXXX" xmlns:xsql="urn:oracle-xsql">
        <xsql:set-page-param name="save-file" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/applInfo.xml"/>
        <xsql:include-owa >
            STUDEV.STUADMSDSET.P_GET_RECRUIT_INFO('A','C');
        </xsql:include-owa>
    </BASE_TAG>-----------------------------------------
    * Author:        Eric Dalquist
    * E-Mail:        [email protected]
    * Date Created:  10-03-2001
    * Last Modified: 10-03-2001
    * Modified By:   Eric Dalquist
    * Description:   This class writes out the contents of the final document produced by the xsql servlet.
    package com.mtu.XSQLSerializers;
    import java.io.FileOutputStream;
    import oracle.xml.xsql.*;
    import oracle.xml.parser.v2.XMLDocument;
    import org.w3c.dom.Document;
    * <P>
    *    XMLWriter is an implementation of the abstract XSQLDocumentSerializer class. It is passed a refrence to a DOM Document
    *    and the servlet environment. The XMLWriter takes the document and writes it out to the servlet's output stream. There
    *    is also the option that the saveFile xsql page parameter can be set to a fully qualified path and file name to write the
    *    document to.
    * </P>
    * <P>
    *    Here is an example of setting the saveFile page paramter. This line would be the first tag inside the root xsql servlet tag.
    * </P>
    * <PRE>
    *    &#060;xsql:set-page-param name="save-file" value="/u01/oracle/ias10210/xdk/java/xsql/Repository/Course_List/XMLDocument.xml"/&#062;
    * </PRE>
    * @author  Eric B. Dalquist
    * @version 1.0 10/03/2001
    public class XMLWriter implements XSQLDocumentSerializer
        /** the header we send if we are returning XML */
        private static final String MIME_XML = "text/xml";
        /** the name of the page parameter we look for to get the path and name to save the XML document to */
        private static final String ATTR_FILE = "save-file";
         * The serialize is called by the servlet engine and is passed the DOM Docuement result
         * from the XSLT transformation if there was one and a refrence to the XSQL servlet environment
         * @param doc The document representation of the XML output of the xsql servlet.
         * @param env A refrence to the servlet's environment.
         * @throws Throwable Any unhandled error is handled by the servlet by default.
        public void serialize(Document doc, XSQLPageRequest env) throws Throwable
            System.out.print("start ... ");
            FileOutputStream fos = null;
            String reqType = env.getRequestType();
            String saveFile = env.getParameter(ATTR_FILE);
            if (!reqType.equals("Command Line"))
                env.setContentType(MIME_XML);
                ((XMLDocument)doc).print(env.getOutputStream());
                env.getOutputStream().close();
            if (saveFile != null && !saveFile.equals("") && saveFile.indexOf("..") == -1 && saveFile.indexOf("~") == -1)
                fos = new FileOutputStream(saveFile);
                ((XMLDocument)doc).print(fos);
                fos.close();
            System.gc();
            System.out.println("end");
    }

    Technically DBMS_XMLSAVE and it's alter ego DBMS_XMLQUERY are not considered part of XML DB. DBMS_XMLSAVE and DBMS_XMLQUERY are legacy Java implementations.
    In 9.2.x these routines were replaced by DBMS_XMLSTORE and DBMS_XMLGEN which are written in 'C' and should be much faster in most cases and address a number of limitations inherant in the older implementations. DBMS_XMLSTORE and DBMS_XMLGEN are part of XML DB and the minimum supported release for XML DB is 9.2.0.3.0.
    DBMS_XMLSAVE issues are addressed in the TECH/XML forum
    http://forums.oracle.com/forums/category.jspa?categoryID=51

  • Recurring Documents run schdule configuration

    Dear all,
    I have a question regarding the recurring document run schdule configuration. my example is below
    I received an insurance policy,
    Period :23.02.2011 - 23.05.2011 (for 3 months)
    amount: 15.000 USD
    First I posted this policy to vendor account
    31 vendor ABC                   15.000 USD
    40 Prepaid Exp.acc.            15.000 USD
    secondly I create a recurring document with below specification.
    *Recuring entry run*
    company code:1000
    first run on :23.02.2011
    Last run on:23.05.2011
    interval months:1
    run date:23
    transfer amounts in local currency
    copy texts
    *Document header information*
    document type:AB
    currency/rate:USD
    translation date:23.02.2011
    Post. key:40 (insurance exp.account) enter amount (for monthly 5.000 USD)
    Post. key:50 (Prepaid exp. account) enter amount (for monthly 5.000 USD)
    and than ı execute document posting by F.14 and the document posted.
    but I want to create a recurring document and posted this document according to the below calculation,
    for february 2011= 1000,00 USD (15.000 USD / 90 days X 6 day)
    for march 2011   = 5.166,67 USD (31 day)
    for april 2011     = 5.000,00 USD (30 day)
    for may 2011    = 3.833,33 USD (23 day)
    how can I configure this recurring document.
    Thank you so much.......

    Hi,
    For this scenario standard is not possible, why because if the recurring documents are maintained only for which is the amounts and date is fixed for this scenario is possibe for recurring document, then discuss with the abaper try to maintain userexits for this.
    Regards,
    Kanike

  • Preparing to Upgrade to LiveCycle ES from 7.x document error: page 85

    Preparing to Upgrade to LiveCycle® ES from 7.x document error: page 85, when configuring the JMS with Microsoft SQL Server 2005 for JBoss 4.0.3 SP1. Step 5: Modifiy <local-tx datasource> element .....   <connection-url> jdbc:microsoft.sqlserver ..... <c/onnection-url>, in mssql-ds.xml file:
    Should be: <connection-url>jdbc:sqlserver://.... </connection-url>
    Notice the word "microsoft" needs to be removed as this is SQL 2005, not SQL 2000.
    Also, in the same JMS configue file, com.microsoft.jdbc.sqlserver.SQLServerDriver should be changed to com.microsoft.jdbc.sqlserver.SQLServerDriver as the driver-class.
    We are using
    SQL 2005 SP1
    JBoss 4.0.3 SP1
    Windows 2003 SP1
    Adobe ES 8.2
    If not corrected, you'll see error like this in log file:
    Caused by: org.jboss.resource.JBossResourceException: Failed to register driver for: com.microsoft.jdbc.sqlserver.SQLServerDriver; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: com.microsoft.jdbc.sqlserver.SQLServerDriver)
    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getDriver(L ocalManagedConnectionFactory.java:287)

    Sorry - wrong spot. I will re-post this in ES Installation Discussion forum.

Maybe you are looking for