Prior Posting Period Sales Value

Hi ,
I got one requirement, I need to get the Prior period Sales value for some other calculations.
Eg:
    Period       Sales
      1           10
      2           20
      3           30
      4           40
Here i need to capture the value 30 based on the period 3.
CurrnetSales=40
PriorSales = 30
How to get the prior sales.
Thanks,
Kiran

Hi Kiran,
You can use a variable on Fiscal period to get the current period in one column and in column 2 use the same and set an offset of -1.
Hope this helps...

Similar Messages

Error that "specify a value for variable posting period (single value entry

hi
My query is running testing fine in RSECADMIN under some username..but when i try and open it using analyzer (under same username) it gives me error that "specify a value for variable posting period (single value entry, mandatry)" it does'nt even asks to enter variable values and gives this error message.
However the same query appears to be working fine under different username.
plz advise.

Hi Abhinav,
Just do one thing compare the Roles of two different users for which Query is getting executed and not.
Check the Object S_RFC.
Compare the Objects detail for Both the Users.
Please Assign points if useful.
Regards,
Rajdeep.

Error while running a query-Input for variable 'Posting Period is invalid

Hi All,
NOTE: This error is only cropping up when I input 12 in the posting period variable selection. If I put in any other value from 1-11 I am not getting any errors. Any ideas why this might be happening?
I am getting the following error when I try and run a query - "Input for variable 'Posting Period (Single entry, mandatory)' is invalid" - On further clicking on this error the message displayed is as follows -
Diagnosis
Variable Posting Period (Single Value Entry, Mandatory) is used as a lower limit (X) and an upper limit () in an interval selection. This limit has the value #.
System Response
Procedure
Enter a different value for variable Posting Period (Single Value Entry, Mandatory). If the value of the other limit is determined by another variable, you can change its value also.
Procedure for System Administration

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

Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan

2 Sales order types to post to 2 value fields

Hi,
Previously, 2 sales order types ZSA4-samples med. & ZSA5-samples adv. posts to one value field which is VV310 Local mktg mgt. Business users now requires these sales order types to post to 2 new separate value fields.
So, in Controlling I assigned condition types Z231 VAT Expense & Z232 VAT Exp/Sample FOC to value fields VV230 & VV201 respectively.
The SD consultant then changed the ZTHV07 pricing procedure to include these 2 condition types by creating 2 new steps and assigning them to routines 914 & 915. I am not sure if I should change these routines.
ZSA5 sales order type is posting correctly to value field VV201 but ZSA4 is also posting to VV201. It should post to VV230.
Thanks to advise if there's any setting whether in SD or CO I should change.
P.S.
The following are the other configurations inside the system:
ZSA4 & ZSA5 sales order types are assigned to D (Sample) document pricing procedure.
Pricing procedure ZTHV07 is assigned to document pricing procedure D.
Thanks and regards,
Thess

Let us understand more on your requirement.
For doc.type ZSA4, you want to have only condition type Z231. And for doc type ZSA5, you want to have only condition type Z232. Therefore, each document type will post to COPA to correct value field.
Well, then if that's the case, I would say your requirement number 914, 915 doesn't work (it's definitely on SD side). They are developed based on your requirements so I cannot comment since it is not standard routine.

Fund Managment: Posting period not opened for value type 66

Hi,
I have already opened all the posting periods FM thru' TC: FMIR from period 0 to 16 for all account assignments.
While posting through thru' a customised program (i.e customised program is using FB01) I am getting error 'Period 002/fiscal year 2010 not open for FM posting in value type 66', please let me know why this error inspite of opening all the periods and for all account assignment.
Thanks,
Suresh

hi suresh,
Check this link
FMIR - For fiscal yr based encumbrance, the whole fiscal will be open
Hope it will resolve your question.
Thanks and regards
Praveen.J

Strange error in MIRO if sales invoice is priorly posted.

Hello,
Our scenario is, we create a Sale Order which creates a auto PR then with reference to this PR we are creating a PO then GR of this PO.
Then, outbound delivery & then invoice which released to accounting. Then MIRO with reference to PO
If we post the sales invoice & release for accounting & then if we do the MIRO for the PO then we're getting below error:-
No account is specified in item 0000500002
Message no. F5670
Diagnosis
No account was specified for account type "S" in item "0000500002" of the FI/CO document.
System Response
The Financial Accounting program cannot process the document.
Procedure
A system error has probably occurred in the application you called up. Check the data transferred to item "0000500002" of the FI/CO document.
And if we cancel the sales invoice then above error is not coming & we're able to post the IR against PO in MIRO.
So, is there any relation or link between sales invoice posting & IR via MIRO?
We have invoice receipts in MIRO in last month which were successfully posted without any error even if we had posted sales invoice before it.
Any idea about this error to get it fixed?

Hello Ravi,
Please check if the Cost condition is relevant for accruals in your scenario. If there is an update of the costs in a 3rd party process, there is no new account determination but the system use again the already determined accounts for the update posting. Please check if the Invoice posted on SD side has this accrual account posted.
Regards,
Raghavendra

How to re-issue a disputed billing doc when mat posting period is closed

I'm working a client site that has to deal with disputed invoices that come in after the material posting period has been closed.
What needs to happen is that the billing document is cancelled (no problem) and this returns the stock (fuel put back in the tank).
Howeve, the problem is we do not know the best way to re-issue the billing document so that the posting date is against the original date which is often outside the current of previous month's posting period.
Is it practical to open the period prior to last month again? We suspect that this may cause more issues than it solves. What tis the industry standard process for dealing with such disputes?
Thanks for your suggestions
Phil

Hi,
It is not good to open the period again, as you are in current period.
The best business practise is to raise an return order request against the billing docuement followed by credit memo to give the credit to customer. The return delivery also will be created against return order as you need to return the suplied goods.
The sales docuement type 'RE' is used for sales return in standard SAP, followed by delivery docuement type 'RE' and billing type 'RE' (Credit Memo).
regards
Vivek.

Error determining posting period(info structureS008,variant ,RC 3)" addin

Hello,
I am having one issue with my current project.The issue is
Error determining posting period (info structure S008, variant XX, RC 3)" error when trying to add material 10000 on line item 11 onto the existing order.
The actual issue is our user by mistake entered date in Sales Order with Header material in Billing plan tab-->Billing date entered as 31.12.1950 for milestone billing.Now when i am in change mode it is displaying as current date ,but where as in display mode ,it is diaplaying as 31.12.1950.Table also showing the same as display value only.The correspond table is FPLT-AFDAT
Now user wants to add one more lineitem to this header material.It is preventing and throwing error like above.
We are in ECC5.0.
Kindly help me out how we can change the date field to current date ?
Thanks&Regards
SaiDev

Hi Hemant,
Thanks for update.My issue is with Infostructure S008.Related sales order billing plan date,which prevents to delete or further processing .The table FPLY-AFDAT-is having value of 31.12.1950.This needs to corrected to current date This is by mistakenly entered by user.
The note refer different infostructure.
We are ECC5.0.
Thanks&Regards
SaiDev

Close MM Posting Period

Dear Gurus,
What is the procedure to Close Prior MM Posting Period.Pls help me in method
Thanks
Abhinav Royal

Abhyut,
The t code for closing the period is MMPV.
Give input for 'From compny code', 'To company code', Period (Next period), Fiscal year, & also you have option of giving the input for date too.
Select 'Check & close period' . Also you have options of 'Allow Negative Quantities in Previous Period' & 'Allow Negative Values in Previous Period'
Execute.
The priod opening (next) & closing (previous) will be done.
The result you can check in MMRV.
Hope this helps you.
SmanS

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

FG Valuation basis - Std Cost estimate or Net sale value whichever is less

Dear SAP Experts,
Query 1 -
Valuation of Finished goods is done on basis of standard cost estimate (CK24) or Net sale value whichever is less
*Net sale value u2013 Net sales ( Sales value minus Sales deductions)
Eg : Std cost estimate gives FG price as $100, whereas Net sale value price of FG $80,
      now the client wants FG values should be at $80
Is there any standard way, wherein SAP can capture whichever is less i.e standard cost estimate vs Net Sale Value
Pl let us know the options and which options would be ideal for query 1
Query 2 u2013 Can we use CRK1 and MR21 to manually change FG price whenever Net sale value is less than std cost estmate price?
u2022     In case the market value is less than the std cost estimate (CK11n) ,then Is this the approach to manually value FG price using CRK1 & MR21.
u2022     What could be the impacts if we follow this approach
For Eg: Impact on prev months WIP, Scrap, stock returns etc
u2022     We simulated CRK1 & MR21 and MR21 entries are posted successfully, however following below warning is the message is showed when CRK1 is executed
             Note u2013 Material Ledger is not active
Warning Message
Deleting current standard cost estimates can cause inconsistencies. Your comments please
Message no. CK669
Diagnosis
u2022     If you delete a current standard cost estimate, the fields for the cost estimate are set to zero in the material master record. If you use the material ledger, the standard prices in the material ledger master data are also deleted when you delete the current standard cost estimate. The material master record for the material thus does no longer contains a current standard price from a standard cost estimate.
u2022     If you delete an active standard cost estimate, you can no longer determine scrap, work in process and variations for previous periods.
u2022     In certain countries, it is a legal requirement to maintain records of standard pricing. Therefore, you should check whether you are obliged by law to keep records of your standard cost estimates. Please also contact the relevant accounting and inventory management departments.

Dear,
Query 1;
The FG or SFG will be valuated at Standard Cost there is no provision to enter Net sale value
Query 2:
Do not user CKR1 to delete Cost Estimate because it can bring lot of Descripenceies in CO, SAP do not recommend the same.
You can run the revaluation at the month end or revise your activity rates so that you standard price will be change accordingly and your inventory will be re valuated.
Hope it is clear, it not then please revert.
Br,Vivek

Open and close Posting Periods. Different societies.

Hi all.
We have 2 societies 0001 and 0002.
In transaction S_ALR_87003642 or OB52 I want that user of society 0001 only can see posting periods of his society ( 0001 ) and the same with society 0002 users.
How I can do this ???
thanks a lot.
Ismael

Hi,
This requires bit of ABAP help.
WE have achieved this scenario successfully based on the information provided below -(found the source on the internet!)
Goto SE11 copy the view V_T001B to ZV_T001B_000X (000X indicate the Posting Variant)
In Change mode, tabstrips Selection Conditions Insert line 2 with
Table     Field Name   Operator   Comparative Value    AND/OR
T001B   BUKRS           EQ            '000X'                          AND
Save your entries
Third Step :-
Goto SE54, Options Generated Objects -> Create
Authorizations Group FC31
Function Group          Z00F0
Maintenance Type     One Type
Overview Screen       65
Single Screen             0
Final Step :-
Goto SE93, Create a new transaction code ZOB52_000X
Start object - Transaction with parameters (parameter transaction)
Transaction SM30, Tick Skip initial screen
Name of screen field       Value
VIEWNAME                     ZV_T001B_000X
UPDATE                           X
Save your entries.
Now have the ABAPer to have company code on the selection screen. Based on user selection, invoke the corresponding neww transaction code ZOB52_000X which will only display the
Posting Variant that you have define in your table view.
Hope this solves your problem.
Regards,
Sridevi

Open and close posting period authorization control TCODE: S_ALR_87003642

HI All,
Is there any chance to control the user to open and close another company code posting period variant in TCODE: S_ALR_87003642.
In our system we are using the same client for different countries. So user can able to change the other country company code posting periods.
We would like to control either on the country (or) organizational unit(company code) (or) posting period variant so that user can only open/close their country / company code posting periods.
Our present authorization role for open and close posting period contain the auth.Obj. : S_TABU_DIS.
Please share your knowledge if you come across this problem..
Thanks in advance..

Hey Sandhya,
Congratz, this can be done using linbe item authorization with the object S_TABU_LIN.
Field ORG_CRIT - Value 02
Field ORG_FIeld1 - Value ZT001B
We have successfully done it in our client.
You need to contact your BASIS consultant for this.
Thanks,
Nitish

Error while posting a sales order created with reference from contract for

Hi,
I am posting a sales document( Type: WA) created with reference from contract document( type wk2) for delivery. The item category in the sales order of the Item is WAN. On posting this document for delivery I am getting the error as "Item category WAN is not defined". Please help me out how to resolve this issue.
Thanks
Jayant

Hi Jayant,
I think its value contract releated error,
You suppose to check material item category group through T.code-MM02 into sales2 tab and maintain VCIT,
and do item category assignment through T.code- VOV4.
plz.maintain like that,
WK2 -          -VCIT-         -           - WAN(contract item category),
wk2 -          -        -VCTR-          - WAN((contract item category),
you should also maintain same against your standard Sales Document type and for Standard Item category into VOV4,
WA(standard docu.type) -VCIT-                             -                -TAN(your standard docu.type item category),
WA(standard docu.type) -         -VCTR(item usage)-              -TAN(your standard docu.type item category),

Prior Posting Period Sales Value

Similar Messages

Maybe you are looking for