Fiscal Year Variant for non calendar year

Dear Experts,
The fiscal year for my client is as follows:
     Start Date     -
     End Date
Month 1     -
     21-Mar     -
     20-Apr
Month 2     -
     21-Apr     -
     21-May
Month 3     -
     22-May     -
     21-Jun
Month 4     -
     22-Jun     -
     22-Jul
Month 5     -
     23-Jul     -
     22-Aug
Month 6     -
     23-Aug     -
     22-Sep
Month 7     -
     23-Sep     -
     22-Oct
Month 8     -
     23-Oct     -
     21-Nov
Month 9     -
     22-Nov     -
     21-Dec
Month 10     -
     22-Dec     -
     20-Jan
Month 11     -
     21-Jan     -
     19-Feb
Month 12     -
     20-Feb     -
     20-Mar
Accordingly i have created a fiscal year variant with following details:
Month     -
     Date     -
     Period     -
     Year Shift
4     -
     20     -
     1     -
     0
5     -
     21     -
     2     -
     0
6     -
     21     -
     3     -
     0
7     -
     22     -
     4     -
     0
8     -
     22     -
     5     -
     0
9     -
     22     -
     6     -
     0
10     -
     22     -
     7     -
     0
11     -
     21     -
     8     -
     0
12     -
     21     -
     9     -
     0
1     -
     31     -
     10     -
     -1
1     -
     20     -
     10     -
     -1
2     -
     21     -
     11     -
     -1
3     -
     20     -
     12     -
     -1
But when i try to save the above periods for the variant it gives an error as
"Financial year variant periods T1 incomplete (31.12 missing)".
Can you help me know where am I going wrong in this?
Regards
Amar
Edited by: Z_Amarendra on Dec 7, 2009 9:52 AM

Dear Experts,
Solved the problem myself. Thank you
Regards
Amar

Similar Messages

  • How to create a running total formula for different calendar years

    Hello everyone,
    I am looking for some help in creating a running total formula for different calendar years in Oracle. This is what I currently have organized in the crosstab report: vertically I have the cities from our database organized, then horizontially have the following information for each city:
    2006 /2007 /2008
    Amount /Amount Spent /Unspent Amount Amount Recieved/Amount Spent /Unspent Amount Amount Recieved/Amount Spent/Unspent Amount
    Recieved
    I am trying to create a formula that will specify each calendar year. For example, I'd like to have a formula in 2007 which would total the: 2007= {2006 unspent amount + the unspent amount in 2007} and same for 2008= {2007 unspent amount + the unspent amount in 2008}. I hope this is clear, I have simplified the report into a basic interpretation of what i've been trying to accomplish.
    Would anybody know if this is possible and how to approach this?
    Really appreciate it! Thanks.
    Alex

    Hi,
    you can try and define a running total as a calculation in the crosstab as:
    sum(Unspent Amount) over (partition by city order by year)
    i find the crosstab format comfusing sometime since the aggregation is auto applied.
    I would start with a flat table and then "duplicate is as a cross tab"
    for your running total you can sort the data by the city,year and get it to 3 lines for each city, for example:
    city year Unspent Amount all other amount...
    X 2007 10
    X 2008 20
    X 2009 30
    Y 2007 5
    Y 2008 15
    Y 2009 25
    then you can use a funtion to calculate the amount :
    sum(Unspent Amount) over (partition by city order by year)
    this is the sql i used just to check it:
    SELECT city,year,"Unspent Amount"
    ,SUM("Unspent Amount") over (PARTITION BY city ORDER BY YEAR)
    FROM (
    SELECT 'X' city, 2007 YEAR, 10 "Unspent Amount" FROM dual UNION ALL
    SELECT 'X', 2008 ,20 FROM dual UNION ALL
    SELECT 'X', 2009 , 30 FROM dual UNION ALL
    SELECT 'Y', 2007 , 5 FROM dual UNION ALL
    SELECT 'Y', 2008 , 15 FROM dual UNION ALL
    SELECT 'Y', 2009 , 25 FROM dual
    Tamir

  • APO-DP : Change in Fiscal Year Variant for the year 2008

    As per earlier Fiscal Year variant configuration, the data has been forecasted in APO system till the end of Year 2008. But recently the fiscal year variant configuration modified in R/3 which has been impacting APO-DP storage buckets which are not matching with that of earlier fiscal year variant. So, there is a mismatch in the storage bucket profile where in the data already stored in “Weekly, Monthly and Posting Period” based on the earlier Fiscal year 2008 configuration.
    Now the system is not allowing to do any Interactive Planning.
    The business would like to use the latest fiscal calendar and also not ready to loose the forecasted data for the year 2008. So, we are not in a position to deactivate and reactivation of Planning Area and also we are not using back-up infocubes functionality.
    Please update me if anybody experienced this type of situation or know the solution.

    I think your suggestion should work but it takes more resource time and need more database size.
    I am thinking to retain some important forecast keyfigures data in the following workaround method;
    1) Now the Planning Area Initialized for 2yrs historical + 1Yr forecast horizon
    2) Run first set of new macros to copy from year (say 2008) to year (say 2006)
    3) Re-initialize the Planning Area (Jan'2006 to Dec'2007)
    4) Re-build the New Fiscal Calendar from R/3
    5) Re-initialize the Planning Area for history and forecast horizon (ex: from Jan'2006 to Jan'2009)
    6) Run second set of new macros to copy back ( ex: from 2006 to Year 2008) and wipeout the duplicate records in 2006
    7) The above macros can be utilized to run every year end when ever the new fiscal calendar introduced
    Suggestions are welcome

  • GL Account determination for new calendar year

    I notice in the SAP database that the GL account determination for 2010 has the accounts filled in as they came over from 2009, however in some of our clients's databases we had to manual enter them. Is there some setup we missed?

    You may check this thread first:
    Re: Newly Entered Posting Date - System Message in 2007
    Thanks,
    Gordon

  • Fiscal year variant AM is not maintained for calendar year 2008

    Hi All,
    I want to have a different fiscal year variant for asset accounting do to the company go live will be at the third quarter of the year we want to use a shortened fiscal year variant.
    I've already create a fiscal year variant called 'AM' for year 2008 and it is a shortened year-depent variant. Next step is to assign this year variant to the company code in this customizing path
    spro>Financial Accounting>Asset Accounting>Valuation>Fiscal Year>Fiscal Year Variants>Specify other versions on company code level
    When I try to set this and press save button this message is displayed
    "Fiscal year variant AM is not maintained for calendar year 2008"
    Do you know why is displayed this message? Am I missing any customizing step?.
    Many thanks.

    Hi Suresh Upadhyayula ,
    In fact it appears in the proposed value when I press F4. When I press save button this message appears.
    I mean that in this path
    IMG>Financial Accounting>Asset Accounting>Valuation>Fiscal Year>Fiscal Year Variants>Specify other versions on company code level
    You can assign a diferent fiscal year variant to the company code at AA level keeping the one that you have in global paramenters at GL level. We are cosidering this solution due to we want to depreciate the assets in a shortened fiscal year variant at AA level.
    Many thanks.

  • Use of different fiscal year variant in leading&non leading ledgers and Asset closing&Reporting

    Experts,
    Need one clarification on using different fiscal year variants for Leading(0L)&non Leading(NL) Ledgers and impact on Fixed Asset Accounting.If I use say V6(Jan2013-Dec2013) for Leading Ledger and April2013-March2014 for non leading Ledger,(local GAAP)-please clarify the following.
    1.Does Asset Accounting gives all standard reports as expected in both(Leading&Locals) the Depreciation areas?Do we need to any settings specially for in the above scenario?(I am assuming point#4 given below may not help for this as system gives an error if both the fiscal year variants have different start&end dates)
    2.How is Year end in Asset Accounting handled?If I close the year end in Asset Accounting for Company Code as per Leading Ledger i.e say by Dec 2013,can I still post the asset entries in non leading ledger?Because Financial year for Leading ledger will be 2014 and non leading will be still 2013(in Jan2014).
    3.I am aware SAP has some restrictions way back in 2005-2007 (SAP note 844029) for different fiscal year variants in Leading&Non Leading Ledgers,Does SAP come out with any solution later?
    4.What is the exact use of the settings at  Asset Accounting>>Valuation>>>Fiscal year>>Fiscal year variants  at company code level or Depreciation area level?My understanding here is,they are not meant for using different fiscal year variant with different start&end dates but they are meant for using different fiscal year variant with same START&END DATES  and have different number of posting periods i.e 1 can have 12 and other can have 13.
    Please can you give your comments?
    regards
    hinfi

    Hi Hinfi,
    It seems standard SAP does not manage different fiscal year variants (at least with different start/end dates) in different depreciation areas.
    However, they came up with an add-on solution called Multiple Calendar Tool and based on a mirroring solution that synchronizes asset transactions in a mirror company code.
    It's all explained in following notes:
    Note 1175751 - Project solution for alternative fiscal year variant
    Note 1636025 - Asset acctg multi calendar tool 1.0_ SP Note
    Note 1658489 - Installation of Asset acctg multi calendar 1.0 software
    Note 1658714 - Asset acctg multi calendar tool_ Overview Note
    Note 1691481 - Release strategy_ Asset acctg multi calendar tool
    Note 1951069 - Different fiscal year variants in General Ledger Accounting (New) (NewGL) under the new Asset Accounting (FIN_AA_PARALLEL_VAL)
    I don't know if it's commonly used and personnaly have no feedback on it. I was curious to check how to manage a depreciation area 01 posted in a leading ledger in US GAAP (FYV january to december) and another depreciation posted in a non leading ledger in Indian GAAP (FYV april to march).
    BR
    Gregory

  • Calendar assignment in OAVH for '03' period control for calendar year dependent fiscal year.

    Hi
    We have a year dependent Fiscal Year in our client's system. It is a 5-4-4 Fiscal Year variant starting from March till Feb.
    While trying to create a new asset we faced an error "You cannot save this asset(Correct depreciation error)." I checked and found that the error is due to a missing calendar assignment in OAVH for the period control key '03' (Pro rata at mid-period) for our fiscal year variant. Till the last fiscal year it had been maintained, but for current fiscal year the assignment is not maintained.
    Can someone help me to understand how the calendar assignment is done in OAVH for a 03 period control key for a year dependent fiscal year like ours?
    I tried using the transaction OA84 (Generate Period Control), but it provides the calendar assignment for all other period control methods except for '03'. Is there some specific reason as to why OA84 does not generate for '03' period control?
    I checked the last fiscal year's assignments in OAVH for our fiscal year variant for '03' period control, but could not understand how it was configured, because it did not relate to the fiscal year variant assignment that we have done in OB29. Also, I even checked whether we need to enter the mid date of the periods, but that also was not done for the last fiscal year. I am unable to understand how the dates have been assgined.
    Given below is our last Fiscal Year's OAVH settings for '03' period control:
    FYV
    Period Cont
    Description
    Year
    Month
    Day
    Period
    AG
    3
    Pro rata at mid-period
    2014
    3
    17
    0
    AG
    3
    Pro rata at mid-period
    2014
    4
    18
    1
    AG
    3
    Pro rata at mid-period
    2014
    5
    16
    2
    AG
    3
    Pro rata at mid-period
    2014
    6
    16
    3
    AG
    3
    Pro rata at mid-period
    2014
    7
    18
    4
    AG
    3
    Pro rata at mid-period
    2014
    8
    15
    5
    AG
    3
    Pro rata at mid-period
    2014
    9
    15
    6
    AG
    3
    Pro rata at mid-period
    2014
    10
    17
    7
    AG
    3
    Pro rata at mid-period
    2014
    11
    14
    8
    AG
    3
    Pro rata at mid-period
    2014
    12
    15
    9
    AG
    3
    Pro rata at mid-period
    2014
    12
    31
    10
    AG
    3
    Pro rata at mid-period
    2015
    2
    13
    11
    AG
    3
    Pro rata at mid-period
    2015
    2
    28
    12
    Please advice.
    Thanks in Advance.
    Regards
    Ambarish

    Dear Ambarish,
    As it is a year dependent fiscal year variant, we should create the year for the variant via OB29, then generate the period via OA84.
    Best regards.
    Beam

  • Error: "posting period is not defined for fiscal year variant" in  FBICS3

    Hi,
    I got error  "posting period is not defined for fiscal year variant" when I execute t code FBICS3.
    I checked in OB29 &  t code FBIC010 & noted that the fiscal year variant had ben maintained.
    Please advice.

    HI,
    It was noted that the mentioned t code had been maintain but below mentioned error appear:
    Posting period  is not defined for fiscal year variant
    Message no. GU506
    Diagnosis
    You have tried to determine a posting date in fiscal year variant for period , fiscal year , but this period is not defined for the variant.
    Procedure
    You maintain fiscal year variants in table T009.
    It was referring to t code OB29. I have checked the detail, in OB29 also details maintain.
    Please advice why the error still prompt.

  • Multiple Fiscal Year Variant in the same client in SEM-BCS...

    I have already looked at some earlier threads relating to this but didn't get a convincing answer to what I would like to know.
    We have had a working SEM-BCS system with fiscal year variant K4. There was no need for defining leading fiscal year variant and none was defined. SAP, by default takes, K4 as the leading fiscal year variant.
    Now there is a requirement for going on a different fiscal year variant for which we have created another databasis (there were a few other reasons besides these) with the same InfoObjects that we used earlier but with different fixed parameters, one of which is fisc year variant V9. Soon, we started experiencing bizarre dumps in the configuration which ultimately convinced me to define a leading fiscal year variant. I was reluctant to do so because there is a lot of old data (which will become 'historical' from new data basis point of view) from the working system on K4 that would still need to be reported on even when we have new BCS solution in the new fiscal year variant V9. That is not going away. There is a need to keep the old data for reporting (hence the rationale for a different data basis among a few others).
    Since earlier Master Data was configured in the old fisc year variant K4, now I have defined the leading fiscal year variant as V9 so that MDF can appropriately identify the period dependency.
    I would like to know if any of you have had an unexpected behavior from the system going forward. Does the system dump out when you try to read the old data (from earlier K4).
    I have tried to explain the dilemma as clearly and succinctly as possible but if you need more clarifications, please do let me know.
    I would really appreciate your help in this.

    Is your requirement is that K4 to be changed to Z5.
    The best way you can do it is in the transformation. Instead of directmapping,
    Write a code like this in the trransformation to the cube
    If SOURCE FIELD - 0FISCVAR eq 'k4'.
    SOURCE FIELD - 0FISCVAR = 'Z5'.
    I dont think we can change th data in the query being displayed. we can change the keyfigure values in query by frmulas etc...
    but for a characteristic, i think we will be able to restrict bt not change the value.
    to obtain the requirement, w have to get the data change before query designer that is in the cube leve.
    Hope this helps,
    Sri...

  • Fiscal Year Variant (OB29)

    I am trying to copy over a fiscal year variant's periods from one year, to the next. However, I am running into the error "Financial year variant periods MI are not in increasing order". This exact setup of periods is saved in prior years, but it will not let me save it in the current year. Any suggestions? (T-Code OB29)
    Month     Day     Period     Year Shift
    1             3          3             0
    1             31        4             0
    2             28        5             0
    4             4          6             0
    5             2          7             0
    5             30        8             0
    7             4          9             0
    8             1          10           0
    8             29        11           0
    9             30        12           0
    10           1          1             -1
    11           29        2             -1
    12           31        3             -1

    Try pasting the below data
    If the fiscal is Jan - Dec ie calendar year, just create the fincal year variant and select the option Calendar year in the third column.
    If the fisacl year is Apr - March
    Month     Days     Period     Year Shift
    4     30     1     0
    5     31     2     0
    6     30     3     0
    7     31     4     0
    8     31     5     0
    9     30     6     0
    10     31     7     0
    11     30     8     0
    12     31     9     0
    01     31     10     -1
    02     28     11     -1
    03     31     12     -1
    If the fiscal is for calendar year, just create the fincal year varient and select the option Calendar year in the third column.
    It is always better to copy standard (V3 for apr-march or K4 for Jan-Dec)
    Edited by: JithuMat on Dec 1, 2011 2:20 PM

  • What is the difference between Fiscal year variant, Fiscal year and Calyear

    hi,,
    What is the difference between
    1. Fiscal Year Variant (0FISCVARNT)
    2. Fiscal Year (0FISCYEAR)
    3. Calendar Year (0CALYEAR)
    In what scenarios they should be used. If we are getting 0FISCVARNT data from ODS. Can we change into other in cube at update rules level or some other level?
    How can we get factory calendar????
    Message was edited by:
            Avneet M

    Hi Gurus
    I was going through this thread and came up some more questions in my mind.
    1. Do we need to set Fiscal Year, Fiscal Varient settings once for all in BW ? ( The path is given in one of the thread above ) need to know if this is one time setting / rebuilding the tables. what will happen when we select and execute factory calender and Fiscal Varient and Rebuild tables in transfer global setting ? Is this one time we have to do for whole BW system?
    2. when we go to SCAL t-code what we need to do and what it do in the system ? I know its for Factory calender but just want to know what it does. It it also for one time during BW build phase ?
    3. How can we link Factory calender and Fiscal year? IS it thro Fiscal varient ?
    Pl help me to clear this doubt,thanks in advance.

  • Use of Different Fiscal Year Variant-Statistical Depreciation Area Postings

    An existing Company Code in SAP is going to have Fixed Assets implemented.  This Company Code is setup just like the others in our SAP instance: Same Chart of Accounts, Same Fiscal Year Variant, Fixed Asset procedures, etc.  For purposes of this question our company's Fiscal Year is from August 1st to July 31st.  In addition, this Company Code will post Fixed Assets just like the other SAP enabled Company Codes into Book Depreciation Area 01.  The company I work with is on ECC 6 but we use the Classic Ledger for Financials, and the Special Ledger is posted to but not really utilized.
    For the Country Specific/Tax Reporting purposes within Fixed Asset Accounting we have created a Statistical Depreciation Area 03 (I will call it Tax) with its own Life and Depreciation Key assignments with a setting of 0 in OADB-No Posting in GL for this Fixed Asset go-live, so I think we are set there.  The tricky part comes in the reporting.  The country in question requires information to be generated on a Calendar Year basis, which is obviously different than the Fiscal Year outlined above.  To my knowledge we would have to assign Tax Depreciation Area 03 to the Calendar Fiscal Year Variant: Financial Accounting>>Asset Accounting>>Valuation>>Fiscal Year>>Fiscal Year Variants>>Specify Other Versions on Depreciation Area Level. 
    The other piece of this is to get the Fixed Asset Reporting for Tax Depreciation Area 03 to work on a Calendar Year basis for the Company Code in question.  When I did some research I stumbled upon the link below.  In summary it says that you have to manipulate the standard Fixed Assets reports in Excel for Asset Acquisitions and Depreciation, and setup a new Retirement routine/transaction for posting into the Special Depreciation Area.
    http://help.sap.com/saphelp_46c/helpdata/en/05/bc0bf3d8f811d1953e0000e82debf7/content.htm
    My questions are:
    1) Besides assigning a different Fiscal Year Variant for Tax Depreciation Area 03, is there anything else I need to worry about on the setup end?
    2) Is the article I posted accurate when it comes to how the reporting works and the need for setting up a Calendar Year specific Asset Retirement Routine?  If so, what are the configuration steps for setting up a Calendar Year specific Asset Retirement Routine?
    3) Is there anything else that I need to consider for enabling Fixed Assets at an existing Company Code with different Reporting requirements for Book/Tax purposes?
    Thanks in advance for all responses.  I am willing to answer any other questions on this subject if needed.
    Roman

    Hello Rio.  In our scenario, we still had to load assets in the legal entity with this issue.  When we loaded the fixed asset data into SAP we did with data accurate as of December 31, 2011; which for book purposes is 5 months into our company's fiscal year, and for tax purposes is the end of the 2011 calendar year.  The calendarized reporting for the tax depreciation will need to be pieced together manually using the SAP recommended methodology of combining report values, which I have pasted below.
    Since this is the only SAP-enabled entity that has this scenario right now we are in wait and see mode to see if this sufficient.  In the end the SAP path for Dual Calendar was too much of a risk.
    I hope this helps.
    Roman
    Asset Acquisitions 
    Run the acquisitions list. Report date: 7/31/2012. Posting Date: 1/1/2012 to 7/31/2012. Export the report to MS Excel.
    Run the acquisitions list. Report date: 7/31/2013. Posting Date: 8/1/2012 to 12/31/2012. Export the report to MS Excel.
    Add the values of both reports together, using MS Excel.
    Asset Retirements
    Run the retirements list. Report date: 7/31/2012. Posting Date: 1/1/2012 to 7/31/2012. Export the report to MS Excel.
    Run the retirements list. Report date: 7/31/2013. Posting Date: 8/1/2012 to 12/31/2012. Export the report to MS Excel.
    Add the values of both reports together, using MS Excel.
    Depreciation
    Run the depreciation list. Report date: 7/31/2012. Export the report to MS Excel.
    Run the depreciation list. Report date: 12/31/2011. Export the report to MS Excel.
    Run the depreciation list. Report date: 12/31/2012. Export the report to MS Excel.
    Using MS Excel functions, subtract the second report from the first, and then add the third report (I - II + III).

  • Different fiscal year variants

    Our client follows two fiscal year variants. For global reporting purpose they follow a different convention 445. For meeting local reporting requirements at subsidiaries in different countries calendar year Jan to Dec is followed. Both the fiscal year variants will have different start and end dates for any fiscal year. As far as GL reporting is concerned we could achieve this by using new ledger solution.
    I am facing a challenge while configuring these two different fiscal year variants in asset accounting. I am planning to use 445 for my 01 area and I want to create another depreciation area for the calendar year reporting, but I am not able to do it.
    I am getting the below error message
    AC539 :Fiscal year variants in co.code  have inconsistent start date
    Diagnosis
    The first day of the fiscal year for variant K4 in company code in Asset Accounting differs from the first day of the fiscal year for variant SD in General Ledger Accounting.
    However, both variants must have the same start and end date! Only the periods within the fiscal year can be different in the two variants.
    Does any body have come across similar situation and what would be the solution to achieve this ?

    Hello Reuta Kulkarni,
    there is no standard functionality available to cover your requirement. Still, a customer specific project solution for a workaround can be offered by SAP Custom Development. Please note, that such a solution requires detailed analysis of the customer requirements and is chargeable.
    If you are interested you will find details in note 1175751.
    Best regards,
    Andreas

  • Different Company Code with same fiscal year variant and controlling area

    Hi
    I have three company codes in three three different countries: 1000 (ABC India), 2000 (ABC Inc, US), 3000 (ABC Dubai)
    But our consultants have assigned only one fiscal year variant V3 and one controlling area 1000 (with fiscal year variant v3)
    So what problem one may face because of above settings and what is ideal setting for such scenario
    Edited by: Meenu_ND on Oct 18, 2010 2:35 PM

    I have one leading ledger and two non leading ledger (i.e Group ledger and IFRS ledger). But Fiscal year variant is not mentioned for both the non leading ledgers.
    So i think it will take V3 only for non leading ledgers too.
    And in your solution, since India is main company, fiscal year variant for leading ledger needs to be V3 only.
    What if i keep non leading ledger as fiscal year from Jan to Dec. Then it will be:
    Leading Ledger: April to March
    Non leading ledger: Jan to Dec
    In above case, do i need to create separate controlling area ?
    Edited by: Meenu_ND on Oct 19, 2010 10:43 AM

  • Fiscal year variant V3 uFF0Cdo year end closing

    Hello everyone,
    I use the  Fiscal year variant V3(month 4 year *-month 3 year **+1) for the HK company ,and Dec. 2009 I did the year end closing, but I found that,the amount of GL Account balance carry of 2010 is not the cumulative balance of 2009,but just the balance of Dec. 2009;IN fs10n double click the balance carry of 2010, the detail is the cumulative balance of 2009.What can I do the amount of GL Account balance carry of 2010 will right?
    Thank you for your answer.
    Best Regards
    Doris

    Hi,
    You can try carrying forward, GL, customer and vendor balances from the beginning.  There is no impact even if you execute again.
    Best Regards,
    Madhu

Maybe you are looking for

  • How to find out the manditary fields in an IDOC

    Hi, How to find out the manditary fields in an IDOC. For example MATMAS05 . For this 2 segments I want to find out the manditary fields. E1MARA E1MAKTM

  • Apple ProRes QuickTime Decoder will not install

    Hi, I just got in my new iMac so I can edit video with Final Cut Express. Problem. I can't install the Apple ProRes QuickTime Decoder. I have this setup on my current computer. I have Final Cut Express with the decoder installed so that I can import

  • Has anyone else had trouble connecting their YouTube account to the Apple TV?

    My YouTube account is connected to my Gmail account.  I never set up a second YouTube account with a username, etc.  When I try to log in to the AppleTV YouTube app, it says "this type of account cannot be used."  I'm not sure what the issue is.  Can

  • Creating hyperlinks in form region

    How can I create hyperlinks in the form region.when clicked on hyperlink it should take to a different page.Thanks in advance.

  • SM30 Wrong Data retention on screen

    Hi , I have a requirement as follows : Create a table maintenance for a table with material number and plant as primary key.Then while maintaining the values I have to check if that matnr+werks is present in MARC table . If say 10 material plant are


HashFlare