PARKING FACILITY WHILE RECEIPT POSTINGS THRO F-28

Hi,
Anyone can you send me the details in FI with regard to document parking while receipt making thro the T- Code of F-28 / F-29 as we need to check these transactions before posting into FI.
Thanks
G. Jana

Hi,
1. I do not know whether the problem is solved or not.
2. The process is not clear. F-28 is to be used by Finance department. So is it that Sr collects money and they post directly in F-28. if it so then it should not be allowed from internal control point of view.
3. One work around is possible.. This scenario is helpful. when you do not want to clear the customer before the money is really deposite in bank account.Check pay ment advice.
briefly i am describing the same.
1. Create a payment advice- FBE1 first when you gat any payment from customer.
2. after when accounts is satisfied with the data then with referrence to that payment adive number you can post in F-28.
Check from your business process point of view.
3. As you are having a mass distribution system please check with your banker HDFC/corporation bank..etc... whwther they can give you any customised file which you can verify before clearing the customer account through F-28. when customer directly deposit in bank or banker collects check from the warehouses.
Please let me know whether it is helpful ornot .. and also let me know the detail of your particular process..
Regards
Prabhat

Similar Messages

  • E.     They are getting material from customers. This while receipt will be non

    Hi Friends,
                       1. They are getting material from customers. This while receipt will be non valuated. But they want to avail CENVAT on this.
                        2. In some times, Supplies from customer are delayed.So they are adjusting this against their stock.and after recieving, they are taking back their stock.how this can be mapped?.

    Hi JPAnnett
    I can investigate what has happened for you.
    Send me an email using the contact the mods link in my profile you will find it in the section 'About Me'.
    Thanks
    Stuart
    BTCare Community Mod
    If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
    We are sorry that we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)

  • Parking facility in payment document

    Hi expert
    My client want to use parking facility in payment transactions similar to what we are using  in parking  of vendor/customer invoice and credit memo.Whether any standard T codes are available in SAP which is used for parking of  payment transactions also.
    Points assured.
    Thanks in advance.
    sk

    Hi
    In  some company the parking function is used by the entry level employees but the same documents are approved(Say posted as  used in SAP terms)  and the same is used only in case of posting invoice and credit memo.
    So the payment T code like F-53/F-58/f110 whether it can have parking  facility what we are using in case of invoice/credit memo.
    Regards.
    Sk

  • Trigger on RCV_SHIPMENT_HEADERS while Receipt Updation in Put Away Report

    Hi,
    I am working on PUT Away Label Report :
    The process is follows:
    When receipt is saved , a trigger will fire on RCV_SHIPMENT_HEADERS and in trigger a package will be called which in turn will submit the report for the receipt that is newly created.
    The problem here is trigger is working fine when new receipt is created,But when receipt is updated using ADD to receipt option or In case of Internal sales order.The trigger is not firing as trigger is fired for every new insertion.
    I am not able to find any column to know that receipt is updated and to track the quantity that is receipted recently . Since RCV_SHIPMENT_LINES table will have the track of the Total receipted quantity till date.
    I am attaching the script of Trigger i am using for insertion.Please suggest me how to approach in this scenario.
    Trigger that is used for new receipt insertion:
    AFTER INSERT
    ON rcv_shipment_headers
    FOR EACH ROW
    DECLARE
    PRAGMA AUTONOMOUS_TRANSACTION;
    l_request_id1 NUMBER;
    BEGIN
    BEGIN
    If :NEW.RECEIPT_NUM IS NOT NULL
    Then
    l_request_id1 :=
    fnd_request.submit_request ('XXINV',
    'MTUPUTAWAY',
    NULL,
    :NEW.RECEIPT_NUM,
    :new.SHIP_TO_ORG_ID
    commit;
    End If;
    END;
    EXCEPTION
    WHEN OTHERS
    THEN
    NULL;
    END;
    Thanks in advance,
    Best Regards,
    Mahesh

    you should post this question in the ebusiness-forum..

  • AR cash receipts postings analysis

    Our auditors want to confirm 2010 Accounts Receivable balance by analyzing subsequent cash  receipts in 2011.  They want to know from the AR cash receipts received in 2011 what total dollar amount applies to 2010 AR documents.  I ran the report S_ALR_87012198 but this shows only "cleared" items for a specific date range fpr open items at 12-31-2010.  I need a report that shows cleared and partially cleared items as well.  Is there another way to look at cash receipts that "partially" cleared items that related to a prior period?
    Listed below is the entry I am using for the S_ALR_87012198 report that will show fully cleared items:
    ALR87012198 report
    This query only shows fully cleared items
    I need a report that shows 2011 cash receipts that were applied to 2010 receivables for fully cleared and partially cleared items.

    ATTRIBUTEXX columns are customer specific and you control their contents - so feel free to do what you need to them via direct database updates - you know what you put in them, so you control whether or not you corrupt them! Backup the table (primary keys and attribute columns) first!
    Regards,
    Gareth

  • "Method Not allowed" Error while submitting request thro proxy server

    I have an application that uses JSSE to talk to a http/https
    server, everything worked until I tried using https and a
    proxy. Http with or without a proxy worked, https without a
    proxy worked, but I can't get https with a proxy to work. The
    only thing my application does different is to setup the proxy
    stuff with the following function
    if (strTunneling.equalsIgnoreCase("ON")) {
    /** Setting the proxy host-name and proxy port in the system */
    String strProxyHost = ((String) objRouterProp.getProperty("PROXYHOST")).trim();
    String strProxyPort = ((String) objRouterProp.getProperty("PROXYPORT")).trim();
    System.setProperty("https.proxyHost",strProxyHost);
    System.setProperty("https.proxyPort",strProxyPort);
    The Exception i am getting is as follows
    java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.0 405 Method not allowed"
    Any Help is highly appreciated
    Thanks
    Thirumaran

    It means your proxy-server doesn't allow HTTPS tunneling. Have you looked at the "Allow" header in the response? If the proxy is coded correctly, it's supposed to contain ways you can reach the requested resource in ways the proxy will allow.
    Some proxies don't allow HTTPS tunneling because they want to be able to log the traffic contents. Perhaps this is one of them.
    Grant

  • Withholding tax Amount not being displayed in the Invoice while posting a Parked Document

    Hi,
    I have created a parked document for the Vendor who has the Witholding tax code w9 - 15% . I created Parked Document using FBV1 and then tried posting the same using FBV0.Somehow I am not getting the Withholding tax Amount in the FI Document created. However the W/Tax Base Amount and the W/ Base LC are being displayed correctly.
    Say if the Line item Amount is 1,000$ then both the amounts mentioned above in the Additional tab "Withholding tax Data" are being displayed as 1,000 usd but the W/Tax Amount is 0,00 USD.
    2. Also We have the PI and the Interface is written to post the Parked document while the xml file. There is a Method Execute_Asynchronous which has two BDCs one  for FBV2 ( Change Parked Document ) followed by the Post Parked Document FBV0. Hence When I try to post the Parked Document using the SPROXY Interface which has two BDCs Viz FBV2 & FBV0 I still get the Invoice with the Same Amounts and at times with additional 2 zeros added to it in the Additionsal Tax Data Screen.
    I am not sure what is the reason for this. Can anybody help  me sort out this Issue.
    Can there be any Config issues. Please let me know what all config Settings we need to do to sort out this Issue.
    Also let me know why the 2 Zeros are getting added to the Base Amount e.g if the Vendor Line item is 12,000 USD it shows as 12,00000.00 in the Withholding tax Data  Tab in the Invoice.
    Regards,
    Deepak.

    Dear Praveen,
    please check into IMG if You defined the WT type You are using for Your Comapny code:
    IMG --> Assign Withholding Tax Types to Company Codes
    I hope this helps.
    Mauri

  • User needs parking and posting facility but not to post doc parked by him

    Hi All,
    Please Let Me know whether it is possible or not
    Requirement : For Instance, we have two users user1 and user2.
    Both the users should have posting and parking facility. But they should not have the authorization of posting a document which was parked by them.
    i.e. If user 1 is parking a document he should not be able to post that particular document but he should be able to post the document which was parked by user2 and vice versa.
    Regards
    Karthik

    It was possible... take your basis people help... you can authorisation of parking document tcodes to one person and you can give authorisation for chaging, posting, deleting or rejecting parked document to another one...
    for document parking --> f-02, fb50, f-65  : only give authorisation to this tcodes the person for parking
    for parked document changes --> fv50, fbv0 to fbv6   only give authorisation to this tcodes the person for changing parked documents

  • 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

  • Error: while creating Service Entry Sheet - for HELD PO

    Hi experts,
    While PO XXXXXXXXXX is in the status of Hold. System allowed me to create & delete a service entry sheet(SES) on particular date.
    Another day i tried to create SES for the same PO. System is not allowing me to create SES and it gives me error as  'Purchase order XXXXXXXXXX incomplete (parked)'.
    While debugging I found that ekko-memory field set to 'X'. At this point I am getting error.
    My question is why the system is allowed me to create SES for a PO which is in HELD status?.
    Please help me.
    Thanks In advance,
    Vinod

    Thanks for the reply.
    We are aware that system will not allow to create Service entry sheet for held po. But it is allowed me to create on a particular date. Another day i tried to create/delete a SES for the same PO or new PO(held status)  system is not allowing me to delete/create SES.
    Please help me what might be the reason which allowed me on a particulare date.
    Thanks in Advance,
    Vinod....

  • Error While Deploying Webdynpro Application.

    Dear Experts,
    While deploying web dynpro application having webservice based Model, I am getting following errors-
    <b>'SERVICEID' not defined for model class 'Request_ZHRESS_STATION_REQUISITION'</b>
    I have checked model structure where I can see that this attribute "SERVICE ID" is there and properly configured with the Model. It's also generating with the autocompeletion facility while writing the code. This attribute is used to pass the parameter to Model for its execution.
    Please Help! to resolev this problem as I am not able to proceed ahead in my project.
    Thanks in advance!
    Regards,
    Roshan

    Hi Roshan,
    Reimport the bapi once again.
    In the diagram view do the context mapping properly between
    1>     component controller and used model (Bapi Model)
    2>      views and component controller.
    According to context structure.
    Bapi_Employee_Getdata_Input
    |--- Output
    | -
    Personal_Data(under Output node )
    |--- Employee_Id
    Take a method say “GetEmployeeDetailsByNo” inside component controller with parameter “empid” of type string.
    Use this implementation.
    public void GetEmployeeDetailsByNo( java.lang.String empid )
    //@@begin GetEmployeeDetailsByNo()
    IWDMessageManager msg = wdComponentAPI.getMessageManager();
    try {
    Bapi_Employee_Getdata_Input input = new Bapi_Employee_Getdata_Input();
    input.setEmployee_Id(empid);
    wdContext.nodeBapi_Employee_Getdata_Input().bind(input);
    wdContext.currentBapi_Employee_Getdata_InputElement().modelObject().execute();
    wdContext.nodePersonal_Data().invalidate();
    } catch (Exception e) {
    // TODO Auto-generated catch block
    msg.reportSuccess(e.getMessage());
    e.printStackTrace();
    //@@end
    Now go to the view and bind the Model node (Bapi_Employee_Getdata_Input
    ) in the view layout.
    And inside “on action” event of “Search”button uses this code.
    public void onActionGoEmpSearch(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
    //@@begin onActionGoEmpSearch(ServerEvent)
    wdThis.wdGetEmployeeCompController().GetEmployeeDetailsByNo(wdContext.currentBapi_Employee_Getdata_InputElement().getEmployee_Id());
    //@@end
    public void wdDoInit()
    //@@begin wdDoInit()
    Bapi_Employee_Getdata_Input bapiInput = new Bapi_Employee_Getdata_Input();
    wdContext.nodeBapi_Employee_Getdata_Input().bind(bapiInput);
    //@@end
    Use the code according to your BAPI name.
    Regards,
    Mithu

  • Parking Vendor payment / customer payment

    Hi Gurus,
    Is it possible to park vendor / customer payments ? As FV60 & FV70 are available for parking vendor and customer invoices is there a similar functionality available to park payments.
    We have already configured workflow. But the problem is, workflow is triggered only when the document is parked and as there is no parking facility available in payments the same cannot be done. So workflow is functional only in invoice parking and posting.
    Kindly let me know the solution.
    Rgds
    Nikit

    Hello Nikit,
    Due to the payment is only for a inovoice,unfortunately the functionality you required is not existed in the SAP standard.
    Alternatively you could post a credit memo dodument like below:
    revenue  1000 / customer 1000 or  vendor 1000/ expense 1000,
    by using FV75 or FV65, then clear them in clearing transaction code( FB1K, FB1D....).
    Best Regards,
    Gladys xing
    Edited by: Gladys Xing on Jul 12, 2009 10:26 AM

  • WBS Settlement and FI Postings

    Hi All,
    Need your input on this.
    We are doing settlement of costs from WBS to cost center. Let us two cost elements are carrying the costs for the same project. At the time of settlement, an accounting document is being created, but only for one cost element- debiting and crediting the carrier cost element in FI.But for the other cost element there is not posting done in the FI.
    Here is my questions regarding this issue:
    Should the accounting document be created at all?
    If not then what might be causing the creation of FI postings for one cost element while no postings for the other?
    If it should be created what might be causing the creation of FI postings for one cost element while not for the other? What doc type it should be?
    If FI doc should or shouldn't be created, does it apply to both classic GL and New GL. BTY, we are on new GL.
    Has it anything to do with the type of CE?

    Thanks for your comments.
    I have checked the allocation structure and could not find anything missing in the config. We are not using source structure. For both the cost elements, the WBS is credited and cost center debited in the CO document. The FI document only contains postings for one cost element. One more thing, the FI document does not have WBS number populated for the credit line item while debit line item is populating the cost ctr. Should the credit line item be populated with the WBS number in the WBS # field? What doc type the FI document should be?

  • Tax Percentage varience while caluculating FB01 and FBB1

    Dear team,
    While making postings through FB01 and FBB1 the tax is calculating with two different percentages for the same tax code i.e ZF.
    The tax code ZF (VAT)we are using it for both.System is calculating tax code 19% tax is deducting while doing Fb01 and 5% is deducting on FBB1.
    Kindly let me know why system is calculating this variance for the same TAX code.
    Thanks for the cosideation.
    Regards,
    Suma

  • Status Message - Park Document

    Hi All,
         In F-64 Park Document, while Parking, a Document Number appears in the status bar as Document '510000001' was parked. How to retreive this number into transaction Display Document 'FB03'in Document Number Field.
              Or how to get that number into a table field. Since i want to display the line items of the parked document,i need to store the document number in a table field.
       Can anyone help me out to solve it.
    Regards,
    Surya

    i am uable to Understand what are u trying to get ?
    1.If u using BDC to park the document, in the Return messages u will get the Park Document Numer.
    2.If it wis manual Entry no body can help.
    Regards
    Prabhu

Maybe you are looking for