FAGLF101-Account determination for transaction V02 is missing for account

Morning
When I run the "faglf101" transaction, i get this error : 
"Account determination for transaction V02 is missing for account 0000401142
Y1 PCG                                                                     
Message no. FR005       "
I have tried to customize the adjustments accounts and postings keys in the IMG
"Financial accounting > Accounts Receivable and payable >
Business Transactions > Closing >Regrouping > Define adjustments
accounts for changes reconciliation accounts".,  but i don't see the part "Regrouping" in the IMG.
I have tried to use the OBBW transaction, but his transaction code "A00-Transfer postings: changed recon. acct" don't correspond to mine (V02);
We are in ECC6.
Can somebody explain to me how can i correct this error please?
Best regards

This is meant for account determination for Receivables/payables sorting. Check your configuration in SPRO->General Ledger Accounting (New)->Periodic Processing->Reclassify->Transfer and Sort Receivables and Payables->Define Adjustment Accounts for Receivables/Payables by Maturity

Similar Messages

  • Pls tell the revenue account determination Menu Path or Tx Code for PO

    Hi all,
    Pls tell the revenue account determination Menu Path or Tx Code for PO as we have VKOA in SD, or tell me how to do G/L account determination for PO
    Thanx
    Vikas Chhabra

    hi
    u can do it in spro>mm>Valuation and Account Assignment>Account Determination>Account Determination Without Wizard>Configure Automatic Postings
    t code is OMWB or OBYC
    take help of following link
    http://www.sapstudymaterials.com/search/label/0170-MM-FICO%3A%20Automatic%20Account%20Determination
    regards
    kunal

  • DMEE - error in conditions for node: node attribute missing for ref. ID

    Hi,
    I've got an error 'error in conditions for node XXX: node attribute missing for ref. ID XXXXX' - may I kindly ask you to suggest where this attribute need to be specified.
    thanks in advance.
    BR
    Renatas

    Hi Renatas ,
    When using Reference IDs for Conditioning in DMEE you should give  node attribute in the  2nd field of the  conditioning ....
    look the below example
    Arg1-1     Arg1-2     T     O     Arg2-1     Arg2-2     T      O
    E2E     1A     3     =     SPACE          1     
    DMEE: node attribute as a comparison value
    Definition
    Node attribute to be used in a condition. The following values are possible:
    1: contents in output format
    1A: contents in internal format
    2: length
    3: counter reading
    4: counter reading of segments per file (only for DMEE format tree)
    5: counter reading of segments with CR/LF (only for DMEE format tree)
    Regards,
    Komaravolu

  • Error in account determination ( Created a new tax code for CST 2%)

    Dear friends,
    iam facing a problem while doing vf01.the error is o account detrmination for jn7 which is for condition type CST.
    My customer master is also checked
    I have maintained the account key and GL a/c for ers,erl,erf,jn6,jn7 etc in tcode vkoa.
    I have also mainatined the GL a/c for jn7 in tcode ob40 also.
    In ftxp also the rates are maintained.
    I have also maintained the condtion record for UTXJ  in vk11 tcode.
    Now still i dont know if i have missed out some step in customizing or mainatining some record
    I have a doubt in ob40. Lets say if i have 2 tax codes s7 & s8 , Do i need to maintain the G/L account for both tax codes?correct na. But in FTXP The G/L account is assigned automatically, inspite of that do i need to maintain ?
    Pls clarify, & Wishing u all a colourful HOLI in advance
    Thanks in advance
    Regards

    Dear SD teamsters,
    iam facing a problem while doing vf01.the error is  account detrmination for jn7 which is for condition type CST.
    My customer master is also checked
    I have maintained the account key and GL a/c for ers,erl,erf,jn6,jn7 etc in tcode vkoa.
    I have also mainatined the GL a/c for jn7 in tcode ob40 also.
    In ftxp also the rates are maintained.
    I have also maintained the condtion record for UTXJ in vk11 tcode.
    Now still i dont know if i have missed out some step in customizing or mainatining some record
    I have a doubt in ob40. Lets say if i have 2 tax codes s7 & s8 , Do i need to maintain the G/L account for both tax codes?cBut in FTXP The G/L account is assigned automatically, inspite of that do i need to maintain ?
    In OB40 there are two rules displayed, one is taxcode & the other is debit & credit . which do i need to select.
    Regards
    G.S.Gupta

  • Transaction Data Icon Missing For FlatFile Datasource

    Hi All,
    We are loading the data by using the flat file data is loaded successfully.But beside the cube we will have activation icon , Aggregates Icon and Transaction data icon. In our case we are missing transaction data icon.What could be the reason.
    But data loading is fine and for some of time chars also data missing .
    Pls anybody can throw some light on this.
    Thanks in Advance,
    Shah.

    Hello S SR,
    How r u ?
    just see the top and make the column adjustment like we do in MS-EXCEL you can see the Transactional Data ICON.
    Best Regards....
    Sankar Kumar
    +91 98403 47141

  • Hi Everybody, Ship to party not updating for Transaction number in "CRMD_ORDER" for some users?

    Process :
    1. We are updating ship to party for contracts(Transaction number ) , Here every thing is updating fine But i am facing the issue in CRMD_ORDER, Here what ever selected ship to party was not updating.
    2. i have find out the issue reason for failure  in  Debugging , its giving error as "  no_display_authority " in one standard function module  'CRM_ORDER_READ'.We are passing Header GUID to this FM .
    3. Even i went inside this FM 'CRM_ORDER_READ', Here it was checking for ACE(ACCESS Control ENGINE) authority check by using Standard FM
      "CRM_ORDER_CHECK_AUTHORITY_ACE"  this FM giving error as "Access denied by Access Control Engine".
    Can any help me on this how can i resolve this issue.
    Thanks in Advance.
    Regards,
    Venugopal

    Hi,
    Go to SPRO - SD - BASIC FUNCTIONS - PARTNER DETERMINATION Just check whther your partner function (SH) is assigned to your account group and also exists in the partner determination procedure.
    Just try and maintain it there against your account group and against your sales document type in VOV8.
    Also open your customer master for which you are trying to create this sales order. Just check whther in the partners tab , SH is shown? You can either use transaction BP or XD03.
    Let me know, reward points if helpful.
    Regards
    Ravi

  • How to implement bapi for transaction code f-02 for multiple line items

    Hi All,
    I am having one requirement to of implementing bapi for tcode f-02.
    I have identified the name of the badi e.i.  BAPI_ACC_GL_POSTING_POST.
    but i dont have any idea how implement it.
    i have multiple line items for one header.
    Please help me in this.
    Regards,
    Shoaib.

    HI
    In recording once u save, the recording comings out the transaction.
    If u want the pop-up to display before save. Then in recording also
    after entering all data and before Save press enter or do check.Try
    this way after that save the transaction.
    Regards,
    Raghu.

  • NNM iSPI Performance for Traffic silentInstall*.properties missing for Linux

    HP -- I've been trying to figure out a way to get this information to you, and this is the best I could find.  When performing a silent installation of HP NNM iSPI Performance for Traffic, you need the silentInstallExt.properties, silentInstallMaster.properties, and silentInstallLeaf.properties files.  These files are not supplied with the Linux installation DVD image (Software_NNM_iSPI_Perf_Traf_Linux_9.20_Eng_TB770-15009.iso) -- you might want to remedy that.  If anyone needs to find the files for a silent install on Linux, you can get them from the Windows installation DVD image (Software_NNM_iSPI_Perf_Traf_10.00_Win_TB770-15014.iso) in the Traffic_NNM_Extension, Traffic_Master, and Traffic_Leaf directories.

    HP -- I've been trying to figure out a way to get this information to you, and this is the best I could find.  When performing a silent installation of HP NNM iSPI Performance for Traffic, you need the silentInstallExt.properties, silentInstallMaster.properties, and silentInstallLeaf.properties files.  These files are not supplied with the Linux installation DVD image (Software_NNM_iSPI_Perf_Traf_Linux_9.20_Eng_TB770-15009.iso) -- you might want to remedy that.  If anyone needs to find the files for a silent install on Linux, you can get them from the Windows installation DVD image (Software_NNM_iSPI_Perf_Traf_10.00_Win_TB770-15014.iso) in the Traffic_NNM_Extension, Traffic_Master, and Traffic_Leaf directories.

  • Accounting Determination -FKFR  function is missing

    When I created the accounting document it doesn't release the accounting
    document to Finance and it comes up with the message -
    For object RF_BELEG YASH, number range interval 01 does not exist FBN1
    Message no. NR751
    Diagnosis
    The database table NRIV has the delivery class 'C', i.e. the SAP default settings are only in client 000.
    Procedure
    Create the missing number range interval in customizing.
    Transaction code: FBN1
    When you create the number range, it then comes up with the message
    Requested function FKFR is not available here
    Any help what might be causing this?  I could not figure out as I have done the account determination in VKOA.
    Regards,
    Jans

    Hi,
    For creating an accounting document, U need to have number range for specific fiscal year and for that specific company code.
    So, go to T. code SNRO, give object name as RF_BELEG.
    go to change mode. U have number range icon in the menu bar, create a number range for particular company code and save.
    Now go to VF01, and release billing document to accounting.
    Reward if helpful....
    Praveen.

  • Change GL account in OBYC for transaction keys GBB and BSV

    Dear Logistics Colleagues
    I would like to have your opinion on the following topic:
    I have an request to change an GL account in account determination (OBYC) for transactions:
    - GBB > Offsetting entry for inventory posting
    -BSV > Change in stock account
    What cutover should I consider or which actions should be executed before implementing the change?
    Many thanks in advance for your help?
    Regards,
    Mohamed

    Hi,
    Just check all the orders whose GR is done, there LIV also done, for the scenario where this key will be utilized,
    BSV - change in stock account, this will hit in subcontracting process. When you do GR against 101 mvt type this BSV will get credit, BSV is the balancing account to BSX for Finished goods, this amount goes to P&L accounts
    GBB - Most of the time this will be 0, because it is for offsetting entries, check there is no balance in this GL,
    If you want create OBYC for this 2 for some new valuation class then i do not think you need to look at cutover

  • Account determination for document splitting

    hi to everyone,
    When i try to clear the down payment against an invoice in F-39 its gives following error.
    "The online document splitting is active in your system. Here, each document is assigned to a accounting transaction variant and each document row to an item category.
    You determine for each business transaction variant which item categories can or must be posted here.
    A splitting rule is defined for each business transaction variant, which determines which item categories are to be split and how the splitting should be determined.
    Additional rows need to be created in a G/L account that was defined in the account determination in an account determination key.
    The following error occurred for the document you entered:
    No account has been entered for account determination key 000 in the chart of accounts".
    I had activated doc splitting and assigned std  method 0000000012 to it.i have also assign G/L accounts for document splitting. Still i am getting above error.
    Can anybody help me out.?
    its urgent
    thanks in advance
    tanuja naik

    Hi
    Account determination key 000 is for document splitting Zero balance clearing account. Create a clearing account and assign the same.
    Regards
    Venkat

  • Business transaction key in account determination..?

    Hi all
    Can anybody explain me in simple form form, what is business transaction key in account determination , for eg, GBB,BSA,BSX,PRD,VBR,.WRX....etc (Approximately 60 transaction keys in std SAP)
    If i want to do configuration the for new client, what are all the business transaction key,,, How the configuration wil happen..?
    Pls giv me expaination,
    Reply will be rewardable..
    Thanks
    sap-mm

    Hi MM,
    Please Search in SDN threads solution is given already in lot of threads.
    Go to SAP Library
    SPRO> Help> SAP Library
    Or go to SPRO> IMG> MM>Valuation and Account Assignment>Account determination> Account det without wizard> configure Automatic postings
    Click on IMG ACTIVITY DOCUMENTATION
    These transactions are important for Accounts.
    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
    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.
    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:
    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.
    Reg,
    Ashok
    assign points if useful.

  • Debugging PGI document for Account determination

    Hi ABAP gurus,
    Can anyone help me in debugging PGI process to find out the account determination . There were some issue in getting the correct GL account from customization (OBYC) and hence would like to place break point in appropriate function module . I have tried few FMs and these were not hit during PGI from VL02N. Can some one can help me in terms of Function module to place break point for this issue .
    Your immediate help in this regard is highly appreciated.
    with regards,
    Joseph Anand B

    Actually, his issue is very clear; he's looking for the point of account determination during goods issue because the configured accounts in OBYC are not the ones selected (or so it seems).
    Runtime Analysis is the best tool for things like this, unless you really enjoy debugging step by step.  Most automatic accounting postings go through AC_DOCUMENT_CREATE and AC_DOCUMENT_POST.  You'll find these function calls in your analysis.  You'll also find MB_CREATE_GOODS_MOVEMENT which will call the accounting posting.

  • Problem Receivable account determination, cash sales (EVV)

    Hello all,
    I need work with cash sales, billing type BV, then in the BV invoice type I have the EVV in the Account key for cash allocation.
    I create correctly the G/L account determination, introducing one account in the entry for the key EVV.
    And another for the receivables account, for example key ERL 700000
    When I save the invoice, the account determination procedure works correctly, it found the account 700000, but the FI doc is not generated....
    If i delete the EVV from the BV, the determination work correctly (accoutn 700000) but the cash account is not determined because I delete the EVV.
    ¿why is the reason?¿why it doesn't work when the BV have the EVV? I miss some customizing?¿depend of the definition of the FI accounts?
    Best regards,
    Javier

    Hi Javier,
    To begin with why you need to maintain both EVV and ERL in account determination?
    The purpose of the account key in Billing document control is :-
    Account key for cash allocation
    account key that causes the system to post to a G/L account rather than to a receivables account. You can enter G/L accounts for the key entered in account assignment. (Account determination can be found in Basic Functions).
    Use
    You can use this to allow cash transactions to be carried out directly for the customer rather than receivables being created.
    So this means that once you maintain the Account key for cash allocation,Direct entry will hit the relavant GL account rather than creating a receivable entry.
    In your case you are trying to do both the things at same time.
    In my view either you should maintain EVV or ERL.
    Hope you will try and let me kow if it works allright
    Reward points if useful
    Regards,
    Amrish Purohit

  • Sales order - KOFK account determination - incompletion procedure

    Hi Gurus,
    i am a little bit confused and need help!
    When I am creating a sales order (free of charge) and assign a WBS Element i get the message in the imcompletion routine that the account for type KOFK is missing.
    I know where to maintain this but I am confused, because if i don't assign a WBS Element there is no account determination!!
    Why is there an account determination when i use WBS Elements and no account determination when using no WBS Elements. This is in the sales order only.
    I also want to deactivate the account determination for WBS Elements in Sales Order.
    Can someone help me?
    Thanks in advance

    Hi Yoganand,
    sorry for writting so late - i was in vacation the last 2 weeks
    I had a lot of discussion about this with an FI/CO Consultant - first he also didn't know, but after some more discussion he could remember from a former project that this is standard when there is a planing relevanz for the wbs-element.
    An WBS-Element can not only cause costs (through orders, etc.)  which are planned, it can also cause proceeds (through sales orders) which also have to be planned.
    And thats why the account determination for KOFK is active in the sales order when typing in a WBS element. So the whole accounting procedure is due to the planning of costs/proceeds within the element. For reporting purposes you need both costs and proceeds.
    Georg

Maybe you are looking for