Tax calculation in Purchase requisition

Dear All
My clients release strategy is applicble to PR and not on PO due to some reason
Now in PR tax doesnt gets calculated that is the pricing prcedure doesnt gets caleed in PR.
Is there any method that the tax gets calculated in PR so the decision for releasing the PR is on the taxable value and not on the non taxable value
please note that we are using taxinj
regards
shailesh

Dear All
Please give me ur input whether tax procedure can be calledin Purchase requistion and if yes how it can be called
I have heard that it can be called in Purchase req.. please let me know the config required for the same
regds
shailesh

Similar Messages

  • Tax calculation in Purchase order

    Hi,
    i had created new key combination vandor/taxcode/plant/material for maintaining tax. Tax rate maintain in fv11 for this combination. But in Purchase order this value of this rate is not populating in tax procedure.
    Thank's & Regard's
    Parag Lute

    Hello
    Go to OBYZ and select Access seq and select your access sequence and go to access tab on the left.
    In that check whether your key combination is there.also select your combination and click on fields tab also.
    Then come back to the access page and check whether the eclude tick is checked for the combination given by you. if so remove the tick and save.
    Hope this helps
    Regards
    Gregory Mathews

  • Tax calculation at the time of creating service entry sheet.

    Dear Experts,
    I have got a Company Code : P320 having the Plants : P324, P325, P326.
    I am making a Services Purchase Order by using the Item Category as u201CDu201D and Accounts Assignment as u201CKu201D for Cost Center and Order and u201CPu201D for WBS element.
    I am entering a Tax Code : 29-Service Tax 10.30% and Jurisdiction Code : IN00 for all the Plants : P324, P325, P326.
    The tax calculations in purchase order are displayed properly.
    But on preparing the service entry sheet for Plants P324 and P325 for Accounts Assignment u201CKu201D and u201CPu201D, the service tax amount is getting calculated and posted correctly along with the base amount.
    But on preparing the service entry sheet for Plant P326 for Accounts Assignment u201CKu201D and u201CPu201D the service tax amount is not getting calculated and only accounting entries for base amount is posted.
    For example : Suppose the value of the SES is Rs. 10000/-. Service tax [((Rs. 10000 * 10.30)/100) = Rs.1030).
    The accounting entries for Plants P324 and P325 are for Rs. 10000/- + Rs. 1030/- = Rs. 11030.
    The accounting entries for Plant P326 are for Rs. 10000/- only.
    Please suggest what could be the problem and how can it be resolved.
    Thanks in advance
    AJ

    Hi.
    Th service cost is 1000 an tax is10.3% (130 rs). Hence the amount shoul be 1130. In your case it is showing 1000only. Am i right? Thouigh you have seleceted apt tax code and tax is not getting updated means please check the tax code linkage in tax determination procedure.Please cross check the tax determination procedure and the tax code assigned in SES is correct or not. I hope this will help you. Thanking you.

  • Tax Calculation for Service Process at service entry level

    Hi all ,
    We have Service process where the tax calculation is Purchase Item level and the Tax calcaulation is happening from there .
    and also during MIRO .
    system is not able to determine the tax calculation at service entry level , how can we achieve this ?
    can some help me on this .
    thanks ,
    ksr

    Hi,
    please check additionally the following OSS notes:
    495316     Taxes with services
    See consulting Note 498878 for information about the functioning of    
    taxes for service documents.                                           
    For service orders, you can set in Customizing (Transaction ML100 or the          
    following path: -> Materials Management -> External Services Management           
    -> Taxes at Individual Service Level) whether the taxes are calculated            
    at individual service level or at item level.    
    If you set the 'Taxes at individual service level' indicator for a     
    country, you can maintain tax data (tax indicator MWSKZ and tax        
    jurisdiction code TXJCD) in a purchase order at service level AND at   
    item level in Customizing.                                             
    The tax calculation only occurs at service level.    
    Regards,
    Edit

  • Tax Calculation in PO

    hi all,
         Can you send the code for Tax Calculation for Purchase Order or  Can you tell the procedure for Tax Calculation in PO.
    Thanx & Regards
    Rami Reddy

    Hi,
    You will get all the condition types in PO in KONV table , and all the tax details like VAT , BED, CST etc you will get from A363 table , you can access the values from A363 table by passing plant , vendor , date.
    Regards,
    Bharat

  • Tax Calculation in SAP Purchase Order

    Hi Experts,
    My Requirment is so get the US and Canadian tax automatically from external tax system ( other than Vertax Sabrix and taxware) while creating Purchase Order. We are using SAP XI to get the TAX AMOUNT from external system.
    The probelm is , the external system provides me directly tax amount rather than tax code. As per my knowledge , the tax calculation in Sap is done through tax code only.
    Please help me on this. Do I need to do something like , create a new condition type and put the tax amount there ?

    Check Financial A/C Global Settings>Tax on sale and purchase>Basic Settings>Check calculation Procedure>define procedure
    Which are the Tax conditions available ,In next step check assignment of country to tax procedure check for US TAXUSX is assigned
    Create TAX CODE in FTXP , now for the tax code maintain the condition value( you can use standard conditions based on your tax
    type or create Z Condition type)  in FV11 with tax code amount and validity
    Now when yoo use this tax code your condition value will be defaulted , probabaly you need to create program to use FV11 and update
    New condition value fetched by external system to update the tax code and amount everytime or create Z table to store and update
    condition values fetched by external system ..please explore further
    Thanks
    Diwakar

  • Taxes in Purchase Requisition

    Hi all,
    We have a requirement to get item wise taxes in PR.  for this the approach that was decided is to create a PO with all the items of PR, and the PO will any how calculate the taxes for all items; then read the PO and get the taxes back to PR for all items, and then mark the PO for deletion.
    To achieve this we are trying to find some enhanccement/exit/BADI under PR save, where we have all the PR data available (all items, to create a single PO for the entire PR).  We found some but we were unable to modify the PR data there.
    Please suggest any enhancement options for this problem. 
    Thanks,
    SreeRaj.

    Hi,
    The answer is a simple NO.
    The Purchase requisition does not have a full range of pricing conditions, it merely has a value that is used in the release sttrategy.
    The "price" on the PR is not meant to be a purchase price anyway and so any taxes would be wrong. The price is only fixed when the PO is created.
    Steve B

  • Extended classic purchase order tax calculation

    We are running extended classic on SRM 4.0.  We are connecting to our R/3 backend version 4.7.  The backend is utilizing Vertex for it's tax calculation.  We have confirgured SRM to use the backend for tax calculation. 
    We have a 5% state sales tax and a 1% local option sales tax at this location.  If we procure an item from a vendor residing in the same state then the local option sales tax applies (i.e. 6%).  If we procure an item from a vendor outside of the state then the local option tax does not apply (i.e. 5%).  I've tested this by creating PO's on the backend for both scenrios and the tax is calculated correctly.
    The issue we have is that the shopping cart is calculating the tax amount correctly, the replicated purchase order in R/3 also has the correct tax amount, however the purchase order residing in SRM does not have the correct amount, it is always calculating 6%, which is incorrect.
    My question is does anyone know the function module being called to calculate tax when the SRM PO is being created?  For the shopping cart I have verified that BBP_CALCULATE_TAX_ITEM46B is being used, is it not the same for the SRM PO?
    Best regards,
    Shawn O'Connor

    Hi Shawn,
    I do not know your SRM release... but did you already see OSS note 656398 and 888896 ?
    Hope this helps,
    Regards,
    Yann

  • Exit or BADI when Tax Calculation in MIRO from Purchase order

    Hi Gurus,
    I Need a Exit or BADI when Tax Calculation in MIRO from Purchase order.
    The problem is the tax is automatically calculated from tax code in PO but I want it to be calculated
    from PO condition. Is there any exit available by which I can modify the value of tax when ticking the check box of tax calculation in MIRO.

    BADI has method COPY_DRSEG_SELKZ but since there only importing paramters and no exporting or changing parametrs you cannot change the values of rseg here.
    Try using proper Implicit enahncement by debugging .
    For implicit enhancement check
    Re: How do we search enhancement point/section
    Edited by: Gautam Totekar on May 29, 2009 5:56 PM

  • Tax on sales/purchases - Calculation Procedure

    Is there a standard configuration of calculation proceedure for India? If no, how can i define the same for VAT & Service Tax calculations?

    Hi
    Check the link
    http://help.sap.com/bp_bl604/BBLibrary/HTML/102_EN_IN.htm
    Regards
    Sanil Bhandari

  • User Exit/BADI for Purchase Order and Purchase Requisitions

    HI,
    I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
    Is there a User Exit or Badi that i can use where this information is availaible.
    also i have to check that release strategy is assigned to every purchase order where the version has been completed.
    Is there a User Exit or Badi where Information of EREV table is availaible.
    Regards,
    Tarun Bahal

    For Purchachase requisition , the BADIs and USER EXITS are
    ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
    ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
    ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
    try with the above BADI's
    MEREQ001 Customers' Own Data in Purchase Requisition
    for Purchase order , the BADIs and USER EXITS are
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_BAPI_PO_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PR_CREATE_02
    ME_BSART_DET Change document type for automatically generated POs
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_CHECK_OA Check BAdI for Contracts
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_COMMITMENT_RETURN Commitment for return item
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PURCHDOC_POSTED Purchasing Document Posted
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_REQ_POSTED Purchase Requisition Posted
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    SMOD_MRFLB001 Control Items for Contract Release Order
    AMPL0001  User subscreen for additional data on AMPL             
    LMEDR001  Enhancements to print program                          
    LMELA002  Adopt batch no. from shipping notification when posting
    LMELA010  Inbound shipping notification: Transfer item data from 
    LMEQR001  User exit for source determination                     
    LMEXF001  Conditions in Purchasing Documents Without Invoice Rece
    LWSUS001  Customer-Specific Source Determination in Retail       
    M06B0001  Role determination for purchase requisition release    
    M06B0002  Changes to comm. structure for purchase requisition rel
    M06B0003  Number range and document number                       
    M06B0004  Number range and document number                       
    M06B0005  Changes to comm. structure for overall release of requi
    M06E0004  Changes to communication structure for release purch. d
    M06E0005  Role determination for release of purchasing documents 
    ME590001  Grouping of requsitions for PO split in ME59           
    MEETA001  Define schedule line type (backlog, immed. req., previe
    MEFLD004  Determine earliest delivery date f. check w. GR (only P
    MELAB001  Gen. forecast delivery schedules: Transfer schedule imp
    MEQUERY1  Enhancement to Document Overview ME21N/ME51N           
    MEVME001  WE default quantity calc. and over/ underdelivery toler
    MM06E001  User exits for EDI inbound and outbound purchasing docu
    MM06E003  Number range and document number                       
    MM06E004  Control import data screens in purchase order          
    MM06E005  Customer fields in purchasing document                 
    MM06E007  Change document for requisitions upon conversion into P
    MM06E008  Monitoring of contr. target value in case of release or
    MM06E009  Relevant texts for "Texts exist" indicator             
    MM06E010  Field selection for vendor address                     
    MMAL0001  ALE source list distribution: Outbound processing      
    MMAL0002  ALE source list distribution: Inbound processing       
    MMAL0003  ALE purcasing info record distribution: Outbound proces
    MMAL0004  ALE purchasing info record distribution: Inbound proces
    MMDA0001  Default delivery addresses                             
    MMFAB001  User exit for generation of release order              
    MRFLB001
    Regards,
    Anirban

  • User exit/BADI  for Purchase requisition through release of Process order

    Hi ,
    i need to add some text to the Pur Req.
    The Pur Req will be created THROUGH the release of PROCESS order. Please let me know any exits are available for the same.
    regards

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
    MM06E001                                User exits for EDI inbound and outbound purchasing documents
    MM06E003                                Number range and document number
    MM06E004                                Control import data screens in purchase order
    MM06E005                                Customer fields in purchasing document
    MM06E007                                Change document for requisitions upon conversion into PO
    MM06E008                                Monitoring of contr. target value in case of release orders
    MM06E009                                Relevant texts for "Texts exist" indicator
    MM06E010                                Field selection for vendor address
    MM06E011                                Activate PReq Block
    MMAL0001                                ALE source list distribution: Outbound processing
    MMAL0002                                ALE source list distribution: Inbound processing
    MMAL0003                                ALE purcasing info record distribution: Outbound processing
    MMAL0004                                ALE purchasing info record distribution: Inbound processing
    MMDA0001                                Default delivery addresses
    MMFAB001                                User exit for generation of release order
    MRFLB001                                Control Items for Contract Release Order
    AMPL0001                                User subscreen for additional data on AMPL
    LMEDR001                                Enhancements to print program
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001                                Customer-Specific Source Determination in Retail
    M06B0001                                Role determination for purchase requisition release
    M06B0002                                Changes to comm. structure for purchase requisition release
    M06B0003                                Number range and document number
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    SMOD_MRFLB001                           Control Items for Contract Release Order
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    Reward points if useful
    Regards
    Anji

  • Excise not captured in the MIGO & Tax calculation is not correct in the PO.

    Excise Settings completed.                    02.11.2007
    a)     Configuration done as per J05 Building block.( Tax Procedure TAXINN)
    b)     Maintained J1ID, all steps.
    c)     Maintained tax code in FTXP.
    d)     FV11  Maintained for Material, vendor, Plant in combination with Tax code input tax maintained in FTXP.
    e)     Checked CIN Health, all tick are green.
    f)     Given all G/L accounts for Excise Transaction Type (ETT)
    g)     Maintained all number Ranges.
    Issue  1)
    Tax calculation is not correct in the PO, tax tab
    a)     JMIP is appearing 12% in condition amount, (as per condition record) but condition value is Zero, (Not calculated by the FI Pricing procedure). Screen shot for Pricing procedure, PO taxes and condition record given below.
    b)     JIPC Sales tax 4% in condition amount (as per condition record) , calculated by the FI Pricing procedure is 8%, condition value is Rs 8 instead of Rs 4
    Fi pricing procedure.
    PO Taxes  wrong Tax calculated
    FV11 Condition record
    Issue  2)
    While creating Goods receipt aginst PO (Tax code V2 in PO). Movement type 101, Excise tab appears at Header and Item level and we need to put the Vendors Excise Invoice and date, nothing is copied from the PO for Excise duty  & sales tax.
    Now we put the values for ED and Sales tax manually in the MIGO and saved the document. While display material document, excise tab is not there i.e. no excise related activiy is captured here in goods receipt.
    If you need more detail, please revert on cell 093295 53235.
    Please suggest.
    Manish Gupta
    93295 53235
    [email protected]

    Hai,
    1.Check the condition types JMIP & JMIC in IMG - Financial accting New - FI AC Global settings - Taxes on sales and purchases - Check calculation procedure - Define condition type.
    2.The condition types you have used are defined for non deductible taxes i.e., it gets inventorised, added to the material account.And also the accural key assigned to this condition types are NVV - defined for non ded input taxes.
    3.Instead the condition types defined by SAP Standard system for BED & ST are JMOP & JIPS and the accurals assigned to this are VS1 & VS5.
    If you want clear details mail the screen shots to my id [email protected]

  • Warning: An error occurred during tax calculation. Please correct the problem or contact your system administrator.

    Hi All
    We are creating POs from interface program "Import Standard Purchase Order Program". Only for few of the POs, we are encountering the error 'Warning: An error occurred during tax calculation
    . Please correct the problem or contact your system administrator.'
    This error is happening for few PO's, other POs with same vendor, ship to and bill to location created successfully by the program
    Any inputs on how to resolve this error is greatly appreciated.
    Regards,
    Brajesh

    Hi Hussein,
    Thank for the prompt response.
    We have already applied the patch related to doc 1272684.1.
    Below are the environment detail.
    Database: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    Application : 12.1.3
    Diagnostic tool output :-
    INTERFACE_
    TRANSACTION_ID
    INTERFACE_TYPE
    COLUMN_NAME
    PROCESSING_DATE
    TABLE_NAME
    ERROR_MESSAGE_NAME
    ERROR_MESSAGE
    100148
    PO_DOCS_OPEN_INTERFACE
    09-Aug-2013
    PO_HEADERS_INTERFACE
    PO_PDOI_TAX_CALCULATION_ERR
    Warning: An error occurred during tax calculation. Please correct the problem or contact your system administrator.
    Log file :-
    +---------------------------------------------------------------------------+
    Purchasing: Version : 12.0.0
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    POXPOPDOI module: Import Standard Purchase Orders
    +---------------------------------------------------------------------------+
    Current system time is 09-AUG-2013 21:09:04
    +---------------------------------------------------------------------------+
    +-----------------------------
    | Starting concurrent program execution...
    +-----------------------------
    Arguments
    STANDARD
    N
    INCOMPLETE
    12805
    +---------------------------------------------------------------------------+
    Start of log messages from FND_FILE
    +---------------------------------------------------------------------------+
    To get the log messages for PDOI, please use the following id to query against FND_LOG_MESSAGES table:
    AUDSID = 12076063
    +---------------------------------------------------------------------------+
    End of log messages from FND_FILE
    +---------------------------------------------------------------------------+
    +---------------------------------------------------------------------------+
    Executing request completion options...
    Output file size:
    69
    +------------- 1) PRINT   -------------+
    Printing output file.
                   Request ID : 55116524
             Number of copies : 0
                      Printer : noprint
    +--------------------------------------+
    Finished executing request completion options.
    +---------------------------------------------------------------------------+
    Concurrent request completed successfully
    Current system time is 09-AUG-2013 22:27:42
    +---------------------------------------------------------------------------+
    Brajesh

  • Questions on Rules-Based ATP and Purchase Requisitions for STOs

    Hello experts,
    We are working on rules-based ATP configuration and have several questions about the functionality.  Iu2019m hoping that some of you are using this functionality and can help give us direction.
    In our environment we have multiple distribution centers and multiple manufacturing plants.  We want to confirm sales orders against stock and production orders in any of those plants, depending on the locations that have stock or planned production.  For example, we will place a sales order against plant A.  If there is not enough stock in plant A then rules-based ATP will use location determination to check in plant B, then C.  The scope of check on the ATP check will include stock and released production orders.  We will configure plant A as the u201Cconsolidation locationu201D so if stock is found in plants B or C then stock transport orders will automatically be created to move the stock to plant A before shipping to the customer.
    We have configured rules-based ATP and this functionality is working well in our Development system.  The ATP check is executed and uses the rules-based ATP to find eligible stock in other plants.  The system is also creating purchase requisitions to move the stock to the consolidation plant. 
    Our first concern is that there doesnu2019t appear to be any firm linkage between the sales order and the resulting purchase requisition.  For example, if we create sales order 123 for plant A and the rules-based ATP finds stock in plant B it automatically creates a purchase requisition 987 to move the stock from plant B to plant A.  However, there doesnu2019t appear to be a linkage between sales order 123 and purchase requisition 987.  For instance, if we delete sales order 123 the purchase requisition doesnu2019t get deleted. 
    Our second concern is that the quantity on the purchase requisition can still be confirmed against later sales orders.  For example, say the above scenario resulted in a purchase requisition 987 that consumed all the stock available in plant B.  We then create a second sales order 456 for the same product.  Plant A is out of stock so the rules-based ATP looks in plant B.  We would expect that plant B would also not have any stock because itu2019s all been consumed by the purchase requisition.  Instead, the system creates a second purchase requisition to move quantity from plant B to plant A.  Itu2019s as if the system doesnu2019t realize that the purchase requisition 987 is already planning to move stock out of plant B.
    Does anyone have any thoughts or suggestions on these two scenarios?  Is there a way to configure the system so there is a hard linkage between the sales order and the purchase requisition so that if the sales order is deleted then the purchase requisition is also deleted?  Should ATP realize that purchase orders are consuming inventory and not allow later sales orders to confirm against that same inventory?  Any advice or experience would be greatly appreciated.
    Thanks,
    David Eady
    Application Delivery Team Lead
    Propex, Inc.

    Hi,
    The scheduling is done in SCM, and from there, whenever the RBA is triggered, the calculation is done always with the old route in SCM. Until you get back to R/3 this is when your route is determined. But the ATP check is always with the original route. So the idea would be that you change the values of the route while still in APO, this is possible via the user exit. Should be done in scheduling in APO.  
    Hope this information is helpful.
    Regards,
    Tibor

Maybe you are looking for