PRQs.

Hi,
during PRQs creation <b>system takes the standard price in material master
and not the recordinfo price</b>.
I don't understand why....
Best regards

hi,
while you are creating purchase requisitions, it will take the price maintianined in the material master. ( becasue PR is internal document ).
if you assigned the vendor in PR, if info record is maintained in the combination of mateiral and vendor, it will pick the price from the info record.
hope this may help you,
Regards,
Srinivas

Similar Messages

Copy user fields between PRq and PO.

Hello.
I have little problem.
I prepare new user field in Purchase Requisition called for example ZFIELD it is displayed and save into table EBAN by user exit MEREQ001. Now I want to copy this field to Purchase Order when I create PO with reference to PRq. How to do that? I can't find any user exit or badi
The new field is prepare at item level in Preq and I want to copy it to PO at item level also.
I have extend table EKPO.
Thank you for any help.
A.J.

Hi,
Implement the BADI 'ME_REQ_OI_EXT'.
This may help to your requirement
regards,
Siva

Create prq with reference

Hi Gurus,
Where in purchasing are customizing settings for PRQ creation with reference to another type of document.... contract.... PO order.... is this possible in MM? In sales this is easy and solved with copying control...
Thanks + br
Saso

Hello Saso,
A requisition cannot be created with reference to a contract. The reason is that PreReq is generally created when materials are in need and it does not matter whether there is any concerning contract at the moment.
The contract will come to consideration when the purchasing department makes a decision where to order the material from. Basing on that , you can only adopt other PreReqs in ME51N by "drag and drop" but no other documents like contracts, requests for quotations and so fourth.
What can be done is to use the contract as a source of supply on PRe In t-code ME51N you inform the material, quantity, plant and PurOrg you will see tab "source of supply". here you need to click button "assign source of supply" and select the contract and clicking "assign source". The contract will be defaulted into the field 'agreement'.
Regards,
Mauro

PRQ field and related table.

Hi,
in what table is located the field ESTKZ ?
I want to create a characteristic with the above field for PRQs.
Regards

ESTKZ is in the following tables:
EBAN             Purchase Requisition
ESTKZ           Creation Indicator (Purchase Requisition)
EKEH             Scheduling Agreement Release Documentation
ESTKZ           reation Indicator (Purchase Requisition)
EKES             Vendor Confirmations
ESTKZ           Creation Indicator: Vendor Confirmation
EKET             Scheduling Agreement Schedule Lines
ESTKZ           Creation Indicator (Purchase Requisition)
EKETH            Scheduling Agreement Schedules: History Tables
ESTKZ            Creation Indicator (Purchase Requisition)
It is in the following structure if you are desiring to use it in a characteristic (e.g. release strategy?).
CEBAN                          Communication Release Strategy Determination: Requisition
ESTKZ                          Creation Indicator (Purchase Requisition/Schedule Lines)
Regards

Authorization for user to release a PRQ

Hi,
I would enable in SU01 the authorization so that only users allowed to release PRQ can do this
What is the authorization to add in SU01 for PRQ ?
Thanks
Best Regards

- create a role(approver role) with Tcode ME55(collective release) and ME54N(individual release) if its only for PR,if you want for PO, add ME28(collective release) and ME29N(individual release).
- when you create the role in PFCG, you can also see the authorization objects when you add the TCODES, so you can restrict even for plant level or purchase organization level.
- In PFCG, assign the specified users to the role and also "check and compare users"
Now authorization for approval is restricted

PRQs and release procedure.

Hi,
how can I set a releasing procedure for PRQs <b>by document type</b>?
Best regards

hi,
in the release procedure:
for document type:
1. Create the charecteristic --> in additional data,
give the TABLE Name: CEBAN and FIELD Name : BSART,
for purchase requisitions : B is the charecter value.
and follow the process.
hope this may help you,
Regards,
Srinivas

PRQ conversion into PO and conditions

Hi,
I converted a PRQ into a PO related to a service for a vendor X. This service has a price of 100u20AC.
Then I create another PRQ for the same service and I set 12u20AC as price. When I convert the PRQ into a PO, system
proposes 100u20AC as price instead of the price of the last PRQ (i.e. 12u20AC). As the PO is created as reference of the PRQ
is not correct this.
Best Regarda

Here I see two requirements...
If you want to just restrict the system not to default last purchase order price,
-SPRO - MM - purchasing - environment - default value for buyer - price adoption. and you need to assign parameter object to EVB parameter /role
If you want to copy PR price to PO, go to OMET and check adopt PO price.
You have assign this paramter object to EFB paramter for the user/role

PRQs Release

Hi,
I set a release procedure for PRQs based on MRP controller field value.
Now each PRQ can be released from any MRP controllers. How can I set system so that only every MRP controller will release his own PRQs ?
MRP controllers are:
A;
B;
C;
If the PRQ has A in the field EBAN-ESTKZ the PRQ will only be released from MRP controller A that has a username in SAP
If the PRQ has B in the field EBAN-ESTKZ the PRQ will only be released from MRP controller B that has a username in SAP
and so on
Regards
Regards

1) the autorization is based on release code and release group.
If you want secure that each planner can only release his own requistions, then you have to develope the release strategy in a way that you either have a different release code or a different release group for each planner.
Yes, I created different release codes
I would like that with trx ME54N or ME55 MRP controller could release only it's own PRQs. This means that he can set only his release code in ME55 and that in trx ME54N when clicking on the pen icon, system will only admit the release of the MRP controller (user) A if in the field EBAN-ESTKZ indicates MRP controller A, B if the field EBAN-ESTKZ indicates MRP controller B and so on.
2) Why do you create requisitions with the MRP run if you want release them by the planners himselfes?
Probably because the planning data is worse and you would like a control before these requisitions go to purchasing derpartment, correct?
Yes
Regards

Converting a PRQ to a PO.

Hi,
how can I convert a purchase requisition to a purchase order using for the purchase order
a particular document type?
Best regards

Hi
Go in Tcode ME21N and press tab "Document overview on". press "Selection Variant" as "My Purchase Requisition".
Select your PR and press adopt.
And make changes you want and save it.
regards
rb

Converting a production order in PRQ (purchase requisition).

Hi,
how converting a production order in a purchase requisition?
Best regards

hi,
u cant convert the production order into Pr.
ho ever u can procure the material against the Production order using the account assignment category.
also check with ur PP consultant for automatic creation of PR with ref to Production order, after exploding the BOM.
check MRP run.

POs with reference to a PRQ

Hi,
I want to customize the system so that if I create a PO with reference to a RFQ and I modify the quantity of the
PO (i.e. I set a quantity in PO that is > of the quantity in the RFQ) the system will create a message errore
Regards

Check
PO allows qty more than RFQ

Goods issue/receipt print out

Hi could any body let me know the print settings for goods issue & receipts and Logistics invoice verification.
i tried with we01 for GRN , wa01 for GI, in nace settings but could not find the result.
pls let me know the settings.especially for sub contract components issue print settings.
regards
Bheemasimha
9900163939

hi bheema,
Configure Automatic Postings
In this step, you enter the system settings for Inventory Management and Invoice Verification transactions for automatic postings to G/L accounts.
You can then check your settings using a simulation function.
Under Further information there is a list of transactions in Materials Management and their definitions.
What are automatic postings?
Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
Example:
Posting lines are created in the following accounts in the case of a goods issue for a cost center:
Stock account
Consumption account
How does the system find the relevant accounts?
When entering the goods movement, the user does not have to enter a G/L account, since the R/3 System automatically finds the accounts to which postings are to be made using the following data:
Chart of accounts of the company code
If the user enters a company code or a plant when entering a transaction, the R/3 System determines the chart of accounts which is valid for the company code.
You must define the automatic account determination individually for each chart of accounts.
Valuation grouping code of the valuation area
If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas.
You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code.
Transaction/event key (internal processing key)
Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting. Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers.
You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is assign the relevant G/L account to each posting transaction.
Account grouping (only for offsetting entries, consignment liabilities, and price differences)
Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code.
An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting".
Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping, that is, assign G/L accounts.
If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key.
Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities.
Valuation class of material or (in case of split valuation) the valuation type
The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials.
You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class.
If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.
Requirements
Before you maintain automatic postings, you must obtain the following information:
1. Valuation level (plant or company code)
Establish whether the materials are valuated at plant or at company code level
When valuation is at plant level, the valuation area corresponds to a plant.
When valuation is at company code level, the valuation area corresponds to a company code.
Define valuation level
2. Chart of accounts and valuation grouping code per valuation area
Find out whether the valuation grouping code is active.
Activate split valuation
If it is not active, determine the chart of accounts assigned to each valuation area (via the company code).
If it is active, determine the chart of accounts and the valuation grouping code assigned to each valuation area.
Group valuation areas
You must define a separate account determination process for chart of accounts and each valuation grouping code.
3. Valuation class per material type
If you wish to differentiate the account determination process for specific transactions according to valuation classes, find out which valuation classes are possible for each material type.
Define valuation classes
4. Account grouping for offsetting entries to stock accounts
Under
Define account grouping for movement types , determine for which movement types an account grouping is defined for the transaction/event keys GGB (offsetting entry to stock posting), KON (consignment liabilities) and PRD (price differences).
Default settings
G/L account assignments for the charts of accounts INT and the valuation grouping code 0001 are SAP standard.
Activities
1. Create account keys for each chart of accounts and each valuation grouping code for the individual posting transactions. To do so, proceed as follows:
a) Call up the activity
Configure Automatic Postings .
The R/3 system first checks whether the valuation areas are correctly maintained. If, for example, a plant is not assigned to a company code, a dialog box and an error message appear.
From this box, choose Continue (next entry) to continue the check.
Choose Cancel to end the check.
The configuration menu Automatic postings appears.
b) Choose Goto -> Account assignment.
A list of posting transactions in Materials Management appears. For further details of the individual transactions, see Further information.
The Account determination indicator shows whether automatic account determination is defined for a transaction.
c) Choose a posting transaction.
A box appears for the first posting transaction. Here you can enter a chart of accounts.
You can enter the following data for each transaction:
Rules for account number assignments
With Goto -> Rules you can enter the factors on which the account number assignments depend:
- debit/credit indicator
- general grouping (= account grouping)
- valuation grouping
- valuation class
Posting keys for the posting lines
Normally you do not have to change the posting keys. If you wish to use new posting keys, you have to define them in the Customizing system of Financial Accounting.
Account number assignments
You must assign G/L accounts for each transaction/event key (except KBS). You can assign these accounts manually or copy them from another chart of accounts via Edit -> Copy .
If you want to differentiate posting transactions (e.g. inventory postings) according to valuation classes, you must make an account assignment for each valuation class.
Using the posting transaction "Offsetting entry for inventory posting", you have to make an account assignment for each account grouping
If the transaction PRD (price differences) is also dependent on the account grouping, you must create three account assignments:
- an account assignment without account grouping
- an account assignment with account grouping PRF
- an account assignment with account grouping PRA
If the transaction KON (consignment and pipeline liabilities) is also dependent on the account grouping, you must create two account assignments:
- an account assignment without account grouping (consignment)
- an account assignment with account grouping (pipeline)
d) Save your settings.
2. Then check your settings with the simulation function.
With the simulation function, you can simulate the following:
Inventory Management transactions
Invoice Verification transactions
When you enter a material or valuation class, the R/3 system determines the G/L accounts which are assigned to the corresponding posting transactions. Depending on the configuration, the SAP system checks whether the G/L account exists
In the simulation you can compare the field selection of the movement type with that of the individual accounts and make any corrections.
If you want to print the simulation, choose Simulation -> Report.
To carry out the simulation, proceed as follows:
a) Choose Settings to check the simulation defaults for
- the application area (Invoice Verification or Inventory Management)
- the input mode (material or valuation class)
- account assignment
Instructions
b) Choose Goto -> Simulation.
The screen for entering simulation data appears.
c) Depending on the valuation level, enter a plant or a company code on the screen.
d) When you simulate Inventory Management transactions, goods movements are simulated. The R/3 system suggests the first movement type for simulation. If several movements are possible with this movement type, you can select a line.
When you simulate Invoice Verification transactions, a list appears on the screen of the possible transaction types. Select a line.
e) Then choose Goto -> Account assignments.
A list appears of the posting lines which can be created by the selected transaction. For each posting line, the G/L account for the debit posting as well as the G/L account for the credit posting are displayed.
f) From this screen, choose Goto -> Movement+ to get a list of the posting lines for the next movement type or transaction type.
If you work with valuation classes, choose Goto -> Valuation class+ to receive the simulation for the next valuation class. This function is not possible when simulating with material numbers.
Choose Goto -> Check screen layout to compare the movement type with the G/L accounts determined by the system and make any necessary corrections.
Note
The simulation function does NOT obviate the need for a trial posting!
Further Notes
The following list shows the individual transactions with examples of how they are used:
AG1 - No documentation currently available.
AG2 - No documentation currently available.
AG3 - No documentation currently available.
Expense/revenue from consumption of consignment material (AKO)
This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
Expenditure/income from transfer posting (AUM)
This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
Provisions for subsequent (end-of-period rebate) settlement (BO1)
If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
Income from subsequent settlement (BO2)
The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
Income from subsequent settlement after actual settlement (BO3)
If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
Supplementary entry for stock (BSD)
This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
Change in stock (BSV)
Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
Stock posting (BSX)
This transaction is used for all postings to stock accounts. Such postings are effected, for example:
In inventory management in the case of goods receipts to own stock and goods issues from own stock
In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
@1A@Caution
Take care to ensure that:
A stock account is not used for any transaction other than BSX
Postings are not made to the account manually
The account is not changed in the productive system before all stock has been booked out of it
Otherwise differences would arise between the total stock value of the material master records and the balance on the stock account.
Revaluation of "other" consumptions (COC)
This transaction/event key is only relevant to Brazil. It is used if a revaluation report is used for company codes in Brazil.
The revaluation report uses the actual prices determined by the material ledger/actual costing to:
Revaluate costs on the basis of actual prices
Post the price differences arising from "other" consumptions (e.g. consumption to cost center) to a collective account
This transaction/event key is needed to post the price differences. The account specified here is posted with the price differences for "other" consumptions.
No documentation currently available.
Small differences, Materials Management (DIF)
This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
These transactions are used only if
Purchase Account Management is active in the company code.
Note
Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
Before you use this function, check whether you need to use it in your country.
Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
You can also enter your own transactions for delivery costs in condition types.
External service (FRL)
The transaction is used for goods and invoice receipts in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
External service, delivery costs (FRN)
This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
AUA: for order settlement
AUF: for goods receipts for orders (without account assignment)
and for order settlement if AUA is not maintained
AUI: Subsequent adjustment of actual price from cost center directly
to material (with account assignment)
BSA: for initial entry of stock balances
INV: for expenditure/income from inventory differences
VAX: for goods issues for sales orders without
account assignment object (the account is not a cost element)
VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
VBO: for consumption from stock of material provided to vendor
VBR: for internal goods issues (for example, for cost center)
VKA: for sales order account assignment
(for example, for individual purchase order)
VKP: for project account assignment (for example, for individual PO)
VNG: for scrapping/destruction
VQP: for sample withdrawals without account assignment
VQY: for sample withdrawals with account assignment
ZOB: for goods receipts without purchase orders (mvt type 501)
ZOF: for goods receipts without production orders
(mvt types 521 and 531)
You can also define your own account groupings. If you intend to post goods issues for cost centers (mvt type 201) and goods issues for orders (mvt type 261) to separate consumption accounts, you can assign the account grouping ZZZ to movement type 201 and account grouping YYY to movement type 261.
@1A@Caution
If you use goods receipts without a purchase order in your system (movement type 501), you have to check to which accounts the account groupings are assigned ZOB
If you expect invoices for the goods receipts, and these invoices can only be posted in Accounting, you can enter a clearing account (similar to a GR/IR clearing account though without open item management), which is cleared in Accounting when you post the vendor invoice.
Note that the goods movement is valuated with the valuation price of the material if no external amount has been entered.
As no account assignment has been entered in the standard system, the assigned account is not defined as a cost element. If you assign a cost element, you have to enter an account assignment via the field selection or maintain an automatic account assignment for the cost element.
Purchase order with account assignment (KBS)
You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
Exchange rate differences in the case of open items (KDM)
Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
Differences due to exchange rate rounding, Materials Management (KDR)
An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
KDV - No documentation currently available.
Consignment liabilities (KON)
Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
None for consignment liabilities
PIP for pipeline liabilities
Offsetting entry for price differences in cost object hierarchies (KTR)
The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
LKW - No documentation currently available.
Price differences (PRD)
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
None for goods and invoice receipts against purchase orders
PRF for goods receipts against production orders and
order settlement
PRA for goods issues and other movements
PRU for transfer postings (price differences in the case
of external amounts)
PRK - No documentation currently available.
PRP - No documentation currently available.
PRQ - No documentation currently available.
PRV - No documentation currently available.
PRY - No documentation currently available.
RAP - No documentation currently available.
RKA - No documentation currently available.
Provision for delivery costs (RUE)
Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
Taxes in case of transfer posting GI/GR (TXO)
This transaction/event key is only relevant to Brazil (nota fiscal).
Revenue/expense from revaluation (UMB)
This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
Expenditure/income from revaluation (UMD)
This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
Unplanned delivery costs (UPF)
Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
Input tax, Purchasing (VST)
Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
Goods issue, revaluation (inflation) (WGI)
This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
Goods receipt, revaluation (inflation) (WGR)
This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
GR/IR clearing (WRX)
Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
Caution
You must set the Balances in local currency only indicator for the GR/IR clearing account to enable the open items to be cleared. For more on this topic, see the field documentation.
see the below link also
http://209.85.175.104/search?q=cache:7FJheuTAxiQJ:help.sap.com/bp_afsv1500/CP_AFS_DE/documentation/AFS_Solution_Scope_EN_DE.docprintsettingsforgoodsissue%26receiptsandLogisticsinvoice+verification.&hl=en&ct=clnk&cd=2
thanks
saGAR
REWARD ME IF USEFULL

MM and SD question

Hi,
I'm setting the following procedure:
1) A customer makes an order and I create a sales order from SD with trx VA01 which creates automatically a purchase requisition (PRQ);
2) I convert the purchase requisition into a purchase order (PO) because I'll buy the material the customer ordered from a vendor;
3) I post the goods receipt related to that purchase order (PO);
4) I post the outbound delivery for that customer and then I post the goods issue;
5) I post the logistic invoice verification (MIRO) for the material I buy from a vendor and I resell to the above customer;
6) I post the billing document;
but......:
is there a way to allow logistic invoice verification of an invoice so that is not possible to do it before the SD invoice has been posted ?
Regards

Hi,
To the best of my knowledge not possible, however you can keep the invoice in block mode so as to not pay the vendor, once the SD cycle is complete you may then manually release the vendor invoice via MRBR & then proceed with your MM cycle.
Hope the above helps.
Regards,
Vivek

Exchange rate diff. influencing the available cost of WBS-element

Hi all,
here is a intricate problem I need help to solve. I am not so very experienced withon CO/PS, my main competence is within PM. This issue involves PM/MM/PS and CO so I am not sure if this is the correct group to post to, but I give it a try..
In PM (Plant Maintenance) workorders the u201DPlanned Costu201D is calculated. Exchange rate type for the u201DPlanned costu201D is picked from the CO Cost Version u201D0u201D that uses exchange rate type u201DPu201D. This is a exchange rate type that have one yearly fixed exchange rate. The actual costs are posted with exchange rate type M, which is daily updated.
The Planned cost in the workorder is a part of the u201DAssigned Costu201D that are influencing the available budget on the WBS-element. u201DRemaining/Residual order planu201D.
In cases where the PRQ/PO are created in other currency than the Company code currency we have a problem:
The difference in exchange rate are causing the u201DAvailable budgetu201D to be too low u2013 and the only workaround I have found is to decrease the planned cost in the WO to release the available cost for the Budget. (make the available cost higher )
Does anyone have an idea how to solve this?
- I have thought of setting the exchange rate type for the planned cost to be the same as for the actual costs u2013 but it is not recommended to change the exchange rate type in CO for cost version u201D0u201D and not a good ide to change the exchange rate type for actual cost eather. This will also not solve the problem of exchange rate difference caused by PRQ/PO beeing created for a whole year for varying exchange rates.
- Is there a way to exclude the u201D Remaining/Residual order planu201D from the u201DAssigned Costu201D? And what consequences will this have? Only cost from PRQ/PO will appear? (Since internal material (reservations) and internal hours not triggers a PRQ/PO)? I see there is a transaction CJE5 where you can exclude the u201D Remaining/Residual order planu201D from the u201DAssigned costu201D u2013 but I think this will only exclude it from beeing shown in the report S_ALR_87013558?- not from the calculation of available cost at the WBS-element? which is what I need. (see Note 668240)
-Is there any u201DExchange rate differenceu201D setting in the customizing u2013 how exchange rate difference are treated for PM orders? And will this help my problem?
Best regards
Ellen

Hi ,
try this way...
Go to T-code>CJE0>Enter CO Area-->and execute the report 12KST1A ->in the selection screen -->
go to menu -->system -->status check the program name and ...copy
next go to se38 and copy yhe above program name and execute and use submit report with selections,,,,
Prabhudsa

Kernel 2.6.2 & 8139too

I am having trouble with my network module 8139too. After upgrading my kernel to 2.6.2 from the stock arch kernel 2.4.21, my network won't start.
modprobe 8139
dhcpcd eth0
Network will not start on boot. dmesg reports that the dhcp request has timed out. Weird thing though is that I can pop in knoppix and get network access fine.

Here is what I did:
pacman -Syu
pacman -S kernel26
rebooted
generate-modprobe.conf > /etc/modprobe.conf
none /dev/pts devpts defaults 0 0; to fstab
network will not start. Here is my dmesg output:
king if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 4112.38 BogoMIPS
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
CPU0: AMD Athlon(tm) XP 2800+ stepping 00
per-CPU timeslice cutoff: 1462.65 usecs.
task migration cache decay timeout: 2 msecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Total of 1 processors activated (4112.38 BogoMIPS).
ENABLING IO-APIC IRQs
init IO_APIC IRQs
IO-APIC (apicid-pin) 1-2, 1-16, 1-17, 1-18, 1-19, 1-20, 1-21, 1-22, 1-23 not connected.
..TIMER: vector=0x31 pin1=0 pin2=-1
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2079.0127 MHz.
..... host bus clock speed is 332.0660 MHz.
Starting migration thread for cpu 0
Brought up 0 CPUs
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=2
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040116
IOAPIC[0]: Set PCI routing entry (1-9 -> 0x71 -> IRQ 9 Mode:1 Active:0)
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [_SB_.PCI0.P0P3._PRT]
ACPI: PCI Interrupt Routing Table [_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 16)
ACPI: PCI Interrupt Link [LNKB] (IRQs 18)
ACPI: PCI Interrupt Link [LNKC] (IRQs 18)
ACPI: PCI Interrupt Link [LNKD] (IRQs 19)
ACPI: PCI Interrupt Link [LNKE] (IRQs 16)
ACPI: PCI Interrupt Link [LUS0] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [LUS1] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [LUS2] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [LKLN] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [LAPU] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [LAUI] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [LKMO] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [LKSM] (IRQs 23)
ACPI: PCI Interrupt Link [LFWR] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [LETH] (IRQs 20 21 22)
ACPI-0145: *** Error: Return object type is incorrect [_SB_.LATA._CRS] (Node c154cb60), AE_TYPE
ACPI: PCI Interrupt Link [LATA] (IRQs 20 21 22)
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
ACPI: Unable to set IRQ for PCI Interrupt Link [LKSM] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: PCI Interrupt Link [LAPU] enabled at IRQ 20
IOAPIC[0]: Set PCI routing entry (1-20 -> 0xa9 -> IRQ 20 Mode:1 Active:0)
00:00:05[A] -> 1-20 -> IRQ 169
ACPI: PCI Interrupt Link [LAUI] enabled at IRQ 22
IOAPIC[0]: Set PCI routing entry (1-22 -> 0xb1 -> IRQ 22 Mode:1 Active:0)
00:00:06[A] -> 1-22 -> IRQ 177
ACPI: PCI Interrupt Link [LKMO] enabled at IRQ 21
IOAPIC[0]: Set PCI routing entry (1-21 -> 0xb9 -> IRQ 21 Mode:1 Active:0)
00:00:06[b] -> 1-21 -> IRQ 185
ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 22
Pin 1-22 already programmed
ACPI: PCI Interrupt Link [LUS1] enabled at IRQ 21
Pin 1-21 already programmed
ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 20
Pin 1-20 already programmed
ACPI-0145: *** Error: Return object type is incorrect [_SB_.LATA._CRS] (Node c154cb60), AE_TYPE
_CRS returns NULL! Using IRQ 20 fordevice (PCI Interrupt Link [LATA]).
ACPI: PCI Interrupt Link [LATA] enabled at IRQ 20
Pin 1-20 already programmed
ACPI: Unable to set IRQ for PCI Interrupt Link [LFWR] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: PCI Interrupt Link [LKLN] enabled at IRQ 22
Pin 1-22 already programmed
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKA] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 18
IOAPIC[0]: Set PCI routing entry (1-18 -> 0xc1 -> IRQ 18 Mode:1 Active:0)
00:01:00[b] -> 1-18 -> IRQ 193
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKA] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
Pin 1-18 already programmed
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 18
Pin 1-18 already programmed
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKA] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
Pin 1-18 already programmed
Pin 1-18 already programmed
Pin 1-18 already programmed
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKA] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
Pin 1-18 already programmed
number of MP IRQ sources: 15.
number of IO-APIC #1 registers: 24.
testing the IO APIC.......................
IO APIC #1......
.... register #00: 01000000
....... : physical APIC id: 01
....... : Delivery Type: 0
....... : LTS : 0
.... register #01: 00170011
....... : max redirection entries: 0017
....... : PRQ implemented: 0
....... : IO APIC version: 0011
.... register #02: 00000000
....... : arbitration: 00
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 00F 0F 0 0 0 0 0 1 1 31
01 00F 0F 0 0 0 0 0 1 1 39
02 000 00 1 0 0 0 0 0 0 00
03 00F 0F 0 0 0 0 0 1 1 41
04 00F 0F 0 0 0 0 0 1 1 49
05 00F 0F 0 0 0 0 0 1 1 51
06 00F 0F 0 0 0 0 0 1 1 59
07 00F 0F 0 0 0 0 0 1 1 61
08 00F 0F 0 0 0 0 0 1 1 69
09 001 01 0 1 0 0 0 1 1 71
0a 00F 0F 0 0 0 0 0 1 1 79
0b 00F 0F 0 0 0 0 0 1 1 81
0c 00F 0F 0 0 0 0 0 1 1 89
0d 00F 0F 0 0 0 0 0 1 1 91
0e 00F 0F 0 0 0 0 0 1 1 99
0f 00F 0F 0 0 0 0 0 1 1 A1
10 000 00 1 0 0 0 0 0 0 00
11 000 00 1 0 0 0 0 0 0 00
12 001 01 1 1 0 0 0 1 1 C1
13 000 00 1 0 0 0 0 0 0 00
14 001 01 1 1 0 0 0 1 1 A9
15 001 01 1 1 0 0 0 1 1 B9
16 001 01 1 1 0 0 0 1 1 B1
17 000 00 1 0 0 0 0 0 0 00
IRQ to pin mappings:
IRQ0 -> 0:0
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9-> 0:9
IRQ10 -> 0:10
IRQ11 -> 0:11
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ18 -> 0:18
IRQ20 -> 0:20
IRQ21 -> 0:21
IRQ22 -> 0:22
.................................... done.
ACPI: Unable to set IRQ for PCI Interrupt Link [LKSM] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: No IRQ known for interrupt pin A of device 0000:00:01.1
ACPI: Unable to set IRQ for PCI Interrupt Link [LFWR] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: No IRQ known for interrupt pin A of device 0000:00:0d.0
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKA] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: No IRQ known for interrupt pin A of device 0000:02:06.0
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKA] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: No IRQ known for interrupt pin A of device 0000:02:06.1
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: No IRQ known for interrupt pin A of device 0000:02:07.0
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKA] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: No IRQ known for interrupt pin A of device 0000:01:00.0
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
Machine check exception polling timer started.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
ikconfig 0.7 with /proc/config*
VFS: Disk quotas dquot_6.5.1
devfs: v1.22 (20021013) Richard Gooch ([email protected])
devfs: boot_options: 0x1
Installing knfsd (copyright (C) 1996 [email protected]).
udf: registering filesystem
SGI XFS with ACLs, security attrs, no debug enabled
SGI XFS Quota Management subsystem
Initializing Cryptographic API
ACPI: Power Button (FF) [PWRF]
ACPI: Processor [CPU1] (supports C1)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
pty: 256 Unix98 ptys configured
Linux agpgart interface v0.100 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: IDE controller at PCI slot 0000:00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA
hda: SAMSUNG SV1204H, ATA DISK drive
hdb: WDC WD600BB-32BSA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: HP DVD Writer 300c, ATAPI CD/DVD-ROM drive
hdd: TDK CDRW4800B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 234493056 sectors (120060 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3
hdb: max request size: 128KiB
hdb: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
/dev/ide/host0/bus0/target1/lun0: p1 p2
hdc: ATAPI 40X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 48X CD-ROM CD-R/RW CD-MRW drive, 2048kB Cache, UDMA(33)
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
ehci_hcd 0000:00:02.2: EHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: irq 169, pci mem e086dc00
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
drivers/usb/core/usb.c: registered new driver hiddev
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
input: PC Speaker
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
8regs : 3152.000 MB/sec
8regs_prefetch: 2868.000 MB/sec
32regs : 2388.000 MB/sec
32regs_prefetch: 1932.000 MB/sec
pIII_sse : 3392.000 MB/sec
pII_mmx : 5564.000 MB/sec
p5_mmx : 7456.000 MB/sec
raid5: using function: pIII_sse (3392.000 MB/sec)
md: multipath personality registered as nr 7
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.0.0-ioctl (2003-06-04) initialised: [email protected]
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
NET: Registered protocol family 1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
ACPI: (supports S0 S1 S3 S4 S5)
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 240k freed
Adding 586144k swap on /dev/discs/disc0/part2. Priority:-1 extents:1
EXT3 FS on hda3, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
8139too Fast Ethernet driver 0.9.27
ACPI: Unable to set IRQ for PCI Interrupt Link [LNKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
ACPI: No IRQ known for interrupt pin A of device 0000:02:07.0
eth0: RealTek RTL8139 at 0xe08c1c00, 00:e0:29:71:88:aa, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139B'
Disabled Privacy Extensions on device c0572980(lo)
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00002000. (queue head)
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000.
eth0: Tx descriptor 3 is 00002000.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00002000. (queue head)
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000.
eth0: Tx descriptor 3 is 00002000.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00002000. (queue head)
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000.
eth0: Tx descriptor 3 is 00002000.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Here is my rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# Localization
# Note: HARDWARECLOCK is either "UTC" or "localtime"
KEYMAP=us
TIMEZONE=Arizona
HARDWARECLOCK="UTC"
# Networking
HOSTNAME="menator"
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
MODULES=(8139too ehci-hcd usb-ohci !usbserial !ide-scsi)
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# (prefix an interface in INTERFACES with a ! to disable it)
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcpcd"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
DAEMONS=(!pcmcia network crond inetd)
# End of file

PRQs.

Similar Messages

Maybe you are looking for