Issue regarding posting period and due date and document date

Dear Sir,
when i am creating sales order/purchase order and in posting date /delivery date/document date 
how it is allowing me to add the marketing document of date before 3 months. i have checked the box on document setting
block allow posting date.
please help me how to block the before and after posting date
thanks
Aditee

Hi,
I don't have $38.10.number in my query. Where did you get this field?
please follow below steps:
1. Run above query in generator. Sure it gives an error message and ignore this message.
2. save it under query manager
3. Assign this FMS at AP invoice posting date and set auto refresh when customer vendor refer is changed.
Thanks & Regards,
Nagarajan

Similar Messages

  • Linking a Period Indicator to a Posting Period and Document Numbering

    Dear All,
    Could you please tell me that, what will be the consequences if I do not link a Period Indicator to a Posting Period and use the Period Indicator in any document numbering?

    Hi,
    The use of the period indicators depends on the accounting practice of the company.
    The consequence you will face when you are not using period indicators:
    1.Your document numbering series will be continued from year to year,for ex.if your last document numbering series for AP Invoice is 3489 for FY200809,then the starting series for the FY200910 will be 3490.
    2.You should perform period end closure before proceeding to the next financial year,which would not be possible(Atleast one month in the new financial yr) as we may need to use adjustment transaction for accounting/auditing purpose
    3.Unless you perform year end closure the new series can not be continued,if you continue there must be accepted/explained in the accounts auditing too .
    4.But you don't use period indicator,there will not be any necessity to create new document series for every new financial year.
    Also check this document on [Period indicators|https://websmp105.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000513532005E] for better understanding.
    Hope this is helpful!

  • Display the 0 fiscper3 (posting period)and 0fiscyear (fiscal year) in bw re

    Hi I need a quick help, please resolve my issue in step by step. Report is required to display the 0 fiscper3 (posting period)and 0fiscyear (fiscal year) in bw report. I have a  0fiscper Fiscal Yr / Period in my datasource and infosource but not 0fiscper3 (posting period)and 0fiscyear (fiscal year). Can any body help me how to add the abap code to convert the 0fiscper Fiscal Yr / Period to display 0fiscper3 (posting period)and 0fiscyear (fiscal year in report or how to add by abap code 0fiscper3 (posting period)and 0fiscyear (fiscal year)in datasource. User will select the value of 0FISCYEAR
    Fiscal year during the execution of report. please help
    will reward all points.
    thanks
    soniya kapoor

    Hi Soniya,
    Y don't you enhance ur datasource with these fields?
    Anyways the workaround could be add 0FISCPER3 and 0FISCYEAR in ur data target, and write ABAP code for it in transformation.
    Map 0FISCPER with both the fields, and now click rule type of both the fields independently.  Select rule type as routine.
    0FISCPER stores data in format YYYYPPP, so you have to write code accordingly.
    Likie in 0FISCPER3 assign last 3 digits of 0FISCPER to 0FISCPER3 and first 4 to 0FISCYEAR.
    Suppose u have pne temp variable with name fis_yp which stores value of 0FISCYEAR. For getting period from it you have to write:
    period = fis_yp+4(3), ( 3 characters from 4 place)
    and similarly for year,
    year = fis_yp+0(4),  ( 4 charaters from 0 place)
    I hope now u can write code for it easily?
    KJ!!!

  • Posting periods and account segmentation

    the company has several suboffice/division, but they want all under one company in B1. also they receive some of they invoices 2 months lates. Data migration will go back 2 years. So what is best way to set up posting period and account segmentation.

    Hello,
    Take a look at this thread and copied to your notepad :
    Division in SAP Business One
    about how to create suboffice/division.
    The posting period can be created go back more than 1 years from now as long when performing data migration, do not forget to set the current period that match with your data dates. The invoices and other opening balances can be migrated using DTW templates.
    So, I suggest you could create posting period more than 2 years ago in the last time and create 2 segmented accounts consists of sub office and division beside natural account. E.g. :
    12111-01-02 : 12111 is natural account, 01 is suboffice code and 02 is division.
    Rgds,

  • 0 fiscper3 (posting period)and 0fiscyear (fiscal year) in bw report

    Hi I need a quick help, please resolve my issue in step by step. Report is required to display the 0 fiscper3 (posting period)and 0fiscyear (fiscal year) in bw report. I have a 0fiscper Fiscal Yr / Period in my datasource and infosource but not 0fiscper3 (posting period)and 0fiscyear (fiscal year). Can any body help me how to add the abap code to convert the 0fiscper Fiscal Yr / Period to display 0fiscper3 (posting period)and 0fiscyear (fiscal year in report or how to add by abap code 0fiscper3 (posting period)and 0fiscyear (fiscal year)in datasource. User will select the value of 0FISCYEAR
    Fiscal year during the execution of report. please help
    will reward all points.
    thanks
    soniya kapoor

    In de update rules from infosource to datatarget you fill the rules like this:
    For 0FISCYEAR:
      result = comm_structure-fiscper(4).
    For 0FISPER3
      result = comm_structure-fiscper+4(3).
    Note that this can also be done by using formula's. If you can't ABAP you may prefer to use formula's.

  • Starnge issue with posting periods

    Hi All,
    I am facing a strange issue with posting periods....
    When I go to OMSY i can see that periods 10 & 9 are open. the I go to MMPV and close periods. Again when I go back into OMSY I can see that now periods 11 & 10 are open. But after sometime when I try to do invoice posting I get the error that posting only possible in periods 10 & 9. I checked in OMSY and it now shows that periods 10 & 9 are open!!
    I have closed periods using MMPV atleast 5 times now....I really fail to understand why or how the periods are changing in OMSY?
    Regards,
    V S

    Hi,
    Check in MARV table, if it is still open, while close the period in MMPV, check you are getting message as "Period closed log issued"
    Regards,
    Prabu

  • OHS - Protocol (Periodic) Next due dates are not being captured properly

    Protocol (Periodic) Next due dates are not being captured properly in the Planning Cockpit (EHSH_D_PCP) report nor the Protocol report (S_SH8_7200013).  The Planned date is not resetting itself for the medical service sometimes.
    Any idea what might be causing this issue?
    Regards
    Naveen

    HI Naveen
    Have you overridden the std BADI for calculating Next due date?
    Thanks
    Jagdsh

  • Posting Key and Document type

    Hello,
    I have just detected an inconsistency in one of my SAP environment (Development).  I have an invoice posted from the SD module, document type of this invoice is RV.
    If there is a reason to cancell this invoice, the transaction used is VF11. The document type in SD for this cancellation is S1. Thereafter an FI document is generated with document type AB.
    Even though the settings in both Production and Acceptance and Developement are the same.
    I have realised that the initial document when cancelled (reversed) has an FI document RV  and posting key 11. whiles in customizing the settings for posting keys and document types are different from what has been customized. Below is my current settings.
    The posting key 01 has a  reversed posting key 12 and the document type RV has a reverse document type AB. This customizing is in correct in SPRO.
    Transactions : OB41 and OBA7
    Can anyone help on this....
    Thanks
    Elvis

    Hello,
    Did you verify whether AB document type in OBA7 is marked in "Account Types allowed" the Customer checkbox?
    If not, maybe that is why it is not selecting AB as the reversal document type for RV, even though it is set up in RV document the AB document type as reverse document type.
    Other than this (if the mentioned above doesn't solve your issue), I would say there should be any user-exit that can be changing the document type, according to some specific business rule of your SAP client or even a substitution.
    I hope it helps you.
    Regards,
    Daniel.

  • Posting period in back date (MMPV)

    Hello All,
    Can i open the posting period in back date.
    like my current opening period is 11 (01.02.2009) and perious posting period is 10 (01.01.2009).
    can i open the 09 posting period, if yes then how, please tell.
    i am using MMPV and MMRV.
    Thanks
    Pankaj Garg

    REOPEN THE PERIODS:
    It is possible to re-open a previously closed period. However, it is NOT advisable to do so because the valuation data of the previous period could be affected.
    In general, it is only safe to reopen a previously closed period when no material postings have been done after the period shifting to the new period.
    If there has already been postings after the period shifting to the new period, reverting the period back will cause database inconsistencies in the history tables.
    If you decide to proceed with this process, you can use the program RMMMINIT, but, please review the documentation of this program first!! and the check the SAP notes 487381 (for the error message that you are receiving) and the 369637 (for an explanation about the inconsistencies that will be generated.
    Steps are as below;
    Go to Transaction Code SE38
    Enter program name RMMMINIT
    Execute or press F8 function button
    Enter your company code (From and To)
    Enter relevant date: Say 01/03/2008 for Mar. 2008 month to be opened as of now
    That means, user can post for the month of Feb 2008 as well as Mar. 2008
    Refer SAP Note No. 487381 for more details.
    As per SAP Notes 487381 ( If the periods are opened in advance in mmpv to again change it to current period the following process should be follow ), Go to Tcode MMPI, then go to menu bar and select system -> user profile->owndata.In that screen , under the parameters tab enter MMPI_READ_NOTE in Parameter ID field and enter, then under short description you will get Initialise period. Next Save.
    Again go to MMPI enter company code, period and year and execute.
    Other way of doing it is follow these steps( But try this method in Sand box Only):
    1. Go to OX18, and delete the plants assigned to your CO.Cd and save.
    2. Go to OMSY and change the posting period to the one u want and save.
    3.Go to OX18 and assign the plants you have deleted in step 1.and save.

  • Function module to get the posting period based on date

    Hi to all,
    Is there any function module to get the posting period based on date?
    Regards,
    Nagesh

    hi,
    CALL FUNCTION 'FIRST_DAY_IN_PERIOD_GET'
          EXPORTING
            I_GJAHR        = GV_GJHAR
            I_PERIV        = GC_24
            I_POPER        = GV_POPER
          IMPORTING
            E_DATE         = S_FKDAT-LOW
          EXCEPTIONS
            INPUT_FALSE    = 1
            T009_NOTFOUND  = 2
            T009B_NOTFOUND = 3
            OTHERS         = 4.
        IF SY-SUBRC <> 0.
          MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                  WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
        CALL FUNCTION 'LAST_DAY_IN_PERIOD_GET'
          EXPORTING
            I_GJAHR        = GV_GJHAR
            I_PERIV        = GC_24
            I_POPER        = GV_POPER
          IMPORTING
            E_DATE         = S_FKDAT-HIGH
          EXCEPTIONS
            INPUT_FALSE    = 1
            T009_NOTFOUND  = 2
            T009B_NOTFOUND = 3
            OTHERS         = 4.
        IF SY-SUBRC <> 0.
          MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                  WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    ags.

  • Regarding posting periods

    Hi All,
    I already closed previous periods upto 03 2010 in mmpv.
    Now i created new po and trying to do GR wrt PO.
    The system issue a message "posting period 004 2010 is not open"
    Please help me how to post this GR.
    Thanks & Regards
    Suresh

    First, do check the last period at tcode OMSY.
    Then go to tcode MMPV.
    Provide todays date
    Press the execute button.
    System show the warning message.
    Then press the outer execute button.
    System will show you the log.
    Then again go to tcode OMSY and check the changes.
    Go on opening till you reach the current one.
    From FI side you can open the periods via tcode OB52.
    Thanks & Regards
    JP

  • Need information regarding local , foreign and document currency

    Hi All,
      I need to know the difference between local, foreign and document currencies.
    Thanks in advance,
    vinay

    Hi,
    Document currency:
    This is the currency set at the POS for the sales documents. If the POS system is not able to send this currency to head office, the POS currency is used as the document currency.
    Local Currency :
    Local Currency - This is, in most cases, the formal currency of the country. In SAP Business One, all the reports displayed in the local currency, and all the foreign currency transactions are translated automatically to local currency. This way, the local currency is the common denominator for all currencies, which enables balance calculation of multi-currency accounts/business partners.
    Foreign Currency: This currency we will talk mostly in the Financial areas
    http://help.sap.com/saphelp_erp2004/helpdata/EN/a6/004940f0030272e10000000a155106/content.htm
    For More detailss:
    http://www50.sap.com/businessmaps/5CE8CE5FA6854AC984502823ACC3AA62.htm
    Difference In Currency :
    http://www.sap-img.com/financial/explain-the-difference-in-currency.htm
    Regards
    Ram.
    Edited by: Ramakanth Deepak Gandepalli on Dec 9, 2009 11:52 AM

  • Issue regarding posting in back date in co

    Dear All,
    My client is facing the following problem, could you please advice me on this
    During July Month end procedure there is an out of balance for a Production order ie, KOB1 balance is not matching with Production order inventory change.
    The issue was due to the reversal of already confirmed labour on 31/07/2009. but the cancellation was done for the confirmation pretaining to Feb & March 2009 which is on previous FY.
    Questions are
    1 ) Since the controlling period is closed for the Previous FY can we confirm that the posting has not occured, how can i confirm the same?
    2)The OH rate for labour is not able to correct since this is a areversal of labour and the values are not settled... how can i move forward on this?
    3)Can a journal entry to the Production order can correct these with offset going to a dummy internal order ,, what will be the effect of the same?
    4)I need to understand how posting in controlling could occur four months after the prior fiscal year end.?
    Thank you In advance
    Regards
    Arun R

    Dear Arun,
    If you assume you will post JV using dummy internal order.... amount which will get posted in internal order will be unabsorbed...
    For taking impact of the amount in activity or material you will have to settle this to some cost center or asset as per your scenario. Other wise it will remain ideal for ever and activity cost and std. cost will not 100% accurate for the period.
    Regards
    Rupesh kumar Singh

  • Issue regarding Thin Installer and driver packages

    Hello everybody,
    I have recently started to work for a new company and have been tasked with creating a new Windows deployment solution.
    My company are using Lenovo desktop and laptop and my installation image use Thin Installer to deploy drivers to our workstations during Windows deployment.
    I have been having some difficulties getting everything to work and I want to write about it here to hopefully help someone in the same situation as me and call out for better quality control at Lenovo.
    Here are the command line I call to start Thin Installer from the local computer:
    START /WAIT thininstaller.exe /CM -search A -action INSTALL -repository \\wds\lenovo -noicon -showprogress -IncludeRebootPackages 1,3,4  -noreboot
    Hers the issues I have expirienced:
    1. Sometimes packages downloaded with Update Retriever will be set to "Reboot type: Forces a reboot" as default. This causes the Thin Installer to reboot reguardless of the -noreboot switch.
    Its possible to change reboot type "Requires a reboot" in Update Retriever and than the updates installs fine.
    This causes problem with scripted installs where you cannot have the system reboot "out of order".
    Updates should never be default "forces a reboot".
    2. On my Thinkcenter e93z (10B8) the Intel Displaydriver (v 9.18.10.3220) wont install because the PnPID is not listed in the XML file. (my PnPID is VEN_8086&DEV_041E&SUBSYS_309C17AA (309D17AA is listed tho)). Manualy editing the XML files to include my PnPID solves the problem.
    Lenovo should really have better qualitycontrol here.
    3. On a t440s machine i have the Synaptics UltraNav Driver (v. 17.0.12.60) wont install automatically with Thin Installer.
    This is because the machine i installed failed the "BIOS test" in the XML file of the update package. I manually edited the XML file and replaced the "BIOS TEST" with one from another update that worked on that system and now everything installs automatically and works fine.
    Its possible that Lenovo has detected some kind of problem with my BIOS version and the Synaptics driver but everything seems to work fine for me.
    I hope this post will help someone in the future
    EDIT: Other people have called out some problems with the information provied in this post. You should read the whole thread before making any changes to your systems.
    Kind Regards,
    2bi

    2bi,
    Thanks for posting your findings.  I will investigate and escalate the missing PnP id issue for the Display Driver issue.  We absolutely need to avoid these kinds of escapes.
    For you ThinInstaller command line I would recommend not using the -showprogress parameter if you are using in a scripted deployment scenario with something like MDT and/or SCCM.  These solutions typically will not allow TI to interact with the desktop during deployment which is what -showprogress will cause.
    Also, you are telling TI to include packages that will automatically reboot your system (type 1), requires a reboot which can be delayed (type 3), will shutdown the machine automatically (type 4).  We have very few type 4 packages anymore; however we definitely have type 1 and type 3.  As sclexman mentioned, the -noreboot will only apply to the type 3 packages which leave the execution of the reboot up to TI.  So -noreboot tells TI that even if it installs updates of type 3, it should not reboot when finished.
    Changing the Reboot Type value in Update Retriever only changes how TI sees the package and does not alter how the package itself executes.  So if a package is designed to always automatically reboot, changing it to type 3 in UR will have no affect.  We have recently had a display driver released by Intel that will automatically reboot if the driver installer detects that it is upgrading an older version of the driver.  In a clean deployment scenario, the automatic reboot will not happen so in this case it is safe to change the type to type 3.
    This leads to another point.  All of our content that is available through Update Retriever is also intended for consumption by System Update which is the utility aimed at individual consumers to help them keep their drivers up to date.  Therefore this becomes our lowest common denominator that we have to support.  This leads to situations that may not be ideal for the deployment scenario.  If we had an army of resources we might be able to manage all of our content for both consumers and enterprise deployments; in effect doubling our efforts.  Unfortunately this is not the case and we are trying to do the best we can.
    Regarding the UltraNav update for T440s, I see that the XML has a _BIOS section under the Dependencies.  However it is defined such that any BIOS level will work because the first level listed is a wildcard asterisk (*).  This BIOS section is actually included for a completely different solution which also uses the XML.  It is not intended to control the targeting of the update for System Update or Thin Installer.  Perhaps there was a mistake made initially and the XML was released without the * and has since been fixed.
    (from the current UltraNav driver package:  )
    <_Bios>
    <Level>*</Level>
    <Level>GGET*</Level>
    <Level>GFET*</Level>
    <Level>GHET*</Level>
    <Level>GIET*</Level>
    <Level>GJET*</Level>
    <Level>GLET*</Level>
    <Level>GMET*</Level>
    <Level>GNET*</Level>
    <Level>GRET*</Level>
    </_Bios>

  • Issue regarding : ESI - Full and final Settlement

    Hi,
    Regarding ESI :
    While doing Final settlement for the employee;  ESI is calculating on overall Gross..Actually, it has to take on Actual Gross Earned. for that month i.e. for 15 days and Esi should be calculated on that 15 days only.
    Any inputs on the above issue is highly appreciated
    Regards
    Tinkoo.

    Hi Tinkoo,
    The ESI is calculated on half yearly basis. From Apr to Sep and Oct to Mar. Assume that if an employee is drawing payment Rs 9500/- in the month of Apr 2010 and his salary is increased by Rs 1000/- in the month of May and his gross will become Rs 10500/- which is more than the ESI limit i.e. Rs 10000/- In this case ESI contribution for this employee will be continued to deduct up to Sep 2010 and the same will be discontinued from 2010 automatically.
    In your case it seems the ESI is getting deducted for the period left i.e. first 6 months period.
    Regards
    Mohan
    Edited by: Mohan Reddy on May 24, 2010 12:56 PM
    ESI limit has been changed from 10000 to 15000  Please have a note of it rest mohan has updated

Maybe you are looking for