Catalog error : Index of values is missing for characteristic PLANTu0092

Error" Index of values is missing for characteristic " in mapping 
Hi
We are in SRM
I was trying to transfer Master records to catalog using
BAdi : BBP_CCM_CHAR_MAINT but I’m getting an error’ Index of values is missing for characteristic PLANT’.
Plant has multiple value.
I’ve following code in the method ENHANCE_CTY_DEF
ls_char_definition-char_name = 'PLANT'.
ls_char_definition-char_datatype = 'CHAR'.
ls_char_definition-MULTIVAL_INDICATOR = 'X'.
APPEND ls_char_definition TO et_char_definition.
Following code in the method VALUATE_PRODUCT
**"plant data
v_index = 1.
  ls_char_valuation-char_name = 'PLANT'.
  LOOP at t_plant into WA_plant.
ls_char_valuation-char_value = WA_PLANT-PLANT_1.
  IF  WA_plant-PLANT_1 is not initial.
   ls_char_valuation-MULTIVAL_INDEX = v_index.
   APPEND ls_char_valuation TO et_char_valuation.
   v_index = v_index + 1.
  ENDIF.
  ENDLOOP.
Can anyone tell me how to resolve it. I’ll definitely reward points to any useful answer.
-Joe

Hi
Have you raised any OSS message with SAP yet ? If no, raise one immediately.
Meanwhile, try this ->
<u>It seems the Following code in the method VALUATE_PRODUCT
has some problem -></u>
**"plant data
v_index = 1.
ls_char_valuation-char_name = 'PLANT'.
LOOP at t_plant into WA_plant.
ls_char_valuation-char_value = WA_PLANT-PLANT_1.
IF WA_plant-PLANT_1 is not initial.
ls_char_valuation-MULTIVAL_INDEX = v_index.
APPEND ls_char_valuation TO et_char_valuation.
v_index = v_index + 1.
ENDIF.
ENDLOOP.
Try changing the code - like this ->
**"plant data
LOOP at t_plant into WA_plant.
v_index = sy-tabix.
ls_char_valuation-char_name = 'PLANT'.
ls_char_valuation-char_value = WA_PLANT-PLANT_1.
IF WA_plant-PLANT_1 is not initial.
ls_char_valuation-MULTIVAL_INDEX = v_index.
APPEND ls_char_valuation TO et_char_valuation.
ENDIF.
ENDLOOP.
Some SAP OSS notes to refer ->
<b>Note 850613 - Maintaining the BBP_CCM_CHAR_MAINT BAdI using Customizing
Note 875039 - BBP_CCM_CHAR_MAINT: Valuating predefined characteristics
Note 724097 - Search of the comp. in case of structured characteristics</b>
Do let me know.
Regards
- Atul

Similar Messages

  • Error: FF805 Tax statement item missing for tax code

    Hi all,
    We are getting an error when releasing billing document to accounting in 4.7system.
    Error: FF805 Tax statement item missing for tax code O0
    No tax item exists for tax code O0 in a G/L account item. A possible cause is an incorrect transfer of
    parameters by the application to the Accounting interface.
    Please give your inputs and will be rewared.
    Quick reponse will be appreciated.
    Thanks & Regards.

    Dear Mehak,
    I am sorry for the late reply, but I started (in fact) to work in SDN Forum this year, even I entered earlier.
    We have many FF805 errors reported by customers and the same solution has resolved the problem. Please note that the SD-FI interface changed from earlier releases. The note 400766 eplxains the checks made.
    So it is possible that now you get error message FF805, when in an earlier release you didn't get it, eventhough no customizing change.
    Please review note -> 392696   R/3 Tax Interface Configuration Guide
    However please note => In the vast majority of cases, error FF805 occurs because of an error in your pricing procedure. The attached note 112609 explains in detail how tax codes are transfered to conditions.
    The note 400766 explains the checks performed by the system on the Tax codes:
    1. system checks whether there is a revenue line for each tax line.
    2. in the reverse case, for each revenue line containing a certain tax indicator there must be a tax line with this indicator.
    If the tax condition has condition value zero and condition base value zero, then it is not transferred to FI.
    If you have revenue lines containing a tax indicator XX, but no tax line with tax indicator XX, then the error FF805 issues, and it is justified. => Please check these informations.
    -> EXAMPLE
       If tax condition MWST has base amount zero and value zero; for this reason it is not passed to accounting. But, according to the criteria reported by note 112609, its tax indicator EG: A7
       has been assigned to the condition EG: ZBR1.
       So in accounting there would be a revenue line with tax indicator A7, but there isn't any tax line with indicator A7 (because MWST doesn't pass to FI). The note 400766 states situation is unallowed, and error FF805 is justified.
    IMPORTANT: Just a hint, any issue with FI, kindly report in the forum:
    Expert Forums - SAP Solutions - ERP Financials
    There you will find a lot of people that works with FI and can help you with future issues, including me
    I hope I could help you
    Kind Regards,
    Vanessa Barth.

  • SQL Error: ORA-12899: value too large for column

    Hi,
    I'm trying to understand the above error. It occurs when we are migrating data from one oracle database to another:
    Error report:
    SQL Error: ORA-12899: value too large for column "USER_XYZ"."TAB_XYZ"."COL_XYZ" (actual: 10, maximum: 8)
    12899. 00000 - "value too large for column %s (actual: %s, maximum: %s)"
    *Cause:    An attempt was made to insert or update a column with a value
    which is too wide for the width of the destination column.
    The name of the column is given, along with the actual width
    of the value, and the maximum allowed width of the column.
    Note that widths are reported in characters if character length
    semantics are in effect for the column, otherwise widths are
    reported in bytes.
    *Action:   Examine the SQL statement for correctness.  Check source
    and destination column data types.
    Either make the destination column wider, or use a subset
    of the source column (i.e. use substring).
    The source database runs - Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    The target database runs - Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
    The source and target table are identical and the column definitions are exactly the same. The column we get the error on is of CHAR(8). To migrate the data we use either a dblink or oracle datapump, both result in the same error. The data in the column is a fixed length string of 8 characters.
    To resolve the error the column "COL_XYZ" gets widened by:
    alter table TAB_XYZ modify (COL_XYZ varchar2(10));
    -alter table TAB_XYZ succeeded.
    We now move the data from the source into the target table without problem and then run:
    select max(length(COL_XYZ)) from TAB_XYZ;
    -8
    So the maximal string length for this column is 8 characters. To reduce the column width back to its original 8, we then run:
    alter table TAB_XYZ modify (COL_XYZ varchar2(8));
    -Error report:
    SQL Error: ORA-01441: cannot decrease column length because some value is too big
    01441. 00000 - "cannot decrease column length because some value is too big"
    *Cause:   
    *Action:
    So we leave the column width at 10, but the curious thing is - once we have the data in the target table, we can then truncate the same table at source (ie. get rid of all the data) and move the data back in the original table (with COL_XYZ set at CHAR(8)) - without any issue.
    My guess the error has something to do with the storage on the target database, but I would like to understand why. If anybody has an idea or suggestion what to look for - much appreciated.
    Cheers.

    843217 wrote:
    Note that widths are reported in characters if character length
    semantics are in effect for the column, otherwise widths are
    reported in bytes.You are looking at character lengths vs byte lengths.
    The data in the column is a fixed length string of 8 characters.
    select max(length(COL_XYZ)) from TAB_XYZ;
    -8
    So the maximal string length for this column is 8 characters. To reduce the column width back to its original 8, we then run:
    alter table TAB_XYZ modify (COL_XYZ varchar2(8));varchar2(8 byte) or varchar2(8 char)?
    Use SQL Reference for datatype specification, length function, etc.
    For more info, reference {forum:id=50} forum on the topic. And of course, the Globalization support guide.

  • Error:  FF805 Tax statement item missing for tax code O0

    Hi Gurus
    We are working in Upgrade Project 4.6C to ECC 6
    We are getting an error when releasing billing document  to accounting in ECC 6 System.
        Error:  FF805 Tax statement item missing for tax code O0
        No tax item exists for tax code O0 in a G/L account item. A possible cause is an incorrect transfer of
        parameters by the application to the Accounting interface.
    This issue occurs in both DEV and QA2.
    Please give your iputs and will be rewared
    Thanks and Regards,
    Sateesh.K

    hi,
    The problem may be due to missing authorizations.
    Please looking into the note 780589 and 188200.
    Hope this might be of some help.
    Regards,
    Imran

  • I am getting error "ORA-12899: value too large for column".

    I am getting error "ORA-12899: value too large for column" after upgrading to 10.2.0.4.0
    Field is updating only through trigger with hard coded value.
    This happens randomly not everytime.
    select * from v$version
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE     10.2.0.4.0     Production
    TNS for Linux: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    Table Structure
    desc customer
    Name Null? Type
    CTRY_CODE NOT NULL CHAR(3 Byte)
    CO_CODE NOT NULL CHAR(3 Byte)
    CUST_NBR NOT NULL NUMBER(10)
    CUST_NAME CHAR(40 Byte)
    RECORD_STATUS CHAR(1 Byte)
    Trigger on the table
    CREATE OR REPLACE TRIGGER CUST_INSUPD
    BEFORE INSERT OR UPDATE
    ON CUSTOMER FOR EACH ROW
    BEGIN
    IF INSERTING THEN
    :NEW.RECORD_STATUS := 'I';
    ELSIF UPDATING THEN
    :NEW.RECORD_STATUS := 'U';
    END IF;
    END;
    ERROR at line 1:
    ORA-01001: invalid cursor
    ORA-06512: at "UPDATE_CUSTOMER", line 1320
    ORA-12899: value too large for column "CUSTOMER"."RECORD_STATUS" (actual: 3,
    maximum: 1)
    ORA-06512: at line 1
    Edited by: user4211491 on Nov 25, 2009 9:30 PM
    Edited by: user4211491 on Nov 25, 2009 9:32 PM

    SQL> create table customer(
      2  CTRY_CODE  CHAR(3 Byte) not null,
      3  CO_CODE  CHAR(3 Byte) not null,
      4  CUST_NBR NUMBER(10) not null,
      5  CUST_NAME CHAR(40 Byte) ,
      6  RECORD_STATUS CHAR(1 Byte)
      7  );
    Table created.
    SQL> CREATE OR REPLACE TRIGGER CUST_INSUPD
      2  BEFORE INSERT OR UPDATE
      3  ON CUSTOMER FOR EACH ROW
      4  BEGIN
      5  IF INSERTING THEN
      6  :NEW.RECORD_STATUS := 'I';
      7  ELSIF UPDATING THEN
      8  :NEW.RECORD_STATUS := 'U';
      9  END IF;
    10  END;
    11  /
    Trigger created.
    SQL> insert into customer(CTRY_CODE,CO_CODE,CUST_NBR,CUST_NAME,RECORD_STATUS)
      2                values('12','13','1','Mahesh Kaila','UPD');
                  values('12','13','1','Mahesh Kaila','UPD')
    ERROR at line 2:
    ORA-12899: value too large for column "HPVPPM"."CUSTOMER"."RECORD_STATUS"
    (actual: 3, maximum: 1)
    SQL> insert into customer(CTRY_CODE,CO_CODE,CUST_NBR,CUST_NAME)
      2                values('12','13','1','Mahesh Kaila');
    1 row created.
    SQL> set linesize 200
    SQL> select * from customer;
    CTR CO_   CUST_NBR CUST_NAME                                R
    12  13           1 Mahesh Kaila                             I
    SQL> update customer set cust_name='tst';
    1 row updated.
    SQL> select * from customer;
    CTR CO_   CUST_NBR CUST_NAME                                R
    12  13           1 tst                                      Urecheck your code once again..somewhere you are using record_status column for insertion or updation.
    Ravi Kumar

  • Replicat error: ORA-12899: value too large for column ...

    Hi,
    In our system Source and Target are on the same physical server and in the same Oracle instance. Just different schemes.
    Tables on the target were created as 'create table ... as select * from ... source_table', so they have a similar structure. Table names are also similar.
    I started replicat, it worked fine for several hours, but when I inserted Chinese symbols into the source table I got an error:
    WARNING OGG-00869 Oracle GoldenGate Delivery for Oracle, OGGEX1.prm: OCI Error ORA-12899: value too large for column "MY_TARGET_SCHEMA"."TABLE1"."*FIRSTNAME*" (actual: 93, maximum: 40) (status = 12899), SQL <INSERT INTO "MY_TARGET_SCHEMA"."TABLE1" ("USERID","USERNAME","FIRSTNAME","LASTNAME",....>.
    FIRSTNAME is Varchar2(40 char) field.
    I suppose the problem probably is our database is running with NLS_LENGTH_SEMANTICS='CHAR'
    I've double checked tables structure on the target - it's identical with the source.
    I also tried to manually insert this record into the target table using 'insert into ... select * from ... ' statement - it works. The problem seems to be in the replicat.
    How to fix this error?
    Thanks in advance!
    Oracle GoldenGate version: 11.1.1.1
    Oracle Database version: 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
    NLS_LANG: AMERICAN_AMERICA.AL32UTF8
    NLS_LENGTH_SEMANTICS='CHAR'
    Edited by: DeniK on Jun 20, 2012 11:49 PM
    Edited by: DeniK on Jun 23, 2012 12:05 PM
    Edited by: DeniK on Jun 25, 2012 1:55 PM

    I've created the definition files and compared them. They are absolutely identical, apart from source and target schema names:
    Source definition file:
    Definition for table MY_SOURCE_SCHEMA.TABLE1
    Record length: 1632
    Syskey: 0
    Columns: 30
    USERID 134 11 0 0 0 1 0 8 8 8 0 0 0 0 1 0 1 3
    USERNAME 64 80 12 0 0 1 0 80 80 0 0 0 0 0 1 0 0 0
    FIRSTNAME 64 160 98 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
    LASTNAME 64 160 264 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
    PASSWORD 64 160 430 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
    TITLE 64 160 596 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
    Target definition file:
    Definition for table MY_TAEGET_SCHEMA.TABLE1
    Record length: 1632
    Syskey: 0
    Columns: 30
    USERID 134 11 0 0 0 1 0 8 8 8 0 0 0 0 1 0 1 3
    USERNAME 64 80 12 0 0 1 0 80 80 0 0 0 0 0 1 0 0 0
    FIRSTNAME 64 160 98 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
    LASTNAME 64 160 264 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
    PASSWORD 64 160 430 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
    TITLE 64 160 596 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
    Edited by: DeniK on Jun 25, 2012 1:56 PM
    Edited by: DeniK on Jun 25, 2012 1:57 PM

  • File_To_RT data truncation ODI error ORA-12899: value too large for colum

    Hi,
    Could you please provide me some idea so that I can truncate the source data grater than max length before inserting into target table.
    Prtoblem details:-
    For my scenario read data from source .txt file and insert the data into target table.suppose source file data length exceeds max col length of the target table.Then How will I truncate the data so that data migration will be successful and also can avoid the ODI error " ORA-12899: value too large for column".
    Thanks
    Anindya

    Bhabani wrote:
    In which step you are getting this error ? If its loading step then try increasing the length for that column from datastore and use substr in the mapping expression.Hi Bhabani,
    You are right.It is for Loading SrcSet0 Load data.I have increased the column length for target table data store
    and then apply the substring function but it results the same.
    If you wanted to say to increase the length for source file data store then please tell me which length ?Physical length or
    logical length?
    Thanks
    Anindya

  • Error CL_TAO_GUI_SESSION_SM- Create: Mandatory Attribute missing for Technical RFC destination

    hai
    We have installed solution manager and CBTA for test automation. For SUT , We have created Technical RFC for development client and quality client
    as TST_BID_CLNT220 and TST_BID_CLNT_909 respectively.  Similarly SMBID_CLNT_220 and SMBIQ_CLNT_909 are the business RFC destination to connect SUT.
    Now I have created test System data container which have both target system (Quality and development) . I have also created Test profile
    for both . In the Test Profile I have mentioned Techinical RFC name , Test profile name, business user and password.
    I have record va01 tcode in development client. The same script is used for quality also .
    I am able to execute the script in development . But when I execute for quality it is giving following error
    Error CL_TAO_GUI_SESSION_SM->Create: Mandatory Attribute missing for Technical RFC destination TST_BIQ_CLNT909
    Can any one help me . Pls tell me whether I followed the steps correctly
    Regards
    Jaya

    Hi,
    It will be very difficult to solve without being on the customer site and having all information.
    Right now, the error code is network error...
    Kind regards,
    Yann

  • Overlapping values were maintained for characteristic Cost Element

    Dear SAP Gurus,
    I am Finding one error while chaing my Primary Cost Planning in CJ40. The error note as follows.
    *"Overlapping values were maintained for characteristic Cost Element*
    *Message no. K9050
    Diagnosis
    You maintained several characterisic values for characteristic Cost Element in layout maintenance or in the entry screen for planning.
    Within these characteristic values
    individual values appear more than once
    individual values are included in an inteval
    intervals overlap
    These duplications and overlaps are not forseen in planning.
    System Response
    The entries for characteristic Cost Element are rejected.
    Procedure
    Change the entries in the layout maintenance/entry screen for planning."
    Please help.
    Rgds
    Rohit

    Hi,
    Step1. Go to CJ40.
    enter in the cost planning area->Select the topmost line item->Primary cost.
    Then Extras->Group Display--> Cost element
    Is it the same what you have checked in the KAH2?
    Step2: Then check Extras---> Error Log
    Step3: Then check Extras--->Diplay Profile
    Step4: Now Go to Tcode: KP34 and check the layout assigned to WBS elements: Cost element/acty inputs and make sure the check mark is present against it in item column.
    Step 5: Now check Extras--> Display Profile.
    Make sure its same as that of Step4.
    Hope its useful.
    Reward points if useful.
    Thanks..

  • Number range missing for characteristic 0AF_SEAN after importing request

    Hii friends,
    I m facing one problem while transporting request from development to quality , the request contains info object 0MATERIAL in which i have added new attribute 0AF_SEAN.
    Then error which i m getting is ,
    Number range interval for characteristic 0AF_SEAN is missing
    Error when activating InfoObject 0MATERIAL
    Characteristic 0MATERIAL: Error when generating master data routines
    Error when resetting InfoObject 0MATERIAL to the active version
    I am waiting for ur positive reply.
    Thanks & Regds,
    Kavan Shah

    hi Kavan,
    try
    transaction rsrv ? >> all elementry tests >> master data >> compare number range and maximum sid >> execute. press button 'correct error' if any error exists
    Error calling number range object 0MATERIAL for dimension D4 ( )
    or check oss note 903291 ?
    Manual solution
    Get the name of the number range object from the error message shown above, for example, RS_OBJNUMG. Start Transaction SNRO. To display the intervals, use the number range function key and enter the name of the number range object as the object name. Change the intervals. The following from-numbers and to-numbers apply:
    - RS_OBJNUMG: 0000001 - 9999000
    - RSDDAGCUBE: 100000 - 199999
    - RSSBRAUTH: 00000001 - 99999999
    BW 3.0B
    Import Support Package 30 for 3.0B
    BW 3.10 Content
    Import Support Package 24
    BW 3.50
    Import Support Package 16
    BW 7.0
    Import Support Package 07
    Transporting DataSources
    hope this helps.

  • I am trying to send data from textfield to database but it is showing error "ORA-12899: value too large for column "HR"."DOCTORS"."NAME" (actual: 658, maximum: 20)"

    Although i am entering only one character into the textfield then too it is reflecting the same error.
    private void initEvents()
      okButton.addActionListener(new ActionListener() {
      public void actionPerformed(ActionEvent e) {
      Connection conn = null;
        Statement stmt = null;
        try{
           //STEP 2: Register JDBC driver
           Class.forName("oracle.jdbc.driver.OracleDriver");
           //STEP 3: Open a connection
           System.out.println("Connecting to database...");
           conn = DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","hr","hr");
           //STEP 4: Execute a query
           System.out.println("Creating statement...");
           stmt = conn.createStatement();
           System.out.println(txtField);
           String sql = "INSERT INTO DOCTORS VALUES ('"+txtField+"','"+textField_1+"','"+textField_1+"','"+textField_2+"','"+textField_3+"')";
           JOptionPane.showMessageDialog(null,"Inserted Successfully!");
           ResultSet rs = stmt.executeQuery(sql);
           rs.close();
           stmt.close();
           conn.close();
        }catch(SQLException se){
           //Handle errors for JDBC
           se.printStackTrace();
        }catch(Exception e1){
           //Handle errors for Class.forName
           e1.printStackTrace();
        }finally{
           //finally block used to close resources
           try{
              if(stmt!=null)
                 stmt.close();
           }catch(SQLException se2){
           }// nothing we can do
           try{
              if(conn!=null)
                 conn.close();
           }catch(SQLException se){
              se.printStackTrace();
           }//end finally try
        }//end try

    What is a the size of the text you are trying to insert?
    Have you tried the increasing the size of 'Name' column to 658?
    Most likely the size of Name column is 20. This isn't enough to fit in the value you are trying to insert.
    You can increase the size of the Name column with alter table Hr.doctors modify ( Name column_type (658));
    Let me know if this helps.
    Regards,
    Suntrupth

  • Inserted value too large for column error while scheduling a job

    Hi Everyone,
    I am trying to schedule a PL SQL script as a job in my Oracle 10g installed and running on Windows XP.
    While trying to Submit the job I get the error as "Inserted value too large for column:" followed by my entire code. The code is correct - complies and runs in Oracle ApEx's SQL Workshop.
    The size of my code is 4136 character, 4348 bytes and 107 lines long. It is a code that sends an e-mail and has a +utl_smtp.write_data([Lots of HTML])+
    There is no insert statement in the code whatsoever, the code only queries the database for data...
    Any idea as to why I might be getting this error??
    Thanks in advance
    Sid

    The size of my code is 4136 character, 4348 bytes and 107 lines long. It is a code that sends an e-mail and has a utl_smtp.write_data(Lots of HTML)SQL variable has maximum size of 4000

  • Error : Tax statement item missing for tax code

    Hello Gurus,
    I have issue while releasing a billing document to accounting from VF02. The error says 'Tax statement item missing for tax code AA'
    Any idea??
    Prase

    Dear Prasanth,
    Please review note 112609 and 400766 carefully, which explain the
    tax rules.
    The FF805 error is most likely triggered due to configuration in
    the pricing procedure.
    If an active tax condition record is found (for example on UTXJ), even
    though it is statistical, the tax code (linked to the record) is then
    distributed to the active price conditions for that item pricing.
    When it passes to FI, the active tax condition is passed but not
    the price because an active price condition cannot be found.
    In the SD-FI interface, for every price condition sent over,
    there MUST be a tax condition sent over, hence the FF805.
    I think may be what is happening in your case.
    If after setting reference steps in your procedure according to the
    guidelines in 112609, you still encounter the FF805, please let me know.
    Hope this is helpful. Thank you.

  • Input Value long enough for date format ,Error in executing parallel query

    Hi,
    My Table: ANML( ID, STATUS,B_DATE,B_MONTH,B_YEAR, DEATH_DATE)
    status 1 for alive and 2 for dead.
    i wrote a view to get age.
    as
    create or relace view view1 as
    select top."ID",top."STATUS",top."DOB",top."DEATH_DATE",top."ANML_AGE",top."DAYSDIFF",
    CASE
    WHEN anml_age < 1
    THEN 'D'
    ELSE 'M'
    END age_unit,
    CASE
    WHEN anml_age < 1
    THEN TO_CHAR (daysdiff || ' Day(s)')
    WHEN anml_age < 12
    THEN TO_CHAR (anml_age || ' Month(s)')
    WHEN MOD (anml_age, 12) = 0
    THEN TO_CHAR (ROUND (anml_age / 12, 0) || ' Year(s) '
    ELSE TO_CHAR ( ROUND (anml_age / 12, 0)
    || ' Year(s) '
    || MOD (anml_age, 12)
    || ' Month(s)'
    END age_string
    from
    (SELECT a.*,
    CASE WHEN status IN ( 1)
    THEN FLOOR(MONTHS_BETWEEN(TRUNC(SYSDATE),dob))
    WHEN death_date IS NOT NULL AND status IN (2)
    THEN FLOOR(MONTHS_BETWEEN(death_date,dob))
    END anml_age,
    CASE WHEN status IN (1)
    THEN FLOOR(TRUNC(SYSDATE)-TRUNC(dob))
    WHEN death_date IS NOT NULL AND status IN (2)
    THEN FLOOR(TRUNC(death_date) - TRUNC(dob))
    END daysdiff
    from (
    SELECTanml.id, status,
    TO_DATE ( DECODE (b_date,
    NULL, 1,
    b_date
    || '-'
    || DECODE (b_month,
    NULL, 1,
    b_month
    || '-'
    || b_year,
    'dd-mm-yyyy'
    ) DOB,
    death_date
    FROM anml
    WHERE b_year IS NOT NULL
    ) a) top
    when i tried to fetch all values from view its working fine.
    But when i tried to fetch values based on condition like as follows,
    select * from view1 where anml_age > 20 and anml_age<30
    I am getting error like:
    Input Value long enough for date format and Error in executing parallel query
    Please tell me wht is wrong.

    Here is your formatted code
    create or relace view view1 as
    select top."ID",top."STATUS",top."DOB",top."DEATH_DATE",top."ANML_AGE",top."DAYSDIFF",
    CASE
    WHEN anml_age < 1
    THEN 'D'
    ELSE 'M'
    END age_unit,
    CASE
    WHEN anml_age < 1
    THEN TO_CHAR (daysdiff || ' Day(s)')
    WHEN anml_age < 12
    THEN TO_CHAR (anml_age || ' Month(s)')
    WHEN MOD (anml_age, 12) = 0
    THEN TO_CHAR (ROUND (anml_age / 12, 0) || ' Year(s) '
    ELSE TO_CHAR ( ROUND (anml_age / 12, 0)
    || ' Year(s) '
    || MOD (anml_age, 12)
    || ' Month(s)'
    END age_string
    from
    (SELECT a.*,
    CASE WHEN status IN ( 1)
    THEN FLOOR(MONTHS_BETWEEN(TRUNC(SYSDATE),dob))
    WHEN death_date IS NOT NULL AND status IN (2)
    THEN FLOOR(MONTHS_BETWEEN(death_date,dob))
    END anml_age,
    CASE WHEN status IN (1)
    THEN FLOOR(TRUNC(SYSDATE)-TRUNC(dob))
    WHEN death_date IS NOT NULL AND status IN (2)
    THEN FLOOR(TRUNC(death_date) - TRUNC(dob))
    END daysdiff
    from (
    SELECTanml.id, status,
    TO_DATE ( DECODE (b_date,
    NULL, 1,
    b_date
    || '-'
    || DECODE (b_month,
    NULL, 1,
    b_month
    || '-'
    || b_year,
    'dd-mm-yyyy'
    ) DOB,
    death_date
    FROM anml
    WHERE b_year IS NOT NULL
    ) a) top

  • Tax statement item missing for tax code A0

    I got intercompany billing that has not been released to accounting, when I tried to release to accounting got this error message :
    Field Profit Ctr is a required field for G/L account 6000 14112100
    Message no. F5808
    Diagnosis
    The value for field "Profit Ctr" in the interface to Financial Accounting is an initial value but you are required to make an entry in the field selection for G/L account "14112100" in company code "6000" linked to the field selection for posting key "50".
    System response
    Error
    Procedure
    It might be an error in the configuration of the G/L account field selection. The initial application, used to call up the interface must otherwise define a value for field "Profit Ctr". If this is the case, contact the consultant responsible for the application used to call up the interface or get in contact with SAP directly.
    when I looked at it because IV01 in billing document is empty and PI01 in sales document is empty, when I tried to add the value IV01 in intercompany billing manually and tried to release again got this error message:
    Tax statement item missing for tax code A0
    Message no. FF805
    Diagnosis
    No tax item exists for tax code A0 in a G/L account item. A possible cause is an incorrect transfer of parameters by the application to the Accounting interface.
    Procedure
    Enter an OSS message.
    Can someone help please? I can't correct the SO and DO because it's in the past already can't be reversed.
    regards,
    Dwi

    Hi,
    Please check the following note
    Note 971253 - Causes for error message FF805 in SD
    I hope it will help you.
    Regards,
    Jigar

Maybe you are looking for