Auto Billing with T-code VF06

Hi Expert,
I use t-code VF06 (program RV60SBAT) for the automation of billing doc generatoin. There is a billing date in this t-code. As I know, the date should be set it for dynamic. How do I set this dynamically. Or just leave this date to "blank".
As I tested, I saved a variant which is the billing date is on the past. So when the job is finised, there is nothing created in the background job. Meaning that, there is no billing documents have been created right? And there is no list/log to monitor the created billing doc. right?
Thanks & regards,
Poi Yoke

Hi,
You can choose a dynamic variant following this instructions:
1) SE38
Program: RV60SBAT and choose Variants
2) Create Variant (Choose a name) and Create
3) Attributes
Billing date field ... Selection variable = 'D' and choose the rule (name of variable)
Rules:
Current Date
Current date +/- ??? days
current date +/- ??? work days
First day of current month
nth working day of current month
First day of next month
First day of previous month
Last day of previous month
Last Day of the Current Month
Regards
Leonardo Rocha

Similar Messages

  • Movie DVD auto ejects with "error code -43" message

    This issue first came up about 3 years ago but I was never able to find an answer to. This is a Combo drive (HL-DT-ST; RW/DVD GCC-4120B; revision 2.13) which still reads/writes CDs and reads DVD-ROMs without any problem. Is there any way to fix this error?

    There may be system logs, reports and other evidence of
    this issue in the Console or perhaps in System Profiler logs.
    Some other noted error code -43 messages seen elsewhere
    related to software and plugins for third party applications or
    disc burn applications; but troubleshooting could include a
    look to see if the cables to the optical drive are OK, and a
    fix may include a replacement drive. There was an included
    Apple Hardware Test with the original system software packet
    so that may be something to try and hope it tells you more.
    The error code may have several different causes, it would
    seem; at least according to the results of some searches.
    In my limited experience, my Macs have never shown that.
    The code is not limited to the model of the computer; so a
    repost elsewhere is not really necessary. And a similar error
    code appears in later OS X versions.
    Good luck & happy computing!

  • STO WITH OUT BILLING BETWEEN COMPANY CODES

    Hai experts,
       In my client , thy use following procedure for STO with out billing between company codes .
    First create purchase order in receving plant after that they sales order in supply plant by using purchase order ,manually.Here the end user change the qty and other details.So the client wants that , I want create sales order with respect to purchase order.
    give me suggestion

    7679,
    Your proposed solution sounds like a lot of unnecessary work.  A simple STO can usually meet all business requriements for either intra- or inter-company stock transfers, without adding the complexity of a sales doc.
    Why can't you use a standard 'U' Stock Transport order?
    Best Regards,
    DB49

  • Aggregated bill with multiple tax code

    Hi experts! I need information about aggregated bill with multiple tax code. Do you know something about or do you have some documentation? Regards Luke

    Luke,
    Taxes and additional account assignments are posted in the same way as standard postings at individual customer level in aggregated posting, when you create the aggregated bill.
    Thanks,
    Sai

  • I signed up for auto pay and just received my bill with last months bill and $5 late fee.  would like late fee reversed and last month credit applied.

    i signed up for auto pay and just received my bill with last months bill and $5 late fee.  would like late fee reversed and last month credit applied.

    << Duplicate post, see Re: Problems with Auto Pay Activation >>
    This discussion is over two years old and will be locked to further replies.

  • Auto bill Passing Of IV

    Sir/Mam ,
          In our company we are Trying the option of Auto bill passing of IV through a work around , That is running the BDC for IV . Although the Query I Post looks like Function Oriented Pls help me out if Possible .
    While making an LIV with refernce to Delivery note , the planned cost i.e the freight condition are not brought in , We also know that it can be done through bill of ladding refernce ,but we need to make the payment for the freight to the vendor account so he can settle with freight party later. If we proceed with refernce to the PO all the GR's whatver made are proposed , which we do not want , So pls advice me on how to proceed .
    Thanks in advance
    Harish

        Patfromcork
    I'm sorry to hear your plan was not set up as expected! We definitely want to make sure this is resolved quickly for you. This does sounds like an option with Auto Pay set up on a PrePaid ALLSET plan. Is that the plan you're on now? We only have access to Post Pay accounts on this site, so if this has not been resolved I do recommend reaching out to our PrePay Team directly.
    To reach our Prepay Team, please dial 888-294-6804 from a number other than your prepaid phone. When prompted, enter your prepaid phone number. Then press 4 (for questions or to change something), then 5 (for Store Locations or Billing Questions), then 4 (for Customer Service Rep) and then enter your pass code for your account.  If you do not know the pass code enter in four zeros. Then the system will transfer you to a Prepaid representative.
    RuthW_VZW
    Follow us on twitter @VZWSupport

  • CIN Study material with t-codes

    Sir plz send me a link from which i will get complite CIN study material with t-codes.

    Hi,
    CIN is Country Version India
    A Country Version is designed specifically to cater the business operations of that country over and above the generic SAP system functionalities. It comprises of functionalities degined for the laws and business practices pertaining to the country.
    Most of the country-specific functions for India relate to Financials and Logistics.
    The main areas are as follows:
    Excise duty and the central value-added tax system (CENVAT)
    Withholding tax (also known as tax deducted at source)
    Sales tax
    Maintenance and printing of statutory excise registers
    In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing scenario's. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself. 
    Here is some information on CIN Configuration. While it may not appear understandable as given below, it will be understood better when you check on screen. 
    Country Version India comes with four pricing procedures as follows:
    JINFAC (Sales from manufacturing plants)  
    JINEXP (Export sales)  
    JINDEP (Sales from depots)  
    JINSTK (Stock transfers 
    CIN:
    IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
    Maintain Excise Registrations
    Use
    In this IMG activity, you maintain the data relating to your excise registrations.
    Activities
    Enter each of your excise registrations, specifying a four-character code for each
    Excise Registration IDs
    In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
    Activities
    For each excise registration in your business create a registration ID and state: 
    Which taxes the registration covers (additional excise duty, special excise duty, and cess)Fields for any taxes that are not covered will be hidden in transactions involving excise duty. 
    The maximum number of items to be printed on each excise invoice 
    Whether you are allowed partial CENVAT credits
    Maintain Registration ID NUMBER, Excise code number, excise registration number 
    Excise Registration Number
    A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
    Every entity with an excise registration number is required to keep its own excise books.
    ECC Number
    Specifies the organization's ECC number.
    Excise Registration Number
    A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
    Every entity with an excise registration number is required to keep its own excise books.
    Excise range: Specifies the excise range in whose area the excise registration is located.
    Excise Division
    Specifies the excise division in whose area the excise registration is located.
    Excise Collectorate
    The code of the excise collectorate in whose area the excise registration is located.
    Indicator for confirming AED usage
    Additional Excise Duty Percentage. These are leviable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty.
    Example
    Additional Excise duty is leviable in case of textile products, tobacco and sugar.
    Similarly for SED CESS
    Number of Items in Excise Invoice
    Shows the maximum number of line items that the authorities allow per excise invoice.
    Dependencies
    This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements.
    This information is used to split the transfer postings' items into multiple subcontracting challans.
    Excise register set description
    Description of the excise registers set.
    Partial CENVAT Credit
    Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account.
    Dependencies
    When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
    This information is also shown when you post the vendor's excise invoice.
    Maintain Company Code Settings
    Use
    In this IMG activity, you maintain the data relating to your company codes.
    Document Type for CENVAT Postings
    It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
    Indicator for providing debit account overwriting
    Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
    Automatic balance Indicator
    Excise year start month
    The calendar month marking the beginning of the excise year
    Use
    This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
    Excise invoice selection procedure
    Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received.
    Number of excise invoices to be selected
    Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
    Days to be considered for excise invoice selection
    Number of days from document date for excise invoice selection.
    Example
    If the value of this field is 20 and today is 28-03-97. The excise
    invoice selection will show the related invoices only for the
    period 08-03-97 to 28-03-97.
    Document type for TDS FI posting
    Financial accounting document type for TDS posting.
    Document type for FI posting on Utilisation
    Financial accounting document type for TDS posting.
    Indicator for item level excise duty round off
    This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
    Rounding off of Excise duty for outgoing excise invoice
    You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
    Immediate Credit on Capital Goods
    Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts.
    The rest is posted the CENVAT on hold account, for use in the following year.
    CVD Clearing Account
    Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
    Exchange rate type
    Key representing a type of exchange rate in the system.
    Use
    You enter the exchange rate type to store different exchange rates.
    Example
    You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts. 
    Exchange rate type to be used for Export excise duty converts
    When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
    Maintain Plant Settings
    Use
    In this IMG activity, you maintain excise information relating to your plants.
    Plant Settings
    In this activity, you maintain excise information relating to your plants.
    Activities
    For each plant:
    ? Specify whether it is a manufacturing site or a depot.
    ? Assign it an excise registration ID.
    You can assign the same ID to more than one plant, if required.
    Depot
    Indicates that the plant in question is a depot.
    Dependencies
    Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
    Number of goods receipt per excise invoice.
    Multiple GR for one excise invoice, Single credit
    Multiple GR for one excise invoice, Multiple credit
    Maintain Excise Groups
    Use
    In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
    Excise Groups
    In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
    Recommendation
    Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
    If your company has only one set of excise registers, then you need to maintain only one excise group.
    Activities
    1. Create one excise group for each set of registers that you need to keep.
    1. Assign the excise groups to plants.
    2. Maintain whether this Excise group is for a depot or not.
    3. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
    4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
    5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
    6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
    7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
    8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
    9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
    10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers. 
    11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
    Excise Group
    Governs which set of excise registers a business transaction will be included in.
    Following is the relation between excise group, plant and registration.
    Dependencies
    In define excise groups in Customizing.
    Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to.
    At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
    Indicates that the plant in question is a depot.
    Dependencies
    Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
    GR Per Excise Invoice
    Multiple GR for one excise invoice , Multiple credit
    Multiple GR for one excise invoice , Single Credit
    Create Excise Invoice Automatically
    Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
    The excise invoice is created in the background.
    Dependencies
    If you want to make use of this function, you must also define the default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
    RG23D Sales Creation and posting option
    RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step. 
    If this is not selected then you need to separately do RG23D selection followed by PGI and then RG23D verification and posting. 
    If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
    Default excise qty in GR
    If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
    Folio number for depo
    Posting
    If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
    Also we can set indicator for creation of part 1 for:
    Blocked stock 
    Stock transport order
    Consignment stock
    Maintain Series Groups
    Use
    In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
    Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
    Activities
    ? Define excise series groups based on type of outgoing document
    ? Assign series group to excise registration ID
    ? If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    ? If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
    Example
    You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
    No account postings for CENVAT in sales cycle
    No utilization Flag
    If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
    IF the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
    Immediate Utilization of CENVAT
    Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
    If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
    Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
    Maintain Excise Duty Indicators
    Use
    In this IMG activity, you maintain the excise duty indicators.
    IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
    Select Tax Calculation Procedure
    Use
    In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
    ? If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
    ? If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
    This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
    We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents. 
    Maintain Excise Defaults
    Use
    In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
    Activities
    If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
    If you use formula-based excise determination, fill out all of the fields as follows:
    ? Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
    ? Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
    ? Specify the conditions in the sales order that are used for excise rates.
    ? Specify the countervailing duty condition type used for import purchase orders.
    See also
    SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination. 
    IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
    Condition-Based Excise Determination 
    Use
    When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
    Features
    The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
    Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
    When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
    Activities
    Customizing
    Make the settings in Customizing Basic? India?for Logistics - General, by choosing Taxes on Goods Movements Account? Excise Duties Using Condition Technique and ...?Settings Determination. 
    These activities include one activity where you define a tax code for condition-based excise determination.
    Master Data
    Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
    Day-to-Day Activities
    When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
    When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
    Creating Condition Records for Excise Duty 
    1. In the command field, enter FV11 and choose . 
    2. Enter the condition type that you want to create a condition record for and choose . 
    The Key Combination dialog box appears.
    3. Select the combination of objects that you want to create the condition record for. 
    On the dialog box, Control Code means "chapter ID."
    So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
    4. Choose . 
    5. Enter data as required. 
    In the Tax Code field, enter the dummy tax code that you have defined.
    6. Save the condition record.
    Formula-Based Excise Determination 
    Use
    When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
    Prerequisites
    In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data?access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.?
    You maintain the following types of data:
    ? Plant master data
    You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
    See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
    ? Vendor master data
    For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type - for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry. 
    For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
    ? Customer master data
    Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
    Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
    ? Material master data
    Each material is assigned a chapter ID.
    ? Excise tax rate
    For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
    If your business only qualifies for partial CENVAT credit, you must customize your system accordingly. 
    Activities
    Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
    1. Looks up the customer master data to see what status you have assigned the customer. 
    Let's assume you've assigned the customer status 3.
    2. Looks up the plant master data to see what status you have assigned the plant. 
    Similarly, your plant has status 2.
    3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indictor is for customer status 3 and plant status 2: It is 7. 
    4. The system determines the chapter ID of the ball bearing for the plant. 
    Let's assume the chapter ID at plant for the ball bearings is 1000.01.
    5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.
    Define Tax Code for Purchasing Documents
    Use : In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
    Only carry out this activity if you use condition-based excise determination.
    Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
    Assign Tax Code to Company Codes
    Use
    In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
    Only carry out this activity if you use condition-based excise determination.
    Classify Condition Types
    Use
    In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
    The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
    In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
    ? For taxes on purchases, use the condition types contained in the tax procedure.
    ? For taxes on sales, use the condition types contained in the pricing procedures.
    Standard settings
    The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
    Use these settings as a basis for your own.
    IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
    Define G/L Accounts for Taxes
    Use
    In this IMG activity, you specify which G/L accounts you will use to record which taxes.
    Requirements
    You have set up G/L accounts for each of the processing keys listed below.
    Activities
    Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
    ? VS1 (basic excise duty)
    ? VS2 (additional excise duty)
    ? VS3 (special excise duty)
    ? VS5 (sales tax setoff)
    ? MWS (central sales tax)
    ? MW3 (local sales tax)
    ? ESA (service tax)
    ? ESE (service tax expense)
    Specify Excise Accounts per Excise Transaction
    Use
    In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
    If you use subtransaction types, enter the accounts for each subtransaction type as well.
    Activities
    Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
    The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
    Example
    Excise TT DC ind Account name
    GRPO CR CENVAT clearing account
    GRPO CR RG 23 BED account
    GRPO DR CENVAT on hld account
    Specify G/L Accounts per Excise Transaction
    Use
    In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
    When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
    ? Excise group
    ? Company code
    ? Chart of accounts
    Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types. 
    Requirements
    You have already:
    ? Defined the G/L accounts
    ? Defined the excise groups
    ? Maintained the transaction accounts
    Activities
    For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
    Note
    You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
    Config setting needed to be done in order to get the Excise Details Screen in Material Master.
    Even though this functionality is available in enterprise version, a small config step has to be made in Screen Sequences for Material Master.
    Following document helps you to do this configuration.
    ? Material Master ? Logistics General ?1. Go to IMG Define Structure of Data Screen for each?Configuring the Material master Screen Sequence.
    2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
    3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is "Foreign Trade: Import Data". Select the same and click on Subscreens in the left frame.
    4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view subscreen and ensure that the subscreen is blank.
    5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 - 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
    6. Save the setting.
    7. Create a Material Master and check whether in Screen Foreign Trade - Import, Excise related subscreen appears.
    Back to ERP Operation Home.
    Transaction Codes for India
    Transaction
    Action
    J1I2
    Prepare a sales tax register
    J1I3
    Create outgoing excise invoices in batches
    J1I5
    Update the RG 1 and Part I registers
    J1IEX
    Incoming Excise Invoices (central transaction)
    J1IEX_C
    Capture an incoming excise invoice (excise clerk)
    J1IEX_P
    Post an incoming excise invoice (excise supervisor)
    J1IF01
    Create a subcontracting challan
    J1IF11
    Change a subcontracting challan
    J1IF12
    Display a subcontracting challan
    J1IF13
    Complete, reverse, or recredit a subcontracting challan
    J1IFQ
    Reconcile quantities for subcontracting challans
    J1IFR
    List subcontracting challans
    J1IH
    Make a CENVAT adjustment posting
    J1IIN
    Create an outgoing excise invoice
    J1IJ
    Assign excise invoices to a delivery for sales from depots
    J1INJV
    Adjust withholding tax Item
    J1INREP
    Reprint a withholding tax certificate for a vendor
    J1IQ
    Year-End Income Tax Depreciation Report
    J1IR
    Download register data
    J1IS
    Process an excise invoice (outgoing) for other movements
    J1IU
    Process exemption forms
    J1IW
    Verify and post an incoming excise invoice
    J1IX
    Create an incoming excise invoice (without reference to purchase order)
    J2I8
    Transfer excise duty to CENVAT account
    J2IU
    Remit excise duty fortnightly
    J2I9
    Monthly CENVAT return
    J1IG
    Excise invoice entry at depot
    J1IGA
    Create additional excise entry at depot
    J2I5
    Extract data for excise registers
    J2I6
    Print excise registers
    Hope this will help.
    Rewad Point if helpful.
    thanks,
    Raja

  • High bill with unusual calls and texts from non-functioning numbers?

    We have a family share plan with 3 phones, one phone for my husband and two phones for our employees.  Our usual phone bill runs around $150.  Our last bill was over $600, the majority charges being on one of our employee's lines.  This particular employee has been with us for over 10 years, and has always been extremely trustworthy and very frugal in his usage of his phone to make personal calls (very infrequent and always less than 5 minutes in duration, unless made during the free nights and weekends timeframe).  Our latest bill showed over 1,000 texts to/from his phone, as well as over 3,000 peak calling minutes (both to/from his phone) alone.  Many of the peak calls are lengthy in duration (30+ minutes, up to 120 minutes).  I realize this post is long, so will divide it into headings so that it makes more sense:
    Information on usage:
    Our employee insists that he did not make these calls and texts (he does not even know how to text), and what is odd about the numbers that appear on the detail (both text and voice) is that they fit into one of two categories:
    1.  There are calls to two particular non-local area code numbers (and possibly bogus, as they have area codes 523 and 352(?)).  When I call the two numbers, I get the following messages:
    From my landline:  When called from my landline, adding a "1" before the 10 digit number, I get the recording stating that "your number cannot be completed as dialed, please check the number and dial again"
    From a cell number- When calling from my own VZW phone (on separate account from husband's), I get a VZW message that the number "has been changed, disconnected or is no longer in service"
    2. They are local area code numbers, but when I call the number, I get a recording asking me to enter my pin number (in other words, they are numbers that cannot receive incoming calls, but according to our bill, have not only made calls to our employee's phone, but also received calls.  I have done an online lookup on these numbers and they are all cell phones.
    3.  When I have tried to text the non-local numbers from my VZW phone, I get messages back stating that these are landline numbers and cannot be texted; when I text the local numbers, I have texted a generic message along the lines of "I can't reach you on the phone.  Please call me as soon as you can" but I do not receive a call back.
    We cannot speak directly with our employee right now (he is in Mexico to pick up his elderly grandmother),  nor can we access our employee's phone to check the log, call history, etc. because he has the phone with him.  Due to this, when we discovered the high usage, we immediately "suspended" the phone line so that no calls could be made or received.  Subsequent to suspending the line, we have talked to his family a couple of times -- one time he happened to call them on another line, so we talked to him "indirectly" through a family member on another line with him.  He was alarmed about the calls and insists he did not make them. 
    He does have children but they are forbidden (by him) from using the phone, and he states that he always keeps the phone in a case on his hip, thus no one else has access to the phone.  To go even further, it seems that most all of the calls to these unusual numbers are made on weekdays, during school hours, so I feel sure the calls were not made by his kids.
    Calls to Verizon:  When we first called Verizon, they suggested we suspend the phone until we could speak to our employee.  Subsequent to our indirect conversation with him mentioned above, we called them back and told them he stated that he did not make the calls nor send the texts, and that we believed the phone might have been compromised, cloned, hijacked or whatever.  First, the customer svc rep looked at our account and suggested that we put an unlimited text on the phone for the current unbilled usage (there were a lot of texts, and we have no text plan on the employee's phone), and then remove that plan once we get to the bottom of this matter. 
    Due to our concern about fraudulent usage, the customer svc. rep called the fraud dept. while my husband was holding on the line.  She came back on the line and told my husband that the fraud dept. said that "it cannot be fraud because if it was, there would be thousands of dollars in international long distance to countries like Pakistan and India." (WTH?)  Also, she said that it couldn't be fraud "because texts were sent to and from the telephone number so we know it was your phone."  (another WTH?)
    She then went on to say that it looks like texts were sent to international numbers (???) recently (these same 523 and 352 area code numbers I referred to above).  Number one, if these were international texts, it seems odd to me that these texts show up on our billed and unbilled activity as "domestic text" and there is no premium charge assessed to our account for international texts.  Number two, if these numbers were international numbers, I imagine that we would be charged for outgoing international calls, which we were not.  Further, I imagine that the numbers would be displayed on our bill in other than a ten digit format, but am not sure, as no one has ever made an international call or text on our phone.
    Next steps:
    Does anyone have advice for the next steps we should take and how we can get to someone in customer service who can actually help us with this problem, instead of what we experienced on our previous call?  Can we demand that Verizon launch an investigation through its fraud department on the activity on this phone, or is this at the discretion of VZW to launch an investigation?  I am unsure, since this was not given as an option by the customer service rep... 
    If we can get Verizon to launch an investigation, is payment of the portion of the bill with the unusual and disputed usage (namely, that which is over and above the usual usage) waived pending the investigation results, or will we have to pay the entire bill to both avoid having the phones turned off, as well as any detrimental effects to our credit?  We've been hit hard by the economy, both personally (I am out of work right now) and business wise (my husband's business has been doing only about 25% of its usual business), and we don't have the extra $$ for the bill unless we take it out of our grocery budget. 
    If anyone has any insight, suggestions or otherwise, I sure would appreciate it.  Sorry for the lengthy first post, but I thought it would be helpful to outline as much about the situation as I could in order that people could respond.  Thanks in advance!

    kbinga,
    I know this is a confusing and frustrating situation for you. I would be happy to review the account in detail to see what is happening with the usage and charges to ensure it does not continue to be a problem for you. Please send me a direct message for further support assistance.
    Thank you!
    AdamE_VZW
    Follow us at @VZWSupport

  • Formated Search: Auto refresh with two conditions.

    Hi,
    I've created a Formated Search in one of my column.
    I defined my formated search as :
    - Auto refresh "When Exiting Altered Column" Item No.
    - Display Saved Values.
    Now how can I make it Auto refresh with two conditions?
    - Auto refresh "When Exiting Altered Column" Item No.
    And
    - Auto refresh "When Field Changes" Customers/Vendor Code.
    - Display Saved Values.
    Is there any way to make it work?
    Thanks In Advance.
    Bruce.

    Hi Bruce,
    You could try this trick.
    You need to execute SELECT1 in Col1 when Item No. column is altered or the Customer code is changed.
    Then, in the Item No. column asign a new Formatted Search which selects the Item No. column value (Its value) when the Customer code is changed.
    And in the Col1 asign a formatted search that acts when the Item No. column is altered.
    I think this should do the trick.
    Let us know if works.
    Regards,
    Ibai Peñ

  • Error ,Field catalog not found while doing billing with DP90

    Dear Guru's
    while doing billing with DP90 transaction code.i have given service order no xxxx and execute.Then i received the below error
    Field catalog not found , Message no. 0K530.Kindly help me in solving the issue.
    Thank u
    S Babu

    hi naga suribabu,
    I am also facing same issue. can you please help, where to  check the configuration for this issue

  • Error FS206 Down pmnts w/ taxes not permitted when processing with jur.code

    Issue:   I am encountering a problem entering Taxes when applying  down payments received from customers since we are using a jurisdiction code taxation procedure.  This process works as desired in Europe for our firm.  I found OSS 97288 which is not valid for version ECC 6.0.  Please assist due to US go-live in 2 weeks.Process:  Create Down Payment Request for cash in advance.  Required to tax at this point.  Billing document creates a noted item in the G/L (Special G/L).  I apply customer's payment via transaction F-29 and receive error "FS206 Down pmnts with taxes are not permitted when processing with jur.code."
    Settings:  1) Alternative Recon account for Special GL posting has The tax category on the GL account = B "Output tax - down payments managed gross."  2) Transaction OBXB specifies tax clearing account for transaction key MVA.  This G/Laccount has same tax category setting (B). My settings work perfectly for Europe since they are not taxed via juridicition codes.
    Thank you in advance!

    Check the GL master of the alternative recon account. Ideally there should be no setting in the tax fields as there is no tax calculated on down payment but only on the final amount. Leave the tax fiel blank and do not check mark posting without tax allowed.

  • Purchase Bill with Service Tax & VAT

    Hi Friends,
    Here i have received the Purchase bill with both service tax and VAT.
    Pls let know how to prepare the PO and MIRO/MIRO.
    Here i am giving the break-up for e.g.,
    Total Value                  80100.00
    Ser Tax 10.3%               8250.30
    Total                           88350.30
    + VAT 4%                     3534.01
    Round Off                            .31
    Total Payable            91884.00
    Pls let know how the clear and give me  the solutions
    Regards,
    Lakshman

    Hi Laxman,
    You can have a seperate condition for service tax with keeping posting key for the tax key & post the PO.
    Condition
    ZPRI           80100.00
    ZSER(10.3%) 8250.30
    Total          88350.30
    According to vat code defined it will calculate on this value.
    Regards
    Rang

  • DB startup failed with return code 12

    Hi,
    we have installed ECC6.0 on cluster in HPUX plotform and oracle database. Some temp. problem the server was swithced off automatically. After that i tried to start server but not started.
    first i started lsnrctl start in ora user in db host.
    then i started startdb in db host but getting return code 12.
    please give me the solution.
    Thanks,
    venkat.

    Hi Patel,
    When i start startdb getting like this,
    (SID )startsap DB
    no start profiles found
    #(SID) startdb
    Trying to start PRD database ...
    Log file: /home/prdadm/startdb.log
    /usr/sap/PRD/SYS/exe/run/startdb: Terminating with error code 12
    And here sending logs which i got in alert log.
    Mon Aug 25 13:03:26 2008
    Starting ORACLE instance (normal)
    Mon Aug 25 13:03:26 2008
    Specified value of sga_max_size is too small, bumping to 3539992576
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Shared memory segment for instance monitoring created
    Picked latch-free SCN scheme 3
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =10
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
      processes                = 80
      sessions                 = 96
      event                    = 10191 trace name context forever, level 1
      sga_max_size             = 3539992576
      shared_pool_size         = 1744830464
      shared_pool_reserved_size= 173663059
      filesystemio_options     = setall
      control_files            = /oracle/PRD/origlogA/cntrl/cntlrPRD.dbf, /oracle/PRD/origlogB/cntrl/cntrlPRD.dbf, /oracle/PRD/sapdata1/cntrl/cntrlPRD.dbf
      control_file_record_keep_time= 30
      db_block_size            = 8192
      db_cache_size            = 1744830464
      compatible               = 10.2.0
      log_archive_dest         = /oracle/PRD/oraarch/PRDarch
      log_buffer               = 14548992
      log_checkpoint_interval  = 0
      db_files                 = 254
      log_checkpoints_to_alert = TRUE
      dml_locks                = 4000
      undo_management          = AUTO
      undo_tablespace          = PSAPUNDO
      undo_retention           = 43200
      recyclebin               = off
      remote_os_authent        = TRUE
      remote_login_passwordfile= EXCLUSIVE
      job_queue_processes      = 1
      background_dump_dest     = /oracle/PRD/saptrace/background
      user_dump_dest           = /oracle/PRD/saptrace/usertrace
      core_dump_dest           = /oracle/PRD/saptrace/background
      optimizer_features_enable= 10.2.0.1
      sort_area_size           = 2097152
      sort_area_retained_size  = 0
      db_name                  = PRD
      open_cursors             = 800
      optimpeek_user_binds   = FALSE
      pga_aggregate_target     = 2315507466
      workarea_size_policy     = AUTO
      statistics_level         = typical
    PMON started with pid=2, OS id=93551
    PSP0 started with pid=3, OS id=93553
    MMAN started with pid=4, OS id=93555
    DBW0 started with pid=5, OS id=93557
    LGWR started with pid=6, OS id=93559
    CKPT started with pid=7, OS id=93564
    SMON started with pid=8, OS id=93566
    RECO started with pid=9, OS id=93568
    CJQ0 started with pid=10, OS id=93570
    MMON started with pid=11, OS id=93572
    MMNL started with pid=12, OS id=93574
    Mon Aug 25 13:03:30 2008
    CREATE DATABASE PRD CONTROLFILE REUSE  MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXLOGHISTORY 1000 MAXDATAFILES 254 MAXINSTANCES 50 NOARCHIVELOG CHARACTER SET WE8DEC NATIONAL CHARACTER SET UTF8 DATAFILE '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 400M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE PSAPTEMP TEMPFILE '/oracle/PRD/sapdata2/temp_1/temp.data1' SIZE 2000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M UNDO TABLESPACE PSAPUNDO DATAFILE '/oracle/PRD/sapdata3/undo_1/undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M SYSAUX DATAFILE '/oracle/PRD/sapdata1/sysaux_1/sysaux.data1' SIZE 200M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
    LOGFILE GROUP 1 ('/oracle/PRD/origlogA/log_g11m1.dbf',
    '/oracle/PRD/mirrlogA/log_g11m2.dbf') SIZE 50M  REUSE ,
    GROUP 2 ('/oracle/PRD/origlogB/log_g12m1.dbf',
    '/oracle/PRD/mirrlogB/log_g12m2.dbf') SIZE 50M  REUSE ,
    GROUP 3 ('/oracle/PRD/origlogA/log_g13m1.dbf',
    '/oracle/PRD/mirrlogA/log_g13m2.dbf') SIZE 50M  REUSE ,
    GROUP 4 ('/oracle/PRD/origlogB/log_g14m1.dbf',
    '/oracle/PRD/mirrlogB/log_g14m2.dbf') SIZE 50M  REUSE
    Mon Aug 25 13:03:31 2008
    Database mounted in Exclusive Mode
    Mon Aug 25 13:03:35 2008
    Successful mount of redo thread 1, with mount id 1727369506
    Assigning activation ID 1727369506 (0x66f59122)
    Thread 1 opened at log sequence 1
      Current log# 1 seq# 1 mem# 0: /oracle/PRD/origlogA/log_g11m1.dbf
      Current log# 1 seq# 1 mem# 1: /oracle/PRD/mirrlogA/log_g11m2.dbf
    Successful open of redo thread 1
    Mon Aug 25 13:03:35 2008
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Mon Aug 25 13:03:35 2008
    SMON: enabling cache recovery
    Mon Aug 25 13:03:35 2008
    create tablespace SYSTEM datafile  '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 400M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
      EXTENT MANAGEMENT LOCAL online
    Mon Aug 25 13:03:37 2008
    Incremental checkpoint up to RBA [0x1.3.0], current log tail at RBA [0x1.3.0]
    Mon Aug 25 13:03:38 2008
    Completed: create tablespace SYSTEM datafile  '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 400M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
      EXTENT MANAGEMENT LOCAL online
    Mon Aug 25 13:03:38 2008
    create rollback segment SYSTEM tablespace SYSTEM
      storage (initial 50K next 50K)
    Completed: create rollback segment SYSTEM tablespace SYSTEM
      storage (initial 50K next 50K)
    Mon Aug 25 13:03:42 2008
    CREATE UNDO TABLESPACE PSAPUNDO DATAFILE  '/oracle/PRD/sapdata3/undo_1/undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
    Successfully onlined Undo Tablespace 1.
    Completed: CREATE UNDO TABLESPACE PSAPUNDO DATAFILE  '/oracle/PRD/sapdata3/undo_1/undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:03:47 2008
    create tablespace SYSAUX datafile  '/oracle/PRD/sapdata1/sysaux_1/sysaux.data1' SIZE 200M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
      EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO online
    Mon Aug 25 13:03:48 2008
    Completed: create tablespace SYSAUX datafile  '/oracle/PRD/sapdata1/sysaux_1/sysaux.data1' SIZE 200M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
      EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO online
    Mon Aug 25 13:03:49 2008
    CREATE TEMPORARY TABLESPACE PSAPTEMP TEMPFILE  '/oracle/PRD/sapdata2/temp_1/temp.data1' SIZE 2000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
    Completed: CREATE TEMPORARY TABLESPACE PSAPTEMP TEMPFILE  '/oracle/PRD/sapdata2/temp_1/temp.data1' SIZE 2000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:03:49 2008
    ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPTEMP
    Completed: ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPTEMP
    Mon Aug 25 13:03:49 2008
    ALTER DATABASE DEFAULT TABLESPACE SYSTEM
    Completed: ALTER DATABASE DEFAULT TABLESPACE SYSTEM
    Mon Aug 25 13:03:50 2008
    SMON: enabling tx recovery
    Mon Aug 25 13:03:50 2008
    Beginning local checkpoint up to RBA [0x1.422b.10], SCN: 10640
    Completed checkpoint up to RBA [0x1.422b.10], SCN: 10640
    Threshold validation cannot be done before catproc is loaded.
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=14, OS id=93626
    Mon Aug 25 13:03:51 2008
    Completed: CREATE DATABASE PRD CONTROLFILE REUSE  MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXLOGHISTORY 1000 MAXDATAFILES 254 MAXINSTANCES 50 NOARCHIVELOG CHARACTER SET WE8DEC NATIONAL CHARACTER SET UTF8 DATAFILE '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 400M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE PSAPTEMP TEMPFILE '/oracle/PRD/sapdata2/temp_1/temp.data1' SIZE 2000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M UNDO TABLESPACE PSAPUNDO DATAFILE '/oracle/PRD/sapdata3/undo_1/undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M SYSAUX DATAFILE '/oracle/PRD/sapdata1/sysaux_1/sysaux.data1' SIZE 200M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
    LOGFILE GROUP 1 ('/oracle/PRD/origlogA/log_g11m1.dbf',
    '/oracle/PRD/mirrlogA/log_g11m2.dbf') SIZE 50M  REUSE ,
    GROUP 2 ('/oracle/PRD/origlogB/log_g12m1.dbf',
    '/oracle/PRD/mirrlogB/log_g12m2.dbf') SIZE 50M  REUSE ,
    GROUP 3 ('/oracle/PRD/origlogA/log_g13m1.dbf',
    '/oracle/PRD/mirrlogA/log_g13m2.dbf') SIZE 50M  REUSE ,
    GROUP 4 ('/oracle/PRD/origlogB/log_g14m1.dbf',
    '/oracle/PRD/mirrlogB/log_g14m2.dbf') SIZE 50M  REUSE
    Mon Aug 25 13:04:07 2008
    Beginning log switch checkpoint up to RBA [0x2.2.10], SCN: 23548
    Thread 1 advanced to log sequence 2
      Current log# 2 seq# 2 mem# 0: /oracle/PRD/origlogB/log_g12m1.dbf
      Current log# 2 seq# 2 mem# 1: /oracle/PRD/mirrlogB/log_g12m2.dbf
    Mon Aug 25 13:04:30 2008
    Beginning log switch checkpoint up to RBA [0x3.2.10], SCN: 54907
    Thread 1 advanced to log sequence 3
      Current log# 3 seq# 3 mem# 0: /oracle/PRD/origlogA/log_g13m1.dbf
      Current log# 3 seq# 3 mem# 1: /oracle/PRD/mirrlogA/log_g13m2.dbf
    Mon Aug 25 13:04:59 2008
    Beginning log switch checkpoint up to RBA [0x4.2.10], SCN: 68608
    Thread 1 advanced to log sequence 4
      Current log# 4 seq# 4 mem# 0: /oracle/PRD/origlogB/log_g14m1.dbf
      Current log# 4 seq# 4 mem# 1: /oracle/PRD/mirrlogB/log_g14m2.dbf
    Mon Aug 25 13:05:28 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2740K exceeds notification threshold (2048K)
    KGL object name :SYS.DBMS_STATS_INTERNAL
    Mon Aug 25 13:05:35 2008
    Thread 1 cannot allocate new log, sequence 5
    Checkpoint not complete
      Current log# 4 seq# 4 mem# 0: /oracle/PRD/origlogB/log_g14m1.dbf
      Current log# 4 seq# 4 mem# 1: /oracle/PRD/mirrlogB/log_g14m2.dbf
    Mon Aug 25 13:05:38 2008
    Completed checkpoint up to RBA [0x2.2.10], SCN: 23548
    Mon Aug 25 13:05:38 2008
    Beginning log switch checkpoint up to RBA [0x5.2.10], SCN: 85086
    Thread 1 advanced to log sequence 5
      Current log# 1 seq# 5 mem# 0: /oracle/PRD/origlogA/log_g11m1.dbf
      Current log# 1 seq# 5 mem# 1: /oracle/PRD/mirrlogA/log_g11m2.dbf
    Mon Aug 25 13:05:38 2008
    Completed checkpoint up to RBA [0x3.2.10], SCN: 54907
    Mon Aug 25 13:05:38 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3532K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:05:38 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3518K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on PLUGGABLE_SET_CHECK to SELECT_CATALOG_ROLE
    Mon Aug 25 13:05:38 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3517K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on PLUGGABLE_SET_CHECK to SELECT_CATALOG_ROLE
    Mon Aug 25 13:05:42 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2900K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :select a.*, b.ts#, b.name tsname,       sys.dbms_rcvman.num2displaysize(filesize) filesize_display  from (select unique 'BACKUPSET' btype, b.recid btype_key,        b.session_recid session_key,        b.session_recid,        b.session_stamp,        a.set_stamp id1,         b.set_count id2, file#,        creation_change#, creation_time,        resetlogs_change#, resetlogs_time, a.incremental_level,        incremental_change#, checkpoint_change#, checkpoint_time,        marked_corrupt,        (datafile_blocks
    Mon Aug 25 13:05:42 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2518K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :select a.,        sys.dbms_rcvman.num2displaysize(filesize) filesize_display  from (select unique 'BACKUPSET' btype, b.recid btype_key,        b.session_recid session_key,        b.session_recid,        b.session_stamp,        a.set_stamp id1,         b.set_count id2,        creation_time,        resetlogs_change#,resetlogs_time,checkpoint_change#,checkpoint_time,        (datafile_blocks+1)a.block_size filesize,       1 compression_ratio    from v$backup_datafile a, v$backup_set_details b where         a.
    Mon Aug 25 13:05:42 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3087K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :select a.,   case when      input_bytes/decode(output_bytes, 0, null, output_bytes) > 1   then      input_bytes/decode(output_bytes, 0, null, output_bytes)   else 1 end compression_ratio,   sys.dbms_rcvman.num2displaysize(input_bytes) input_bytes_display,   sys.dbms_rcvman.num2displaysize(output_bytes) output_bytes_display  from (select sum(num_times_backed) num_files_backed,        count() num_distinct_files_backed,       count(distinct ts#)    num_distinct_ts_backed,       min(min_checkpoint_change#) mi
    Mon Aug 25 13:05:43 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2650K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :select a.*,   case when      input_bytes/decode(output_bytes, 0, null, output_bytes) > 1   then      input_bytes/decode(output_bytes, 0, null, output_bytes)   else 1 end compression_ratio,   sys.dbms_rcvman.num2displaysize(input_bytes) input_bytes_display,   sys.dbms_rcvman.num2displaysize(output_bytes) output_bytes_display  from (select sum(num_times_backed) num_files_backed,        1 num_distinct_files_backed,       min(min_checkpoint_change#) min_checkpoint_change#,       max(max_checkpoint_change#) max_
    Mon Aug 25 13:05:43 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5156K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :select a.*,   case when      input_bytes/decode(output_bytes, 0, null, output_bytes) > 1   then      input_bytes/decode(output_bytes, 0, null, output_bytes)   else 1 end compression_ratio,   sys.dbms_rcvman.num2displaysize(input_bytes) input_bytes_display,   sys.dbms_rcvman.num2displaysize(output_bytes) output_bytes_display  from (select sum(num_files_backed) num_files_backed,       sum(distinct_files_backed) distinct_files_backed,       min(min_first_change#) min_first_change#,       max(max_next_change#)
    Mon Aug 25 13:05:43 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2172K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:05:43 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2138K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on v_$backup_archivelog_summary to select_catalog_role
    Mon Aug 25 13:05:43 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2137K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on v_$backup_archivelog_summary to select_catalog_role
    Mon Aug 25 13:05:43 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2514K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :select num_files_backed,        num_distinct_files_backed,        min_modification_time,        max_modification_time,        input_bytes,    sys.dbms_rcvman.num2displaysize(input_bytes) input_bytes_display  from (select count(*) num_files_backed,        min(modification_time)min_modification_time,        max(modification_time) max_modification_time,        sum(bytes) input_bytes     from v$backup_spfile     where (set_stamp, set_count) in      (select set_stamp, set_count from v$backup_set_details)), (sele
    Mon Aug 25 13:06:06 2008
    Beginning log switch checkpoint up to RBA [0x6.2.10], SCN: 98175
    Thread 1 advanced to log sequence 6
      Current log# 2 seq# 6 mem# 0: /oracle/PRD/origlogB/log_g12m1.dbf
      Current log# 2 seq# 6 mem# 1: /oracle/PRD/mirrlogB/log_g12m2.dbf
    Mon Aug 25 13:06:09 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2070K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_constraint1_view to select_catalog_role
    Mon Aug 25 13:06:09 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2070K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_constraint1_view to select_catalog_role
    Mon Aug 25 13:06:09 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2221K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:09 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2312K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_constraint_view to public
    Mon Aug 25 13:06:09 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2310K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_constraint_view to public
    Mon Aug 25 13:06:11 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2839K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:11 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2934K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_hnt_view to select_catalog_role
    Mon Aug 25 13:06:11 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2933K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_hnt_view to select_catalog_role
    Mon Aug 25 13:06:11 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2924K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:11 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3029K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_iont_view to select_catalog_role
    Mon Aug 25 13:06:11 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3026K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_iont_view to select_catalog_role
    Mon Aug 25 13:06:12 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 6968K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:12 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 7360K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_nt_parent_view to select_catalog_role
    Mon Aug 25 13:06:12 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 7357K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_nt_parent_view to select_catalog_role
    Mon Aug 25 13:06:12 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3379K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:13 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3460K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_htable_view to public
    Mon Aug 25 13:06:13 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3457K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_htable_view to public
    Mon Aug 25 13:06:13 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3445K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:13 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3581K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_htable_view to public
    Mon Aug 25 13:06:13 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3580K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_htable_view to public
    Mon Aug 25 13:06:13 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5046K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:14 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5165K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_phtable_view to public
    Mon Aug 25 13:06:14 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5165K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_phtable_view to public
    Mon Aug 25 13:06:14 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5119K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:14 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5329K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_phtable_view to public
    Mon Aug 25 13:06:14 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5329K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_phtable_view to public
    Mon Aug 25 13:06:15 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 11315K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:16 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 12040K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_fhtable_view to public
    Mon Aug 25 13:06:16 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 12038K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_fhtable_view to public
    Mon Aug 25 13:06:17 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 11418K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:18 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 12308K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_fhtable_view to public
    Mon Aug 25 13:06:18 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 12304K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_fhtable_view to public
    Mon Aug 25 13:06:19 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13209K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:20 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13975K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_pfhtable_view to public
    Mon Aug 25 13:06:20 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13972K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_pfhtable_view to public
    Mon Aug 25 13:06:21 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13322K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:22 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 14285K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_pfhtable_view to public
    Mon Aug 25 13:06:22 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 14283K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_pfhtable_view to public
    Mon Aug 25 13:06:23 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 11242K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:24 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 11972K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_iotable_view to public
    Mon Aug 25 13:06:24 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 11971K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_iotable_view to public
    Mon Aug 25 13:06:25 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 11348K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:26 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 12239K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_iotable_view to public
    Mon Aug 25 13:06:26 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 12237K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_iotable_view to public
    Mon Aug 25 13:06:27 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 12377K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:28 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13155K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_piotable_view to public
    Mon Aug 25 13:06:28 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13152K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_piotable_view to public
    Mon Aug 25 13:06:29 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 12488K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:30 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13450K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_piotable_view to public
    Mon Aug 25 13:06:30 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13449K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_piotable_view to public
    Mon Aug 25 13:06:31 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3669K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:31 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3941K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_table_data_view to public
    Mon Aug 25 13:06:31 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3939K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_table_data_view to public
    Mon Aug 25 13:06:31 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3677K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:31 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3949K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_table_data_view to public
    Mon Aug 25 13:06:31 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3948K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_10_1_table_data_view to public
    Mon Aug 25 13:06:33 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3777K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:33 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3924K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_view_view to public
    Mon Aug 25 13:06:33 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3922K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_view_view to public
    Mon Aug 25 13:06:36 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5201K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:36 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5431K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_h_view to public
    Mon Aug 25 13:06:36 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5429K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_h_view to public
    Mon Aug 25 13:06:37 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 6880K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:37 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 7178K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_ph_view to public
    Mon Aug 25 13:06:37 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 7176K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_ph_view to public
    Mon Aug 25 13:06:38 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13185K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:39 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 14163K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_fh_view to public
    Mon Aug 25 13:06:39 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 14161K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_fh_view to public
    Mon Aug 25 13:06:41 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 15085K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:42 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 16142K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_pfh_view to public
    Mon Aug 25 13:06:42 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 16138K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_pfh_view to public
    Mon Aug 25 13:06:43 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13103K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:44 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 14086K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_iot_view to public
    Mon Aug 25 13:06:44 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 14084K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_iot_view to public
    Mon Aug 25 13:06:46 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 14242K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:47 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 15296K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_piot_view to public
    Mon Aug 25 13:06:47 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 15293K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_piot_view to public
    Mon Aug 25 13:06:48 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3506K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:48 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3656K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_log_h_view to public
    Mon Aug 25 13:06:48 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3655K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_log_h_view to public
    Mon Aug 25 13:06:48 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5183K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:48 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5407K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_log_ph_view to public
    Mon Aug 25 13:06:48 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 5404K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_log_ph_view to public
    Mon Aug 25 13:06:49 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 11488K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:50 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 12387K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_log_fh_view to public
    Mon Aug 25 13:06:50 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 12387K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_log_fh_view to public
    Mon Aug 25 13:06:51 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 13391K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:06:52 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 14366K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_log_pfh_view to public
    Mon Aug 25 13:06:52 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 14364K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ku$_m_view_log_pfh_view to public
    Mon Aug 25 13:07:09 2008
    Thread 1 cannot allocate new log, sequence 7
    Checkpoint not complete
      Current log# 2 seq# 6 mem# 0: /oracle/PRD/origlogB/log_g12m1.dbf
      Current log# 2 seq# 6 mem# 1: /oracle/PRD/mirrlogB/log_g12m2.dbf
    Mon Aug 25 13:07:11 2008
    Completed checkpoint up to RBA [0x4.2.10], SCN: 68608
    Mon Aug 25 13:07:12 2008
    Beginning log switch checkpoint up to RBA [0x7.2.10], SCN: 109934
    Thread 1 advanced to log sequence 7
      Current log# 3 seq# 7 mem# 0: /oracle/PRD/origlogA/log_g13m1.dbf
      Current log# 3 seq# 7 mem# 1: /oracle/PRD/mirrlogA/log_g13m2.dbf
    Mon Aug 25 13:07:12 2008
    Completed checkpoint up to RBA [0x5.2.10], SCN: 85086
    Mon Aug 25 13:07:36 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2391K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:07:36 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2259K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ALL_REPOBJECT to PUBLIC with grant option
    Mon Aug 25 13:07:36 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2255K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ALL_REPOBJECT to PUBLIC with grant option
    Mon Aug 25 13:07:37 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2440K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:07:37 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2311K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ALL_REPPROP to PUBLIC with grant option
    Mon Aug 25 13:07:37 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2309K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ALL_REPPROP to PUBLIC with grant option
    Mon Aug 25 13:07:37 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2403K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:07:37 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2279K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ALL_REPKEY_COLUMNS to PUBLIC with grant option
    Mon Aug 25 13:07:37 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2276K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on ALL_REPKEY_COLUMNS to PUBLIC with grant option
    Mon Aug 25 13:07:38 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2397K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:07:38 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2267K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on all_repcolumn_group to public with grant option
    Mon Aug 25 13:07:38 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2266K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on all_repcolumn_group to public with grant option
    Mon Aug 25 13:07:38 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3418K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:07:38 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3285K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on "_ALL_REPCOLUMN_GROUP" to PUBLIC with grant option
    Mon Aug 25 13:07:38 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3283K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on "_ALL_REPCOLUMN_GROUP" to PUBLIC with grant option
    Mon Aug 25 13:07:39 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3545K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    Mon Aug 25 13:07:39 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3412K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on "_ALL_REPRESOLUTION" to public with grant option
    Mon Aug 25 13:07:39 2008
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 3408K exceeds notification threshold (2048K)
    Details in trace file /oracle/PRD/saptrace/usertrace/prd_ora_93659.trc
    KGL object name :grant select on "_ALL_REPRESOLUTION" to public with grant option
    Mon Aug 25 13:07:41 2008
    Beginning log switch checkpoint up to RBA [0x8.2.10], SCN: 124739
    Thread 1 advanced to log sequence 8
      Current log# 4 seq# 8 mem# 0: /oracle/PRD/origlogB/log_g14m1.dbf
      Current log# 4 seq# 8 mem# 1: /oracle/PRD/mirrlogB/log_g14m2.dbf
    Mon Aug 25 13:08:24 2008
    Thread 1 cannot allocate new log, sequence 9
    Checkpoint not complete
      Current log# 4 seq# 8 mem# 0: /oracle/PRD/origlogB/log_g14m1.dbf
      Current log# 4 seq# 8 mem# 1: /oracle/PRD/mirrlogB/log_g14m2.dbf
    Mon Aug 25 13:08:24 2008
    Completed checkpoint up to RBA [0x6.2.10], SCN: 98175
    Mon Aug 25 13:08:25 2008
    Beginning log switch checkpoint up to RBA [0x9.2.10], SCN: 137726
    Thread 1 advanced to log sequence 9
      Current log# 1 seq# 9 mem# 0: /oracle/PRD/origlogA/log_g11m1.dbf
      Current log# 1 seq# 9 mem# 1: /oracle/PRD/mirrlogA/log_g11m2.dbf
    Mon Aug 25 13:08:25 2008
    Completed checkpoint up to RBA [0x7.2.10], SCN: 109934
    Mon Aug 25 13:10:33 2008
    Beginning log switch checkpoint up to RBA [0xa.2.10], SCN: 153003
    Thread 1 advanced to log sequence 10
      Current log# 2 seq# 10 mem# 0: /oracle/PRD/origlogB/log_g12m1.dbf
      Current log# 2 seq# 10 mem# 1: /oracle/PRD/mirrlogB/log_g12m2.dbf
    Mon Aug 25 13:11:46 2008
    CREATE TABLESPACE PSAPSR3 DATAFILE '/oracle/PRD/sapdata1/sr3_1/sr3.data1' SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M  LOGGING ONLINE PERMANENT  EXTENT MANAGEMENT  LOCAL  AUTOALLOCATE  SEGMENT SPACE MANAGEMENT AUTO
    Mon Aug 25 13:11:59 2008
    Completed: CREATE TABLESPACE PSAPSR3 DATAFILE '/oracle/PRD/sapdata1/sr3_1/sr3.data1' SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M  LOGGING ONLINE PERMANENT  EXTENT MANAGEMENT  LOCAL  AUTOALLOCATE  SEGMENT SPACE MANAGEMENT AUTO
    Mon Aug 25 13:12:00 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3_2/sr3.data2'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:12:12 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3_2/sr3.data2'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:12:13 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3_3/sr3.data3'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:12:25 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3_3/sr3.data3'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:12:26 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3_4/sr3.data4'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:12:39 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3_4/sr3.data4'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:12:39 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3_5/sr3.data5'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:12:43 2008
    Completed checkpoint up to RBA [0x8.2.10], SCN: 124739
    Mon Aug 25 13:12:53 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3_5/sr3.data5'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:12:53 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3_6/sr3.data6'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:13:06 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3_6/sr3.data6'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:13:07 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3_7/sr3.data7'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:13:20 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3_7/sr3.data7'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:13:20 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3_8/sr3.data8'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:13:28 2008
    Completed checkpoint up to RBA [0x9.2.10], SCN: 137726
    Mon Aug 25 13:13:33 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3_8/sr3.data8'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:13:34 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3_9/sr3.data9'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:13:46 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3_9/sr3.data9'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:13:47 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3_10/sr3.data10'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:13:59 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3_10/sr3.data10'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:14:00 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3_11/sr3.data11'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:14:12 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3_11/sr3.data11'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:14:13 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3_12/sr3.data12'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:14:26 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3_12/sr3.data12'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:14:26 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3_13/sr3.data13'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:14:39 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3_13/sr3.data13'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:14:39 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3_14/sr3.data14'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:14:52 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3_14/sr3.data14'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:14:53 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3_15/sr3.data15'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:15:06 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3_15/sr3.data15'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:15:06 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3_16/sr3.data16'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:15:19 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3_16/sr3.data16'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:15:20 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3_17/sr3.data17'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:15:32 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3_17/sr3.data17'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:15:33 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3_18/sr3.data18'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:15:37 2008
    Completed checkpoint up to RBA [0xa.2.10], SCN: 153003
    Mon Aug 25 13:15:46 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3_18/sr3.data18'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:15:47 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3_19/sr3.data19'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:16:00 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3_19/sr3.data19'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:16:01 2008
    ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3_20/sr3.data20'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:16:13 2008
    Completed: ALTER TABLESPACE PSAPSR3 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3_20/sr3.data20'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:16:15 2008
    CREATE TABLESPACE PSAPSR3700 DATAFILE '/oracle/PRD/sapdata1/sr3700_1/sr3700.data1' SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M  LOGGING ONLINE PERMANENT  EXTENT MANAGEMENT  LOCAL  AUTOALLOCATE  SEGMENT SPACE MANAGEMENT AUTO
    Mon Aug 25 13:16:29 2008
    Completed: CREATE TABLESPACE PSAPSR3700 DATAFILE '/oracle/PRD/sapdata1/sr3700_1/sr3700.data1' SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M  LOGGING ONLINE PERMANENT  EXTENT MANAGEMENT  LOCAL  AUTOALLOCATE  SEGMENT SPACE MANAGEMENT AUTO
    Mon Aug 25 13:16:33 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3700_2/sr3700.data2'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:16:46 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3700_2/sr3700.data2'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:16:46 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3700_3/sr3700.data3'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:16:59 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3700_3/sr3700.data3'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:17:00 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3700_4/sr3700.data4'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:17:12 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata1/sr3700_4/sr3700.data4'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:17:13 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3700_5/sr3700.data5'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:17:25 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3700_5/sr3700.data5'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:17:26 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3700_6/sr3700.data6'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:17:38 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3700_6/sr3700.data6'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:17:39 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3700_7/sr3700.data7'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:17:51 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3700_7/sr3700.data7'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:17:52 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3700_8/sr3700.data8'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:18:04 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata2/sr3700_8/sr3700.data8'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:18:05 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3700_9/sr3700.data9'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:18:18 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3700_9/sr3700.data9'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:18:19 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3700_10/sr3700.data10'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:18:31 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3700_10/sr3700.data10'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:18:32 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3700_11/sr3700.data11'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:18:45 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3700_11/sr3700.data11'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:18:46 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3700_12/sr3700.data12'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:18:58 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata3/sr3700_12/sr3700.data12'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:18:59 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3700_13/sr3700.data13'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:19:11 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3700_13/sr3700.data13'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:19:12 2008
    ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3700_14/sr3700.data14'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Aug 25 13:19:24 2008
    Completed: ALTER TABLESPACE PSAPSR3700 ADD DATAFILE  '/oracle/PRD/sapdata4/sr3700_14/sr3700.data14'  SIZE 2000M  REUSE  AUTOEXTEND  ON NEXT 20M MAXSIZE 10000M
    Mon Au

  • Address to pay bill through bank auto bill pay?

    I am trying to set-up auto bill pay through my bank in Oregon and need the address that verizon uses for this type of payment.

    Rhasker:
    I have been using my bank's bill pay service for 20+ years with no problems, and no missed payments.
    The simplest thing to do is to set up the bill payment using the same address that you would mail your personal check to.
    Make sure that you use your proper account number --not just your telephone number.
    Your bank will then either use that address, or they will decide to use an electronic address provided to them by Verizon.
    Note: when you set up that particular payment option they may automatically offer you the option to use the 'address' they have 'on file'.

  • Calls Getting disconnected with reason code 26

    Hi,
    Few of my calls are getting disconnected with reason code 26. on agent screen it just flash and disconnect.as per RCD its showing Error code 0( fine) and finally its ending at Skill Group Node. talk time is 1 or 2 seconds. agents having auto answer setting as well as IP Phone set auto ans with headset.
    my setup is IPIVR based UCCE setup.
    Please help
    Regards-
    PK

    Hi PK,
    CD 26 normally indicates Resource Not available in CUCM side. please check the Jtapi gateway process logs for the failed calls. you should be able to see something similar to below
    19:08:37:896 PG1A-jgw1 Trace: ConnFailedEv CID: 27224748 Addr: 80002985 CiscoCause: CAUSE_RESOURCESNAVAIL Cause: CAUSE_RESOURCES_NOT_AVAILABLE.
    if that is the case , please check from CUCM perspective as well.
    Regards,
    Sasikumar.

Maybe you are looking for

  • Copying files is estimating 24 days to complete. Is this harmful to my iMac?

    I have an external hard drive that wouldn't mount to my 27" iMac. I finally got it to mount but through USB 2.0 (normally through FireWire800). Once it mounted, my goal was to go into the iPhoto "masters" folder to back up all my original photos sinc

  • Getting Job Output

    Hi there. I have a job that I run as a DBA Script that does the following: 1)Runs dbms_stats.gather_schema_stats with the STALE option to get stale stats. 2) If this first job fails then does a dbms_stats.gather_schema_stats on the whole schema. (the

  • Smart Playlists on iOS

    Still not working properly for me. How about anyone else? It's an improvement - I see a few songs in them now, but in some I am only seeing one or two where there should be hundreds. Haven't been able to check the play count / last played yet but wil

  • Converting .avi files to iDVD

    First time using anything like this and I'm pretty lost in the dark. I downloaded some .avi files off of limewire. I'm planning to burn them to a dvd, or have them in at least something that quicktime can play. Is there anyway to do this? Basically I

  • Understand SP stacklevel for ECC6

    Hi all, I've installed a ECC6 SR3 system which came with a default patchlevel.ABAP/BASIS/PI-BASIS were on level 14. I was to update my system to latest patch level,while checking for patches for SAP-ERP ECC6 the highest patchlevel was 16. the same wa