Create Journals for Closed Period

HI,
In July, the user forgot to run journal entries in FA subledger, so the depreciation expenses didn't get posted to GL. So there were variances between FA and GL.
How to capture the July Depreciation journal entries, since the period is already closed.
Since the July period can't be opened, how to deal with these in August.
Thanks in advance.

Hello.
Once you cannot open the GL period (which will be the best solution), note down the impact that it will cause. You can run the Journal Entry Reserve Ledger Report, where you wil find the total depreciation for the month and also the accumulated depreciation. Between this report and you GL Trial Blance for July you will have this difference. In August, post both the FA journals from July and August and, at that moment you shall have no differences.
Hope this helps.
Octavio

Similar Messages

Reserval of Assessment Cycles for closed periods - FAGLGA15

Hello,
We have assessment cycles in closed periods which we want to reverse / repost in current period. We are using ECC New GL functionality. Tcode KISR does not seem to recognize Assessment cycles created with FAGLGA1* .
Suggestions / options to achieve the end result, please.
Regards
Jayesh.

Hi:
If your CO allocation has some external postings (like GL or fixed assets) or generating some intercompany documents, then it needs FI to be open also. It happens sometimes if the allocation goes external so it would need fI period to be open also. If FI is close but CO is open, it would only work for CO specific allocations and others would error out.
Please check the cycle/segment which is in error. If it is suppose to hit FI, then FI (OB52) and CO (OKP1) periods should be in sync.
Thanks.
Rahul

Can SAP run the depreciation for closed Period and posting to diff month?

My client forgot to run the depreciation for Jan 2011, and now the Jan period has been closed and report also done.
My solution was to re-open the Jan and does the depreciation, once completed reclassify Jan depreciation posting to Feb 2011 manually.
I am just wandering whether SAP can handle this different way.
Can SAP performs Jan (Closed Period) depreciation and post to Feb period automatically or any other suggestions?
Cheers

Hi
Yes, you can do that
Follow this thread... Unable to post depreciation- Error AA730
Using ABF1, you can do it
Br, Ajay M

Create values for analogous periods in the same table with DS

Hi,
in the course of a pilot we want to create additional columns with data for analogous periods.
We have values for a month and need to create new columns for values for last month and last year in order to compare.
Attached youu2019ll find a few sample rows resembling the basic concept of what we have
Region     Country     Year     Month     Value
Europe     Spain     2009     1     285
Europe     Spain     2009     2     129
Europe     Spain     2009     3     153
Europe     Spain     2008     1     288
Europe     Spain     2008     2     284
Europe     Spain     2008     3     125
Europe     France     2009     1     135
Europe     France     2009     2     125
Europe     France     2009     3     284
Europe     France     2008     1     208
Europe     France     2008     2     221
Europe     France     2008     3     220
In this case, new columns would be
LastMonth (125 for Spain month 1 year 2009, since this is the value for month 3 year 2008)
LastYear (288 for Spain month 1 year 2009, since this is the value for month 1 year 2008).
Can you help on what function to use in the DS query transformation?
thanks everybody, and enjoy!

Hi David,
Probably the easiest way of resolving this would be to add extra columns which show the projected date each row should be shown on e.g.
Region     Country     Year     Month     Value     LM_Year     LM_Month     LY_Year     LY_Month
Europe     France     2008     1     208     2008     2     2009     1
Europe     France     2008     2     221     2008     3     2009     2
Europe     France     2008     3     220     2008     4     2009     3
Europe     France     2009     1     135     2009     2     2010     1
Europe     France     2009     2     125     2009     3     2010     2
Europe     France     2009     3     284     2009     4     2010     3
This would be written to a staging table then used as a source with the original source file to produce the target table. I've illustrated an example of how this could be achieved below:
Create two dataflows; DF 1 and 2.
In DF 1 read source, add additional columns to show the date (year, month, etc) this should be projected as. This would need to be done for both the last month and last year. Load staging table.
In DF 2 Read the source and outer join to the new staging table twice. Use the region, Country, Year, Month, to join and use the new additional projected date columns. Ensure the last month date fields are used on one staging table and last year date fields are used on the next staging table. The value from the two staging tables is then used in the last month and last year value.
Load into target table.
To calculate the projected date columns you would probably want to format the source fields into a date then add the required number of months. e.g. to_date('01' || month || year, 'DDMMYYYY') + 12
Obviously this would need the stage table to be truncated before each load and you would need to assess your load strategy. When doing these calculated fields if you have any retrospective updates on the source then these would then need recalculating, therefore this assumes it's a complete reload each time.
Edited by: Richard Saltern on Jul 16, 2010 2:01 PM
Edited by: Richard Saltern on Jul 19, 2010 10:10 AM

Creat Job for LSMW (periodical data transfer)- idoc BLAORD

Hi,
We are trying to create job for LSMW (thru frame program for periodic data transfer) for idoc BLAORD (Purchasing contract)
When I am running the job that I created, the job is cancelled and the error is:
"Upload from front-end is not possible in batch mode.
Message no. /SAPDMC/LSMW_OBJ_070 020"
How can I correct that? so I will be able to run a job (the job mast run background?)
Thanks,
Tal Sasson

Hello,
I was also receiving the same message /SAPDMC/LSMW_OBJ_070 020 even though I specified in /SAPDMC/SAP_LSMW_INTERFACE the server path. The problem was that in LSMW->Specify Files you have to delete the definition of front-end files and define application server files.
That Flag File (Path and Name) (field /SAPDMC/LSOINP-FILENAME in program /SAPDMC/SAP_LSMW_INTERFACE) is kind of useless since it is ignored anyway and files defined in LSMW object are imported and they have to be read anyway if you use more than one file.
Regards,
Peter

Invoice cancellation should not allow for closed periods

Dear All,
We will be closing the posting period for each quarter,and declare the sales figure.,what ever the invoices we have made should not be cancelled in that quarter.,i want the a check in the system that if any cancellation during this quarter which is closed ,should not allow to cancel the invoice.ofcourse the accounting document will not be generated as the posting period is closed but still the invoice is generated and blocked for accounting.i want the creation of billing document should be blocked.
i Know this can be achieved By defining new routine in VOFA and assign it in VTFL., but is there any standerd routine there which will solve my purpose or i hae to go for new routine.
REgards
Shakthi

Hello Shakthi,
In standard, there is note 180756.
Unfortunately the note 180756 just helps for billing creation, it is not useful for
billing cancellation.
The note 180756 suggests to develop a copy requirement routine checking
the periods.
But in VF11 copy requirement routine are not performed.
Unfortunately there is not a ready-to-use workaround.
In transaction VOFA is possible to define a "copy requirement" routine,
which is performed when the invoice is cancelled.
You could create a routine doing the necessary check, and put
it here.
Regards,
Alex

Run CKMLCP (material ledger cockpit) for closed period in MMPV

Hi,
I would like to run CKMLCP for period 12.2008, however MMPV was run in 02.2009, and only january and fabruary 2009 are allowed for material postings.
How can I settle material ledger in 12.2008? I know about note 361236 (CKMLCP: No period-end closing operations after period shift), but don't know if this will do all the proper postings or only close 12.2008 technically.
Regards,
Karol

Hi Carol ,
Please remeber costing Run i.e CKLMCP is a closing activity so it should be done only at the time of closing a particular period .A syou said two periods are open for MM but costing also post some Accounting enteries if FI period is closed the its not possible.
And its not recommended to run costing any time in middle of the period.
Thanks
Deepa

Create records for missing periods in transformation

I need to create some routine that creates fical periods missing with 0,00 as value in de key figure and the characteristics remain the same. It is possible to create in the transformation something like this? Should put it in the initial routine or in the end one?
Source
Company 1; Account 1; Fiscper 012009; KF 345 Eur
Company 1; Account 1; Fiscper 032009; KF 123 Eur
Company 1; Account 1; Fiscper 062009; KF 678 Eur
Company 1; Account 2; Fiscper 012009; KF 987 Eur
Final destination
Company 1; Account 1; Fiscper 01.2009; KF 345 Eur
Company 1; Account 1; Fiscper 02.2009; KF 0 Eur
Company 1; Account 1; Fiscper 03.2009; KF 123 Eur
Company 1; Account 1; Fiscper 04.2009; KF 0 Eur
Company 1; Account 1; Fiscper 05.2009; KF 0 Eur
Company 1; Account 1; Fiscper 06.2009; KF 678 Eur
Company 1; Account 1; Fiscper 07.2009; KF 0 Eur
Company 1; Account 2; Fiscper 01.2009; KF 987 Eur

you are right, that's what I'm afraid of.
I already have a end routine:
PROGRAM trans_routine.
*       CLASS routine DEFINITION
CLASS lcl_transform DEFINITION.
PUBLIC SECTION.
* Attributs
    DATA:
      p_check_master_data_exist
            TYPE RSODSOCHECKONLY READ-ONLY,
*-    Instance for getting request runtime attributs;
*     Available information: Refer to methods of
*     interface 'if_rsbk_request_admintab_view'
      p_r_request
            TYPE REF TO if_rsbk_request_admintab_view READ-ONLY.
PRIVATE SECTION.
    TYPE-POOLS: rsd, rstr.
*   Rule specific types
    TYPES:
      BEGIN OF _ty_s_TG_1,
*      InfoObject: ZIGCHENTI Magn_ci - Entity.
        /BIC/ZIGCHENTI           TYPE /BIC/OIZIGCHENTI,
*      InfoObject: ZIGCHPART Magn_ci - Partner.
        /BIC/ZIGCHPART           TYPE /BIC/OIZIGCHPART,
*      InfoObject: ZIGCHCTSH Magn_ci - CtShare.
        /BIC/ZIGCHCTSH           TYPE /BIC/OIZIGCHCTSH,
*      InfoObject: ZIGCHCURR Magn_ci - Currency.
        /BIC/ZIGCHCURR           TYPE /BIC/OIZIGCHCURR,
*      InfoObject: ZIGCHZONE Magn_ci - ZONE.
        /BIC/ZIGCHZONE           TYPE /BIC/OIZIGCHZONE,
*      InfoObject: 0FISCPER Exercício / período.
        FISCPER           TYPE /BI0/OIFISCPER,
*      InfoObject: 0FISCVARNT Variante de exercício.
        FISCVARNT           TYPE /BI0/OIFISCVARNT,
*      InfoObject: ZIGKFCSAM Magnitude - Consolidated Amount.
        /BIC/ZIGKFCSAM           TYPE /BIC/OIZIGKFCSAM,
*      InfoObject: 0CURRENCY Código da moeda.
        CURRENCY           TYPE /BI0/OICURRENCY,
*      InfoObject: 0FISCYEAR Exercício.
        FISCYEAR           TYPE /BI0/OIFISCYEAR,
*      InfoObject: 0FISCPER3 Período contábil.
        FISCPER3           TYPE /BI0/OIFISCPER3,
*      InfoObject: ZIGCHAINT Magn_ci - Audit ID.
        /BIC/ZIGCHAINT           TYPE /BIC/OIZIGCHAINT,
*      InfoObject: ZIGCHFINT Magn_ci - Fluxo.
        /BIC/ZIGCHFINT           TYPE /BIC/OIZIGCHFINT,
*      InfoObject: ZIGCHGLAC Magn_ci - Conta.
        /BIC/ZIGCHGLAC           TYPE /BIC/OIZIGCHGLAC,
*      InfoObject: ZIGCHCINT Magn_ci - Categoria.
        /BIC/ZIGCHCINT           TYPE /BIC/OIZIGCHCINT,
*      InfoObject: ZIGCHPINT Magnitude - Perímetro de Consolidação.
        /BIC/ZIGCHPINT           TYPE /BIC/OIZIGCHPINT,
*      InfoObject: ZIGCHCCUR Magn_ci - Consolidation Currency.
        /BIC/ZIGCHCCUR           TYPE /BIC/OIZIGCHCCUR,
*      InfoObject: ZIGCHVINT Magnitude - Versão de Consolidação.
        /BIC/ZIGCHVINT           TYPE /BIC/OIZIGCHVINT,
*      InfoObject: ZIGCHPROD Magn_ci - PROD.
        /BIC/ZIGCHPROD           TYPE /BIC/OIZIGCHPROD,
*      InfoObject: ZIGCHDEST Magn_ci - Dest.
        /BIC/ZIGCHDEST           TYPE /BIC/OIZIGCHDEST,
*      InfoObject: ZIGKFCSAC Magn - Cons.Amount - CURR.
        /BIC/ZIGKFCSAC           TYPE /BIC/OIZIGKFCSAC,
*      InfoObject: ZIGKFCAIP Magn - Cons.Amount - IVA - PMP.
        /BIC/ZIGKFCAIP           TYPE /BIC/OIZIGKFCAIP,
*      InfoObject: ZIGKFCAIR Magn - Cons.Amount - IVA - PMR.
        /BIC/ZIGKFCAIR           TYPE /BIC/OIZIGKFCAIR,
*      InfoObject: ZIGKFVLM Dados Magnitude - Valor Mensal.
        /BIC/ZIGKFVLM           TYPE /BIC/OIZIGKFVLM,
*      Field: RECORD.
        RECORD           TYPE RSARECORD,
      END   OF _ty_s_TG_1.
    TYPES:
      _ty_t_TG_1        TYPE STANDARD TABLE OF _ty_s_TG_1
                        WITH NON-UNIQUE DEFAULT KEY.
*$*$ begin of global - insert your declaration only below this line *-*
    ... "insert your code here
*$*$ end of global - insert your declaration only before this line   *-*
    METHODS
      end_routine
        IMPORTING
          request                  type rsrequest
          datapackid               type rsdatapid
        EXPORTING
          monitor                  type rstr_ty_t_monitors
        CHANGING
          RESULT_PACKAGE              type _ty_t_TG_1
        RAISING
          cx_rsrout_abort.
    METHODS
      inverse_end_routine
        IMPORTING
          i_th_fields_outbound         TYPE rstran_t_field_inv
          i_r_selset_outbound          TYPE REF TO cl_rsmds_set
          i_is_main_selection          TYPE rs_bool
          i_r_selset_outbound_complete TYPE REF TO cl_rsmds_set
          i_r_universe_inbound         TYPE REF TO cl_rsmds_universe
        CHANGING
          c_th_fields_inbound          TYPE rstran_t_field_inv
          c_r_selset_inbound           TYPE REF TO cl_rsmds_set
          c_exact                      TYPE rs_bool.
ENDCLASS.                    "routine DEFINITION
*$*$ begin of 2nd part global - insert your code only below this line *
... "insert your code here
*$*$ end of 2nd part global - insert your code only before this line   *
*       CLASS routine IMPLEMENTATION
CLASS lcl_transform IMPLEMENTATION.
*       Method end_routine
*       Calculation of result package via end routine
*       Note: Update of target fields depends on rule assignment in
*       transformation editor. Only fields that have a rule assigned,
*       are updated to the data target.
*   <-> result package
METHOD end_routine.
*=== Segments ===
    FIELD-SYMBOLS:
      <RESULT_FIELDS>    TYPE _ty_s_TG_1.
    DATA:
      MONITOR_REC     TYPE rstmonitor.
*$*$ begin of routine - insert your code only below this line        *-*
    DATA: wa_result_fim type _ty_s_TG_1.
    DATA: l_tabix type sy-tabix.
    CLEAR wa_result_fim.
    l_tabix = 0.
    SORT RESULT_PACKAGE BY /BIC/ZIGCHENTI /BIC/ZIGCHAINT /BIC/ZIGCHGLAC
    /BIC/ZIGCHPINT
    /BIC/ZIGCHVINT FISCPER.
    LOOP AT RESULT_PACKAGE assigning <RESULT_FIELDS>.
      IF sy-tabix = 1.
        <RESULT_FIELDS>-/BIC/ZIGKFVLM = <RESULT_FIELDS>-/BIC/ZIGKFCSAM.
      ELSE.
        l_tabix = sy-tabix - 1.
        READ TABLE RESULT_PACKAGE INDEX l_tabix INTO wa_result_fim.
        IF sy-subrc EQ 0.
          IF wa_result_fim-/BIC/ZIGCHENTI =
          <RESULT_FIELDS>-/BIC/ZIGCHENTI
          AND wa_result_fim-/BIC/ZIGCHAINT =
          <RESULT_FIELDS>-/BIC/ZIGCHAINT
          AND wa_result_fim-/BIC/ZIGCHGLAC =
          <RESULT_FIELDS>-/BIC/ZIGCHGLAC
          AND wa_result_fim-/BIC/ZIGCHPINT =
          <RESULT_FIELDS>-/BIC/ZIGCHPINT
          AND wa_result_fim-/BIC/ZIGCHVINT =
          <RESULT_FIELDS>-/BIC/ZIGCHVINT
          AND wa_result_fim-FISCYEAR = <RESULT_FIELDS>-FISCYEAR.
Before I do this calculation I want it to validate if exist the period if not should append it with 0,00 and them do the subtraction.
<RESULT_FIELDS>-/BIC/ZIGKFVLM =
            <RESULT_FIELDS>-/BIC/ZIGKFCSAM -
            wa_result_fim-/BIC/ZIGKFCSAM.
ELSE.
            <RESULT_FIELDS>-/BIC/ZIGKFVLM =
            <RESULT_FIELDS>-/BIC/ZIGKFCSAM.
          ENDIF.
        ELSE.
          EXIT.
        ENDIF.
      ENDIF.
    ENDLOOP.
*-- fill table "MONITOR" with values of structure "MONITOR_REC"
*-   to make monitor entries
    ... "to cancel the update process
*    raise exception type CX_RSROUT_ABORT.
*$*$ end of routine - insert your code only before this line         *-*
ENDMETHOD.                    "end_routine
*       Method inverse_end_routine
*       This subroutine needs to be implemented only for direct access
*       (for better performance) and for the Report/Report Interface
*       (drill through).
*       The inverse routine should transform a projection and
*       a selection for the target to a projection and a selection
*       for the source, respectively.
*       If the implementation remains empty all fields are filled and
*       all values are selected.
METHOD inverse_end_routine.
*$*$ begin of inverse routine - insert your code only below this line*-*
    ... "insert your code here
*$*$ end of inverse routine - insert your code only before this line *-*
ENDMETHOD.                    "inverse_end_routine
Edited by: João Piçarra on Aug 13, 2009 12:18 PM

How to Create records for n periods

hello,
Iu2019m new to script logic and MDX and need any help.
I would like to know how to do it:
Include a new information (100) for dimension account Sales, from time period 2008.NOV, 5 periods, like that:
2008.nov / 2008.dec/ 2009.JAN/ 2009.FEB/ 2009.MAR
100/ 100/ 100/ 100/ 100
Any suggestions?
Thanks in advance.
Sue

Hello Kyle,
Thanks for your reply.
The application has a user-defined dimension, Emp. There is a property called date1 at the Emp dimension. Depending on the Emp selected, it will have a different initial time.
The number of periods (5 in the example) can be different. There is a member at the account dimension, period, that defines how many periods must be stored.
Information for Sales comes from other account, SalesTot. User inputs other values for SalesTot calculation.
So I have,
For emp1.dat1 = 2008.NOV
have to update Sales account, beginning from 2008.NOV and updating for the others periods. The biggest difficulty is because of the initial time and I have to create new records for the sequence, and I cannot have a hierarchy for this.
Hope this clarifies a bit.
Thanks again.
Sue

Performing GR for closed period

Hi Experts,
we closed mm period but unfortunitely we have notice still one product we need to do GR.
so plz advice me how to perfor GR for close MM period
Thanks,
Rajesh

Hi
Check in Tcode MMRV for Post to previous period and activate it.
Now you try to post in previous month it will allow.
You can also use Tcode OMSY to change the period but you have to be cautious if you are in live system.
Hope it helps
Thanks/Karthik
Edited by: Karthik on Aug 18, 2009 5:25 AM

Prevent to create billing document in a closed period

hello
i want to know what is the best way to use transaction VF01 in SD for a billing date which is in an open period in Finance
today i have many users which are creating billing documents for closed periods and this is stuck in VFX3
is there any way to prevent users to do it and create billing documents in a previous period?
thanks
Stephane

Hi
Welcome to SDN! I Hope your 1st experience here is good
The intention of not posting the document and throwing it into VFX3 is exactly what you are looking for.. You need to cancel your document from VF02 and re-create it again...
If you want to put an ABAP check, to that saving in VF01 should not be allowed, use exit RV60AFZZ or RV60AFZB... But, I would say discipline is the apt solution to such issues
you can write logic in this exit with the help of ABAP consultant...
Regards
Ajay M

Closing Period Authorization Change Non GL Documents

Version: SAP 2007 PL15
Description of requirements: A new authorization or period setting that would allow users to modify non-journal affecting attributes of a document like the due-date from a PO or the remarks field in a sales order after the period is set as a closing period without granting all users authorization to post within the closing period.
Valid as of: As soon as possible
Business needs: Many businesses have large PO's with multiple lines having different delivery dates which are used in MRP. The company does not want to allow these users to create new documents but as the due-dates get adjusted by the vendor the PO needs to be updated and when the PO is created in the closing period they are currently being blocked.
Examples: The customer creates a large POin January with 12 lines each line delivering on the 1st of the next month. on Feb. 1st the January period is set to closing period and all appropriate financial statements are genertaed. The vendor then calls and informs the purchasing employee that their March shipment will be late, sine that shipment contains goods that are used in production the estimated Duedate needs to be updated so MRP will not suggest incorrect stock levels ofother items or mistakenly suggest goods can be ready when they could not be. If this happens multiple times per day to several sales people then the individuals with modification authorization in the closing period would become enundated with requests.
Current Workaround: assign users authorization to closing periods which is not a sufficient long term work around, one clients books have already been corrupted by user error's in the purchasing and sales departments.
Proposed solution: A new Authorization that would allow modifications to documents that do not affect journal entries within the closing period. or the locked except sales period.
This has already impacted 2 customers strongly, Ioline systems and Dri-Eaz Inc.
Submitted By Dan Love for Omega Group

Hi Greig,
Period Closing means users who have period closing authorization can post all types of transactions and documents. So if you have authorization to do this, you will still be able to post transactions.

T CODE FOR OPEN PERIOD.

Dear all Guru's
I know that for closing period the T.CODE is MMPV , Pl tell
me that wat is the code for opening period . & also suggest wat is to enter when using MMPV & ( T CODE for opening period.
rewarded if helps.
rc

Dear RC,
This T-code for opening period to company.
it means to plant reports will take every month.so we need to close plant transactions in every month ending.then only we will see the reports of every month of plant.
in MMPV we have to give company code and opening month name and press execute button.
this is the main uses and functions or MMPV.
Hope this will helps you
Prem.

Can we prevent posting in Leading Ledger by closing periods in NLL?

Is it possible?
I have 24 periods in non leading ledger(2 per calendar month) and want to prevent posting in the leading ledger if the posting period is closed in non leading ledger.
E.g. if I close periond 1 in non leading ledger which corresponds to Jan 1 to Jan 15, I should not be able to post anything in leading ledger till Jan 15, but whatever I post from Jan 16 - Jan 31 would be posted in 1st period of LL and 2nd period on NLL as that period is now open.
Currently when I try to post thru FB50L, for closed period, if I mention the non leading ledger, the document is not posted. But when no ledger group is mentioned. the document is posted in both ledgers..
Thanks for your thoughts on this.
Regards,
SSK

You have to define a separate Fiscal year variant to non leading ledger using with the following path
Financial Accounting (New) > Financial Accounting Global Settings (New) > Ledgers > Ledger > Define and Activate Non-Leading Ledgers
Rgds
Murali. N

Preventing posting in leading ledger by closing period in non leading ledge

Is it possible?
I have 24 periods in non leading ledger and want to prevent posting in the leading ledger if the posting period is closed in non leading ledger. Currently when I try to post thru FB50L, for closed period, if I mention the non leading ledger, the document is not posted. But when no ledger group is mentioned. the document is posted in both ledgers.
Thanks for your thoughts on this.
Regards,
SSK

You have to define a separate Fiscal year variant to non leading ledger using with the following path
Financial Accounting (New) > Financial Accounting Global Settings (New) > Ledgers > Ledger > Define and Activate Non-Leading Ledgers
Rgds
Murali. N

Create Journals for Closed Period

Similar Messages

Maybe you are looking for