Value date issue

hi,
can u please tel me where we have to configure the value date in fi ?

Hi,
LSMW for Asset Data was intended for "historical asset" via transactions AS91 (AS92) not AS01.
Anyway, this program is creating asset one per one, so the field you mention is irrelevant.
See the Note 550176 - FAQ note legacy data transfer asset master records
Thanks,
Raviteja

Similar Messages

  • Master data Issue  ---   materials have unassigned or # values ...!!

    Hello Experts,
    I am facing an issue that the Customer Data is missing in a BEx Report.
    Data Flow is   2LIS_13_VDITM  --> DSO1 --> Merging DSO -->  Cube --> Multiprovider --> Bex Report.
    Exact issue is Customers in the Bex Report  has unassigned to Sales Office, Sales Group, Sales District.
    The only reason a customer should show up under u201Cunassignedu201D or u201C#u201D is if itu2019s improperly set up in the system.
    customers are assigned with two values. one which has data and the other which has unassigned value.
    I wanted to know, how do i check if the matierials are valid to have unassigned Values ?
    Checked the Merging DSO and saw that there are actually values assigned values for the affected matierials.
    After that checked the Cube data values are displayed except the Master Data values.
    I guess..its completely related to Master data. I would like to know how can i resolve this issue.
    Please reply me if you face this kind of master data issue in your expeiriance.
    Thanks,
    SN.

    Hi,
    Are Sales Office, Sales Group, Sales District are attributes of Customer?
    In case they are, then the customers will be unassigned to Sales Office, Sales Group, Sales District in case the data for these attributes is loaded to the customer attributes.
    and also check if the customer characteristic is properly assigned in the multiprovider.
    Check if it helps.
    Regards,
    Joe

  • OBIEE 11g .0d date issue

    Hi,
    I create an initialization block to populate a couple of repository variables.
    After saving the RDP the value for the default initializer changes from 2011 to 2011.0d
    I have been using several workaround. But I need some permanent fix in rpd itself. Can anyone point to some Oracle Document? Is this issue been resolved in latest release of OBIEE. I am using 11.1.1.6.6.
    Workaround Ref : The .0d date issue
    Re: OBIEE 11.1.1.6.2 BP1 Repository Variable data type

    Have you gone through my suggestions at the below links?
    The .0d date issue
    Re: OBIEE 11.1.1.6.2 BP1 Repository Variable data type
    You have to do it where ever you are using that rep. variable not in the init block.

  • Asset Acquisition with Asset Value Date earlier than GI post.date

    Dear all,
    I am curently using SAP ECC 6.0. We are not creating AuC assets but directly capitalizing assets from investment accounts.
    If a material is issued with a date in March and i try to acquire it with asset value date from a previous period, for example in February, the system doesnt issue any message and lets me post the transaction. The accountants claim that this hadnt been possible in the earlier version of SAP 4.6 that we had been using and that the system had issued an error message - "Posting not possible (Value date earlier than capitalization date)"
    The accounting logic is that you cant capitalize an asset with a date earlier than the date when it has been in use, i.e. in our case it`s the date the material has been issued from the warehouse.
    Does someone know what logic does SAP follow in this case - and if i can set a validation control that will check and compare the two dates?
    Any opinion would be appreciated
    KR
    Severina Koleva

    We are on ECC 5.0 and we do get that message, but it is a warning.
    AA348...
    that said, you can setup a validation using GGB0 and asset accounting

  • Asset Value Date Exit and Enhancement

    Hi,
    We have a requirement from customer, that the asset value date in ANY asset posting transaction cannot be less than or equal to 30.06.2014 it should always be 01.07.2014 or higher.
    So, please let me know if there is any User Exit which can be used to restrict the Asset Value Date. If yes, then will this User Exit work for all transaction codes, or we need to write different logic for every transaction code.
    Please advise.
    Regards,
    Devdatth

    Hi,
    To transfer one asset to another asset within a company code can be done through ABUMN only.
    While doing this transfer you have enter the document date, posting date, and value date for the transaction, but all these dates should be in same fiscal year only.
    In your case you must have been entered the dates for asset value date and posting date , and these two dates are in diff financial years.
    Please make sure that both the dates are in same FY.
    Hope this will fix your issue.
    Thanks,
    Srinu

  • Asset value date and posting date are not in same fiscal year

    Hi,
    Our business user has created an asset under an incorrect asset class, which he is trying to transfer to a new asset whcih was created under correct asset class. However system is restricting user with the error message "Asset value date and posting date are not in same fiscal year". Can you please advise me how we can proceed further with this error.
    Regards,
    Asam.

    Hi,
    To transfer one asset to another asset within a company code can be done through ABUMN only.
    While doing this transfer you have enter the document date, posting date, and value date for the transaction, but all these dates should be in same fiscal year only.
    In your case you must have been entered the dates for asset value date and posting date , and these two dates are in diff financial years.
    Please make sure that both the dates are in same FY.
    Hope this will fix your issue.
    Thanks,
    Srinu

  • Value date cross company code postings

    Dear all,
    it is possible to influence the value date on a company code level via the transaction OB68. With this transaction you can state that the current date is used as the default value for the value date when entering line items.This works fine when posting a G/L posting within the same company code.
    When entering a cross company code posting, the indicator in transaction OB68 is ignored and the document date is used to be proposed as default value for the value date.
    Does anyone know which SAP parameters can influence the value date for cross company code postings ? If this is not standard SAP possible, does anyone already encountered this problem and, if so, how did one solve this issue ?
    Many thanks,
    Regards,
    Kristof

    thank you for the reply ... unfortunately I expected some Z-programmation

  • Configuration of value date calculation by currency

    Hi,
    We are producing a payment file for upload to an internet banking system, and the file typically includes payments in a number of different currencies; however, the cut-off times issued by the bank for their processing of the payments in the file differs depending on the currency in which each payment is to be made.
    To ensure the file contains the correct value date, we need to use rules which can determine the value date based on currency.  There only appears to be options in SAP to configure the number of days deviation by house bank / account and payment method.
    Is our only option to build the deviation rules based on currency into the relevant payment print program, or is there some further configuration I can use?
    Any help would be greatly appreciatied.

    if u hav one or two currencies then having seperate accounts will be better or
    use a table containing the currency and the delta days ..use it in ur print program to arrive at the right date..
    thats the only alternatives..to my knowledge level also.
    regards
    anantha

  • Date issue in processing billing documents that shipped in a prior period

    Date issue in processing billing documents that shipped in a prior period that is now closed:
    SAP values those deliveries with the current document date in A/R when it should be the original delivery date.  Baseline date needs to stay the delivery date, but is getting copied from the billing date in the new period.  A user exit exists (& needs to be applied) to manipulate the baseline date when the accounting document is being created.
    Any input is appreciated.

    Hi
    Try with Invoice Correction Request concept
    Sale document Type: RK
    Reference Document Type : Billing Number
    for Understanding the Invoice Correction request check below link
    [Creating Invoice Correction Requests|http://help.sap.com/saphelp_46c/helpdata/en/dd/55feeb545a11d1a7020000e829fd11/content.htm]
    Regards,
    Prasanna

  • Is it possible to add value date field in the debit entry?

    Hi gurus,
    I'm an abapper and struggling to be an FI consultant since I have no one to consult with. Here's my issue:
    I want to add the Value Date field in a GL acct debit entry. I used optional in Field status group. It doesn't appear unless if I change the posting key to credit. But if I change it to required entry, an error appears " Rules for posting key 40 and acct 115-30-002 set incorrectly for "VALUT" field . Did I miss anything? As much as possible, I don't want to use the other GL Account (a credit entry) since I dont need it in the program flow.
    Need an expert explanation on this. Sorry I only have limited knowlege with regards to FI concepts.

    Hi
    Feild status at entry time looks for the following combination
    S- Supressed
    D- Display
    R- Required
    O- Optional
    System looks for this above combination at first in Posting Key and then in FSV of account which we enter. For this partical purpose the the feilds in posting key are kept optional.
    Check the feild status of posting key & account T-code FBKP.
    thanks
    Colin Thomas

  • Stacked 100% bar chart - Problem with datatips for zero value data points

    I have a stacked 100% bar chart that shows datatips in Flex 4.   However, I don't want it to show datatips for
    data points with zero values.   Flex 4 shows the datatip for a zero value data point on the left side of a bar if the data point is not the first in the series.
    Here's the code that illustrates this problem.    Of particular concern is the July bar.    Because of the zero value data point problem, it's not possible to see the datatip for "aaa".
    Any ideas on how we can hide/remove the datatips for zero value data points ?        Thanks.
    <?xml version="1.0"?>
    <s:Application
    xmlns:fx="
    http://ns.adobe.com/mxml/2009"xmlns:mx="
    library://ns.adobe.com/flex/mx"xmlns:s="
    library://ns.adobe.com/flex/spark"creationComplete="initApp()"
    height="
    1050" width="600">
    <s:layout>
    <s:VerticalLayout/>
    </s:layout>
    <fx:Script><![CDATA[ 
    import mx.collections.ArrayCollection;[
    Bindable] 
    private var yearlyData:ArrayCollection = new ArrayCollection([{month:
    "Aug", a:1, b:10, c:1, d:10, e:0},{month:
    "July", a:1, b:10, c:10, d:10, e:0},{month:
    "June", a:10, b:10, c:10, d:10, e:0},{month:
    "May", a:10, b:10, c:10, d:0, e:10},{month:
    "April", a:10, b:10, c:0, d:10, e:10},{month:
    "March", a:10, b:0, c:10, d:10, e:10},{month:
    "February", a:0, b:10, c:10, d:10, e:10},{month:
    "January", a:10, b:10, c:10, d:10, e:10}]);
    private function initApp():void {}
    ]]>
    </fx:Script>
    <s:Panel title="Stacked Bar Chart - Problems with DataTips for Zero Value Items" id="panel1">
    <s:layout>
    <s:HorizontalLayout/>
    </s:layout>
    <mx:BarChart id="myChart" type="stacked"dataProvider="
    {yearlyData}" showDataTips="true">
    <mx:verticalAxis>
     <mx:CategoryAxis categoryField="month"/>
     </mx:verticalAxis>
     <mx:series>
     <mx:BarSeries
    xField="a"displayName="
    aaa"/>
     <mx:BarSeries
    xField="b"displayName="
    bbb"/>
     <mx:BarSeries
    xField="c"displayName="
    ccc"/>
     <mx:BarSeries
    xField="d"displayName="
    ddd"/>
     <mx:BarSeries
    xField="e"displayName="
    eee"/>
     </mx:series>
     </mx:BarChart>
     <mx:Legend dataProvider="{myChart}"/>
     </s:Panel>
     <s:RichText width="700">
     <s:br></s:br>
     <s:p fontWeight="bold">The problem:</s:p>
     <s:p>Datatips for zero value data points appear on left side of bar (if data point is not the first point in series).</s:p>
     <s:br></s:br>
     <s:p fontWeight="bold">For example:</s:p>
     <s:p>1) For "June", eee = 0, mouse over the left side of the bar to see a datatip for "eee". Not good.</s:p>
     <s:br></s:br>
     <s:p>2) For "July", eee = 0 and aaa = 1, can't see the datatip for "aaa", instead "eee" shows. Real bad.</s:p>
     <s:br></s:br>
     <s:p>3) For "Feb", aaa = 0, datatip for "aaa" (first point) does not show. This is good.</s:p>
     <s:br></s:br>
     <s:p>4) For "Mar", bbb = 0, datatip for "bbb" shows on the left side of the bar. Not good.</s:p>
     <s:br></s:br>
     <s:p fontWeight="bold">Challenge:</s:p>
     <s:p>How can we hide/remove datatips for zero value data points?</s:p>
     <s:br></s:br>
     </s:RichText></s:Application>

    FYI.
    Still have the issue after upgrading to the latest Flex Builder 4.0.1 with SDK 4.1.0 build 16076.   
    Posted this as a bug in the Adobe Flex Bug and Issue Management system.     JIRA
    http://bugs.adobe.com/jira/browse/FLEXDMV-2478
    Which is a clone of a similar issue with Flex 3 ...
    http://bugs.adobe.com/jira/browse/FLEXDMV-1984

  • Value date field is missing in MIRO

    Hi Gurus,
    When I insert an account in transaction code MIRO, in tab "G/L account", the system shows the follwing message error: "An entry is required in Value date field for account XXXXXXXXXXX".
    I try to create a variant to display this field but it' s impossible.
    Could you please say me how I do?
    I would insert the value date in MIRO.
    BR.
    Thanks.
    Angela

    Hi Angela,
    there is an old SAP note available regarding your issue: 391683
    It seems the value date has been removed from the MIRO dynpros. (Nvertheless, when you try to change the layout and set value date fo visible, the length of the field is 0. So no use setting it to visible.)
    But you can activate the "Define default value date" in the Company code global data (T001). So for g/l accounts with required entry for value date, the value date is filled with the system date.
    Hope this helps.
    Best regards,
    Stefan

  • Valu date changes in bank folder will be effect any subaccount clearing

    Hello,
    I have one doubt regarding vendor payment doucment value date is 24/03/2014 in SAP but when i am sending to bank i changed value date in 25/03/2014.once payment done from bank side bank sending the file, that file  uploading to SAP(Mt940) while uploading to SAP payment doucment subaccount will clear automatically in SAP?.
    Thanks for advance help.
    Regards,
    Lakshmi.

    Hello, this Issue is resolved. When we are uploading MT940 bank file into SAP system is checking payment docucment number and year only as per our programme.

  • Oracle 11g - Date Issue?

    Oracle 11g - Date Issue?
    =====================
    I hope this is the right forum for this issue, if not let me, where to go.
    We are using Oracle 11g (11.2.0.1.0) on (Platform : solaris[tm] oe (64-bit)), Sql Developer 3.0.04.
    Our NLS_DATE_FORMAT = 'DD-MON-RR'
    Using 'RR' in the format forces two-digit years less than or equal to 49 to be interpreted as years in the 21st century (2000–2049), and years 50 and over, as years in the 20th century (1950–1999). Setting the RR format as the default for all two-digit year entries allows you to become year-2000 compliant. For example:
    We have a date '01-JUN-31' in our source system. It treat this date as 01-JUN-2031' instead of '01-JUN-1931'. One century forward.
    Do we able to resolve using NLS_DATE_FORMAT change?
    How do we resolve this issue?
    Thanks in helping.

    qwe16235 wrote:
    Our source is Oracle data base, where S_date is defined as DATE. Why did you say STRING , when it defined as DATE data type?I doubt you source is an Oracle database. You may have it stored in an Oracle database, but it cam form somewhere else, and was very likely inserted into the table as a string, wherever it came from. Given a string that resembles a date, Oracle will try to convert it to a date using the nls_date_format parameter for the session (which can either be set in the session or inherited form the database). Perhaps this will help explain:
    SQL> create table t (conv_type varchar2(10), dt date);
    Table created.
    SQL> alter session set nls_date_format = 'dd-mon-rr';
    Session altered.
    SQL> insert into t values ('Implicit', '01-jun-31');
    1 row created.
    SQL> insert into t values ('Explicit', to_date('01-jun-1931', 'dd-mon-yyyy'));
    1 row created.
    SQL> commit;
    Commit complete.
    SQL> select conv_type, to_char(dt, 'dd-mon-yyyy') dt
      2  from t;
    CONV_TYPE  DT
    Implicit   01-jun-2031
    Explicit   01-jun-1931So, unless you are really inserting dates, not strings that look like dates, you are going to have problems.
    John

  • Automatic payment: OBBA Define Value date rules

    hi experts,
    Have you ever tried OBBA to define Value date rules? I met a problem with it.
    In OBBA, my configuration is as follows:
    House banK Account ID Transaction R C1 S Dev C2  A
    CIT1               CNY                              3 CN -    1   CN  -
    CN is the Factory Calendar China.
    According to this configuration, I suppose the Value date will take Due date as reference date, minus one day, and if the Value date calculated is Weekend or Public holiday, it will use the last week day as the Value date.
    But I made two tests:
    In the first test, my OBBA configuration is exactly like above one I listed, in my payment proposal, the invoce Due date is 20-Jun, Value date is also 20-Jun, but I think according to the configuration, the Value date should be 20-Jun minus one day=19-Jun which is a weekend, so should be the last week day 18-Jun.
    My first test tell me the Deviation from reference date in days and the Calendar does not work.
    In my 2nd test, I changed the Reference date to 2 (Posting date), but in my payment run, the Posting date is 9-Jun, the invoice Due date is 20-Jun, the Value date is still 20-Jun.
    My 2nd test tell me the Reference date for determining the value date does not work.
    Have you met such problem, it seems the OBBA totally dose not work.
    many thanks!
    best regards
    Sophie

    Hi Sophie,
    I guess it is too late for you already but maybe this helps to other people with similar issues. You also need to assign the transaction created in OBBA to a specific payment method:
    But what is even more important is that you need to tick this box in the payment method company code settings - "payment per due date".
    Regards,
    Ondrej

Maybe you are looking for

  • My iPad has connect to the wrong number for imessage and facetime. How do I change the number on my iPad for imessage and faceting?

    When setting up my new iPad and entering my own Apple ID my sisters number appeared on the imessage and facetiming; however her number is not associated with my Apple ID. How do I change the number to my own?

  • Target SNR reset request

    After the BT outage a couple of weeks ago I noticed a significant drop in the speed of my broadband connection. It was a little unstable for a few days. The line has now stabilised but my noise margin is now at 12db. I am quite a distance from the ex

  • Business Objects Edge SP2

    Hello, Does anyone have any updated information as to when SP2 will be released for Edge? I have an issue with version 3.1 regarding a reverse pivot not giving correct results, which I think is addressed in this fix: ADAPT01316434 Reverse Pivot trans

  • [SOLVED] /usr/lib/aspell-0.60/xray.cset does not exist...

    Update: I'd still like to understand what this /usr/lib/aspell-0.60/xray.cset file is all about. But apearantly I don't really need it. I fired up my xubuntu installation to spellcheck the LyX document. And because the  ~/.aspell.en.pws on Arch had m

  • Export and import XI are different

    I have seen a similar message in this forum but it does not apply to my scenario. I have exhausted all avenues and SAP has not responded to my customer message so I am hoping someone has seen this error. Below is the entire dump I am receiving when I