Posting period issue while deleting a confirmation posted for a limit PO

Hi ..
I am facing an issue whiel deleting a confirmation posted for a limit PO.
Confirmation was posted for a limit PO in SRM and it created a service entry sheet in SAP. If I deleted that confirmation in the same posting period, then it is getting deleted. No issue here.
But if I deleted that confirmation in the next posting period then the reversal document is going to error in process. RZ20 is showing the error "Positng only possible in periods 2012/2 and 2012/3".
Posting date of reversal document is current date only and the backend posting period is 2012/3, but still it is failing with this posting period error.
If I tried to delete a confirmation posted for a normal PO then I could able to delete it even in next posting period by just changing the posting date.
Why this posting occurs while deleting the limit confirmation, even through the posting date is falls within the backenn posting periiod? Is it like, SAP system is trying to delete the service entry sheet in original posting period? Kindly help.
I am in SRM 5.0 (server 5.5) SP12.
Thanks,
Arun

OK.
Well, if the variable is not used in any interval selection, then I would say "something happened to it".
I would make a copy of the query and run it to check if I get the same problem with period 12.
   -> If not, something is wrong in the original query (you can proceed as below, if changes to original are permitted).
If so, then try removing the variable completely from the query and hardcode restriction to 12.
   -> If problem still persists, I would have to do some thinking.
If problem is gone, then add the variable again. Check.
   -> If problem is back, then the variable "is sick". Only quick thing to do, is to build an identical variable and use that one.
If problem also happens with the new variable, then it's time to share this experience with someone else and consider raising an OSS.
Good luck!
Jacob
P.S: what fisc year variant are you using?
Edited by: Jacob Jansen on Jan 25, 2010 8:36 PM

Similar Messages

  • PGI error related to Posting Period issue

    While delivering, when I do the PGI, it is not allowing ...it says "Posting only possible in periods 2009/02 and 2009/01 in company code 0430"... I closed earler posting periods using Tcode MMPV and opened the current period and fiscal in SPRO IMG. But still PGI is not allowed ...it still says "Posting only possible in periods 2009/07 and 2009/06 in company code 0430". Apart from closing earlier posting periods using MMPV and opening current fiscal in SPRO IMG, what else I need to do to overcome this PGI issue ?

    Hello,
    Please compare the posting periods from MMPV and MMRV
    The posting period for your company in MMRV will show the exact postings periods for your company.
    If this posting periods are not at par to MMPV you have to maintain it.
    regards,
    santosh

  • Posting period issue for company code

    Hi,
    I am getting problem like posting period is not possible in certain duration for particular company code.
    So, what is the path in SPRO  to make configuration changes for this issue.
    Thanks in Advance ...
    Sridhar.

    Dear Go to OB52 there change your configuration as I given below..   enjoy   
    0001     +                                   1     2008     12     2009     13     2008     16     2009        
    0001     A                    ZZZZZZZZZZ     1     2000     12     2010     13     2000     16     2010        
    0001     D                    ZZZZZZZZZZ     1     2000     12     2010     13     2000     16     2010        
    0001     K                    ZZZZZZZZZZ     1     2000     12     2010     13     2000     16     2010        
    0001     M                    ZZZZZZZZZZ     1     2000     12     2010     13     2000     16     2010        
    0001     S                    ZZZZZZZZZZ     1     2000     12     2010     13     2000     16     2010        
    0002     +                                   1     2000     12     2010     13     2000     16     2010        
    V001     +                                   1     2000     12     2010     13     2000     16     2010

  • Error while deleting the confirmation- Reason has to be entered for 102

    Hi,
    When i try to delete the confirmation for Goods, an error -"A reason has to be entered for movement type 102" is occuring. I have maintained the reason for rejection in the document tab at the line item level while deleting the confirmation.The reason for movement field is mandatory in R/3 system for movement type 102. I have maintained this reason for rejection that has maintained in the R/3 system in the SRM config and able to select that during deletion of confirmation, but still i am getting this error. Please suggest.
    Regards
    GGL

    sorry for the very late reply..
    Note 1345896 - Error due to reason for movement when deleting the GR in EBP
    When we try to delete a goods confirmation with the Reason for Rejection text in SRM, we get the error "A reason has to be entered for movement type 102" (M7 325) thrown from the backend R/3 system.
    Other terms
    M7 325, RREJ, Reason for Rejection, MOVE_REAS, c_subtype_ca, LBBP_CFF60, FORM mapping_gr_for_backend.
    Reason and Prerequisites
    This is caused by a program error
    it helps aothers too

  • How to keep FI posting period (OB52) closed but keep CO posting periods (OK

    Hi SAP Guru's,
    how to keep FI posting period (OB52) closed but keep CO posting periods (OKP1) open.
    I.e. on Oct 21th the FI posting period 10 should be open but FI posting period 09 should be closed. But on Oct 21th the CO posting period 09 should be open.
    Thanks in Advance.
    RV

    You've already activeted. You can check in IMG-Financial Accounting Global Settings (New) ® Ledgers ® Real-Time Integration of Controlling with Financial Accounting
    Check this for more info http://help.sap.com/saphelp_dimp50/helpdata/en/22/c2cf4031288131e10000000a1550b0/content.htm

  • Issue while deleting Inbound delivery.

    Hello All,
    Here there is an issue while deleting Inbound delivery.
    GR ie 101 movement type is done for 1000 stocks.
    Later GR reversal ie 102 movement type is done for 200 stocks.
    So now in MD04 transaction inbound delivery is opened for 200 stocks.
    I am trying to delete Inbound delivery for 200 stocks but it doent allow.
    wht to do?please help

    I think you have used 102 and manully amend the qty.
    The inbound has 1000 qty, you reverse 200 qty. You should amend inbound delivery document qty to 800 and not delete it.
    Appreciate to revert is solution works for you.

  • Issue while deleting a row from a table

    Dear friends,
    i am getting an issue while deleting a row from a table, pls check screen shots , the first screen shot is my table contents
    when i delete 2 row , the second row is deleting properly like below screen shot
    but i want like below screen shot , Col1 contents should be like pic 1 . could any one pls let me know how to solve this issue.
    Thanks
    Vijaya

    Hi vijaya,
    please try this code, it will help you.
    DATA : it_rows  TYPE wdr_context_element_set,
              wa_rows LIKE LINE OF it_rows.
       DATA lo_nd_table TYPE REF TO if_wd_context_node.
        DATA lt_table TYPE wd_this->elements_table.
       DATA lo_el_table TYPE REF TO if_wd_context_element.
       DATA ls_vbap TYPE wd_this->element_table.
    DATA: ld_index TYPE i.
    data value TYPE sy-index.
    * navigate from <CONTEXT> to <table> via lead selection
       lo_nd_table= wd_context->get_child_node( name = wd_this->wdctx_table ).
    * @TODO handle non existant child
    * IF lo_nd_table IS INITIAL.
    * ENDIF.
    * get element via lead selection
    * alternative access  via index
    * lo_el_table = lo_nd_table->get_element( index = 1 ).
    * @TODO handle not set lead selection
       IF lo_el_table IS INITIAL.
       ENDIF.
    * navigate from <CONTEXT> to <table> via lead selection
       lo_nd_table = wd_context->get_child_node( name = wd_this->wdctx_table ).
    * @TODO handle non existant child
    * IF lo_nd_table IS INITIAL.
    * ENDIF.
       lo_nd_table->get_static_attributes_table( IMPORTING table = lt_table ).
    * @TODO handle non existant child
    * IF lo_nd_table IS INITIAL.
    * ENDIF.
    ** @TODO compute values
    ** e.g. call a model function
    * navigate from <CONTEXT> to <table> via lead selection
       lo_nd_table = wd_context->get_child_node( name = wd_this->wdctx_table ).
    * @TODO handle non existant child
    * IF lo_nd_table IS INITIAL.
    * ENDIF.
    ** @TODO compute values
    ** e.g. call a model function
    it_rows  =  lo_nd_table>get_selected_elements( ).
       CALL METHOD lo_nd_table->GET_LEAD_SELECTION_INDEX
       RECEIVING
         INDEX  = value .
      LOOP AT it_rows INTO wa_rows.
         CALL METHOD wa_rows->get_static_attributes
           IMPORTING
                  static_attributes = ls_table.
         READ TABLE lt_table INTO ls_table WITH KEY col1 = ls_table-col1.
          ld_index = value.
              ENDLOOP.
       CLEAR : ls_table-col2,
             ls_table-col2.
       MODIFY lt_table INDEX ld_index FROM ls_table.
      lo_nd_table->bind_table( new_items = lt_table set_initial_elements = abap_true ).

  • HT3743 HT4623 We're sorry, we are unable to continue with your activation at this time. Please try again later, or contact customer care.----How to fix this issue while setting up the iphone for the new ios?

    HT4623 We're sorry, we are unable to continue with your activation at this time. Please try again later, or contact customer care.----How to fix this issue while setting up the iphone for the new ios?

    If you don't have a SIM card in the phone, you must put one in. It's required for activation.
    If you do, then your phone was probably hacked to unlock it from the original carrier. Contact them and see if they will unlock it. If they will not do so, then you can't use that phone.

  • SAP posting period error while mainting stock in MB1C

    Hi,
    Error Description:-
    While I am maintain the stock in MB1C i got an error i.e.
    Error:-  Postingonly possible in periods 2006/12 and 2006/11 in company code CLC1 ( CLC1 is mycompany code.)
    To resolve this error  I did some pre-requisite, 
    First :- In OB29, I define my fiscal year variant ( Here,  I copied the K4 andrename S4 and save )
    Second :- then, in OB37, I Assign fiscal year variant to company code.
    Third :- I define variant for open postingperiod, ( Here, I define my ownvariant  to use the following  menu path - IMG-- FAFinancialaccounting global settingsDocuments-- Posting periods--Define variant forposting periods).
    Forth:- in OB52, i define the open and close posting periods ( Here, in new entries i choose my variantwhich i define in 3rd step  and define myperiods).
    still system not allowing me the current dated posting, then i use the following step to resolve the error,
    I mgoing to MMPV for close the periods. (here I  closed all periods, month wisetill 2012/01).
    stilli got the same error,  so  Icheck  MMRV & OMSY, weather postingperiods change or not.. ( Here, systemshows me backdated posting periods i.e. 2006/12).
    Kindly help me to resolve this error.
    reg.Mayur

    Hi,
    As you Said i closed each period as well as fiscal year , but still my problem not resolved .. system shown me following notification after i closed the period..
    Mode: Close period only
    Client:800
    Period entered (month/year):042010
    Invalid period for company code CLC1; no conversion here.
    Period closing complete; log issued.
    Mode: Close period only
    Client:800
    Period entered (month/year):012012
    CoCd CLC1: table T009B incomplete; no conversion here.
    Period closing complete; log issued.
    Mode: Close period only
    Client:800
    Period entered (month/year):022012
    Incorrect period in control rec. of CoCd CLC1; no conversion
    The current period (month/year) of the control record is122006
    Period closing complete; log issued.
    E N D

  • POSTING PERIOD ERROR WHILE DOING GR

    Dear All,
    I am facing error in posting period while doing GR -
    1) Posting period 007 2010 is not open - For current date GR
    2) Posting only lies in periods 2010/07 and 2010/06 in Company Code - For future date in 2010-08
    3) Posting period 006 2010 is not open - For back date GR in 2010-06
    Checked T Code MMRV - Ticked -  Allow posting in previous per. (Still facing the same error)
    Also as per MMRV -
    Current period  07 2010
    Previous period  06 2010
    Last period in prev. year 12 2009
    Please guide
    Vikas

    Hi,
    Check on it:-
    COGI Posting period error
    Re: Error in Opening the Posting Period.
    http://www.sap-img.com/sap-sd/movement-type-posting-error-in-delivery.htm
    pherasath

  • Posting period issue

    Hi People,
                      I recently made some new company code config in my ides. When I did MB1C it gave me usual message which comes for opening posting period  but the problem is that the message was of next fiscal year. I would give an example.
    Lets take todays date that is 02/03/2010. When i did MB1C, it should give me an message as posting only possible in period 2009/11 and 2009/10 . But instead of it the message is posting only possible in period 2010/11 and 2010/10. It is taking posting period of 2010 instead of 2009. Accordingly it is allowing me to do posting in 02/01/2011 as it is 11th period of 2010 which is open, although it get a warning message of posting in the future.
    I  have used fiscal year variant as V3( march to april). In other company codes there is no such problem. Please guide what the issue could be.
    Thanks

    Hi
    Go to OMSY
    enter the company code :
    Enter the year 2010  month 03
    save
    go to MMRV enter the company code check the period will be 03 2010
    You can do the MB1c transaction
    But every month end you should close the previous month and open the next month
    Regards
    G.Ganesh Kumar

  • Posting Period Issue Production

    Hi All,
    Someone at the client Closed Sept and Oct 2008 in MMPV and now , postings cannot be made to Aug 2008.
    in MMRV, it shows current preiod ad Oct 2008 and prev period as Sept 2008.
    How can I fix this in such a way that users can post to August again?
    Appreciate any quck response.
    Thanks in advance

    Reopen The Closed Period
    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.
    XXXXXXXXXXXXXXXXXX
    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.

  • Posting periods issue though I updated in MMPV

    Hi experts,
    I created scheduline agreement and trying to do the PGI , system thrown an error saying 'posting periods possible only 9/2009 and 8/2009'. after this I closed the periods till sep09  in T.code MMPV, still the same error. is there anything else that I have to configure or check to resolve this issue. your help is neede.
    Thanks,
    Kanna.

    Hi,
    This is how you need to do it.
    Go to Tx: OMSY or MMRV & check the current period against your company code.
    Theory behind Posting Periods in SAP
    Posting periods are calculated using a Config: Setting called u201CFiscal Year Variantu201D attached to the Company code. u201CFiscal Year Variantu201D is the deciding factor for the company code, whether to follow the calendar year or any other calculation method.
    Eg: Fiscal year can be start from July & goes to the next year June for some companies.
    Therefore what you see in the OMSY might not be the actual calendar month that SAP is referring.
    (Eg: 01 means Jan, 02 means Feb, 03 means March, etc is not always the case)
    So first you have to check the Fiscal Year attached to your company code.
    Go to below path to check Fiscal Year attached to your company code.
    IMG -> Financial Accounting (New) -> FinanciaI Accounting Basic Settings (New) -> GIobaI Parameters for Company Code -> Enter GIobaI Parameters ->
    Go in to your company & Check the Fiscal Year Variant field. There you can identify whether it equals to the calendar year or not. If its not clear, take that Fiscal year variant 7 go to below IMG path;
    IMG -> Financial Accounting (New) -> FinanciaI Accounting Basic Settings (New) -> Ledgers -> FiscaI Year and Posting Periods -> Maintain FiscaI Year Variant (Maintain Shortened Fisc. Year)
    Go in to the node.
    Select the Fiscal year & double click on Periods node.
    If Fiscal Year is same as calendar year, then you should have that u201CCalendar Yru201D tick box ticked.
    Now check what's the SAP Fiscal month relevant to your calendar month.
    The go to MMPV & open that relevant Fiscal month accordingly.
    Then you should be able to post.
    Hope this helps you !
    Best regards,
    Anupa

  • MM posting period issue

    Dear All,
    We are closing Period in MM by 25th of every month for some reporting purpose. But we did not select ABP(Allow Back Posting).
    But for some cases, we need to post the material documents from 25th to month end. But for these documents, there will not be any value update, only Qty update.
    Please advice.
    Sateesh

    i think, becoz of ur posting period, value n quantity updation will not get affect.
    now, tell me, that material is valuated material, if yes, then check that for this material type under ur valuation area, qty and value updation are ticked or not.
    spro -> LG -> Materail master -> Material types -> Define Attributes of Material Types -> here select ur material type.
    thanks.
    Edited by: Ms. nisha on Jun 2, 2011 8:49 AM

  • Performance issues while accessing the Confirm/Goods Services' transaction

    Hello
    We are using SRM 4.0 , through Enterprise Portal 7.0.
    Many of our users are crippled by Performance issues when accessing the Confirm/Goods Services tab( Transaction bbpcf02).
    The system simply clocks and would never show the screen.
    This problem occurs for some users all the time, and some users for some time.
    It's not related to the User's machine as others are able to access it fast using the same machine.
    It is also not dependent on the data size (i.e.no . of confirmations created by the user).
    We would like to know why only some users are suffering more pronouncedly, and why is this transaction generally slower than all others.
    Any directions for finding the Probable cause will be highly rewarded.
    Thanks
    Kedar

    Hi Kedar,
    Please go through the following OSS Notes:
    Note 610805 - Performance problems in goods receipt
    Note 885409 - BBPCF02: The search for confirmation and roles is slow
    Note 1258830 - BBPCF02: Display/Process confirmation response time is slow
    Thanks,
    Pradeep

Maybe you are looking for