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.

Similar Messages

Depreciation run 'stuck' in a closed period

Dear experts,
I have the following issue (PROBLEM )
Depreciation ran in Jan - no issues. Dep keys for 2 assets were updated in Feb from 0000 to an automatic key Z..., as a result depreciation was recaclulated as of Jan. Then user, by mistake, ran depreciation for Jan again to 'catch up' deprn on these 2 assets. He got an error log - period 01 is closed, which makes sense. In aw01n Jan now shows as green - posted, but when you drill down you see that Jan depn has not been posted and you see the error log again
Now the user is trying to run depn for Feb and gets the following message: Sorry, you had a run that was cancelled in Jan, you have to restart Jan first before posting Feb. There is no way Jan can be opened.
What I've tried:
changed key back to 0000, run AFAR to recaclulate deprn back to zero for these 2 assets, hoping to re-run AFAB for Jan for these 2 assets to get zero and have depn unstuck...didn't help.. still get an error message - period 1 is closed.
Please advise...

Thanks Bernhard -
What is the difference between XBUKZ: 1 Restart Batch-Input and XBUKZ: 0 Restart Setup ANLP. And how to restart TABA? thought that new depreciation run uses the "direct" update of the depreciations via the accounting interface, not batch input like old depreciaton run, so was surprised to see description of XBUKZ: 1
Another question: if the period is opened wouldn't it be easier to run depreciation in period 1 in restart mode?
I was considering to delete records from ANLP - planned derpn and to be posted depreciation... tested it, works okay (delete records, restart depn in closed period 1, no errors, no documents posted, period 2 planned depreciation can be posted. Not sure what is better from the SOX point of view - open closed period or update internal table in prod....:-(
Thanks a lot for your reply...
Elena

How to reverse the closing period document.

Hi
The entry can be reverse Only in current period
You are trying the reverse the entrie in close period which is not possible .. how to reverse the closing period document.
Thank you

Use t code FB02. Enter required parameters and press enter. From the menu slect Extras - Document header. This will take you to next screen. In this screen from the menu select GoTo Document Header. Change the reversal date and save.
Then reverse the document using normal process. The document will get reversed on the new date entered.
Hope this helps. If useful, please reward points.
Regards
Rakesh Pawaskar

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

Changing PO details when posted in closed period

Hi,
We are on SBO2007A PL42.
When we attempt to change details on a purchase order that was posted in a period that is now closed, we are unable to do so.
There shouldn't be a problem modifying these PO's as they don't affect the general ledger in any way.
The only way we have found around it is to modify the posting date of the PO and then change the details we want to change.
Is there any other way to allow us to change the details without changing the posting date?
Thanks,
Michael

This is a problem with authorisations, which is fixed in PL46 of 2007A.
Try giving authorisation to "update posted AR documents", or to allow to "post to Closing Periods".
I have found I needed to give both of these to get this to work.
The other option is to change the date on the PO to a date in an open period.
These should be able to be updated by superusers?

FI - accruals engine - book documents in the previous closed period?

Hi all !!
My Russias user make a question.
Suppose of being in this situation:
- I have closed the period of accruals engine and I have recorded all the writings costs on that period.
- But today my user want to book documents in the previous closed period with starting accruals in the previous period .
My question is following:
Is it correct to book the document in the closed accruals period?
Or user can ONLY book the document IN the first date follow last one closed accruals period?
Thanks Again for your very Kind Aid and Support!
Regards
Saverio

Hi,
If only a limited set of users is to be able to post in a particular posting period, proceed as follows:
Add the posting period authorization (authorization object F_BKPF_BUP) to the authorizations of the selected users. Assign an authorization group (e.g. '0001'), which is to be maintained in the last column of the transaction.
Enter the account type '+' for the posting period variant to which the restriction is to apply. Enter the period(s) whose use is to be restricted in the first period, those which are available to all users in the second period, and the authorization group (e.g. '0001') in the last column.
For Eg,
A posting period can be successively restricted. If, e.g. 10 users have the posting period authorization with authorization group '0001', and 3 of these 10 users also with authorization group '0002'.
If the period is only to be accessible to the 10 selected users the authorization group '0001' is entered in the posting period variant. Access can later be restricted to the remaining 3 users by entering '0002'.
Hope this helps..
Good Luck!!!

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

Posting Period Authorization

SAP Version: SAP B1 8.8 PL 10
Hi All,
            On 1st of every month we close the Previous moth Posting Period, so that No user can Add or Update any Documents which belongs to the previous month. But we had to give authorization to few managers to update.
            We tried to achieve this in this way:
            1. Previous month Posting period set to Closing Period
            2. Set Authorization to all users No Authorization for Period Status: Closing Period & Period Status: Unlocked Except Sales in Authorization window.
            3. And Set Posting Periods to NO Authorization in authorization window.
                   By Doing this should make all users who have got NO Authorization to Period Closing should not be allowed to Update OR Add any Documents which belongs to Previous month.
                   But this is not happening. I am able to cancel the document and add the document in to previous month logging into the user who doesn't have authorizations to do so.
Is there any other way to Achieve this.
Cheers,
Sree.

Check the solution as follows:
dministration -> System Initialization -> Posting Periods
   1. The implications of different Posting Period Status.
When Posting Period status is set as:
Locked
any data entry or journal entry will be disabled for all users.
Unlocked
data or journal entry can be done by any user in this period provided that General Authorization does not restrict the user from certain actions.The functionality is as the following combination of fields values 'Active'=Yes, 'Locked'=No from the previous versions.
Unlocked Except Sales
data and journal entry can be entered within all document types appplications and tools except any Sales document under (Sales - AR). The functionality is as the following combination of fields values 'Active = No, 'Locked'= No from the previous versions. Work under this period status is allowed only for those users who have assigned 'Full Authorization' in General Authorizations form -> General group -> Period Status: Unlocked Except Sales.
Closing Period
data and journal entry can be performed within all document types, applications and tools. Work under this period status is allowed only for those users who have assigned 'Full Authorization' in General Authorizations form -> General group -> Period Status: Period Closing.
NOTE: The Period Indicator set for certain Posting Period does not influence on the possibility of entering data (marketing documents and journal entries).
NOTE: When you log to a company after its upgrade from previous versions then SAP Business One checks for "Unlocked" and "Unlocked Except Sales" periods whether their 'To Date' are older than Actual System Date. If YES those period statuses are changed to "Period Closing".
It is also possible to switch on / off this automatic update of periodstatus and also define a delay in days. For more details please refer to the 'Automatic change of period status' section.
   1. Automatic change of period status:
Period status of just ended posting period (based on actual system date) should be automatically changed from "Unlocked" or "Unlocked Except Sales" to "Period Closing" after the very first log into the system in a new subsequent posting period (based on actual system date) when "Automatic Change of Period Status to 'Closing Period' " checkbox is checked and value in "Date When Automatic Change Is Applied" field equels 1 (what are actually their default settings after upgrade or when new company is created). However, if authorized user would change the period status back to "Unlocked" or "Unlocked Except Sales" from "Period Closing" and the system would be started again e.g. next day or simply in a few seconds later, automatic change would not be applied any more.
User can decide to disable function of Automatic Change of Period Status by unchecking "Automatic Change of Period Status to 'Closing Period' " checkbox.
User can also decide to execute automatic change on the second or later day in new period or even the period after by entering a new value in "Date When Automatic Change Is Applied" field on Posting Period. When the value = 1, the change is applied on the first or later day of new period depending on the first login into the system. When the value = 2, the change is applied on the second or later day depending on the first login into the system. Default value for new company and after upgrade is 1.
   1. "Posting Date To" field is disabled.
When you try to add a new Posting Period, SAP Business One offers the next free year which has not been defined yet. For example, when you have already defined Posting Period for 2006 year and then you want to add a new one, SAP Business One proposes you the next 2007 year (in Administration -> System Initialization -> Posting Periods -> orange arrow callingparticular posting period form -> 'Dates From... To' fields) automatically. Moreover, when you want to add a not annual period (e.g. quarter, month, etc.) then even if the "Posting Date To" field is disabled and has wrong value in process of adding, after the period is created the value of the field "Posting Date To" is recalculated and changed to correct date (usually end of the year).
   1. When any data or journal entry is being created behind some system document (exactly when a user tries to add the document), SAP Business One checks whether the entered date value in 'Posting Date' field fits any defined posting period. If NOT i.e. there is no posting period defined coveringthe entered Posting Date, the following system error message will appear as a pop-up: 'Posting Date deviates from the defined range. To complete the action, define posting period matching the entered Posting Date.'
   2. When deleting Posting Periods (by sub-periods) SAP Business One checks whether there is no data entered within the particular period, additionally SAP Business One checks if at least one very last posting sub-period remains defined in the database. If not, the deletion will not be allowed under any circumstances. As part of this restriction, the following system error message will appear for the user: 'Cannot remove the last period'.
it is from SAP note 1050246. if not resolve, log a message to SAP support or upgrade the PL version from 10 to 13.
JimM

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

Changes to Numbers document on iOS get discarded

I was happily updating my spreadsheet with Numbers on my iPad 3. Then I opened the document in iCloud but the latest changes to my document weren't there. So, I closed the document at icloud.com and went back to my iPad. The latest changes to my Numbers document were completely erased from the iPad as well! There was absolutely no warning of conflicts and I didn't edit the spreadsheet in icloud.com at all!
What makes this happen and what to do to avoid this?

Now those changes aren't showing up in the same document on my iMac.
of course not. iwork on Mac does not even know that icloud exists. Syncing of iwork files is only active in iOS devices, not for Mac.
How can I accomplish this task?
navigate from mac to www.icloud.com , go to the iwork section, up- or download your file :
After editing a downloaded document, you must re-upload it, else the iOS doesn't get the changes . The browser is the missing link, because as I said : iwork on Mac has no cloud integration - none. You can also use Microsoft or Open-Office, it just does not matter.. Basically you would not even have to have iwork09 installed, only those ios apps.

Authorization step by step document on BI 7.0

Dear Friends,
Please send me step by step document on BI 7.0 authorization ,
Thanks in Advances
RA

You can find information from Help.sap.com, related link and initial information listed below.
http://help.sap.com/saphelp_nw2004s/helpdata/en/59/fd8b41b5b3b45fe10000000a1550b0/frameset.htm
Generation of Analysis Authorizations
Use
With the generation of analysis authorizations, you can load authorized values from other systems into DataStore objects and generate authorizations from them.
In this way, necessary authorizations from the data for an application (for example, HR) can be generated so that users are able to see or not see the same data in the BI system as in the transactions of the application, even when the authorization concepts are different.
You can use the generation of authorizations to generate either single authorizations or mass authorizations. It is suitable for scenarios that generate new authorizations periodically, that is, that are constantly changing. It does not necessarily make sense to assign these authorizations to the users in roles and profiles. This is not even possible for automatically generated names that keep changing. Therefore the generated authorizations are assigned directly in the BI system. This is considerably faster than generating them from profiles. If a fixed name is assigned, however, this can be done manually from role maintenance. Keep in mind, however, that there is the danger that you can overwrite constant names.
The generation of authorizations is a dynamic authorization assignment that is an alternative concept to the role concept.
Prerequisites
An extractor must be available for authorizations (up to now, for HR and Controlling).
For HR:
You have to transfer the DataStore objects 0TCA_DS01 and 0TCA_DS02 (optional 03 to 05) from BI Content. These DataStore objects should be copied for each application for which you want a complete data load. For more information about the content objects at BI Content ® Human Resources ® Organizational Management ® DataStore Objects ® Structural Authorizations Hierarchy and Structural Authorizations Values
For controlling:
A complete scenario is available. Transfer the content objects: 0CO_OM_CCA_USER1 (DataSource and InfoSource), as well as the DataStore objects including update rules 0CCA_001, 0CCA_002, and 0CCA_003.
For all other applications:
Copy the templates 0TCA_DS01 and 0TCA_DS02 (optional 03 to 05) in DataStore objects for your application area (department, and so on). Note the naming convention with the digits 1 to 5 at the end.
You need sufficient authorization for generation activities such as deleting, changing and generating analysis authorizations, changing user assignments (authorization object R_SEC), along with any other activities for creating or changing system users using NetWeaver authorization objects for user maintenance. The authorizations required in detail depend on the generation scenario.
Features
You get to this function through management of analysis authorizations (transaction RSECADMIN) at Authorizations ® Generation of Authorizations.
The DataStore objects for generating authorizations have an analogous structure to the authorizations and contain the following authorization values:
●      Authorization data (values) (0TCA_DS01)
●      Authorization data (hierarchy) (0TCA_DS02)
●      Description texts for authorizations (0TCA_DS03)
●      Assignment of authorization users (0TCA_DS04)
●      Generation of users for authorizations (0TCA_DS05)
The actual data to be used in the generated authorizations can be found in the two template DataStore objects 0TCA_DS01 and 0TCA_DS02.
More information:
●      Template for DataStore Objects with Authorization Data (Values)
●      Template for DataStore Objects with Authorization Data (Hierarchy)
You define which authorizations are to be generated from which DataStore objects. You then load your authorization data for them. This can be done for example with CSV files or with extractors. Automatic generation assumes correctly filled DataStore objects. However, the system tries to detect incorrect intervals and some other errors, and to correct them if possible. This is recorded in the log.
For CSV files, the fields User and Authorization need not necessarily be filled with values. In general, however, these fields can be filled with names and numbers. There can be different results when you assign authorizations. You can find more detailed information in the detailed descriptions of the two template DataStore objects above.
You can generate the authorizations on the Authorizations tab page under Generation in the transaction RSECADMIN. As an alternative, the report RSEC_GENERATE_AUTHORIZATIONS starts or schedules generation.
Generating Single Authorizations:
Maintain the user in the DataStore object 0TCA_DS01. It is assigned to the user when the authorization is generated. It can be used for assigning authorizations that are very user specific.
Generating Mass Authorizations:
Leave the User key field empty in the DataStore object 0TCA_DS01 and generate the authorizations. A profile appears that can be assigned to any number of users. The profile gets its texts from the DataStore object 0TCA_DS03. There can be language-dependent short, medium and long texts. You maintain the user in the DataStore object 0TCA_DS04. This generates your mass authorizations.
Generation of Users
You can also generate users with 0TCA_DS05. To do this, specify an existing reference user from which to copy. The newly created users are assigned randomly generated initial passwords that are not transparent. Users can only log on after manually changing the assigned password.
Generating Authorization Names:
Generate explicit (meaningful) authorization names by filling the field for 0TCTAUTH with your desired name. As an alternative, you can also specify numbers to mark characteristic dimensions that belong to the same authorization. If field 0TCTAUTH is empty, technical names are generated according to the pattern RSR_00000012. All entries with the same name (or an empty field) are assigned the same authorization.
If a technical name with eight digits (RSR_nnnnnnnn) was created for an authorization and then generated again, the existing names are deleted and new technical names are generated. As a result, the previous authorization is deleted and replaced with the new authorization. This new authorization might not be identical to the old one. You can prevent unintended overwriting by using a number range. There is an overflow after 100,000,000 generated authorizations and numbering starts with 1 again.
Deletion of Authorizations and Regeneration
For users for which data exists in the DataStore object that has to be regenerated, first the existing, generated authorizations are deleted. Afterwards, authorizations are generated using the data in the DataStore objects in the usual way.
If a data record with the user name 'D_E_L_E_T_E' is loaded into the DataStore object 0TCA_DS01, first the generated authorizations for all users in the BI system for the DataStore object record are deleted (separated by the first part of the name before the digits) and then generated for the rest of the data.
Log for Generation
A detailed log is created during generation that documents the generation steps and that is displayed automatically. Old logs can be viewed from the transaction RSECADMIN under the Analysis tab page ®   Generation Logs or at the start of the report RSEC_GENERATE_AUTHORIZATIONS by clicking on the log symbol.

Need to create report query to get latest open and last closed period for given application

Hi All,
I need to create a report query to get below result displayed in report output.
1)   -   Application name
2)   -    Ledger name
-o/ -Operating Unit
3)   - Last Closed Period
4)   - Current Open Period
5)   - Date Closed – Last Closed Period
6)   - Date Open – Current Open Period
I tr I tried to create the query below is the same. Please let me know if it looks fine.
SELECT *
FROM (SELECT fav.application_name ,
               hou.name Operating_Unit_Name,
               gl.name Ledger_name,
               gl.latest_opened_period_name,
               gps.period_name Period_Name,
               DECODE(gps.closing_status, 'O', 'Open', 'C', 'Closed') status,
               gps.last_update_date Last_status_modified_date
          FROM gl_period_statuses gps,
               gl_sets_of_books   gsob,
               fnd_application_vl fav,
               hr_operating_units hou,
               gl_ledgers         gl
         WHERE gps.period_name = gps.period_name
           AND gps.closing_status ='C'
           AND fav.application_short_name =
               NVL('&p_application_short_name', fav.application_short_name)
           AND gps.application_id = fav.application_id
           AND gsob.set_of_books_id = gps.set_of_books_id
           AND hou.set_of_books_id = gps.set_of_books_id
           AND gl.ledger_id = gsob.set_of_books_id
           AND hou.organization_id=NVL('&p_operating_unit',hou.organization_id)
           AND gl.ledger_id=NVL('&p_ledger_id',gl.ledger_id)
         ORDER BY gps.last_update_date desc )WHERE ROWNUM = 1
UNION ALL
SELECT *
FROM (SELECT fav.application_name Application_Name,
               hou.name Operating_Unit_Name,
               gl.name Ledger_name,
               gl.latest_opened_period_name,
               gps.period_name Period_Name,
               DECODE(gps.closing_status, 'O', 'Open', 'C', 'Closed') status,
               gps.last_update_date Last_status_modified_date
          FROM gl_period_statuses gps,
               gl_sets_of_books   gsob,
               fnd_application_vl fav,
               hr_operating_units hou,
               gl_ledgers         gl
         WHERE gps.period_name = gps.period_name
           AND gps.closing_status = 'O'
           AND fav.application_short_name =
               NVL('&p_application_short_name', fav.application_short_name)
           AND gps.application_id = fav.application_id
           AND gsob.set_of_books_id = gps.set_of_books_id
           AND hou.set_of_books_id = gps.set_of_books_id
           AND gl.ledger_id = gsob.set_of_books_id
           AND hou.organization_id=NVL('&p_operating_unit',hou.organization_id)
           AND gl.ledger_id=NVL('&p_ledger_id',gl.ledger_id)
         ORDER BY gps.last_update_date desc)
         WHERE ROWNUM = 1

It is within the table I believe (I'm not a DBA or a developer) since I created a BLOB column and then used the file browse feature to allow users to attach a resume to the table in order to be able to perform a search of the attached documents.
I'm just having a hard time pointing the link in the search results report to the document in the blob column.
The information on that page is great if you're trying to create a link to the document on the initial report.
But I created a query using Oracle Text to run a report that does a boolean search of the attached word documents in the table.
When it displays the search results, it doesn't create a link to the document and I can't figure out how to do it.
Here's a link the the instructions I used to create the initial search report with Oracle Text, mind you I only created the index and query, I didn't add in all the link data since they're using documents on websites and I'm using documents in a table.
http://www.oracle.com/technology/products/database/application_express/pdf/apex_text_application_v1.6.pdf
If you can help me with this I'd really appreciate it.
Thanks again.
Greg
Edited by: gjones77 on Dec 2, 2008 8:14 AM

Effects of reopening closed periods in Asset Accounting.

Hi SAP Gurus,
My client wants to open the closed periods in Asset accounting. I have used T Code OAAQ and changed the last closed period.
I would like to know what are the effects of opening the closed periods.
Will it effect the already posted depriciation and what further steps should I take after the entries are passed.
Even after I opened the period both in FI and AA it still is giving me a message that I cannot post to this year.
Can you kindly suggest.
Thanks in advance,
Hari

If you post any entries to the asset , the depreciation will change in asset accounting and will not match with the general ledger unless depreciation posting run is executed.
However, since you have already executed depreciation posting, AFAB selecting repeat run in the last period or special period if your company code have special periods.
Caution: It will change the P&L and Balance sheet balances.
Please check the Post Capitalization Option (ABNAN) for asset values missed in the past for capitalization

Opening/closing periods in DEV - good procedure

What's the best way to deal with opening or closing periods in a DEV system? This is a sandpit client in DEV that is normally closed to changes. Should I unlock the client and have the change trigger the creation of a transport, or not bother about forcing the creation of a transport, as it's not going anywhere?

Hey,
It is surprising that your Dev system is closed to changes. So how do you usually use it if you were to test your development prior to moving it to Q. Do you use the Original dev and copy the Transports to the sandpit?
Regardless.. based on your information.. have your Sandpit client unlocked...Unless there is a wierd but valid reason why it has been locked.. BASIS acts strange at times. CTS should be disabled as well. however it should not pose any issues if the transports hang around.. moroever you would not need to log your changes as they serve the purpose. Hope this helps

Open an already closed period

Is it possible to open an already closed posting period? If yes, how? And is it recommended to open any closed period?
Thanks in Advance

Hello,
There are two different places where the period is closed in SAP.
a. FI period
Use transaction OB52.
b. MM period - MMPI
The help extract for the same is given below for your reference:
Short text
Initialize Period for Material Master Records
Description
This program must be viewed in conjunction with the period closing program (RMMMPERI). It does the following:
Sets the current period
However, do not use this program to set the new period at the end of a period, and use it only in addition to the period closing program, never instead of it.
Creates or updates the control record
Makes it possible to create material master records if you are initializing a company code for the first time
However, to initialize company codes, you are recommended using the IMG activity Maintain company codes for materials management instead of this program.
You can also use this program to correct data inconsistencies, for example, due to user errors when running the period closing program, or that occur as a result of skipping several periods in a test system. However, first make sure you understand why the inconsistency arose and then decide whether running this program is the correct way of resolving it.
Caution
Be careful if the period used for initialization precedes the current period in the control record for the company code since this can result in an inconsistency between goods movements and material master segments. This is because the stock information in the material master segments is assigned to the new current period in this case (see the following example).
Example
Current period 02
Opening stock balance 0 pieces
Goods receipt 10 pieces
Period used for initialization 01
According to the material master segment, there are 10 pieces in stock in period 01, although 10 pieces were posted to stock in period 02 according to the goods movement document.

Closing Period Authorization Change Non GL Documents

Similar Messages

Maybe you are looking for