Posting taxes for Purchase order receptions that we dont have invoice yet

Hello experts,
I searched and found rfwere00 program that is used for posting of taxes on open receptions for what we have not yet received an invoice for. The problem is that I always get error message that the taxjurcode is missing. I opened the code and found that the call function is missing the parameter taxjurcode. I modified the code and it calculates the taxes but puts both taxes in the same g/l account. I'm from Québec in canada and we have 2 taxes. In the code they are separated but the value that is used for posting is the value that combines the two taxe amounts in the first g/l account that corresponds to the first taxe and the posting is done only in 1 account. I search oss notes and found no solution. I'm in ecc6 with newgl.
Regards.

This is being adressed by SAP development team for canadian provinces taxation.

Similar Messages

  • I am going through a divorce and she has the computer. I'm trying to tranfer my music to a new computer but for about 100 songs its asking for her authorization password that I dont have. How can I get these songs transfered or can I?

    I am going through a divorce and she has the computer. I'm trying to tranfer my music to a new computer but for about 100 songs its asking for her authorization password that I dont have. How can I get these songs transfered or can I?

    It sounds like two Apple accounts were used in the purchase of songs, yours and hers.  Assuming she won't give you her password, you're kinda stuck.  For $129 or so you can repurchase them all.
    By the way, if she has the computer and it has your account info in it, you ought to change your password.

  • Hey there i downloaded apps using another apple id than the one am using right now and i need to update the apps they keep asking me for the old one that i dont have any more what to do please

    Hey there i downloaded apps using another apple id than the one am using right now and i need to update the apps they keep asking me for the old one that i dont have any more what to do please

    Apps are permanently tied to the ID used to purchase them.
    Go to https://appleid.apple.com/cgi-bin/WebObjects/MyAppleId.woa/ and re-set th password for the old one.
    Then, log into the app store with it and update the apps purchased with that ID.

  • Missing Parts report for Purchase Orders

    Hey Gurus,
    We are running the availability check for Purchase orders and the user group is wondering if there is a standard Missing Parts report in SAP similiar to transaction CO24 for Purchase Orders so that they can view all of the Purchase orders with missing parts.
    As a side note,  we are using subcontracting purchase orders.

    didn't get a response.

  • Getting errors when iam using  BAPI_PO_CREATE1 for Purchase Order creation

    Hi sap Gurus,
      I am getting Errors when iam using  BAPI_PO_CREATE1 for Purchase Order creation that Material (144) does not exist but it is alreardy maintained in MM01.
    I dont get how it is coming.and what are the mandatory fields in bapi BAPI_PO_CREATE1 in item level .that is too material only.
    pls let me know .
    thanks in advance.

    Hi,
    Check the sample code..
    report  zpo_test             .
    *DATA DECLARATION
    constants : c_x value 'X'.
    *Structures to hold PO header data
    data : header like bapimepoheader ,
    headerx like bapimepoheaderx .
    *Structures to hold PO account data
    data : account like bapimepoaccount occurs 0 with header line ,
    accountx like bapimepoaccountx occurs 0 with header line .
    *Internal Tables to hold PO ITEM DATA
    data : item like bapimepoitem occurs 0 with header line,
    itemx like bapimepoitemx occurs 0 with header line,
    *Internal table to hold messages from BAPI call
    return like bapiret2 occurs 0 with header line,
    *Internal table to hold messages from BAPI call
    pocontractlimits like bapiesucc occurs 0 with header line.
    data : w_header(40) value 'PO Header',
    purchaseorder like bapimepoheader-po_number,
    delivery_date like bapimeposchedule-delivery_date.
    data : ws_langu like sy-langu.
    *text-001 = 'PO Header' - define as text element
    selection-screen begin of block b1 with frame title text-001.
    parameters : company like header-comp_code default '122' ,
    doctyp like header-doc_type default 'NB' ,
    cdate like header-creat_date default sy-datum ,
    vendor like header-vendor default '2000000012' ,
    pur_org like header-purch_org default 'PU01' ,
    pur_grp like header-pur_group default '005' .
    *sociedad like HEADER-COMP_CODE default '122' ,
    *vendedor like HEADER-SALES_PERS default 'sale person'.
    selection-screen end of block b1.
    selection-screen begin of block b2 with frame title text-002.
    parameters : item_num like item-po_item default '00010',
    material like item-material default '12000000' ,
    tipo_imp like item-acctasscat default 'K' ,
    *pos_doc like ITEM-ITEM_CAT default 'F' ,
    shorttxt like item-short_text default 'PRUEBA BAPI' ,
    grup_art like item-matl_group default '817230000' ,
    plant like item-plant default '3001' ,
    mpe like item-trackingno default '9999' ,
    *contrato like ITEM-AGREEMENT default '4904000003' ,
    *quantity like ITEM-QUANTITY default 1 .
    po_unit like item-po_unit default 'EA'.
    selection-screen end of block b2.
    Par?mnetros de imputaci?n
    selection-screen begin of block b3 with frame title text-004.
    parameters : centro like account-costcenter default '1220813150',
    cuenta like account-gl_account default '6631400' ,
    num_pos like account-po_item default '10' ,
    serial like account-serial_no default '01' ,
    ind_imp like account-tax_code default 'I2' .
    selection-screen end of block b3.
    start-of-selection.
    *DATA POPULATION
      ws_langu = sy-langu. "Language variable
    *POPULATE HEADER DATA FOR PO
    *HEADER-COMP_CODE = sociedad .
      header-doc_type = doctyp .
      header-vendor = vendor .
      header-creat_date = cdate .
      header-created_by = 'TD17191' .
      header-purch_org = pur_org .
      header-pur_group = pur_grp .
      header-comp_code = company .
      header-langu = ws_langu .
    *HEADER-SALES_PERS = vendedor .
    *HEADER-CURRENCY = 'DOP' .
    *HEADER-ITEM_INTVL = 10 .
    *HEADER-PMNTTRMS = 'N30' .
    *HEADER-EXCH_RATE = 1 .
    *POPULATE HEADER FLAG.
      headerx-comp_code = c_x.
      headerx-doc_type = c_x.
      headerx-vendor = c_x.
      headerx-creat_date = c_x.
      headerx-created_by = c_x.
      headerx-purch_org = c_x.
      headerx-pur_group = c_x.
      headerx-langu = c_x.
    *HEADERX-sales_pers = c_x.
    *HEADERX-CURRENCY = c_x.
    *HEADER-ITEM_INTVL = c_x.
    *HEADER-PMNTTRMS = c_x.
    *HEADER-EXCH_RATE = c_x.
    *HEADER-EXCH_RATE = c_x.
    *POPULATE ITEM DATA.
      item-po_item = item_num.
      item-quantity = '1'.
    *ITEM-MATERIAL = material .
      item-short_text = 'prueba bapi_po_create1'.
    *ITEM-TAX_CODE = ''.
      item-acctasscat = 'K' .
    *ITEM-ITEM_CAT = 'D' .
      item-matl_group = '817230000' .
      item-plant = '3001' .
      item-trackingno = '99999'.
      item-preq_name = 'test'.
    *ITEM-AGREEMENT = '' .
    *ITEM-AGMT_ITEM = ''.
      item-quantity = '1' .
      item-po_unit = 'EA'.
    *ITEM-ORDERPR_UN = 'EA'.
      item-conv_num1 = '1'.
      item-conv_den1 = '1'.
      item-net_price = '1000000' .
      item-price_unit = '1'.
      item-gr_pr_time = '0'.
      item-prnt_price = 'X'.
      item-unlimited_dlv = 'X'.
      item-gr_ind = 'X' .
      item-ir_ind = 'X' .
      item-gr_basediv = 'X'.
    *ITEM-PCKG_NO = '' .
      append item. clear item.
    *POPULATE ITEM FLAG TABLE
      itemx-po_item = item_num.
      itemx-po_itemx = c_x.
    *ITEMX-MATERIAL = C_X.
      itemx-short_text = c_x.
      itemx-quantity = c_x.
    *ITEMX-TAX_CODE = C_X.
      itemx-acctasscat = c_x.
    *ITEMX-ITEM_CAT = c_x.
      itemx-matl_group = c_x.
      itemx-plant = c_x.
      itemx-trackingno = c_x.
      itemx-preq_name = c_x.
    *ITEMX-AGREEMENT = C_X.
    *ITEMX-AGMT_ITEM = c_x.
      itemx-stge_loc = c_x.
      itemx-quantity = c_x.
      itemx-po_unit = c_x.
    *ITEMX-ORDERPR_UN = C_X.
      itemx-conv_num1 = c_x.
      itemx-conv_den1 = c_x.
      itemx-net_price = c_x.
      itemx-price_unit = c_x.
      itemx-gr_pr_time = c_x.
      itemx-prnt_price = c_x.
      itemx-unlimited_dlv = c_x.
      itemx-gr_ind = c_x .
      itemx-ir_ind = c_x .
      itemx-gr_basediv = c_x .
      append itemx. clear itemx.
    *POPULATE ACCOUNT DATA.
      account-po_item = item_num.
      account-serial_no = serial .
      account-creat_date = sy-datum .
      account-costcenter = centro .
      account-gl_account = cuenta .
      account-gr_rcpt = 'tester'.
      append account. clear account.
    *POPULATE ACCOUNT FLAG TABLE.
      accountx-po_item = item_num .
      accountx-po_itemx = c_x .
      accountx-serial_no = serial .
      accountx-serial_nox = c_x .
      accountx-creat_date = c_x .
      accountx-costcenter = c_x .
      accountx-gl_account = c_x .
      account-gr_rcpt = c_x.
      append accountx. clear accountx.
    *BAPI CALL
      call function 'DIALOG_SET_NO_DIALOG'.
      call function 'BAPI_PO_CREATE1'
        exporting
          poheader         = header
          poheaderx        = headerx
        importing
          exppurchaseorder = purchaseorder
        tables
          return           = return
          poitem           = item
          poitemx          = itemx
          poaccount        = account
          poaccountx       = accountx.
    *Confirm the document creation by calling database COMMIT
      call function 'BAPI_TRANSACTION_COMMIT'
      exporting
      wait = 'X'
    IMPORTING
    RETURN =
    end-of-selection.
    *Output the messages returned from BAPI call
      loop at return.
        write / return-message.
      endloop.
    Regards
    Sudheer

  • PS - Set Commitment only for Purchase order

    Hi experts,
    I would like to know if its possible set in the Customizing, the  Commitment just for Purchase Order.
    Because, currently we have fixed Purchase Requisition and Purchase Order.
    Thanks in advance.
    Nacho

    Hi,
    SAP Note:955107 addresses this problem. You may refer the note, but for easy reference, relevant portios of the note are quoted below:
    Quote begins:
    Symptom
    The purchase requisition commitment should not be taken into account in the availability control.
    How can this be achieved?
    Reason and Prerequisites
    This is a customer request.
    It should be possible to enter purchase requisitions with any amount and only the resulting purchase orders should be checked by an availability control.
    Solution
    For Releases 4.6C, 4.70, 5.00 and 6.00 first implement the corrections from Note 955106 if you have not already done this.
    Afterwards proceed as follows.
    1. Create a utility program ZBPFCI21 of the 'Subroutine Pool' type. For the source code of the program refer to the attached correction instruction 488705.
                  Caution: Do not use a different name than ZBPFCI21.
    2. Adjust the source code within the utility program ZBPFCI21 as follows:
                  When the residual order plan should not be included in the assigned value of the availability control, activate the line
                           CLEAR cd_flag_pr_commitment_avac.
                  (That is, delete the sign '*' in front of the line.)
    3. Save and activate the ZBPFCI21 utility program.
    4. Reconstruct the assigned values of the availability control (Transactions KO31 for orders or CJBN for projects).
    Quote ends.
    Kindly acknowledge, if it meets your requirement.
    Muraleedharan.R

  • Blocking material for Purchase order only

    hi all,
    i have a material and i want to block it for purchase order only bcos we dont want to allow to purchase it but it can perform all other operations. can anyone please help me?
    regards saurabh.

    Dear,
    Go to MM02, in Basic1 tab
    X-plant material status -   01     Blocked for procment/whse
    but it is relevant not only for that plant but also for client level becoz while go to MM02, please not select any plant and go to Basic Data 1 tab.
    this may help u
    Reagrds,
    pardeep Malik
    Edited by: Pardeep  Malik on Mar 14, 2009 5:59 AM
    Edited by: Pardeep  Malik on Mar 14, 2009 6:06 AM

  • Workflow for Purchase order

    Hi,
    Can anyone let me know the steps to activate workflow for purchase order so that workflow will be triggered after creation of PO and for any modification done after release.
    What are the customization and tcodes required for PO workflow and is there any technical involvement requires.
    Thanks in advance!
    Karun

    Hi
    I took it from sdn.
    WORKFLOW FOR PO RELEASE PROCEDURE
    Steps involved are :
    1) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
    2) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
    3) Go to OOCU > here under MM, go to MM-PUR,
    4) Click on "activate event linking"
    5) Go for "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button. Activate "Event linkage activated" and also activate "Enable usage of event queue"
    and Save.
    6) Click on "Assign agents" and proceed all above steps.
    BUS2012 is the relevant business object and Releasestep created is the event for the same.
    7) Check SWETYPV transaction for the WF you have activated for BUS2012 and confirm.
    Test the same by creating a PO and check the SBWP for SAP Mail of respective Users

  • Output Message Determination for Purchase Order

    Hi all !
    Can anybody please explain in brief, the procedure for Ouyput message determination for Purchase order. (including printer settings)
    I have tried it throgh the Standard Configuration guide. but i am not able to do.
    Please explain step by step including form attachment.
    Thanks in Advance !!!!

    Hi,
    Customization steps for Output of Purchase Order
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    4. Message Determination Schemas
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
    Note1
    Now Check in SPAD (Printer settings) settings & try to check the printer configuration. Check Device attributes, Access methods etc. are maintained in Spool Administration (SPAD) for the selected printer (your local Printer, may be ur using HP01or any but in SAP std is LP01) but consult with your basis consultant regarding above.
    Check the following also:
    Spool generated using SP01 or SP02.
    Output device.
    Local printer settings.
    Paper Tray, Print Mode, Printer
    Note2:
    Check MN04 and NACE t.codes
    Regards,
    Biju K

  • Offline approval for Purchase order response

    Hi All,
    Currently we are in SRM 7.02. we want to know whether offline approval is applicable for Purchase order response (PCO).
    I have searched all available blogs but in Vain. Hope someone can enlighten me in this topic
    Regards,
    Nishanth

    Hi Nishanth,
    We have implemented custom solution for the same in line of SC offline approval process.
    And its working fine in Production environment.
    Check this blog for SC:
    http://scn.sap.com/docs/DOC-56096
    http://wiki.scn.sap.com/wiki/display/SRM/Debugging+hints+for+sending+email+in+offline+approval
    Thanks
    Ankit Jain

  • 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

  • Goods-Receipt Block for Purchase Order depending on Goods-Receipt Date

    Hi,
    I want to set up the system so it can block the Goods-Receipt for Purchase Order respectively Scheduling Agreement if the Goods Receipt is about to take place 30 days or more before the Desired Delivery Date.
    For Example: If I have a Purchase Order with the desired delivery date 30.09.2008. I want to set up the system so, that it bans (forbids) the Goods Receipt before the 01.09.2008.
    If possible I would want to do that without additional programming. Is it possible to set up the system using only customising settings?
    Thanks for your help
    Bogdan

    Hello Marius-Bodgan,
    as this question is marked answered I assume you have received an solution for your requirement. Could you please share the solution with me by posting it here? I have the same requirement and did not find any possibility to do this in customizing.
    Thanks in advance,
    Emanuel
    Found the solution in thread Re: Goods Receipt
    Edited by: Emanuel Penalver on Jul 15, 2008 11:48 AM

  • No goods receipt possible for purchase order 4000010123 00001

    Hi Experts,
    I created PO with 100 Qty then create GR with 20 Qty with mvt type '101' .
    then I am doing Return PO with 20 then I am creating GR with Reference to return PO with 161 movement type through BAPI 'BAPI_GOODSMVT_CREATE'.but it  giving error as 'No goods receipt possible for purchase order 4000010123 00001'.
    but manual it is working fine and creating GR.Please let me the reason.
    I am unable post GR for first time with fresh return po.but second time after manual posting.i am able to do it.

    Hi,
    have you compare the data you send to bapi with data recorded in GR (mkpf/mseg) tables by the system after manual document posting?
    I would check it first - here usualy is the diference between manual and bapi document creating that causes problems.
    hope it helps
    regards,
    wojciech

  • No goods receipt possible for purchase order 4701088161 00050

    Dear SAP Gurus,
    The Error is coming
    No goods receipt possible for purchase order 4701088161 00050 when we create goods receipt note only 39 qty.
    done..they want all 99 qty.come in single goods receipt....what exactly problem facing at the time of posting???

    Hi,
    Pl. check whether the Goods Receipt has not been done already for this PO.
    Also, check the message details by clicking on the question mark for the message, so that you will get exact reason, due to which the message is being given.
    Regards,
    Prashant Kolhatkar

  • LIV for Purchase Orders with Account Assignment

    Hi SAP Gurus,
    I would like to get your expert advice on this...
    I enabled total based invoice acceptance and reduction by performing the required configuration steps (define vendor tolerance group, set up the auto invoice reduction tolerance checks, assigned the tolerance group to the vendor). I was assuming that this would work for my purchase order which contains an account assignment. However, when I tested it out, instead of behaving as expected (create invoice and credit memo for the excess value), the system generated only 1 accounting document. The price variance was posted back to the account assignment assigned to the PO item.
    Did I miss out on any steps? or is this the way SAP treats account assigned (non-stock) PO items (i.e. no invoice reduction occurs). If so, can you explain to me why?
    Best regards,
    RiVeR
    Edited by: delo celo on Jul 14, 2010 6:16 PM

    Hi Delo,
    Please find answers to your queries below in bold.
    1. I was just wondering why would SAP allow such transaction/s to happen? Wouldn't it compromise the integrity of the whole document trail (PO account assignment is different from the LIV)?  -
    There could be some business scenarios in some organisations, where in Procurement team uses generic cost centre (header), which is specific to particular department or group, to procure. But at the time of Invoice Receipt, AP team knows exact cost centre or order, etc  to post the amounts. To cover these kind of scenarios, SAP probably has provided the option to change acount assignment.
    2. Is there a way to edit the Account Assignment for a Purchase Order line item even if that item has been fully received and invoiced? -
    These field changes at various levels can be configured via t-code OME9.
    a) IR Changeable - This field if selected will allow to change the account assignment of a purchase order item at the time of invoice receipt.
    b) Acct. assg. changeable - This field is selected will allow to change account assignment for an item following goods receipt or invoice receipt.         
    Hope this clarifies your queries.
    -Ravi

Maybe you are looking for