Vendor number in General ledger

Hello team,
we are in ECC 6.0
we need vendor number in general ledger report fagll03
in the layout of FAGLL03 it is available. but it is not updating the field with vendor number.
how can i get.

It will not be displayed in the general ledger, you go the reconciliation account of the vendor and execute for the period required. Now you can see the vendor in the field of assignment, if the field is not available then add the field from change layout button in fbl3n.
In FAGLL03 and double click it will take you to line item display, where you can see the vendor code in assignment field.

Similar Messages

  • How to update check number in general ledger and vendor ledger automatical

    Dear All,
    i need some clarification in check updation in general ledger and Vendor ledger through the  system automatically.
    While making vendor payment system will not update check details in vendor ledger and bank GL code.while doing  bank reconcilation its very difficult to identify check no and amount for that we have updating manually but its time taking. Is there any program or any enahancement for updating check number in general ledger and vendor ledger.
    Kindly suggest me how to update check number . Is there any programm or enahancement for check updation.kindly suggest me.
    Thanks in advance
    Thanks and Regards

    If I am understanding correctly what you are wanting is to be able to see the check number for the payment document in both FBL1N and FAGLL03.
    Special fields for AP line item reporting can be configured via IMG. Define additional fields for line item display> 
    Not all fields are available, but this one is.  Add this entry, you can also add check encashment date if desired.
    PAYR  table name.
    CHECF Field name
    After these fields are saved, they can be selected in the line item layout on FBL1N.
    You may also need to reset the ALV buffer using program BALVBUFDEL
    Resetting the buffer is only necessary once in each client.
    Hope this helps.

  • Reg: how to see the vendor details and general ledger details in tables

    HI all
    how to see the vendor details and general ledger details in tables.
    JK Rao

    General ledger transactions are available in following table;
    1. BKPF & BSEG
    2. BSIS - Open Items
    3. BSAS - Cleared Itesm
    For vendor
    1. BSIK - Open Items
    2. BSAK - Cleared Items
    For Customers
    1 BSID - Open Items
    2. BSAD - Cleared Items
    Rakesh Pawaskar

  • What is the system variables of document number in General Ledger PLD?

    Dear all,
    Would anybody kindly tell me what is the system variables of document number in General Ledger Print Layout Designer?
    The default print layout use transaction number (system variables 272), however, my client wants document number to be displayed in the transaction number column.
    Simon Chiu

    The only list available for Supported variables is for the version 2007A and for some specific localizations like Brazil and India.
    For the 2007A version the list is available in the following link:
    'How To Use the PLD Variables File in Release 2007 A '
    But in general the variables are for documents not for reports.
    In this case I believe there's no variable and you may need to fill a requirement in the Forum for that.
    Paulo Calado
    SAP Business One Forums Team

  • In General Ledger report i want "cheque Number" Column

    Hi All,
    I am seeing General Ledger report in-built in sap B one 2005 for one single bank G/L A/C. i want one column in this report "Cheque Numbers" which is posting in Outgoing Payment, any body help on this.

    please go to form setting and make visible "Ref. 3"
    u will get the number
    please let me know if it does not work
    Avtar singh Saini .

  • How to identify the open items of vendor/customers/general ledger

    i would like to know the t.code for identifing the user wise open items for vendor/customer/general ledger.

    You can use frequently used reports like FBL1N for vendors, FBL3N for GL and FBL5N for customer. You can exeucte open item report and drag Username field from the layout and sort the report in ascending or descending order.
    Chintan Joshi

  • Display the Customer/Vendor Name in the General Ledger Report

    **I have Questions about General Ledger Report in SAP Business One. How can Display the Customer/Vendor Name in the General Ledger Report.**
    *Just would like to ask if its possible to display the Customer/Vendor Name in the General Ledger Report? The format simply have the Customer/Vendor Code on the said report. Is there a work around on this?*

    If ur selection creteria by g/l account,u can display customer/vendor name by including
    offset account from form settings.

  • The Customer/Vendor Name in the General ledger Report Form.

    I have Questions about General Ledger Report in SAP Business One. Display the Customer/Vendor Name in the General Ledger Report.
    Just would like to ask if its possible to display the Customer/Vendor Name in the General Ledger Report? The format simply have the Customer/Vendor Code on the said report. Is there a work around on this?
    Please help me.

    In the Standard Reports, you cannot add a new column.
    As mentioned by me earlier, please check 'Offset Account Name' column in the Form Settings if the same is of help in your case.
    You can check Note No. [1045356|] regarding the issue. The same has been fixed in 2005 A PL23.
    Kind Regards,
    SAP Business One Forum Team

  • Document number ranges in entry view and in General Ledger view

    What is the difference between Document number ranges in entry view and in General Ledger view ?
    We have new GL activated in our system , and  found that the  GL Document types ( SA) are assigned to document number ranges in entry view . What is the need to define document number ranges in General Ledger view ?

    Document Number Range in entry view is the document numbers which are posting in your leading ledger. You cant achieve the same document number range to the general ledger view. A General ledger view can have both Leading ledger view and non leading ledger view therefore document number range should not be kept same for both ledgers as your running document number gets skipped.
    That to some times you can only post documents to only Non Leading ledgers. Therefore a separate number ranges needs to be created for general ledger view
    Hope u understood.
    Edited by: boddupalli srikanth on May 21, 2009 9:28 PM

  • General ledger Number (Field) In purchase requisition

    Dear Group Members Warm Greeting
    In purchase requisition my users changes the general ledger number which come by default by entering the material number as the field is not in gray ( suppress )
    Expert advice needed to fix the issue not to change by the user & the field should be suppressed
    let me know the configuration  

    Go to OME9 and make general ledger account in display mode for your account assignment

  • Post vendor invoice to leading ledger

    Dear all,
    We have 2 ledgers, one is leading.
    I want to post invoice to leading ledger by FB01L but this error occurred:
    Postings to ledger 0L not permitted with account type K
    Message no. FAGL_POST_SERVICE034
    I checked Define doc type for general ledger view but hit this error:
    Leading ledger does not require its own document number
    Message no. FAGL_POST_SERVICE016
    Please advise for how could I post transactions with vendors to leading ledger.
    Thank you a lot.

    Error message you encountered is FAGL_POST_SERVICE034.
    The problem is caused by the GL account:
    If the GL account to which the posting is made is open item managed,
    then it is not possible (due to technical constraints) to post to
    a single ledger or a ledger group only: The posting must be made
    to all ledgers.
    The alternatives to solve the problem are:
    1) Change the IMG settings of the Real-Time Integration of Controlling
       with Financial Accounting so that the posting in FI is done
       not a group of ledgers, but to all ledgers in FI:
       Let the field 'Ledger Group (FI)' empty.
    2) Do not use customer and vendor accounts as company code clearing
       accounts, but use ordinary GL accounts instead.
    And Please go through the below points.
    As by SAP standard, ledger 0L is always the leading ledger, so posting
    to 0L results in posting to all ledgers. If you post a document to a
    non-leading ledger or ledger-group not containing the leading ledger,
    you could achieve via FB50L or FV50L.
    Madhu M

  • General ledger / sub ledger reconciliation, without new GL:

    Hi experts, hope you can help me with this quick question:
    My client is currently reconciling SAP General Ledger  and Subledger balances in excel spreadsheets, for Customer and Vendors.
    The reconciliation is as follows, when the postings are done on general ledger on a reconciliation account and on the correspondent sub ledger, the line items have to be checked on both to be sure that transfer has been done correctly. Currently this process if done by a Vlookup in Excel, using the reference number as join between the data extracted.
    We are running ECC6.0, without the new GL, do you know if there is a standard program to make this reconciliation, I will appreciate any documentation about this topic.
    Thanks in advance.

    Firstly, why would there be any difference between the total of customer/vendor sub-ledger balances and the balance on the reconciliation account(s)?  The posting to the reconciliation account is happening automatically right, when you are posting to a customer/vendor (basing on the reconciliation account assigned in the customer/vendor master)?  And system would not allow direct postings to reconciliation accounts, which eliminates the threat of reconciliation GL account going out of balance as compared to the sub-ledger accounts.
    However, you can run FBL3N or FS10N for the reconciliation account(s) and match it with the total balance on all customers/vendors using transaction FBL5N/FBL1N.

  • General Ledger Accounting (New): Line Items 0FIGL_O14  Performace issue

    Dear Forum,
    We are facing a performance issue while loading the data to 0FIGL_O14 General Ledger Accounting (New): Line Items from  CUBE ZMMPRC01 -> ODSO 0FIGL_O14 DSO.
    Please see my requirement below for updating the data to 0FIGL_O14 DSO.
    This report is generated to display Dry Dock and Running Repair expenses for the particular Purchase orders with respective G/L's.
    1) The G/L DSO will provide us the 0DEBIT_LC and    0DEB_CRE_DC Foreign currency amount with signs (+/-) amounts and.
    2) ZMMPRC01 Cube   will provide us the 0ORDER_VALUE  (Purchse order value)and    0INVCD_AMNT Invoice  amount.
    While we are loading the data from  CUBE ZMMPRC01 -> ODSO 0FIGL_O14 DSO ,we have created nearly 19 InfoObject  level routine to derive the below mentioned fields data for MM Purchase Order related records.
    0CHRT_ACCTS    Chart of accounts
    0ITEM_NUM      Number of line item within accounting documen
    0AC_DOC_NO     Accounting document number
    0GL_ACCOUNT    G/L Account
    0COMP_CODE     Company code
    0COSTCENTER    Cost Center
    0CO_AREA       Controlling area
    0COSTELMNT     Cost Element
    0SEGMENT       Segment for Segmental Reporting
    0BUS_AREA      Business area
    0FUNC_AREA     Functional area
    0AC_DOC_NR     Document Number (General Ledger View)
    0AC_DOC_TYP    Document type
    0POST_KEY      Posting key
    0PSTNG_DATE    Posting date in the document
    0DOC_CURRCY    Document currency
    0LOC_CURTP2    Currency Type of Second Local Currency
    0CALQUART1     Quarter
    0CALYEAR       Calendar year
    For reference Please see the below logic to derive the data for PO related record.
          MONITOR_REC    TYPE rsmonitor.
    $$ begin of routine - insert your code only below this line        -
        ... "insert your code here
        types : begin of ty_FIGL,
                    CHRT_ACCTS type /BI0/OICHRT_ACCTS,
                    ITEM_NUM type /BI0/OIITEM_NUM,
                    AC_DOC_NO type /BI0/OIAC_DOC_NO,
                    GL_ACCOUNT type /BI0/OIGL_ACCOUNT,
                end of ty_FIGL.
        data :it_figl type STANDARD TABLE OF ty_figl,
              wa_figl type ty_figl.
        SELECT single CHRT_ACCTS
                        GL_ACCOUNT from /BI0/AFIGL_O1400
                          into wa_figl
                          where DOC_NUM = SOURCE_FIELDS-DOC_NUM and
                                DOC_ITEM = SOURCE_FIELDS-DOC_ITEM and
                                /BIC/Z_PCODE = SOURCE_FIELDS-/BIC/Z_PCODE
                                /BIC/Z_VOY_NO = SOURCE_FIELDS-/BIC/Z_VOY_NO
                                FISCYEAR = SOURCE_FIELDS-FISCYEAR.
        if sy-subrc = 0.
          RESULT = wa_figl-AC_DOC_NO.
        clear wa_figl.
    Please note the same kind of logic is applied for all the above mentioned fields.
    Here is my concerns and issue.
    For the all above all routines i am referring BI0/AFIGL_O1400
    DSO and finally loading to the Same DSO(BI0/AFIGL_O1400
    The worried part is my DSO  0FIGL_O1400 is currecnly having nearly 60 Lacks records and MM cube is having nearly 55 requests which are required to update to the Above DSO for PO related PO value and Invoice amount.
    The big issue here is while uploading data from MM cube to DSO say for example if the request is having  25,000 records from this  nearly 500-600 records will be updated to DSO.
    But here it is taking huge time ( nearly 3 days for request ) for updating  these records , like this i have to pull 50 more requests from Cube to DSO as per the requirement.
    Please note as of now i haven't created any indexes on DSO to improve this loads.
    Please note am facing this issue in Production environment and need your help ASAP.
    Thanks & Regards,
    Srinivas Padugula

    If selecting data from 0FIGL_O14 is taking long time then you can create secondary indexes on DSO.
    0FIGL_O14 would be huge as data volume directly corresponds to data volume in BSEG.
    But for you requirement, I think what you can do is,
    1. create multiprovider on top of DSO and Cube and create Bex report to give you the fields requried from both the infoproviders, you can then use open hub or APD approach to keep the data in the staging table or direct update DSO and then load the data to the DSO
    2. Create secondary indexes on DSO so that fetching would be faster.
    3. Do the enhancment at R/3 level to fetch fields from MM during load of G/L
    Pravin Karkhanis.

  • Reviewing General Ledger Accounts - No line item detail

    I have just started with a new company using SAP Business One for the first time. My frustration is when reviewing the general ledger line items that there is no detail coming through that lets me see what the amounts relate to.  No Description or Vendor  Name.  There is absolutely no way I can see if there are any posting errors to accounts unless I drill into each and every line item to see what it is.  I have been into Form Settings but the fields required are not available options to select.
    Every accounting system I have ever used has this standard feature - from off the shelf packages to customised SAP R/3. 
    I have spoken to the Implementation Company's Support Line and they have said that it would be a costly exercise to request a report that provides this information. 
    I can't accept that this is standard - why would anyone use the system????
    I guess I just want to hear that this is not the norm with SAP Business One

    Try the General Ledger Report, there is a little more detail there - the BP Name is, I'm sure, included in that and you still get the drill down.
    In the account balance screen, you can add the "Details" field which may give you more information as it usually contains the BP Code. It is not a difficult exercise for you support team to add a formatted search to populat that with the account name instead - it is a reasonably common customisation.

  • Release-12.1.1. General Ledger-Mass Allocation-Error

    I have entered formula for Mass Allocation and I got Valdiated. While I running the Mass Allocation I got an
    error. In the View Output File. "Failure detected. Please see log file." When I seeing the Log file. I got the error
    GLAMAS module: Run MassAllocations
    Current system time is 01-OCT-2009 09:02:38
    glamai() 01-OCT-2009 09:02:38**************************************************
    01-OCT-2009 09:02:38
    AMAS0010: General Ledger MassAllocations Log File
    command_mode = C
    access set id = 1017
    incremental mode = N
    average journal flag = N
    ledger id override value = 1
    ledger override currency = USD
    balance segment override value = 02
    allocation batch id = 10079
    period = Jan-09
    journal effective date = 2009/01/31 00:00:00
    calc effective date = 2009/01/31 00:00:00
    glasob() 01-OCT-2009 09:02:38
    gluini() 01-OCT-2009 09:02:38
    glugsn() 01-OCT-2009 09:02:38<< glugsn() 01-OCT-2009 09:02:38
    << gluini() 01-OCT-2009 09:02:38
    accounted period type = Month
    chart_of_accounts_id = 101
    number of flexfield segments = 5
    balancing segment name = SEGMENT1
    management segment name = NA
    security segment name = NA
    flexfield delimiter = '-'
    active segments =
    flex value sets =
    account segment = SEGMENT3
    account segment length= 5
    flexfield length = 21
    << glasob() 01-OCT-2009 09:02:38
    glasys() 01-OCT-2009 09:02:38***********************************************
    * Warning: profile option has not been set up:*
    * GL: Number of Records to Process at Once *
    * Warning: profile option has not been set up:*
    * GL: Number of Accounts In Memory *
    foundation user id = 1013417
    foundation user name = ZUNAITHA
    concurrent request id = 5807601
    number of target records to process at a time = 1000
    number of flexfields to cache = 2500
    cache control segment = SEGMENT3
    length of control segment = 5
    length of flexfield = 21
    << glasys() 01-OCT-2009 09:02:38
    glavcmd() 01-OCT-2009 09:02:38SHRD0117: Inserted 1 record(s) into gl_alloc_history
    << glavcmd() 01-OCT-2009 09:02:38
    glacab() 01-OCT-2009 09:02:38glacab() - tf = 1, sqlerrd[2] = 1
    glacab--loopcnt = 1 and size 2b Malloced is 984
    << glacab() 01-OCT-2009 09:02:38
    glapst() 01-OCT-2009 09:02:38glapst() - pst0_stmt.arr =
    SELECT period_name,
         to_char(start_date, 'YYYY/MM/DD'),
         to_char(end_date, 'YYYY/MM/DD'),
    FROM gl_periods
    WHERE      period_set_name ='Accounting'
    AND period_type ='Month'
    ORDER BY period_year, period_num
    AMAS0025: glapst() - Found 225 periods (COA=101)
    control->coa_rec.pstat[0].period_name = Dec-95
    control->coa_rec.pstat[0].start_date = 1995/12/01
    control->coa_rec.pstat[0].end_date = 1995/12/31
    control->coa_rec.pstat[0].jstart_date = 2450053
    control->coa_rec.pstat[0].jend_date = 2450083
    control->coa_rec.pstat[0].period_type = Month
    control->coa_rec.pstat[0].period_year = 1995
    control->coa_rec.pstat[0].period_num = 12
    control->coa_rec.pstat[1].period_name = Adj-95
    control->coa_rec.pstat[1].start_date = 1995/12/31
    control->coa_rec.pstat[1].end_date = 1995/12/31
    control->coa_rec.pstat[1].jstart_date = 2450083
    control->coa_rec.pstat[1].jend_date = 2450083
    control->coa_rec.pstat[1].period_type = Month
    control->coa_rec.pstat[1].period_year = 1995
    control->coa_rec.pstat[1].period_num = 13
    control->coa_rec.pstat[2].period_name = Jan-96
    control->coa_rec.pstat[2].start_date = 1996/01/01
    control->coa_rec.pstat[2].end_date = 1996/01/31
    control->coa_rec.pstat[2].jstart_date = 2450084
    control->coa_rec.pstat[2].jend_date = 2450114
    control->coa_rec.pstat[2].period_type = Month
    control->coa_rec.pstat[2].period_year = 1996
    control->coa_rec.pstat[2].period_num = 1
    control->coa_rec.pstat[3].period_name = Feb-96
    control->coa_rec.pstat[3].start_date = 1996/02/01
    control->coa_rec.pstat[3].end_date = 1996/02/29
    control->coa_rec.pstat[3].jstart_date = 2450115
    control->coa_rec.pstat[3].jend_date = 2450143
    control->coa_rec.pstat[3].period_type = Month
    control->coa_rec.pstat[3].period_year = 1996
    control->coa_rec.pstat[3].period_num = 2
    control->coa_rec.pstat[4].period_name = Mar-96
    control->coa_rec.pstat[4].start_date = 1996/03/01
    control->coa_rec.pstat[4].end_date = 1996/03/31
    control->coa_rec.pstat[4].jstart_date = 2450144
    control->coa_rec.pstat[4].jend_date = 2450174
    control->coa_rec.pstat[4].period_type = Month
    control->coa_rec.pstat[4].period_year = 1996
    control->coa_rec.pstat[4].period_num = 3
    control->coa_rec.pstat[5].period_name = Apr-96
    control->coa_rec.pstat[5].start_date = 1996/04/01
    control->coa_rec.pstat[5].end_date = 1996/04/30
    control->coa_rec.pstat[5].jstart_date = 2450175
    control->coa_rec.pstat[5].jend_date = 2450204
    control->coa_rec.pstat[5].period_type = Month
    control->coa_rec.pstat[5].period_year = 1996
    control->coa_rec.pstat[5].period_num = 4
    control->coa_rec.pstat[6].period_name = May-96
    control->coa_rec.pstat[6].start_date = 1996/05/01
    control->coa_rec.pstat[6].end_date = 1996/05/31
    control->coa_rec.pstat[6].jstart_date = 2450205
    control->coa_rec.pstat[6].jend_date = 2450235
    control->coa_rec.pstat[6].period_type = Month
    control->coa_rec.pstat[6].period_year = 1996
    control->coa_rec.pstat[6].period_num = 5
    control->coa_rec.pstat[7].period_name = Jun-96
    control->coa_rec.pstat[7].start_date = 1996/06/01
    control->coa_rec.pstat[7].end_date = 1996/06/30
    control->coa_rec.pstat[7].jstart_date = 2450236
    control->coa_rec.pstat[7].jend_date = 2450265
    control->coa_rec.pstat[7].period_type = Month
    control->coa_rec.pstat[7].period_year = 1996
    control->coa_rec.pstat[7].period_num = 6
    control->coa_rec.pstat[8].period_name = Jul-96
    control->coa_rec.pstat[8].start_date = 1996/07/01
    control->coa_rec.pstat[8].end_date = 1996/07/31
    control->coa_rec.pstat[8].jstart_date = 2450266
    control->coa_rec.pstat[8].jend_date = 2450296
    control->coa_rec.pstat[8].period_type = Month
    control->coa_rec.pstat[8].period_year = 1996
    control->coa_rec.pstat[8].period_num = 7
    control->coa_rec.pstat[9].period_name = Aug-96
    control->coa_rec.pstat[9].start_date = 1996/08/01
    control->coa_rec.pstat[9].end_date = 1996/08/31
    control->coa_rec.pstat[9].jstart_date = 2450297
    control->coa_rec.pstat[9].jend_date = 2450327
    control->coa_rec.pstat[9].period_type = Month
    control->coa_rec.pstat[9].period_year = 1996
    control->coa_rec.pstat[9].period_num = 8
    control->coa_rec.pstat[10].period_name = Sep-96
    control->coa_rec.pstat[10].start_date = 1996/09/01
    control->coa_rec.pstat[10].end_date = 1996/09/30
    control->coa_rec.pstat[10].jstart_date = 2450328
    control->coa_rec.pstat[10].jend_date = 2450357
    control->coa_rec.pstat[10].period_type = Month
    control->coa_rec.pstat[10].period_year = 1996
    control->coa_rec.pstat[10].period_num = 9
    control->coa_rec.pstat[11].period_name = Oct-96
    control->coa_rec.pstat[11].start_date = 1996/10/01
    control->coa_rec.pstat[11].end_date = 1996/10/31
    control->coa_rec.pstat[11].jstart_date = 2450358
    control->coa_rec.pstat[11].jend_date = 2450388
    control->coa_rec.pstat[11].period_type = Month
    control->coa_rec.pstat[11].period_year = 1996
    glamtt() - sqlcode alloc-target drop table = 942
    glamtt() - mtt_stmt.arr is
    CREATE TABLE gl_alloc_target_5807601 (
         allocation_formula_id number(15) not null,
         request_id number(15) not null,
         entered_amount number not null,
         accounted_amount number not null,
         je_batch_id number(15) not null,
         je_header_id number(15) not null,
         je_line_num number(15) not null,
         period_name varchar2(15) not null,
         accounting_date date not null,
         max_amount_flag VARCHAR2(1),
         description      varchar2(240),
         code_combination_id number(15),
         message_number      number(15),
         line_type VARCHAR2(1),
         ledger_id number(15),
         validation_error VARCHAR2(30),
         SEGMENT1      VARCHAR2(25),
         SEGMENT2 VARCHAR2(25),
         SEGMENT3 VARCHAR2(25),
         SEGMENT4 VARCHAR2(25),
         SEGMENT5 VARCHAR2(25),
         SEGMENT6 VARCHAR2(25),
         SEGMENT7 VARCHAR2(25),
         SEGMENT8 VARCHAR2(25),
         SEGMENT9      VARCHAR2(25),
         SEGMENT10      VARCHAR2(25),
         SEGMENT11      VARCHAR2(25),
         SEGMENT12      VARCHAR2(25),
         SEGMENT13      VARCHAR2(25),
         SEGMENT14      VARCHAR2(25),
         SEGMENT15      VARCHAR2(25),
         SEGMENT16      VARCHAR2(25),
         SEGMENT17      VARCHAR2(25),
         SEGMENT18      VARCHAR2(25),
         SEGMENT19      VARCHAR2(25),
         SEGMENT20      VARCHAR2(25),
         SEGMENT21      VARCHAR2(25),
         SEGMENT22      VARCHAR2(25),
         SEGMENT23      VARCHAR2(25),
         SEGMENT24      VARCHAR2(25),
         SEGMENT25      VARCHAR2(25),
         SEGMENT26               VARCHAR2(25),
         SEGMENT27               VARCHAR2(25),
         SEGMENT28               VARCHAR2(25),
         SEGMENT29               VARCHAR2(25),
         SEGMENT30               VARCHAR2(25))
    tablespace APPS_TS_INTERFACE
    PCTFREE 50
    STORAGE(initial 200K next 200K maxextents 121 pctincrease 0)
    gluddl() 01-OCT-2009 09:02:39<< gluddl() 01-OCT-2009 09:02:40
    glamtt() - sqlcode alloc target create table = 0
    glamtt() - mtt_stmt.arr is
    CREATE INDEX gl_alloc_target_5807601_n1
    on gl_alloc_target_5807601 (je_header_id)
    gluddl() 01-OCT-2009 09:02:40<< gluddl() 01-OCT-2009 09:02:40
    glamtt() - sqlcode alloc targets create n1 index = 0
    glamtt() - mtt_stmt.arr is
    CREATE INDEX gl_alloc_target_5807601_n2
    on gl_alloc_target_5807601 (allocation_formula_id, je_line_num)
    gluddl() 01-OCT-2009 09:02:40<< gluddl() 01-OCT-2009 09:02:40
    glamtt() - sqlcode alloc target create n2 index = 0
    << glamtt() 01-OCT-2009 09:02:40
    SHRD0119: Deleted 0 record(s) from GL_ALLOC_JE_ID_INT.
    sqlcaid: sqlabc: 0 sqlcode: 0 sqlerrml: 0
    ORA-00942: table or view does not exist
    sqlerrp:      sqlerrd: 0 0 0 0 0 538976288
    sqlwarn: sqltext:
    oracaid:      oracabc: 0
    oracchf: 0 oradbgf: 0 orahchf: 0 orastxtf: 0 orastxtl: 0
    orasfnmc: oraslnr: 0 orasfnml: 0
    orahoc: 0 ormoc: 0 oracoc: 0
    oranor: 0 oranpr: 0 oranex: 0
    SHRD0015: glamai failed:
    SHRD0033: Error Status: 0
    SHRD0103: Function warning number: -1
    glamai() - fatal sql error
    Process logging off database and exiting ...
    Can anyone help me in this regard

    Have a look on Metalink Doc ID: 857664.1

Maybe you are looking for