OBYC Delivery Costs Transaction Key

Hi,
I want to change the GL accounts that are impacted when i post for delivery costs in a Purchase Order. Can someone let me know in OBYC what is the 'Transaction' where i can configure for the same.
Please Advise.
Thanks,
Safi

Hi,
Please check transaction key UPF for Unplanned delivery costs or FRE for Purchase freight.
Assign points, if useful

Similar Messages

  • OBYC - New Transaction Key

    Hello Masters,
    I would like to know how is the process to create a new Transaction Key in OBYC to assing a new account for a new delivery cost in the Good Receipt.
    Thanks in advance.

    Hello,
      You can create a new Transaction Key in SPRO->Materials Management->Purchasing->Conditions->Define Price Determination Process->Define Transaction/Event Keys. Then assign this in to the Pricing Procedure (SPRO->Materials Management->Purchasing->Conditions->Define Price Determination Process->Define Calculation Schema). Now you can configure Account Determination using OBYC for the Transaction Key created by you.
    Thanks,
    Venu

  • G/L Account  for Unplanned Delivery cost.

    Hi,
    I have a requirement to distribute the Unplanned Delivery cost to different G/L  accounts based on the material type of the item.
    Is there any User exit or standard setting to solve this.
    Thanks & regards,
    Maruthu

    Hi
    Unplanned delivery costs can be trigerred by customizing the the account assignemnts in OBYC under UPD transaction key.
    For trigerring different G/L accounts based on the Material type, use Enhancement LMR1M002- customer exit EXIT_SAPLKONT_011.
    In that you need to determine the G/L account based on account category refernce & Event key UPF.
    You need to take help of ABAPErs for the same
    Award points if useful
    Thanks & regards
    Kishore

  • Unplanned Delivery Costs Post to a different GL Account Cost Center err

    Hi,
    We added GL account  in config (OBYC >> UPF Transaction key ) such that 'Unplanned Delivery Costs' entered during invoice entry in MIRO will be posted a different GL account. We also changed in config from 'Distribute among invoice items' to 'Different GL Line'.
    When we try to post Invoice and add amount in 'Unplanned delivery costs' field in MIRO, system is giving error to enter 'Cost Center' since GL account characteristics is such  that Cost center is mandatory. The Cost Center field at item level in MIRO is disabled. Remember, we want to process this for INVENTORY items only, meaning items that go to stock and later issued, and not for POs created with 'Cost center' as Account assignment. We can create another GL and no cost element and assign that GL Account in OBYC for UPF Transaction key, but the client's requirement is to create 'Cost Accounting Doc' too when invoice is posted, along with Accounting and profit center docs.
    How do we fix above error ?
    Niranjan

    Closing this thread as the heading of the 'message' did not appear properly. Posting another message so heading of 'message' shows correctly.
    Niranjan

  • OBYC- GBB- Transaction keys

    hi
    Can any one tell me what are these keys meant for
    In GBB: AUA,AUF,BSA,INV,VBR,VAX,VAY,ZOF,ZOP are some of the keys I have mentioned.
    I want to know to which key I have assign the inventory,scrap,consumption G/L codes ,etc for process industry in repetitive and discrete manufacturing scenario.

    Hi,
    Check this..
         Transactions     
         Agency business: income (AG1)     
         This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.     
         Agency business: turnover (AG2)     
         This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.     
         Agency business: expense (AG3)     
         This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.     
         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.     
         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.     
         Account determination of valuated sales order stock and project stock     
         Note that for valuated sales order stock and project stock (special stock E and Q) and for the transaction/event keys BSX andGBB, you must maintain an account determination to avoid receiving warning messages when entering data (purchase order or transfer posting) for valuated stock.     
         During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if you enter the data for valuated stock at a later point in time.     
         Revaluation of other consumption (COC)     
         This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.     
         Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger application. This revaluation can either take place in the account where the original postings were made, or in a header account.     
         The header account is determined using the transaction/event key COC.     
         Del credere (DEL)
         Transaction/event key for the payment/invoice list documents in Purchasing. The account key is needed in the calculation schema for payment/settlement processing to determine the associated revenue accounts.
         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.
         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.
         Account determination of valuated sales order stock and project stock
         Note that for valuated sales order stock and project stock (special stock E and Q) and for the transaction/event keys BSX andGBB, you must maintain an account determination to avoid receiving warning messages when entering data (purchase order or transfer posting) for valuated stock.
         During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if you enter the data for valuated stock at a later point in time.
         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 Materials Management(AVR) (KDG)
         When you carry out a revaluation of single-level consumption in the material ledger for an alternative valuation run, the exchange rate difference accounts of the materials are credited with the exchange rate differences that are to be assigned to the consumption.
         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.
         Exchange Rate Differences from Lower Levels (KDV)
         In multi-level periodic settlement in the material ledger, some of the exchange rate differences that have been posted during the period in respect of the raw materials, semifinished products and cost centers performing the activity used in the manufacture of a semifinished or finished product are debited or credited to that semifinished or finished product.
         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.
         Accruals and deferrals account (material ledger) (LKW)
         If the process of material price determination in the material ledger is not accompanied by revaluation of closing stock, the price and exchange rate differences that should actually be applied to the stock value are contra-posted to accounts with the transaction/event key LKW.
         If, on the other hand, price determination in the material ledger is accompanied by revaluation of the closing stock, the price and exchange rate differences are posted to the stock account (i.e. the stock is revalued).
         Price Difference from Exploded WIP (Lar.) (PRA)
         If you use the WIP revaluation of the material ledger, the price variances of the exploded WIP stock of an activity type or a business process are posted to the price differences account with transaction/event key PRA.
         Differences (AVR Price) (PRC)
         In the alternative valuation run in the material ledger, some of the variances that accrue interest in the cost centers, are transfer posted to the semifinished or finished product.
         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)
         Price Differences (Material Ledger, AVR) (PRG)
         When you carry out a revaluation of single-level consumption in the material ledger during the alternative valuation run, the price difference accounts of the materials are credited with the price differences that are to be assigned to the consumption.
         Price differences in cost object hierarchies (PRK)
         In cost object hierarchies, price differences occur both for the assigned materials with standard price and for the accounts of the cost object hierarchy. In the course of settlement for cost object hierarchies after settlement via material account determination, the price differences are posted via the transaction PRK.
         Price Difference from Exploded WIP (Mat.) (PRM)
         If you use the WIP revaluation of the material ledger, the price and exchange rate differences of the exploded WIP stock of a material are posted to the price difference account with transaction/event key PRM.
         Price differences, product cost collector (PRP)
         During settlement accounting with regard to a product cost collector in repetitive manufacturing, price differences are posted with the transaction PRP in the case of the valuated sales order stock.
         This transaction is currently used in the following instances only:
         - Production cost collector in Release 4.0
         - Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
         Offsetting entry: price differences, product cost collector (PRQ)
         The offsetting (contra) entry to price difference postings (transaction PRP) in the course of settlement accounting with respect to a product cost collector in repetitive manufacturing in the case of the valuated sales order stock is carried out via transaction PRQ.
         This transaction is currently used in the following instances only:
         - Production cost collector in Release 4.0
         - Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
         Price Differences from Lower Levels (PRV)
         In multi-level periodic settlement in the material ledger, some of the price differences posted during the period in respect of the raw materials, semifinished products, and cost centers performing the activity used in a semifinished or finished product, are transfer posted to that semifinished or finished product.
         Price differences for material ledger (PRY)
         In the course of settlement in the material ledger, price differences from the material ledger are posted with the transaction PRY.
         Expense and revenue from revaluation (retroactive pricing, RAP)
         This transaction/event key is used in Invoice Verification within the framework of the revaluation of goods and services supplied for which settlement has already taken place. Any difference amounts determined are posted to the accounts assigned to the transaction/event key RAP (retroactive pricing) as expense or revenue.
         At the time of the revaluation, the amounts determined or portions thereof) are posted neither to material stock accounts nor to price difference accounts. The full amount is always posted to the "Expense from Revaluation" or "Revenue from Revaluation" account. The offsetting (contra) entry is made to the relevant vendor account.
         Invoice reductions in Logistics Invoice Verification (RKA)
         This transaction/event key is used in Logistics Invoice Verification for the interim posting of price differences in the case of invoice reductions.
         If a vendor invoice is reduced, two accounting documents are automatically created for the invoice document. With the first accounting document, the amount invoiced is posted in the vendor line. An additional line is generated on the invoice reduction account to partially offset this amount. With the second accounting document, the invoice reduction is posted in the form of a credit memo from the vendor. The offsetting entry to the vendor line is the invoice reduction account. Hence the invoice reduction account is always balanced off by two accounting documents within one transaction.
         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.
         Inflation posting (WGB)
         Transaction/event key that posts inflation postings to a different account, within the handling of inflation process for the period-end closing.
         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.
         WIP from Price Differences (Internal Activity) (WPA)
         When you use the WIP revaluation of the material ledger, the price variances from the actual price calculation that are to be assigned to the WIP stock, an activity type or a business process are posted to the WIP account for activities.
         WIP from Price Differences (Material) (WPM)
         When you use the WIP revaluation of the material ledger, the price and exchange rate differences that are to be assigned to the WIP stock of a material are posted to the WIP account for material.
         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.
         GR/IR clearing for material ledger (WRY)
         This transaction/event key is not used from Release 4.0 onwards.
         Prior to 4.0, it was used for postings to the GR/IR clearing account if the material ledger was active. As of Release 4.0, the transaction is no longer necessary, since postings to the GR/IR account in parallel currencies are possible.
         Customers who used the transaction WRY prior to Release 4.0 must make a transfer posting from the WRY account to the WRX account in order to ensure that the final balance on the WRY account is zero.
    Thanks,
    Rau

  • OBYC - VKA transaction key

    Please anybody clarify my following doubt:
    I see that for cost of goods sold entry, in OBYC, we can use transaction key: VAX
    Then what is the purpose of VKA key ?  Is it also relating to Cost of Goods Sold ?

    HI 
        this is obyc for integration between fi and mm where transaction key vkoa using for sales revenue account only   
    BEST  
    NASERK
    Edited by: naserk on Dec 7, 2011 7:36 AM
    Edited by: naserk on Dec 7, 2011 7:37 AM

  • Transaction code for creation of  transaction keys in obyc

    Dear Experts,
    Can u tell me what is the transaction code for creation of transaction keys in obyc asap.
    Thanks & Regards,
    Radhika.

    Hi
    There is no TCode and the path is
    SPRO-Material Management-Purchasing-Conditions-Price Determination....
    Cheers
    Srinivas

  • Problem with MIRO Transaction while posting Un planned Delivery cost

    Hi all,
    We have entered all the details including unplanned delivery cost in transaction MIRO. When we are trying to post the same by using post button directly with out simulation, system is asking for plant details.
    For first time we have entered wrong Plant details , system immediately asking again for plant details.
    Next time even if we entered correct plant details, the system is coming out from the screen MIRO and it is not posting the document.
    If you go through simulate button and it is working fine and it is giving Warning message, If we enter the wrong Plant details.
    My Client requirement is If we post the MIRO transaction including Un planned delivery cost with Post button. If we enter wrong plant details. System will through Error message, until we enter the correct plant details.
    Is there any way to do this. Pl help me in this regard.
    Regards,
    Ramesh

    In the MIRO T Code, U can see PO reference tab is there, Just below it there is Purchase order/scheduling agreement field is there . enter the purchase order number in blank field next to Purchase order/scheduling agreement and press enter. U can see it will  take the required data automatically.
    hope this helps
    regards

  • [HELP] OBYC Transaction Key - DIF

    Hello Gurus,
    Is there anyway to set another transaction key for small differences?
    I have a customer requirement to set another transaction key for small differences in invoice. And i don't know if it's possible to set a different transaction key than DIF.
    If there is a way to do it, can anyone show me the way?
    Regards,
    Rafael

    Hi Rafael,
    The transaction DIF(Materials management small differences) is triggered in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
    For this you should define the G/L accounts against the key in OBYC settings.
    Let us know why you want diff transaction other then  DIF.

  • Query on OBYC  Transaction key

    Dear Experts ,
    I have a few queries regarding automatic postings :
    1.What process triggers the transaction key AUM ? what type of account should be assigned here ?
    2.What process triggers the transaction key BSV? what type of account should be assigned here ? Hw different is it from GBB-VBO ?
    3. What is the difference between DIF , PRD & UMB ?
    4. Is GBB-VKA relevant for make to stock scenario ?
    Regards
    Anis

    Hi
    1) AUM is triggered if the material iin supplying planrt is  maintained either in MAP or Standard price and  material in recieving plant is in stamdard price and there should be a price difference.The differencial amount will be posted to the Expense/Income  account through AUM
    2)BSV will be triggered during subcontracting GR.it is the Transaction event key which defines the Change in stock account .This is maintained to accomodate the credit side entry for the output material during GR.Whereas GBB-VBO is for input material consumtion during subcontracting GR.It provides the Debit side entry for Input material consumption
    3)DIF is triggered during IV if there is balance and you still want to post it
       PRD is triggered if the material is maintained as Standard Price and the value is differenet from the PO value .
       UMB is triggered if you want to revaluate the material th MR21
    4) GBB-VKA is for make to order scenario where you make a PO directly with reference to sales order
    Regards
    Sandeep

  • OBYC - Transaction key FR1

    Dear All,
    I want to add general modified in rules of transaction key FR1? as per standard SAP, we have debit/credit, valuation modifier and valuation classes are there.
    is there any possibility to add, because as per our client i have to assign different Freight clearing accounts based on Geographical area. by using general modifier i want to assign different Freight clearing accounts.
    Can any one suggest me - how we can meet the requirement?
    thanks & regards,
    Ramesh B

    hi,
    i didn't find any option to add new rules for transaction keys.
    For example for transaction key "WRX" - accounts are determined based on : debit/credit, general modificaiton,valuation modifier,valuation class.
    For FR1 - we have only debit/credit, valuation modifier,valuation class. But here i want to add general modificaiton.
    is it possible. if yes, how can we add.
    I don't want to create any new transaction keys, because we are using only one MM pricing schema and one condition type.
    thanks & regards,
    Ramesh B

  • Unplanned delivery cost account assignment

    Dear Friends,
    I have configure the transaction key UPF in obyc. Here I have entered Inc/Dec account, but during the MIR7 Simulation, The Unplanned delivery cost is hitting Inventory Account of material.
    Can You please suggest, where the issue may be and how to resolve it.
    Rgds, Kraheja.

    Hi,
    Check the settings in the below mention path
    SPRO--  MM -- Invoice Verification --- Logistics Invoice Verification -- Incoming Invoice --Configure How Unplanned Delivery Costs Are Posted Assign 2 against your company code. It will help you to post in another line item
    reagrds

  • MIRO - Unplanned delivery costs

    hi all,
    in MIRO transaction there is a field name "unplanned delivery costs" today all this costs post to GR/IR account and our company want to define a seperate GL account to unplanned delivery costs (INVFO-BEZNAK)
    we ask to know where in the customizing we should do this definition
    thanks,
    meir

    Dear meir
    There is an additional configuration needed for posting Planned Delivery Cost to a specific G/L account apart from OBYC  - Transaction key UPF
    Please use the path below to do your configuration:
    SPRO-->Materials Management --> Logistics Invoice Verification --> Incoming Invoice --> Configure how Unplanned Delivery Cost is Posted
    Here you have to assign the Co Code with Unplanned Delivery Cost type 2 (Post to Diff G/L Acct)
    This will resolve your problem.
    Cheers
    IMK

  • To add new transaction key

    All SAP Gurus,
    We want  to add new transaction key in account determination (OBYC).
    How to add it?
    Regards,

    Hi Rajan,
    If you are talking about the transaction key at Materials Management postings (MM) group (RMK),
    it is merely not advisable to create a transaction key.
    You have General modification like BSA, INV etc for differentiating the postings.
    The transation key mentioned in the earlier mail is for below purpose:
    To enable the system to find the relevant account for provisions (
    accrued delivery costs or miscellaneous provisions, for example),
    must assign a transaction/event (internal processing) key to each
    condition type that is relevant to provisions in the step Define 
    Calculation Schema.                                              
    Cheers
    Arun.

  • G/L Account assignment - Planned delivery cost

    Hi,
    Is it possible via customizing to determine an other G/L Account for a planned delivery cost condition?
    Currently when I want to post the IR I can see two lines for the PO item. One for the cost of the material and one for the delivery cost. However both are having the same G/L Account.
    This planned delivery cost has an other transaction key assigned in the pricing schema and account determination for this key is setup in OBYC (automatic postings). So I supposed the system will use an other account but that's not the case.
    In case that's not possible. Can I give the condition type an other condition category to obtain this result? The cost of material and the cost of delivery should both go into separeted accounts.
    Thanks in advance for your replies!
    Regards,
    Steven

    Hi,
    Freight clearing (FR1), provision for freight charges (FR2)-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.
    Or you can create Z condition type and for same you can assign different GL in OBYC which system trigger during GR to post the value in to different GL
    Rg

Maybe you are looking for

  • Creating xml file from fields of a fmb

    Hi, What i want to do is to create a "generic" button (which can work for all forms of my application) which ables the application to create a xml file completed with all fields on my form. The matter is that i can't know by advance all fields of my

  • In-App Mail (and SMS)-iPhone OS 3.1.3

    I originally had the following code: NSURL *emailURL = [[NSURL alloc] initWithString:emailAddress]; if ([[UIApplication sharedApplication] openURL:emailURL]) with the NSString emailAddress set up properly. What would happen then? I discovered the Mes

  • All of a sudden, report doesn´t work anymore

    Getting really tired of this whole SCOM-thing the last days. Now the reporting doesn´t work anymore. We changed NOTHING. State went from Zero to Healthy 4:14 PM on friday last week. Alright. But a few hours later, when nobody was here anymore, it cha

  • Album frames don't display properly: Since .MAC converted to MobileME help?

    ORIGINAL MESSAGE POSTED TO APPLE SUPPORT Ever since .MAC was recently down - and converted to Mobile Me - I have been having problems with my iWEB site: 1. Frames around Photo Albums no longer display (on mac or win web browsers) - On Windows Compute

  • This phone is **bleep**

    This phone is terrible. I have been a blackberry supporter for 6 years, I always defend their phones against IPhone people and I have always said I will stick with them but this Z10 is a piece of **bleep**. I have gone from being a net promoter to a