Fiscal Period Variant Not defined for year 2010

Hi All ,
  We are using a Planning area with a Fiscal year variant  in the storage bucket profile for DP. We are trying to copy the data from BW to the planning area which also has the same Fiscal year variant. All the settings in SPRO and the T009 tables are setup correctly for this fiscal year variant, still while using the TSCUBE transaction to copy the data from the cube to the planning area we enconter the above mentioned error. While investigating further we found a table /sapapo/T445C2 which assigns the infocube to the technical periods and this table is empty as of now,( A similar table is used in ECC for flexible planning which assings this value there ) , But  in BW side there is no such table. I am not sure if this is the reason for the error. Did anyone face a similar problem in the past . Kindly share your comments on the same.
Regards
Chirag

Hi Kadam,
Thank you for the reply. We already did check the notes , but that is not of relevance in this case, since the error is happening not only in APO but also in BI. The BI team found that the fiscal year variant defined for the year was 100 periods which is not possible since in a year if we make weekly periods the periods cannot exceed more that 53 to 64  hence the system was not creating any SID's they are trying to correct the error.
Regards
Chirag

Similar Messages

  • 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.

  • Consolidation - T Code CXCD Period scrolling not enabled for FY 2010

    Hi Masters
    I am new to EC - CS and having some issues with Display options in T Code CXCD - Data Monitor
    When I enter period 01 and Fiscal Year 2010, system displays following message:
    Period 001/2010 is not a valid period in consolidation cycle 001
    Message no. G00085
    Then it does not show me the arrows on the menu bar to scroll from period to period.
    But if I enter period 01 and fiscal year 2009, these arrows are displayed.
    What should be done to enable these arrows for fiscal year 2010 also?
    Appreciate your help on this.
    Thanks
    Satya

    Hi Masters
    Thanks for your views and replies.
    I found out what is causing this issue. We need to maintain Delta years under "Assignment of Cons Frequencies to Cons Cycle". This is accessible using T Code CX5TD.
    I had assigned one more year as data value with same frequency as earlier years.
    This had solved my issue of navigating arrows in T Code CXCD - Data Monitor for FY 2010.
    Thanks
    Satya

  • Error saying 'Posting period 000 is not defined for fiscal year variant K4'

    Hi All,
       When I try to add a new entry in the transaction OB52, I get an error message saying 'Posting period 000 is not defined for fiscal year variant K4'. The entry that I add is,
    Variant           :  0001
    Account Type: +
    From Period    : 1
    Year               : 1995
    To Period        : 12
    Year               : 2010
    From Period2  : 13
    Year               : 2000
    To period2      : 16
    Year               : 2010
    Please let me know what customising needs to be done to solve this issue.
    Thanks a ton.
    Best Regards,
    Jeff

    Hi,
    Hava you checked in OB52 screen, by default 0001 posting period variant will be there for +, A, D, K, S account types.
    If it is already existed in your OB52 screen, you won't create one more record with the same name. You have to edit the existing 0001 posting period with new values.
    Thanks
    Chandra

  • Version 0 is not defined for fiscal year 2012.

    Hello Experts,
    While am tring to release  a work order, i am getting the below error.
    Version 0 is not defined for fiscal year 2012.
    Message no. GP626
    Diagnosis
    The version 0 is not defined in controlling area DE06 for the fiscal year 2012.
    You have to maintain the fiscal year-dependent version parameters for all actual versions for which multiple valuation is updated.
    System Response
    The version 0 cannot be used for fiscal year 2012.
    Procedure
    Maintain the fiscal year-dependent version parameters for the version 0.
    Execute function
    By this what i understood is we need to change the Settings for each fiscal year for the version 0 in controlling area DE06.
    i.e. we need to add the fiscal year 2012 in that.
    Is this correct????
    If yes what will be the impact of adding 2012 in that screen?
    i think its a soft config only.
    Please let me know the correct process
    Thanks in Advance,
    Satya

    Version 0 is not defined for fiscal year 2015.
    What to do next ? Please help with it.

  • Fiscal year not defined for in Year

    Dear All
    I am trying BDC to record hiring action through PA40 for the purpose of mass hiring. While hiring process at 'Create Car & Conveyance allowance' screen a warning message appears "No automatic updation for pernr 12345 .Allowance grpg not found." I skipped it, then another error comes at  'Create Income From Other Sources' screen, that is "Fiscal year not defined for  in Year". In the description of this error I find 'Fiscal year not defined for  in Year'. I checked PA03 also, but I didn't find any clue there.
    Kindly enable me with your expert suggestions to go ahead.
    Best Regards,
    Anand Singh
    SAP HR Consultant

    HI,
    1. Allowance Grouping
    - Check the hiring date and Infotype 8 date.
    2. Income from other sources
    - Check the control record .
    Is it released for the year for which u r entering the data.
    Regards,
    Param

  • Version  0 not defined for fiscal year...

    Dear Experts..
    Im trying to do an hiring action but system says Version  0 not defined for fiscal year...
    Could someone tell me wat could be the reason???
    Regards
    Shanthini

    Hi,
    Go to SPRO: Controlling -  General controlling - Org - Maintain versions
    On the right hand side select version 0 then select controlling area settings.
    Again select version 0 on the right hand side and select Settings for each fiscal year.
    Then maintain the settings for the relevant fiscal year.
    Regards,
    Dilek

  • VERSION 0 IS NOT DEFINED FOR FISACL YEAR 2007,

    i am learning SAP PP and i hv ides 4.7,
    now WHEN SAVING ORDER i.e DURING COST CALCULATION I GET A MESSAGE THAT VERSION 0 IS NOT DEFINED FOR FISACL YEAR 2007,
    ON ANALYSING IT LEADS TO T.CODE OKEV BUT HERE SYSTEM DOES NOT PERMIT TO CHANGE THE VERSION, BUT IN ECC 5.0 IT ALLOWS ,
    WHAT IS THE PROBLEM, CAN ANY ONE PL. HELP ME,
    analysis of error gives following message:
    Activation of the indicator is not permitted
    Message no. KT253
    Diagnosis
    You activated an indicator (Plan, Actual, WIP/results analysis or Variance calculation ) in the basic settings for version 1 in controlling area 1000. However, a higher order of settings (general version definition) prevents you from setting this indicator in version 1.
    Note
    The following should be taken into account when maintaining a version:
    In general version definition you decide whether a version is allowed for
    •     Panning (with the Plan indicator)
    •     Actual data update (with the Actual indicator)
    Note: In Overhead Cost Controlling, actual data is updated in operational version 0.
    Actual versions different from 0 are found at present only for delta versions in Activity Based Costing (CO-ABC), and when you work with parallel assesment ( additional versions):
    •     A data version from results and WIP determination manages (indicator WIP)
    •     Another version from variance determination manages (indicator Variance)
    •     A version for exclusive use (field exclusive application)
    You must maintain the version basic settings for each controlling area in which you want to update transaction data. General version definition restricts the settings possible for the controlling area:
    •     If general version definition does not allow plan and/or actual data update for version, this applies to the version in all controlling areas. If plan and/or actual data updating is allowed for a version in general definition, this can be reset for each controlling area separately (unmark the plan or actual indicator).
    •     Delta versions in ABC may not be used for parallel valuations in the actual; the same goes for versions with exclusive applications. In both cases, the valuation fields may not be maintained.
    To set indicators WIP/Results- or Variance-determination the following conditions apply:
    •     Both indicators may be set only during setup for the controlling area, when they are already established in the higher level general version definition
    •     If either indicator is already active in the data bank, then the actual indicator may not be subsequently activated
    •     If the actual indicator is inactive and either of these indicators is active, then the valuations in the corresponding versions and in version "000" must agree
    •     If the actual indicator is active, then both indicators must be activated
    Versions 0 and 1 are used regularly for various purposes by the system, which sets the following limitations/restrictions:
    •     Version 0 must always be available. It cannot be used exclusively. The plan and actual indicators must always be active.
    •     The actual indicator may not be activated in version 1.
    If these conditions are violated during version maintenance, error messages are issued. There are three types of error message:
    1. While maintaining the general version definition, you can only make changes if they do not violate the conditions outlined above.
    2. While maintaining the basic settings in the controlling area, the entries must remain consistent with the higher level entries.
    3. You want to maintain version 0 or 1. The restrictions outlined above apply.
    Use the "Extras" menu option to display the structure of the entries in the complex data object version:
    •     Select a version and choose Extras -> Version use.
    The SAP System shows which controlling areas use this version.
    •     Select Extras -> Versions in CO area
    This displays all versions used in the current controlling area.
    The subordinate entries in the hierarchy (settings for each fiscal year, strategic Activity-Based Costing: transactions for a delta versions) will also be shown for both cases.
    Procedure
    Do not activate the indicator, or change the higher order of settings in the general version definition.

    Raj,
    What are you trying to change?
    To me you are not suppose to make any changes, you need to select the version "0" and then hit "Settings for each Fiscal year" subfolder.... here you copy the settings of 2006 and change the year to 2007. This should resolve the problem.
    Regards,
    Prasobh

  • BEx Fiscal Period variables not working in Webi

    Hello,
    We have an BEx user entry variable for Fiscal period, that works correctly in BEx. In the prompt LOV, I get values from year 2003 to 2013.
    When I run it in Webi, the LOV starts from year 0000 to 2040. Also there are 16 periods in a year, wheras the LOV displays 24 period, even after restricting on fiscal variant.
    Has anyone  successfully been able to make Webi work with BEx fiscal period variants?
    Thanks,
    Nikhil

    I created a universe objects with following in the
    "Select"
    [0P_FPER].[NAME]
    "Where" condition
    <FILTER KEY = "@Select(Fiscal year Period\LovPeriod_Fiscal Year)">
    <CONDITION OPERATORCONDITION = "Greater">
    <CONSTANT CAPTION = "AB1000001"/>
    </CONDITION></FILTER>
    When I create a report with this object, I get no data.
    I change the above to
    "Select"
    [0P_FPER].[NAME]
    "Where" condition
    <FILTER KEY = "@Select(Fiscal year Period\LovPeriod_Fiscal Year)">
    <CONDITION OPERATORCONDITION = "Less">
    <CONSTANT CAPTION = "AB1000001"/>
    </CONDITION></FILTER>
    I tried changing the CONSTANT CAPTION values, everytime "Less" works but "Greater" does not. Does "Greater" not work?

  • While creating sales order got error version "0" is not defined for company

    Hi,
    i got a error  while creating a sales order(va01) ,i got an error
    saying that "version 0(zero) is not defined for company code
    if there is any solution please provide....
    Thanks&regards
    kishore kumar

    Go to TCODE:OKEQ
    1)select version 0 here and ext select settings for each fiscal year under controlling area settings
    2)give your controlling area XXXX and version 0 then enter
    3)select new entries maintain data for new year 2008.
    Hope this will give u
    Sri

  • "PERNR" is not defined for the current logical database.

    Hi Experts,
    I have developed a program for HR salary variance but when i execute i getting error in the line " get PERNR"
    the "PERNR" is not defined for the current logical database. so plz suggest me to avoid this issue.
    Thanks,
    Rajesh

    the codes are has below,
    *& Report  ZHRSAL_COMP
    REPORT  ZHRSAL_COMP.
    tables: pernr,
            t512t.                      "Wage type texts
    infotypes: 0001. "Organizational Assignment
    *Tables data containing directory to PCL2 payroll results file.
    data: begin of rgdir occurs 100.
            include structure pc261.
    data: end of rgdir.
    data: result type pay99_result.
    data: rt_header type line of hrpay99_rt.
    data: country like t001p-molga,
          number  like pc261-seqnr. "Number of last payroll result
    types :begin of struc_p0001,
           pernr type  p0001-pernr,
           ename type  p0001-ename,
           werks type  p0001-werks,
           btrtl type  p0001-btrtl,
    end of struc_p0001.
    data : gtab_p0001 type table of struc_p0001,
           gwa_p0001 type struc_p0001.
    types : begin of struc_payroll,
            text(10) type c,
            date     type dats,
            month(2) type c,
            year(4)  type c,
            abkrs(2) type c,
            end of struc_payroll.
    data : gtab_payroll type table of struc_payroll,
           gwa_payroll type struc_payroll.
    types : begin of struc_result,
           lgart type lgart,
           lgtxt type t512t-lgtxt,
           betrg type betrg,
            end of struc_result.
    data : gtab_result type table of struc_result,
          gwa_result type struc_result.
    get pernr.
      rp_provide_from_last p0001 space pn-begda pn-endda.
      call function 'CU_READ_RGDIR'
        exporting
          pernr          = p0001-pernr
        importing
          molga           = country
        tables
          in_rgdir        = rgdir
        exceptions
          no_record_found = 1
          others          = 2.
      if sy-subrc = 1.
        write: / 'No records found for '(001), pernr-pernr.
      endif.
      call function 'CD_READ_LAST'
        exporting
          begin_date      = pn-begda
          end_date        = SY-DATUM
        importing
          out_seqnr       = number
        tables
          rgdir           = rgdir
        exceptions
          no_record_found = 1
          others          = 2.
      if sy-subrc = 1.
        write: / 'No payroll result found for'(002), pn-paper.
      else.
        call function 'PYXX_READ_PAYROLL_RESULT'
             exporting
                  clusterid                    = 'RX'
                  employeenumber               = p0001-pernr
                  sequencenumber               = number
            READ_ONLY_BUFFER             = ' '
            READ_ONLY_INTERNATIONAL      = ' '
            CHECK_READ_AUTHORITY         = 'X'
       IMPORTING
            VERSION_NUMBER_PAYVN         =
            VERSION_NUMBER_PCL2          =
             changing
                  payroll_result               = result
             exceptions
                  illegal_isocode_or_clusterid = 1
                  error_generating_import      = 2
                  import_mismatch_error        = 3
                  subpool_dir_full             = 4
                  no_read_authority            = 5
                  no_record_found = 6
                  versions_do_not_match        = 7
                  others                   = 8.
        if sy-subrc = 0.
          perform print_rx.
        else.
          write: / 'Result could not be read (003)'.
        endif.
      endif.
          FORM PRINT_RX                                        *
          Print Payroll Result                                 *
    form print_rx.
      format intensified on.
      write: / p0001-pernr,
               p0001-ename(15),
               p0001-werks,
               p0001-btrtl.
      format intensified off.
      skip 1.
      move p0001-pernr to gwa_p0001-pernr.
      move p0001-ename(15) to gwa_p0001-ename.
      move p0001-werks to gwa_p0001-werks.
      move p0001-btrtl to gwa_p0001-btrtl.
      append gwa_p0001 to gtab_p0001.
      write: / 'For period/payroll area: '(004),
               30 result-inter-versc-fpper+4(2),
               result-inter-versc-fpper+0(4),
               result-inter-versc-abkrs,
               / 'In-period/payroll area: '(005),
               30 result-inter-versc-inper+4(2),
               result-inter-versc-inper+0(4),
               result-inter-versc-iabkrs.
      skip 1.
      gwa_payroll-text = 'For'.
      move result-inter-versc-fpper to gwa_payroll-date.
      move result-inter-versc-fpper+4(2) to gwa_payroll-month.
      move result-inter-versc-fpper+0(4) to gwa_payroll-year.
      move result-inter-versc-abkrs to gwa_payroll-abkrs.
      append gwa_payroll to gtab_payroll.
      gwa_payroll-text = 'In'.
      move result-inter-versc-fpper to gwa_payroll-date.
      move result-inter-versc-inper+4(2) to gwa_payroll-month.
      move result-inter-versc-inper+0(4) to gwa_payroll-year.
      move result-inter-versc-iabkrs to gwa_payroll-abkrs.
      append gwa_payroll to gtab_payroll.
      write: 'Results table: '(006).
      skip 1.
      loop at result-inter-rt into rt_header.
        perform re512t using result-inter-versc-molga
                             rt_header-lgart.
        write: / rt_header-lgart,
                 t512t-lgtxt,
                 rt_header-betrg currency rt_header-amt_curr.
    move rt_header-lgart to gwa_result-lgart.
    move t512t-lgtxt to gwa_result-lgtxt.
    move rt_header-betrg to gwa_result-betrg.
    append gwa_result to gtab_result.
      endloop.
    endform.                    "print_rx
          FORM RE512T                                          *
          Read Wage Type Texts
    form re512t using value(country_grouping)
                      value(wtype).
      check t512t-sprsl ne sy-langu
         or t512t-molga ne country_grouping
         or t512t-lgart ne wtype.
      select single * from t512t
                  where sprsl eq sy-langu
                  and   molga eq country_grouping
                  and   lgart eq wtype.
      if sy-subrc ne 0.
        clear t512t.
      endif.
    endform.                                                    "re512t

  • Cbs build portal application dc fail.  Build Plugin IS NOT DEFINED for this

    hi all
    I use NW7.0 ehp1,have portal and a nwdi.
    I create a track at nwdi . and develop a portal application .
    local build is ok . but when i check in .run a activitce.  dc is broken.
    log is -
    CBS Request Log - [  300/DEP_PESKM_D  ]
    Build number assigned: 314
    Change request state from QUEUED to PROCESSING
    REQUEST PROCESSING started at 2010-11-05 02:17:38.921 GMT
        ACTIVATION request in Build Space "DEP_PESKM_D" at Node ID: 13,975,650
         [id: 300; parentID: 0; type: 4]
         [options: NO OPTIONS]
        Waiting for access: 79 ms
        ===== Pre-Processing =====  started at 2010-11-05 02:17:39.000 GMT
            List of requested for activation activities:
                'deep.com_PESKM_1' compartment
                    tet
                        [ISN 111][created by YANLIANG at 2010-11-05 10:17:31.0][OID 6b2f604ae87c11df94ff000000d54062]
                There is 1 activity in compartment deep.com_PESKM_1
                1 activity will be processed by this request
            Analyze dependencies to predecessor activities... started at 2010-11-05 02:17:39.031 GMT
                Analyzing predecessors in compartment "deep.com_PESKM_1"
                    No dependencies to predecessor activities found.
            Analyze dependencies to predecessor activities... finished at 2010-11-05 02:17:39.046 GMT and took 15 ms
            Analyze versions... started at 2010-11-05 02:17:39.046 GMT
                List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2010-11-05 02:17:41.812 GMT and took 2 s 766 ms
                Synchronize metadata for [deep.com.cn/dc_logo_par] started at 2010-11-05 02:17:41.812 GMT
                    Verification of DL [ws/PESKM/deep.com_PESKM/dev/active/] finished at 2010-11-05 02:17:41.906 GMT and took 0 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2010-11-05 02:17:41.937 GMT and took 31 ms
                Synchronize metadata for [deep.com.cn/dc_logo_par] finished at 2010-11-05 02:17:41.937 GMT and took 125 ms
                < CHANGE > 'deep.com.cn/dc_logo_par' DC
            Analyze versions... finished at 2010-11-05 02:17:41.937 GMT and took 2 s 891 ms
            Analyze activities... started at 2010-11-05 02:17:41.937 GMT
                Loading component definitions
                1 component to be build in compartment "deep.com_PESKM_1"
            Analyze activities... finished at 2010-11-05 02:17:42.000 GMT and took 63 ms
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2010-11-05 02:17:42.109 GMT
                    'deep.com.cn/dc_logo_par' variant 'default'
                    'deep.com.cn/dc_logo_par' variant 'default' cannot be built. ACTIVATION will fail.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
            Analyze request DC BV... finished at 2010-11-05 02:17:42.140 GMT and took 31 ms
        ===== Pre-Processing =====  finished at 2010-11-05 02:17:42.187 GMT and took 3 s 187 ms
        Change request state from PROCESSING to FAILED
        Error! The following problem(s) occurred  during request processing:
        Error! The following error occurred during request processing:Activation failed due to component "deep.com.cn/dc_logo_par" variant "default". The component is BROKEN.
    REQUEST PROCESSING finished at 2010-11-05 02:17:42.187 GMT and took 3 s 266 ms
    No build logs available for the request.
    Edited by: yan liang on Nov 5, 2010 3:12 AM

    Hi Yan,
    please check the NWDI troubleshooting guide:
    http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29Q0030
    --> Understanding Broken and Dirty DCs
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51309e
    Did you import the dependent build plugins for the track in question?
    (tab "development" in the /devinf --> CMS webui --> Transport studio)
    See also the sap note: #1080927 - Creating CMS Tracks for Common Application Types (http://service.sap.com/sap/support/notes/1080927)
    Best Regards,
    Ervin

  • Fiscal Period is not working on weekly level

    Hello,
    I am building this query where users can use the fiscal period on the weekly level. We do have weekly variant maintained in 0fiscvarnt. Problem is every time I execute the query on weekly level its doesnt not bring in any data but if I execute the query on period level, it brings in tons of data.
    Example: if I execute the query with the following setting it would not bring in any data.
    Fiscal period: 001/2008 - 052/2008
    fiscal period variant: AB (weekly based, 001 - 053)
    If I execute the with following settings it would bring lots of data.
    Fiscal Period: 001/2008 - 012/2008
    Fiscal period variant: YZ (Month based, 4-4-5)
    Addition to that, there is no data available in the cube for fiscal variant:AB (weekly based).
    Any suggestion would be appreciated.
    Thanks,

    Khalid
    what you can do is :
    For reporting based on fiscal month periods create a cube and populate it.
    Put in the time dimension all 0Fisc* infoobjects.
    Do the same for weeks.
    So --> 2 cubes : one with fiscal variant month, the other with weeks.
    let's say Cubefiscweek and Cubefiscmonth
    In order to convert to fiscal periods base on a date you have some standard function like date_to_period_convert.
    For example you have the day of transaction purchasing or sales take the date and convert it in the transformation with a routine.
    One important setting :
    Make sure you retrieved the global settings form source system regarding the fiscal periods.
    Maintain the fiscal variant in tx ob29 or gvar for the week variant and the month variants.
    Maybe this tasks is already done in source system so you just need to recover the global setting in BW.  Check if tables T009x are maintained (the one that is important is t009b)
    If they are not maintained ask a functional to give the repartition.
    regards
    Boujema

  • Error - Excise modvat accounts not defined for DLFC transaction and 01 exci

    Dear All,
    Getting below error while  doing J1IIN - Posting Excise invoice for Sale.
    "Excise modvat accounts not defined for DLFC transaction and 01 excise group"
    I checked with the settings GL are assigned to for DLFC and 01 excise group.
    Is anywhere else I need to mantain the modvat GL
    Regards,
    Rakesh

    Check if you are using any subtransaction type along with excise transaction type.
    Excise group, ETT, company code, sub transaction type (if any), Chart of account, Modvat account (pls maintain all the entries over here) search for modavat clearing field and maintain it.
    BR
    Edited by: Sujoy on Jan 15, 2010 9:45 AM

  • Goods Issue error - batches not defined for delivery item

    Hi,
    We are getting a Goods Issue error  u201CThe batches are not defined for delivery item 000010u201D.   We are only getting this error for a material that is being shipped against a particular third party sales scheduling agreement.  We went live in 2007 and we had no issues, but when we had to create a new Sched Agreement this year, for third party sales, we started to get this error.  However, if we re-activate the old scheduling agreement we do not get the error.  We have a batch job that executes the following steps:
    1.     VL06IG (collective goods receipt)
    2.     VL10 (collective delivery)
    3.     VL06O (collective GI)
    We have compared the 2 scheduling agreements and see no difference.  We are assuming it has something to do with how the scheduling agreement was setup, but are not sure.  Any suggestions on how to correct this problem would be much appreciated.
    Thanks in advance,
    Helen

    Dear Murali,
    The material has not changed at all.  I'm not sure what you mean by maintaining batches while receipt of the material.
    If I re-open the old scheduling agreement, we do not get the error message.  However, as soon as we use the new SD scheduling agreement, we get the error.  We are using the same material master on both scheduling agreements.
    Thanks,
    Helen

Maybe you are looking for