Invoice Creation Date

Hi,
Does anyone know how to get the date when invoice is created in the system? BKPF-CPUDT is changed when a parked invoice is posted and does not reflect the date invoice is created. Are there other fields for this? Thanks for your help!

Hi,
When we do Park documents, we can change the document date and posting date. But the posting date is derived from Posting period variant. Once we saved the parked document. the document is created with number range. later when we do changes SAP will not allow to change posting date.
we can do delete parked documents as well. If you want to change the posing date in the posted document, reverse the posted document and re create again.
Best Regards,
Mohan.

Similar Messages

  • PO creation Date and Invoice creation Date

    Hi,
    Can any one help me regarding which table I can look for PO creation date and Invoice creation date. I require these fields for my reporting requirement.
    Thanks in advance,
    Arvind.

    Thanks for your response Bala.
    I got the Table which I require. I have one more question on this.
    Can you tell me Invoice Creation Date is RBKP-BLDAT(Document Date in Document) or RBKP-BUDAT(Posting Date in the Document) and PO creation Date is EKKO-AEDAT(Date on which the record was created) or EKKO-BEDAT(Document Date in Document).
    Points already rewarded.

  • How to Check product warranty in CRM based on R/3 invoice creation date

    Dear all,
    As per our client business process, for a sales product warranty starts once after creation of Invoice in ECC system. in that case, how to perform warranty check in CRM Complaints based on ECC Invoice creation date.
    Please suggest me the standard SAP solution for this. Your help will be highly appreciated
    Regards
    Raghu ram
    Edited by: Raghu Ram on Jan 11, 2010 7:24 AM

    Hi Raghu,
    This is pure development. But it is possible.
    You need to use a function module to create warranty contract in CRM against to ECC invoice with the following prerequisites
    1. Same SLA should be available in both ECC and CRM (In ECC there is no SLA concept, in that case u need to maintain SLA as text component in delivery/sales order or any Z transaction document, the same can be pulled into CRM warranty contract)
    2. All the products sold in ECC should be having serial number during delivery process. Then the combination of product and serial number will be created an equipment master in ECC. This equipment master should be replicated to CRM as and when it is created in ECC.
    3. The partners in equipment master should be same as in invoice or sales order document in ECC
    4.  Addiitionally, all the products in the ECC invoice to be replaced as service material with SCN item category (We used this logic), so you can use any other logic to get service line item. You can use any common service material also as line item.
    5. Male the status profile settings to release the contract once it is created and saved in CRM
    6. In the complaint or service request document, set the contract determination as Unique number (I think "D")
    As standard, You can create wrranty contract and assign warranty master as and when ECC invoice is created by manual method.
    Hope this development logic will be useful.
    Regards,
    Ram.

  • Pricing date for the tax condition type should be invoice creation date

    HI Folks,
    As per the current design taxes conditions are determining based on the Service rendered date which is similar to the GI date and pricing type is G in copy control .
    New requirement is taxes should calculate based on the Invoice creation date in the invoice.in order to acheive the solution i have customized the tax related condition type functionality "pricing date" as KOMP-ERDAT but still system calcualting the taxes based on the service rendered date and same also writing in the invoice also.
    pLease help me out what need to be configured here to acheive the solution.
    Regards,
    Ram.

    Hello XYZ,
    As you said the tax is calculated in Taxware system, i think taxware system is configured to calculate the taxes based on the "service rendered date". That is the reason why even you have changed the pricing date to be billing date for condition type XR1 taxware is not behaving as you expected.
      You have two options.
    1. Invocie creation date/ blling date is available in the structure "TAX_CAL_ITEM_IN00".If it is available in the structure ask the Taxware team to make changes in their system to consider that field value instead of the service rendered date.
    2. Alternatively you can over write the filed which contains the service rendered date value with the value of billing date. This way no changes required in Taxware system. You can do that in cusotmer exit  "EXIT_SAPLFYTX_USER_001" include ZXFYTU03 .
       Based on my exeperince i think the consistant approach would be going with option 1 . Please revert if you need furhter information on the same
    Thanks,
    Srini
    Edited by: srini vasarao on Jul 14, 2011 12:02 PM

  • Invoice Document Date - PGI Date Vs Invoice creation date

    Hello Guys,
    The way our system works right now is the date on the invoice document is always the date of PGI.
    The business requires that the invoice date be the date it is billed.
    But on the last day of the month it will be the date of PGI. and not the date of billing it.
    Any advice on how the solution could be implemented.
    Thanks

    Through standard it is not possible.  You have to try with USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
    thanks
    G. Lakshmipathi

  • Invoice cancellation doc picking up billing doc creation date

    hi,
         i am cancelling an invoice document which was created and posted last month(july- mm period closed,fi still open) but the cancelled accounting document  is picking up the invoice creation date rather today's date. help would be appreciated.
    regards
    leo

    Hi Leo,
    When any invoice is cancelled it will automatically pick the original invoice date.
    If you want other date on which the cancelled invoice has to be created can give the date in the billing date field, so that it wil creat cancelled invoice on date you entered when cancelling
    T.code VF11.
    kindly reward points if usefull.
    Regards
    RVK

  • Read Invoice Plan data in BADI impl "ME_PROCESS_PO_CUST" during PO creation

    Hello All,
    We had implemented BADI "ME_PROCESS_PO_CUST", during the check & post methods I require to fetch the invoicing plan data for calculating the total value of purchase order. Because invoice plan is splitted just like an instalment for a period and the line item in PO is showing only one instalment, where as the ordered value of PO is the total of all instalments.
    Invoice Plan data will be stored in FPLT table and the FPLNR can be fetched from EKPO.
    Can any one tell me how to read the invoice plan data during the PO creation? Is there an interface & method for reading it?
    Regards,
    Ramesh
    Edited by: Ramesh Babu Srikakollu on Apr 18, 2011 7:37 AM

    Hello All,
    I, myself found the solution for reading the Invoice Plan data of a Purchase Order during the creation/change. i.e. the runtime data for calculation.
    Here is the solution:
    Call this function module in the BADI implementation for the method CHECK or POST using the FPLNR (Invoice Plan Number), this returns the run time data of the invoice plan details during creation or change of a PO.
          data lt_fplt type table of fplt.
          CALL FUNCTION 'ML_INVOICING_SCHEDULE_READ'
            EXPORTING
              fplnr_imp = ls_opp_ekpo-fplnr
            TABLES
              xfplt     = lt_fplt.
    Regards,
    Ramesh

  • Excise invoice creation incase of price increase

    Dear all,
    I am facing a problem in case supplementary billing scenario at my client's place.
    Some times price of the material increases and that price will be effected from past date.Then a supplementary excise is created with values consisting of
    Differential value + 16% excise on differential price + 2 % Ecess + 1%Hecess + sales tax against all the effected invoices previously created.
    " Differential value = (New Price - Old Price)*(total invoiced quantity of the material from effected date to till now ) "
    How can i create excise invoice in sap for this case, where there would be no goods movement..
    With the help of my abaper i can create debitmemo with this pricing structure with some modifications in program for VFRB - Retro-Billing by individual invoice wise.
    But my client is asking for excise invoice creation for this scenario but not debit memo.
    Pls guide me the way to do this scenario.
    Thanks in advance
    Kartheek N

    Hi,
    We also have same scenario and we done work around for this solution.
    Suppose i have
    Base Price 1000
    ED              160
    ECESS         32
    SECC            16
    Based on the above we made Billing document VF01 and Excise Invoice through J1IIN.  After sending the material there is price change and you require to raise suplementary invoice for the same, in that wat you required to do is
    1. Create Sales Order with referene to main billing document
    2. Create Billing document with refernce to sales order and note that the Billing category is M becasue as per standard SAP billing category M and U are only relevent for Exicse Invoice cration.
    Through the above you can rraise the invoice.
    If it helps provide rewards
    Rgds
    Gautam

  • Multiple Invoice Creation

    Hi All,
    I want to create Multiple Invoice Creation through BAPI or FM. For this invoice PO is the Reference.
    As per requirement i have multiple PO in container, at one shot i want to create invoice realted PO as the reference.
    Thanks
    Amit

    hi,
    I am trying in another way - creating one proforma invoice for multiple deliveries. and with that proforma invoice trying to create excise invoice.
    But i am facing problem in creating proforma with multiple deliveries because of DIFFERENT NUMBER RANGE IN HEADER (delivery)AT FOREIGN TRADE --- UNDER ORGANIZATION --- NUMBER OF FOREIGN TRADE DATA - ( which is internally assigned by the system)
    If i can get where this number is assign my problem is solved
    K.S.Rao

  • Invoice List data(VF21/VF22) as IDoc

    Hi,
    We have a typical scenario of converting Invoice List data in SAP into IDoc and to transmit it as an XML to the third party system. In the data to be transmitted, sub-totalling at the material (in the invoice items) and material+invoice date level is required and the sub-totals are to be populated in two kind of segments (for each of the sub-total type) in the IDoc.
    That is, a new IDoc structure will be defined with the segments/fields that the customer wants viz., a header segment with only few fields from the invoice list header, an item segment with only few fields from the invoice list item, and a sub-total segment with two fields, each to hold sub-total at material and material+date level respectively.
    We have output types which, when assigned in the invoice list should create the required Idocs.
    Invoice lists will be created for several partners, but each list will have only one partner.
    What are the steps to be carried out in order to achieve this objective? Please stress upon the FM parameters to be provided and NACE options to be selected.
    Vish.

    Hello ,
    Your requirement is very simple ,However before posting into sdn please do  a proper search on idoc.
    Now coming to your requirement as of now you have the invoice data coming up.
    1. In the NACE transaction create an output type related with the respective partner data.
    2.Create segments with the required fields and set its status to release.
    3.create  Idoc type and message type ..link the message and segents.
    4.Now link the message type and idoc type .
    5.
    6. Now assign process code to the partner function by defining a logical system and in the process code
    put your custom function module where you put your custom code which will filter and
    cumulate the data coming from the invoice into different fields
    using normal abap code,
    Now once you are done with the abap coding the
    function module has few parameters which you can pass  them as it is .
    control_in need to be passed to Control_out as it is.
    Now fill the segments with the required data and append the segment data to the
    EDI_DATA structure which is a exporting parameter for thefunction module .
    Now once you execute the invoice using this partner function and message type
    system would internally call the custom function module which you have assigned to
    the process code and would create an idoc.
    also go through saptechnical-com site for addition details on idoc creation.

  • User Exits for Invoice creation ,cancellation and sales return

    Hi Gurus,
    Pl help me it's very urgent.
    I did not find any user exit invoice creation so i wrote the following code in include program
    MV60AF0B_BELEG_SICHERN.
    This code is to update the Z*table while saving invoice ,cancellation and sales return.
    The code modification is like below
          FORM BELEG_SICHERN                                            *
          Buchen Fakturabelege                                          *
    FORM BELEG_SICHERN.
      READ TABLE XVBRK INDEX 1.
      IF SY-SUBRC NE 0.
        CALL FUNCTION 'DEQUEUE_ALL'.
        MESSAGE S032.
        EXIT.
      ENDIF.
      IF SAMH_MOD = ON.
        EXPORT XKOMFK TO MEMORY ID 'SDBILLDL'.
      ENDIF.
      DATA: CALC_TYPE.
      IF REBATE_DETERMINED = 'Y'.
        CALC_TYPE = 'A'.
      ELSE.
        CALC_TYPE = 'I'.
      ENDIF.
    *{   INSERT         RD1K903017                                        1
    Work Area*********************
    data : wa_xvbrk type VBRKVB.
    data : wa_xvbrp type vbrpvb.
    data : wa_zmigo type zmigo.
    data : wa_vbrp type vbrp.
    Internal table Creation*******
    DATA:  BEGIN OF tab_XVBRP OCCURS 100.
             INCLUDE STRUCTURE VBRPVB.
    DATA:  END OF tab_XVBRP.
    data : begin of tab_vbeln occurs 10,
           vbeln type vbrk-vbeln,
           knumv type vbrk-knumv,
           end of tab_vbeln.
    data : tab_zmigo type table of zmigo.
    data : tab_vbrp type table of vbrp.
    *****Data declaration*************
    data : v_no_of_inv type i.
    data : v_vbeln_no(10) type n.
    data : v_last_inv_no(10) type n.
    data : v_first_inv_no(10) type c.
    data : v_tot_qty type i.
    data : v_frbnr type mkpf-frbnr.
    *******Ranges*********************
    ranges : r_vbeln for vbrk-vbeln.
    *****Populating IT****************
    tab_xvbrp[] = xvbrp[].
    describe table xvbrk lines v_no_of_inv.
    *}   INSERT
      CALL FUNCTION 'RV_INVOICE_DOCUMENT_ADD'
           EXPORTING
                VBSK_I           = VBSK
                WITH_POSTING     = 'A'
                PREISFINDUNGSART = CALC_TYPE
           IMPORTING
                VBSK_E           = VBSK
           TABLES
                XKOMFK           = XKOMFK
                XTHEAD           = XTHEAD
                XVBFS            = XVBFS
                XVBSS            = XVBSS
                XVBRK            = XVBRK
                XVBRP            = XVBRP
                XVBPA            = XVBPA
                XKOMV            = XKOMV.
    *{   INSERT         RD1K903017                                        2
    data : v_count type i,v_fkimg type i .
    data : v_no_of_records(10) type n.
    wa_xvbrk = xvbrk.
    ********Selecting the last rec no from ZMIGO
          select max( sr_no ) from zmigo into v_no_of_records.
    *****If Distribution channel is not ZB*********
    if  wa_xvbrk-vtweg ne 'ZB' and ( wa_xvbrk-fkart = 'ZRIN' or wa_xvbrk-fkart = 'ZRTE' ).
    if v_no_of_inv = 1.              " Process only when there is one invoice
    loop at tab_xvbrp into wa_xvbrp  where (           matnr ne 'CDGSTP0001'       and
                                                       matnr ne 'CD-RW'            and
                                                       matnr ne 'CD-RW65OHS'       and
                                                       matnr ne 'CABLE'            and
                                                       matnr ne 'CD-R'             and
                                                       matnr ne 'CDQ80N4'          and
                                                       matnr ne 'GENERAL'          and
                                                       matnr ne 'NERO'             and
                                                       matnr ne 'OTHERS'           and
                                                       matnr ne 'SPARE PARTS'      and
                                                       matnr ne 'PROMO ITEM'       and
                                                       matnr ne 'PROMO-1'          and
                                                       matnr ne 'PROMO-2'          and
                                                       matnr ne 'PROMO-3'          and
                                                       matnr ne 'PROMO-4'          and
                                                       matnr ne 'PROMO-5'          and
                                                       matnr ne 'PROMO-6'          and
                                                       matnr ne 'PROMO-7'          and
                                                       matnr ne 'PROMO-8'          and
                                                       matnr ne 'PROMO-9'          and
                                                       matnr ne 'PROMO-10' ).
    v_fkimg = wa_xvbrp-fkimg .
    v_fkimg = v_fkimg / 1000.
                do v_fkimg times.
                  v_no_of_records = v_no_of_records + 1.
                  wa_zmigo-sr_no = v_no_of_records.
                  wa_zmigo-po_no = wa_xvbrk-vbeln.
                  wa_zmigo-item_no  = wa_xvbrp-posnr.
                 wa_zmigo-mblnr  = wa_xmkpf-mblnr.
                  wa_zmigo-doc_type = wa_xvbrk-fkart.
                  wa_zmigo-posting_date = wa_xvbrk-fkdat.
                  wa_zmigo-created_on = sy-datum.
                  wa_zmigo-created_time = sy-uzeit.
                 wa_zmigo-bill_lno = v_frbnr.
                  wa_zmigo-material = wa_xvbrp-matnr.
                 wa_zmigo-inv_no = wa_xvbrk-vbeln.
                 wa_zmigo-inv_item_no = wa_xvbrp-posnr.
                  wa_zmigo-plant = wa_xvbrp-werks.
                  wa_zmigo-inv_date = wa_xvbrk-fkdat.
                  wa_zmigo-customer = wa_xvbrk-kunag.
                  wa_zmigo-unit = 1.
                  wa_zmigo-mtype = '601'.
                  insert into zmigo values wa_zmigo.
                enddo.
                clear : wa_zmigo.
    endloop.
    clear : v_count,v_fkimg,wa_zmigo.
    refresh tab_zmigo[].
    clear v_no_of_inv.
    else.                              "When there are Split Invoices
    v_last_inv_no = wa_xvbrk-vbeln.
    v_vbeln_no = v_last_inv_no - v_no_of_inv + 1.
    v_first_inv_no = v_vbeln_no.
    sort tab_xvbrp by vbeln.
    loop at tab_xvbrp into wa_xvbrp  where (           matnr ne 'CDGSTP0001'       and
                                                       matnr ne 'CD-RW'            and
                                                       matnr ne 'CD-RW65OHS'       and
                                                       matnr ne 'CABLE'            and
                                                       matnr ne 'CD-R'             and
                                                       matnr ne 'CDQ80N4'          and
                                                       matnr ne 'GENERAL'          and
                                                       matnr ne 'NERO'             and
                                                       matnr ne 'OTHERS'           and
                                                       matnr ne 'SPARE PARTS'      and
                                                       matnr ne 'PROMO ITEM'       and
                                                       matnr ne 'PROMO-1'          and
                                                       matnr ne 'PROMO-2'          and
                                                       matnr ne 'PROMO-3'          and
                                                       matnr ne 'PROMO-4'          and
                                                       matnr ne 'PROMO-5'          and
                                                       matnr ne 'PROMO-6'          and
                                                       matnr ne 'PROMO-7'          and
                                                       matnr ne 'PROMO-8'          and
                                                       matnr ne 'PROMO-9'          and
                                                       matnr ne 'PROMO-10' ).
    v_fkimg = wa_xvbrp-fkimg .
    v_fkimg = v_fkimg / 1000.
                do v_fkimg times.
                  v_no_of_records = v_no_of_records + 1.
                  wa_zmigo-sr_no = v_no_of_records.
                  wa_zmigo-po_no = v_vbeln_no.                      "wa_vbrp-vbeln.
                  wa_zmigo-item_no  = wa_xvbrp-posnr.
                 wa_zmigo-mblnr  = wa_xmkpf-mblnr.
                  wa_zmigo-doc_type = wa_xvbrk-fkart.
                  wa_zmigo-posting_date = wa_xvbrk-fkdat.
                  wa_zmigo-created_on = sy-datum.
                  wa_zmigo-created_time = sy-uzeit.
                 wa_zmigo-bill_lno = v_frbnr.
                  wa_zmigo-material = wa_xvbrp-matnr.
                 wa_zmigo-inv_no = v_vbeln_no.
                 wa_zmigo-inv_item_no = wa_xvbrp-posnr.
                  wa_zmigo-plant = wa_xvbrp-werks.
                  wa_zmigo-inv_date = wa_xvbrk-fkdat.
                  wa_zmigo-customer = wa_xvbrk-kunag.
                  wa_zmigo-unit = 1.
                  wa_zmigo-mtype = '601'.
                  insert into zmigo values wa_zmigo.
                enddo.
                clear : wa_zmigo.
    at end of vbeln.
    v_vbeln_no = v_vbeln_no + 1.
    endat.
    clear : v_count,v_fkimg,wa_zmigo.
    refresh tab_zmigo[].
    endloop.
    endif.                             "End of first 2nd IF.
    clear : v_no_of_inv, v_vbeln_no.
    endif.
    ****************Sales return************************************
    if  wa_xvbrk-fkart = 'ZRRE' and wa_xvbrk-vtweg ne 'ZB'.
    loop at tab_xvbrp into wa_xvbrp where (            matnr ne 'CDGSTP0001'       and
                                                       matnr ne 'CD-RW'            and
                                                       matnr ne 'CD-RW65OHS'       and
                                                       matnr ne 'CABLE'            and
                                                       matnr ne 'CD-R'             and
                                                       matnr ne 'CDQ80N4'          and
                                                       matnr ne 'GENERAL'          and
                                                       matnr ne 'NERO'             and
                                                       matnr ne 'OTHERS'           and
                                                       matnr ne 'SPARE PARTS'      and
                                                       matnr ne 'PROMO ITEM'       and
                                                       matnr ne 'PROMO-1'          and
                                                       matnr ne 'PROMO-2'          and
                                                       matnr ne 'PROMO-3'          and
                                                       matnr ne 'PROMO-4'          and
                                                       matnr ne 'PROMO-5'          and
                                                       matnr ne 'PROMO-6'          and
                                                       matnr ne 'PROMO-7'          and
                                                       matnr ne 'PROMO-8'          and
                                                       matnr ne 'PROMO-9'          and
                                                       matnr ne 'PROMO-10' ).
             v_fkimg = wa_xvbrp-fkimg.
             v_fkimg = v_fkimg / 1000.
             v_tot_qty = v_tot_qty + v_fkimg.
              do v_fkimg times.
                v_no_of_records = v_no_of_records + 1.
                wa_zmigo-sr_no = v_no_of_records.
                wa_zmigo-po_no = wa_xvbrk-vbeln.
                wa_zmigo-item_no  = wa_xvbrp-posnr.
                wa_zmigo-doc_type = wa_xvbrk-fkart.
                wa_zmigo-posting_date = wa_xvbrk-fkdat.
                wa_zmigo-created_on = sy-datum.
                wa_zmigo-created_time = sy-uzeit.
                wa_zmigo-material = wa_xvbrp-matnr.
               wa_zmigo-inv_no = wa_xvbrk-vbeln.
               wa_zmigo-inv_item_no = wa_xvbrp-posnr.
                wa_zmigo-plant = wa_xvbrp-werks.
                wa_zmigo-inv_date = wa_xvbrk-fkdat.
                wa_zmigo-customer = wa_xvbrk-kunag.
                wa_zmigo-unit = 1.
                wa_zmigo-mtype = '651'.
                condense wa_xvbrk-xblnr.
                wa_zmigo-reference = wa_xvbrk-xblnr.
    ********Bill of lading no**
               select single bill_lno from zmigo_final into v_frbnr where inv_no = wa_xvbrk-xblnr and material = wa_xvbrp-matnr.
               if sy-subrc eq 0.
               wa_zmigo-bill_lno = v_frbnr.
               endif.
                insert into zmigo values wa_zmigo.
              enddo.
              clear : wa_zmigo,wa_xvbrp , v_fkimg, v_frbnr.
    endloop.
    endif.
    *******Invoice Cancellation*****************************
    if  wa_xvbrk-fkart = 'ZRS1' and wa_xvbrk-vtweg ne 'ZB'.
    delete tab_xvbrp[] where shkzg eq 'X'.
    loop at tab_xvbrp into wa_xvbrp where (            matnr ne 'CDGSTP0001'       and
                                                       matnr ne 'CD-RW'            and
                                                       matnr ne 'CD-RW65OHS'       and
                                                       matnr ne 'CABLE'            and
                                                       matnr ne 'CD-R'             and
                                                       matnr ne 'CDQ80N4'          and
                                                       matnr ne 'GENERAL'          and
                                                       matnr ne 'NERO'             and
                                                       matnr ne 'OTHERS'           and
                                                       matnr ne 'SPARE PARTS'      and
                                                       matnr ne 'PROMO ITEM'       and
                                                       matnr ne 'PROMO-1'          and
                                                       matnr ne 'PROMO-2'          and
                                                       matnr ne 'PROMO-3'          and
                                                       matnr ne 'PROMO-4'          and
                                                       matnr ne 'PROMO-5'          and
                                                       matnr ne 'PROMO-6'          and
                                                       matnr ne 'PROMO-7'          and
                                                       matnr ne 'PROMO-8'          and
                                                       matnr ne 'PROMO-9'          and
                                                       matnr ne 'PROMO-10' ).
             v_fkimg = wa_xvbrp-fkimg.
             v_fkimg = v_fkimg / 1000.
             v_tot_qty = v_tot_qty + v_fkimg.
              do v_fkimg times.
                v_no_of_records = v_no_of_records + 1.
                wa_zmigo-sr_no = v_no_of_records.
                wa_zmigo-po_no = wa_xvbrk-vbeln.
                wa_zmigo-item_no  = wa_xvbrp-posnr.
                wa_zmigo-doc_type = wa_xvbrk-fkart.
                wa_zmigo-posting_date = wa_xvbrk-fkdat.
                wa_zmigo-created_on = sy-datum.
                wa_zmigo-created_time = sy-uzeit.
                wa_zmigo-material = wa_xvbrp-matnr.
               wa_zmigo-inv_no = wa_xvbrk-vbeln.
               wa_zmigo-inv_item_no = wa_xvbrp-posnr.
                wa_zmigo-plant = wa_xvbrp-werks.
                wa_zmigo-inv_date = wa_xvbrk-fkdat.
                wa_zmigo-customer = wa_xvbrk-kunag.
                wa_zmigo-unit = 1.
                condense wa_xvbrk-zuonr.
                wa_zmigo-reference = wa_xvbrk-zuonr.
                wa_zmigo-mtype = '602'.
    ********Bill of lading no**
               select single bill_lno from zmigo_final into v_frbnr where inv_no = wa_xvbrk-xblnr and material = wa_xvbrp-matnr.
               if sy-subrc eq 0.
               wa_zmigo-bill_lno = v_frbnr.
               endif.
                insert into zmigo values wa_zmigo.
              enddo.
              clear : wa_zmigo,wa_xvbrp , v_fkimg.
    endloop.
    endif.
    clear : v_no_of_records.
    *}   INSERT
      CALL FUNCTION 'STACK_RESET'.
      R185D-DATALOSS = SPACE.
      FOLGEAUFRUF102 = SPACE.
      PERFORM SETPAR_INIT.
    *{   INSERT         RD1K903017                                        3
    *}   INSERT
      LEAVE.
    ENDFORM.
    This program is working fine for single user but in production where no of people are creating the invoices from different places the data is not getting updated in table ZMIGO.
    sometime populating with wrong data , partial data and sometimes no updation at all.
    I have used the table locking system enqueue and dequeue FM's before n after updation but still the same
    thing is happening.
    What could be the reason.
    Looking for help very urgent any other alternate option.

    Hi,
    Go thru these..
    Enhancement
    SDVFX009 Billing doc. processing KIDONO (payment reference numbe
    SDVFX010 User exit item table for the customer lines
    SDVFX011 Userexit for the komkcv- and kompcv-structures
    V05I0001 User exits for billing index
    V05N0001 User Exits for Printing Billing Docs. using POR Procedu
    V60A0001 Customer functions in the billing document
    V60P0001 Data provision for additional fields for display in lis
    V61A0001 Customer enhancement: Pricing
    SDVFX001 User exit header line in delivery to accounting
    SDVFX002 User exit for A/R line (transfer to accounting)
    SDVFX003 User exit: Cash clearing (transfer to accounting)
    SDVFX004 User exit: G/L line (transfer to accounting)
    SDVFX008 User exit: Processing of transfer structures SD-FI
    SDVFX007 User exit: Billing plan during transfer to Accounting
    SDVFX006 User exit: Tax line (transfer to accounting)
    SDVFX005 User exit: Reserves (transfer to accounting)
    Business Add-in
    SD_CIN_LV60AU02 BADI for billing
    If it is helpful rewards points
    Regards
    Pratap.M

  • Account Payable Invoice Creation

    Hi All,
    I just want to know the Account Payable Invoice creation screen.
    How many data hit by invoice screen for master table
    AP_INVOICE_ALL
    specially invoice_date and gl_date column.
    Please help.
    Regards

    Hi,
    Did you check the settings in VKOA. Check Sales Org/ Order Reason. Check whether GL Accounts assigned is correct or not. Also check the settings in Account key
    Regards,
    Jigar

  • Document date and creation date are diffrence

    dear all,
    please tell me the why are the document date and created on date.
    like customer code is created on 12.11.2011.
    but sales order created on 12.10.2010.
    what is the diffirence of above the issue.
    please solve the problem.
    rajiv kumar

    Hi,
    The absic difference is,
    Document Created Date: The date on which the document was created by the user in SAP.
    Billing Date: The date on which the invoice was created. For example, the user maybe entering the invoicein SAP on 1st december. But in reality the invoice was issued on 30th Nov. Due to some holiday or some reason the user was not able to create on 30th nov and creates it on1st dec. So he makes the invoice date as 30th nov and the document creation date would be 1st dec by default.
    Let me know if this explanation is still not clear.
    Regards,
    Rohan Gudavalli.

  • Parked MM invoice creation time?

    Hi,
    I've been trying to find the parked MM document entry date but can't see it in any standard transactions or in FI tables.. Does anyone know if there is a specific table where the information is contained? Or if this field is maintained at all?
    -Mikko

    Thanks for the info, there I get to see the MM invoice parked document entry date. I saw it earlier from the transactions but just got confused because I thought it was the posted document entry date available also in table BKPF.
    My requirement is basically to find out the "lifetime" of a parked document i.e. the time it was in parked status before posting. The data is then later used for process evaluation.
    Surviving from the confusion and rephrasing my question, do you know where to find the accounting document creation date or the technical MM invoice posting date?
    The posting date field can't be used as such because users can choose any date there. Also the entry date in table BKPF contains the same value as the original parked document creation date.
    The scenario is thus the following:
    1. MM invoice created/parked => entry date available in RBKP
    2. MM invoice posted => Accounting document created (acc doc entry date = parked MM invoice entry date)
    So is there any way to either see when the MM invoice was posted or the accounting document technically created?
    Any help appreciated,
    -Mikko

  • PO Collaboration : Invoice Creation Type field

    Hello,
    The Invoice Creation Type field in the SNC Web UI is always "Invoice Creation not allowed" irrespective of the settings to the Master Data / Transaction Data.
    Given below are the settings I ve maintained
    ECC System:
    PO -> Item Details -> Invoice Tab:
    Inv. Receipt Indicator - Checked
    GR-Bsd IV - Checked / Unchecked
    SNC System:
    Vaildation Checks - Tried both these settings:
    1. PO_INVOICE_CREATION - Active
        PO_INVOICE_DATA_ASSIGN - Active
        PO_INVOICE_RELATED_TO_PO_OR_ASN - Inactive
    2. PO_INVOICE_CREATION - Inactive
        PO_INVOICE_DATA_ASSIGN - Active
        PO_INVOICE_RELATED_TO_PO_OR_ASN - Active
    Infact, I am not able to see the Invoice tab itself in the PO details screen in SNC Web UI.
    Note : I am using the Orders.Orders05 Idoc for sending the PO from ECC to SNC system.

    Hi Bharath
    Your settings are fine
    Please do the following checks
    If you use IDocs of type ORDERS.ORDER05, SAP SNC can instead read the data for these fields from a reference document, such as a contract, that has previously been transferred via the Core Interface (CIF).
    In your PO you would have referenced a contract/agreement, Please check whether it is CIFed or not
    Also before CIFING do implement these notes
    1053121 & 828912
    Now when you send the ORDERS idoc, The RON xml reads this data and puts in structure
    <FollowUpInvoice>
      <RequirementCode>01</RequirementCode>
      <GoodsReceiptBasedInvoiceIndicator>TRUE</GoodsReceiptBasedInvoiceIndicator>
      <CustomerSelfBillingIndicator>FALSE</CustomerSelfBillingIndicator>
      <ProductTaxationCharacteristicsCode>V1</ProductTaxationCharacteristicsCode>
      </FollowUpInvoice>
    Irrespective, whether you create invoice for ASN or PO, the tab should be visible as Nikhil rightly mentioned
    In SAP SNC , Controlling Invoice Creation for POs is done by FollowUpRequirementCode as mentioned above
    Now since you are using ORDERS, you need to check you SA or Contract in Item Details Tab
    the following fields need to be checked "IR" in both cases and In Header Details Field "Invoicing Party"
    Also during creation of PO, make sure you dont check Unlimited Overdelivery in item delivery tab and even in your reference document.
    Now after implementing above two notes reCIF and try creating PO, It will work
    Please do mention whether you are able to see the above structure in your RON xml in SCM side and what details???
    Best Regards
    Vinod

Maybe you are looking for