To enable status  FPLT-FKSAK in VA42 Billing plan for T&M

HI All,
    In VA42 -  Billing Plan, The Billing status is always A even if the bill is done. I have been assigned to change it to C when billing is done. This is happening in T& M only. For Fixed and Milestone, it s automatically closing. But for T & M it is not. Any suggestion ??
Regards

Yes - go back to the SD functional analyst and have them re-evaluate this. If the status is not changing then either something wasn't configured incorrectly or the correct process is not being followed.
There should be no ABAP necessary to change any standard statuses in SAP.

Similar Messages

  • Creation of Budget Billing Plan for Countries with Tax Jurisdiction

    Hello Experts,
    When I create a budget billing plan for a company code with country Canada/USA and jursidiction TAXCAJ/TAXUSJ using transaction EA61, I get the message "Taxes with jurisdiction code not permitted with down payments"(Message no. >0194).  The long text for this message says "Delete your entry in the field for jurisdiction code"  Is any one aware where from this jurisdiction code should be deleted.
    Is it possible to create budget billing plan for countries with jurisdiction code at all ?
    Thanks in advance
    Venkat

    Hello Roopali,
    What I learnt in the process of exploring the functionality is that Payment PLan (BBP or AMB) is the budget billing method for countries with Tax Jurisdiction. Statistical, Partial & Payment Scheme only works when jurisdiction is not defined for tax procedure. Payment scheme is the recommend procedure for Eurpopean market
    Thanks for your clarification
    Best Regards
    Venkat

  • Is it necessary to create a Billing Plan for the Service Contracts

    Hi All,
      Is it necessary to create a billing plan for the service contracts.
      My requirement.
      In CRM 7.0, we created a service contract. For the item in that service contract there is a Billing Plan tab.
      In that tab we have the dates for Period, Billing Date etc.
      Now our requirement is to get the Billing Date quarterly. For this we created date rules and date profiles and assigned these date profiles to header and item level transactions.
    And we are able to see the date rules under the drop down of the billing date.
    I copied the standard date rule BILL004 to ZBILL004.
      But when we changed to our date rule it is not changing to quarterly date.
      Can you please let me know  what are the configurations to be done for this.
      Is the billing plan has to be created for this kind of scenario.
    Thanks in advance
    Thanks and Regards,
    Raghu

    Hi
    On OK button's action  you can Destroy the window and navigate to Page1.
    Go through this link for more details and a step by step guide for creation of pop ups  and dialog boxes
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/903fed0d-7be4-2a10-cd96-9136707374e1?quicklink=index&overridelayout=true
    Hope it works
    Regards
    Suresh

  • Billing in the basis of billing plan for multiple schedule lines

    Hi All,
    I have one scenario in which we have created milestoen billing via project systems in sales order. Now Suppose I have three line items in my sales order and against each line items we have maintained multiple schedule lines. ex. 10%, 40%,50% respectively. Similarly for other line items also we have maintained the same. Now I need to generate invoice on the basis of schedule lines(billing plan). for ex. single Invoice covers 2 schedule lines out of total schedule lines in the line item. Similarly for other line items.
    Kindly guide.
    Thanks.

    Hi
    Your milestone billing plan integrates with PS means that you have an order related billing.
    Hence schedule line is a confusing word and I assume it as a billing plan.
    Each milestone-related billing date is blocked for processing until the Project System confirms that the milestone is completed. The billing block will automatically be removed once the milestone is achieved.
    Do maintain copy controls properly at item category level (VTFA) and your billing should happen standard SAP way.
    If still you face any errors, please post the screenshots.
    Thanks
    Atul

  • Transaction to maintina Billing Plan for Sales order item

    Hi All,
    Is there any transaction other than VA01/VA02 to maintian Billing plan for Sales order item.
    Thanks & Regards,
    Rajanidhi Rajasekeran.

    It is possible to maintain Billing Plan in Sales Document Type (VOV8), as well as Item Category level (VOV7). As you want it at Item level, maintain the same in Item Category Configuration at Item level & it will by default be captured in Sales Order at Item level.
    Step 1: Sales Document Type
    IMG > Sales and Distribution > Sales > Sales Documents >
    Sales Document Header:
    1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
    2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
    3. Assign Sales Area To Sales Document Types:
    A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
    B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
    Sales Document Item:
    1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
    2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
    Regards,
    Rajesh Banka

  • VA42-Authorization to change Billing Plan

    Hi All,
    How to provide authorization to change "sales document" & "item" fields in  VA42 Billing Plan section.
    Regards
    #Alex

    HI,
    http://help.sap.com/saphelp_wp/helpdata/en/52/6714b6439b11d1896f0000e8322d00/frameset.htm
    Steps,
    Go to PFCG
    Enter role name say ZSALES ORDER PROCESSING and click on single role
    Enter discription and save
    Then click on MENU tab,then click on transaction and maintain t-codes like VA41,VA42,VA43 and click on assign transactions and save
    Then click on AUTHORIZATION tab and click to Change autorization data,then it will ask for orgz. level maintain orgz.data or click on FULL Authorization
    Then you can able to see modules from where the the transaction code belongs(SD)
    Expand it to lower level node and maintain autorization for Perticular sales document, sales area
    Then save and click on GENEREATE ICON (Shift+F5)
    Now go to tab USER and assign users
    Click on user comparision >> Complete comparision
    Now when the assigned user log in syatem system will display this role for user and he/she may authorization for perticular sales document and sales area depending uppon your authorization provided in this role.
    You can see existing roles and copy from existing one
    kapil

  • Billing plan and billing status

    Hello Friends,
    I would like to clarify if my understanding is correct before I configure a billing plan:
    1. Billing status is not seen in billing doc but in preceding doc like a DO.
    2. For a Billing Plan, there can be 1 billing plan at item level for a set of settlement dates.
    If the plan is defined at header level, only 1 billing plan is for all items.
    3. Contract is a sales doc type  and contract data is only at header level.
    Is this considered an Order-related billing when invoice is printed at each billing date?
    Is the contract considered as the reference doc for the billing doc sent to customer? I believe so. please confirm.
    4. There is no such thing as master billing plan that item level billing plans need to be linked to.
    5. date category : this is at billing date level and cannot be changed?
    regards
    Pascal

    Hello,
    Milestone billing means distributing the total amount to be billed over multiple billing
    dates in the billing plan.
    As each milestone is successfully reached, the customer is billed either a percentage of
    the entire project cost or simply a pre-defined amount.
    During sales order processing, the system determines from the item category whether a
    billing plan is required and, if so, which type of plan
    The type of billing plan that is determined at this point is set up in Customizing and
    cannot be changed in the sales document.
    Billing plans for periodic billing and milestone billing plans for project-related milestone
    billing have different overview screens so that you can enter data relevant to your
    processing.
    For example, for milestone billing, you must be able to enter data to identify the
    individual milestones.
    Thanks,
    venkataswamy.y
    IMG configuration requires :-
    1. Maintain billing plan types for milestone billing in OVBO.
    2. Define date description in SM30 - V_TVTB.
    3. Maintain Date Category for Billing Plan Type IN OVBJ.
    4. Allocate date category in SM30 - V_TFPLA_TY.
    5. Maintain date proposal for Billing Plan Type in OVBM.
    6. Assign Billing Plan Type to Sales Documents Type in OVBP.
    7. Assign Billing Plan Type to Item Categories in OVBR.
    8. Define rules for determining the date in OVBS.
    Milestone billing is typically used for billing projects, such as plant engineering and
    construction projects. Such projects often include a series of milestones that mark the
    completion of different stages of the work. In the SAP R/3 System, milestones are defined
    in a network along with planned and actual dates for the completion of work. The milestones
    are also assigned to the billing dates in the billing plan.
    Each milestone-related billing date is blocked for processing until the Project System
    confirms that the milestone is completed.
    Delivery-relevant order items for which a milestone billing plan applies are billed on the
    basis of the requested delivery quantity and not on the total of the confirmed quantities.
    The connection between the project and the sales document item is made in the individual
    schedule lines of the item. Each schedule item can be assigned to a network in a project.
    To display the project-related data for a schedule line, proceed as follows:
    In one of the overview screens of the sales document, select
    1. Item -> Schedule lines.
    2. Mark the schedule line and select Procurement details.
    The following figure shows an example of milestone billing where only the Contract have
    been billed :
    Order Item Turbine 100,000
    Billing Plan
    Billing date Description % Value Billing Block Milestone Billing Status
    01-10-94 Contract 10 10,000 - x x
    01-03-95 Assembly 30 30,000 x x
    01-04-95 Maintenance 30 30,000 x x
    01-05-95 Acceptance 30 30,000 x x
    01-06-95 Final invoice .. .. x
    Network/Activities
    Milestone Estimate Actual
    Assembly 01-03-95 01-03-95
    Maintenance 01-04-95
    Acceptance 01-05-95
    For each billing date in a milestone billing plan, you can specify whether the billing
    date is:
    1. fixed
    2. always updated with the actual date of the milestone
    3. updated with the actual date of the milestone, if the date is earlier than the
    planned billing date for the date
    Comments
    the article was great it explained about billng milestone very well

  • Contract Billing Plan

    Using VA42, I have to create the Billing Plan for contract line items.
    I find many Function Modules and BAPIs to update the existing Billing Plan for the contract line.
    Any idea about how to create one? Any BAPI/FM?
    Pranu

    You can update billing plan using following Function module.
    *& UPDATE Billing Plan
    i_bapi_view-header = 'X'.
        i_bapi_view-item = 'X'.
        i_bapi_view-partner = 'X'.
        i_bapi_view-contract = 'X'.
        i_bapi_view-sdcond = 'X'.
        i_bapi_view-sdcond_add = 'X'.
        i_bapi_view-billplan = 'X'.
        i_bapi_view-configure = 'X'.
        sales_documents-vbeln = v_order.
        APPEND sales_documents.
        CALL FUNCTION 'BAPISDORDER_GETDETAILEDLIST'
          EXPORTING
            i_bapi_view            = i_bapi_view
          TABLES
            sales_documents        = sales_documents
            order_headers_out      = order_headers_out
            order_items_out        = order_items_out
            order_contracts_out    = order_contracts_out
            order_billingplans_out = order_billingplans_out
            order_billingdates_out = order_billingdates_out
            order_partners_out     = order_partners_out
            order_conditions_out   = order_conditions_out.
        LOOP AT order_billingplans_out WHERE itm_number = '000000'.
          hfplnr = order_billingplans_out-bill_plan.
        ENDLOOP.
        LOOP AT tab WHERE kbetr IS NOT INITIAL.
          LOOP AT order_conditions_out WHERE itm_number = tab-itm_number
                                       AND cond_type = 'ZZRE'.
            MOVE-CORRESPONDING order_conditions_out TO cond_ch.
            IF order_conditions_out-cond_type = 'ZZRE'.
              cond_ch-cond_value = tab-kbetr.
              APPEND cond_ch.
            ENDIF.
          ENDLOOP.
        ENDLOOP.
    * Read the billing plan
        CALL FUNCTION 'BILLING_SCHEDULE_READ'
          EXPORTING
            fplnr = hfplnr
          TABLES
            zfpla = hfpla
            zfplt = hfplt.
        MOVE hfpla TO hfpla2.
    *READ TABLE zfpla2 INDEX 1.
        hfpla2-lodat = p_stat.
        hfpla2-tndat = p_end.
        hfpla2-rfpln = ''.
        hfpla2-lodar = ''.
        hfpla2-tndar = ''.
        hfpla2-fpart = p_bplan.
        hfpla2-perio = p_bplan.
        hfpla2-horiz = p_hori.
    *** Very important to set field updkz = 'U' ***
        hfpla2-updkz = 'U'. "--> UPDATE!!
        APPEND hfpla2.
        CLEAR pos.
        CALL FUNCTION 'BILLING_SCHEDULE_SAVE'
          TABLES
            fpla_new = hfpla2
            fpla_old = hfpla
            fplt_new = hfplt " --> NEW
            fplt_old = hfplt.
        CALL FUNCTION 'SD_SALES_DOCUMENT_SAVE'
          EXPORTING
            i_no_messages = ' '.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait = 'X'.
    *& END OF UPDATE Billing Plan Header level
    *& UPDATE Billing Plan Item  level
        LOOP AT zbill.
          MOVE v_order TO doc .
          CALL FUNCTION 'SD_SALES_DOCUMENT_READ'
            EXPORTING
              document_number = doc.
          MOVE zbill-itm_number TO pos.
          CALL FUNCTION 'SD_SALES_BILLINGPLAN_READ'
            EXPORTING
              i_vbeln                = doc
              i_posnr                = pos
            IMPORTING
              e_fpla                 = e_fpla
            TABLES
              e_fplt                 = e_fplt
            EXCEPTIONS
              no_billingplan_allowed = 1
              no_billingplan_found   = 2
              OTHERS                 = 3.
          IF sy-subrc NE 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ENDIF.
    * Read the billing plan
          CALL FUNCTION 'BILLING_SCHEDULE_READ'
          EXPORTING
          fplnr = e_fpla-fplnr
    * I_VFKDAT =
    * I_BFKDAT =
          TABLES
          zfpla = zfpla
          zfplt = zfplt.
    * Upddate the ZFPLT2 table with the new values
    *MOVE zfplt TO zfplt2.
          MOVE zfpla TO zfpla2.
    *READ TABLE zfpla2 INDEX 1.
          zfpla2-lodat = zbill-datesfrom.
          zfpla2-tndat = zbill-datesto.
          zfpla2-rfpln = ''.
          zfpla2-lodar = ''.
          zfpla2-tndar = ''.
          zfpla2-fpart = p_bplan.
          zfpla2-horiz = p_hori.
    *** Very important to set field updkz = 'U' ***
          zfpla2-updkz = 'U'. "--> UPDATE!!
          APPEND zfpla2.
        ENDLOOP.
        CLEAR pos.
        CALL FUNCTION 'BILLING_SCHEDULE_SAVE'
          TABLES
            fpla_new = zfpla2
            fpla_old = zfpla
            fplt_new = zfplt " --> NEW
            fplt_old = zfplt.
        CALL FUNCTION 'SD_SALES_DOCUMENT_SAVE'
          EXPORTING
            i_no_messages = ' '.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait = 'X'.
    Edited by: Krupaji on Apr 9, 2011 7:21 AM

  • Billing planes

    Friends,
    How Billing planes (Milestone) can be used in the down payment processing?
    Here we are collecting 30% payment during sales order creation & 70% during shipment.
    Thanks

    Hi Friend,
    Mile stone billing is part of PROJECT SYSTEMS MODULE integrated with SD.
    Milestone billing is practiced by Infrastructure companies and Power Ind,and construction industry(projects).
    Billing Plan for Milestone Billing
    Milestone billing means distributing the total amount to be billed over multiple billing
    dates in the billing plan.
    As each milestone is successfully reached, the customer is billed either a percentage of
    the entire project cost or simply a pre-defined amount.
    During sales order processing, the system determines from the item category whether a
    billing plan is required and, if so, which type of plan
    The type of billing plan that is determined at this point is set up in Customizing and
    cannot be changed in the sales document.
    Billing plans for periodic billing and milestone billing plans for project-related milestone
    billing have different overview screens so that you can enter data relevant to your
    processing.
    For example, for milestone billing, you must be able to enter data to identify the
    individual milestones.
    IMG configuration requires :-
    1. Maintain billing plan types for milestone billing in OVBO.
    2. Define date description in SM30 - V_TVTB.
    3. Maintain Date Category for Billing Plan Type IN OVBJ.
    4. Allocate date category in SM30 - V_TFPLA_TY.
    5. Maintain date proposal for Billing Plan Type in OVBM.
    6. Assign Billing Plan Type to Sales Documents Type in OVBP.
    7. Assign Billing Plan Type to Item Categories in OVBR.
    8. Define rules for determining the date in OVBS.
    Milestone billing is typically used for billing projects, such as plant engineering and
    construction projects. Such projects often include a series of milestones that mark the
    completion of different stages of the work. In the SAP R/3 System, milestones are defined
    in a network along with planned and actual dates for the completion of work. The milestones
    are also assigned to the billing dates in the billing plan.
    Each milestone-related billing date is blocked for processing until the Project System
    confirms that the milestone is completed.
    Delivery-relevant order items for which a milestone billing plan applies are billed on the
    basis of the requested delivery quantity and not on the total of the confirmed quantities.
    The connection between the project and the sales document item is made in the individual
    schedule lines of the item. Each schedule item can be assigned to a network in a project.
    To display the project-related data for a schedule line, proceed as follows:
    In one of the overview screens of the sales document, select
    1. Item -> Schedule lines.
    2. Mark the schedule line and select Procurement details.
    The following figure shows an example of milestone billing where only the Contract have
    been billed :
    Order Item Turbine 100,000
    Billing Plan
    Billing date Description % Value Billing Block Milestone Billing Status
    01-10-94 Contract 10 10,000 - x x
    01-03-95 Assembly 30 30,000 x x
    01-04-95 Maintenance 30 30,000 x x
    01-05-95 Acceptance 30 30,000 x x
    01-06-95 Final invoice .. .. x
    Network/Activities
    Milestone Estimate Actual
    Assembly 01-03-95 01-03-95
    Maintenance 01-04-95
    Acceptance 01-05-95
    For each billing date in a milestone billing plan, you can specify whether the billing
    date is:
    1. fixed
    2. always updated with the actual date of the milestone
    3. updated with the actual date of the milestone, if the date is earlier than the
    planned billing date for the date
    Reward points if helpful.
    Thanks,
    T.Nishanth,

  • Billing block removal in Billing Plan - Transaction VA02

    Hi,
    How can I remove the Billing Block in Billing plan for a single sales order? (header level)
    What I need to remove/change to empty is the field FPLT-FAKSP (from Billing Plan tab) and not the FAKSK from table VBAK (in Billing Document tab).
    Following example is only to remove the VBAK-FAKSK, but what i need is to remove the FPLT-FAKSP.
    Please help.
    Thanks
    REPORT  Z_BILLING_BLOCK.
    PARAMETERS: p_vbeln TYPE vbak-vbeln.
    DATA: l_header_inx TYPE bapisdh1x,
          l_header_in  TYPE bapisdh1.
    DATA: lt_return TYPE STANDARD TABLE OF bapiret2.
    update the flag.
    l_header_inx-updateflag = 'U'.
    l_header_inx-bill_block = 'X'.  " Billing
    l_header_in-bill_block  = ''.   " Remove Billing block.
    Call the bapi.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
      EXPORTING
        salesdocument    = p_vbeln
        order_header_in  = l_header_in
        order_header_inx = l_header_inx
      TABLES
        return           = lt_return.
    check for errors.
    LOOP AT lt_return TRANSPORTING NO FIELDS WHERE type = 'A' OR type = 'E'.
      EXIT.
    ENDLOOP.
    IF sy-subrc = 0.
      WRITE: / 'Error in updating'.
    ELSE.
      WRITE: / 'Billing block removed'.
      COMMIT WORK AND WAIT.
    ENDIF.

    Hi,
    I don't want to use this is the sales order user-exit. What I really want is to have another different program running in background for example and removing this Billing Block (FPLT-FAKSP).
    My code is only working for the billing block in Billing Document Tab and not for the one in Billing Plan.
    Thanks a lot
    Br
    Anyone knows already a solution for this??
    Edited by: Ninfx Ninfx on Feb 27, 2009 4:42 PM

  • Rolling Month in Billing Plan in Sales Order

    I Require rolling month billing dates in Sales Orders . Kindly help on the same the followng format is required.
    Contract Start Date : 05.01.2010
    Contract End Date : 31.03.2010
    Settlement From   Settlement to    Billing Date
    05.01.2010            04.02.2010     04.02.2010
    05.02.2010            04.03.2010     04.03.2010
    05.03.2010            31.03.2010     31.03.2010.
    If there are any user exits where i can make these changes or if there are any configurations that i  can change then suggest.
    Thanx in Advance.
    Dilip

    You have to enable the PERIODIC BILLING as the billing plan for your case.
    You can refer to the OSS note 831158 which gives lot of other OSS notes for you to configure the scenario.

  • About billing plan types

    Sir ,
    I have a need of Billing plan type configuration step by step,i have tried to configure throgh glenc willams but i couldn't able to understand.
    Kindly send me the configuration of billing plantypes and explain me in which situation these are applicable.
    Thankig u

    Milestone billing means distributing the total amount to be billed over multiple billing
    dates in the billing plan.
    As each milestone is successfully reached, the customer is billed either a percentage of
    the entire project cost or simply a pre-defined amount.
    During sales order processing, the system determines from the item category whether a
    billing plan is required and, if so, which type of plan
    The type of billing plan that is determined at this point is set up in Customizing and
    cannot be changed in the sales document.
    Billing plans for periodic billing and milestone billing plans for project-related milestone
    billing have different overview screens so that you can enter data relevant to your
    processing.
    For example, for milestone billing, you must be able to enter data to identify the
    individual milestones.
    IMG configuration requires :-
    1. Maintain billing plan types for milestone billing in OVBO.
    2. Define date description in SM30 - V_TVTB.
    3. Maintain Date Category for Billing Plan Type IN OVBJ.
    4. Allocate date category in SM30 - V_TFPLA_TY.
    5. Maintain date proposal for Billing Plan Type in OVBM.
    6. Assign Billing Plan Type to Sales Documents Type in OVBP.
    7. Assign Billing Plan Type to Item Categories in OVBR.
    8. Define rules for determining the date in OVBS.
    Milestone billing is typically used for billing projects, such as plant engineering and
    construction projects. Such projects often include a series of milestones that mark the
    completion of different stages of the work. In the SAP R/3 System, milestones are defined
    in a network along with planned and actual dates for the completion of work. The milestones
    are also assigned to the billing dates in the billing plan.
    Each milestone-related billing date is blocked for processing until the Project System
    confirms that the milestone is completed.
    Delivery-relevant order items for which a milestone billing plan applies are billed on the
    basis of the requested delivery quantity and not on the total of the confirmed quantities.
    The connection between the project and the sales document item is made in the individual
    schedule lines of the item. Each schedule item can be assigned to a network in a project.
    To display the project-related data for a schedule line, proceed as follows:
    In one of the overview screens of the sales document, select
    1. Item -> Schedule lines.
    2. Mark the schedule line and select Procurement details.
    The following figure shows an example of milestone billing where only the Contract have
    been billed :
    Order Item Turbine 100,000
    Billing Plan
    Billing date Description % Value Billing Block Milestone Billing Status
    01-10-94 Contract 10 10,000 - x x
    01-03-95 Assembly 30 30,000 x x
    01-04-95 Maintenance 30 30,000 x x
    01-05-95 Acceptance 30 30,000 x x
    01-06-95 Final invoice .. .. x
    Network/Activities
    Milestone Estimate Actual
    Assembly 01-03-95 01-03-95
    Maintenance 01-04-95
    Acceptance 01-05-95
    For each billing date in a milestone billing plan, you can specify whether the billing
    date is:
    1. fixed
    2. always updated with the actual date of the milestone
    3. updated with the actual date of the milestone, if the date is earlier than the
    planned billing date for the date

  • Billing plan table

    Folks,
    Please let me know if there is any table where I can se billing plan for a SO and a specific line item.
    Thanks in advance.
    ABY

    Hi,
    The table names are "FPLT" and "FPLA".
    First Goto the T.Code "SE11/SE16".
    Enter the table name as "FPLA".
    Enter your sales order number in "VBELN(Sales Document)".
    Execute.
    It gives you the over all view i.e. billing plan start date,end date etc..
    Copy the "Billing plan number".
    Next goto the table "FPLT".
    Pass this billing plan number here.
    Execute.
    You will get the details about all the billing plan items.
    Regards,
    Krishna.

  • Billing Plan simulation

    Hi,
    I need to use a function module or a bapi to simulate (but no create) billing plan in the contract items.
    So i would like to reproduce the standard function (see how it works in debug) but i don't know how to simulate billing plan. I try to use VA42 but i can't any simulation function or something else.
    Can you help me?
    Thanks

    Hi,
    Ideally you would simulate a cycle from contract to invoice and make sure its working alright.
    To enter a billing plan for a contract (after entering VA41 and the customer, material details), go to the item level screen. There is a tab called billing plan here.
    You assign a billing plan reference for your document type (Path:IMG Settings > Sales and Distribution > Sales Documents Header, and Billing > Billing Plan > Maintain Date Proposals for billing plan types).
    If these settings are maintained, then the billing plan should automatically populate. Then you create the release order, remove billing block and invoice.
    Cheers.

  • Regarding billing plan

    Hi,
    Can anybody can help me in providing document on billing plan i.e
    1.milestone billing
    2.periodic billing
    3.resource related billing ASAP.
    Thanks
    Arun

    Hi
    Billing Plan for Milestone Billing
    Milestone billing means distributing the total amount to be billed over multiple billing
    dates in the billing plan.
    As each milestone is successfully reached, the customer is billed either a percentage of
    the entire project cost or simply a pre-defined amount.
    During sales order processing, the system determines from the item category whether a
    billing plan is required and, if so, which type of plan
    The type of billing plan that is determined at this point is set up in Customizing and
    cannot be changed in the sales document.
    Billing plans for periodic billing and milestone billing plans for project-related milestone
    billing have different overview screens so that you can enter data relevant to your
    processing.
    For example, for milestone billing, you must be able to enter data to identify the
    individual milestones.
    IMG configuration requires :-
    1.  Maintain billing plan types for milestone billing in OVBO.
    2.  Define date description in SM30 - V_TVTB.
    3.  Maintain Date Category for Billing Plan Type IN OVBJ.
    4.  Allocate date category in SM30 - V_TFPLA_TY.
    5.  Maintain date proposal for Billing Plan Type in OVBM.
    6.  Assign Billing Plan Type to Sales Documents Type in OVBP.
    7.  Assign Billing Plan Type to Item Categories in OVBR.
    8.  Define rules for determining the date in OVBS.
    Milestone billing is typically used for billing projects, such as plant engineering and
    construction projects. Such projects often include a series of milestones that mark the
    completion of different stages of the work. In the SAP R/3 System, milestones are defined
    in a network along with planned and actual dates for the completion of work. The milestones
    are also assigned to the billing dates in the billing plan.
    Each milestone-related billing date is blocked for processing until the Project System
    confirms that the milestone is completed.
    Delivery-relevant order items for which a milestone billing plan applies are billed on the
    basis of the requested delivery quantity and not on the total of the confirmed quantities.
    The connection between the project and the sales document item is made in the individual
    schedule lines of the item. Each schedule item can be assigned to a network in a project.
    To display the project-related data for a schedule line, proceed as follows:
    In one of the overview screens of the sales document, select
    1.  Item -> Schedule lines.
    2.  Mark the schedule line and select Procurement details.
    The following figure shows an example of milestone billing where only the Contract have
    been billed :
    Order  Item  Turbine    100,000
    Billing Plan
    Billing date Description    %  Value  Billing Block   Milestone   Billing Status
    01-10-94     Contract      10  10,000      -             x           x 
    01-03-95     Assembly      30  30,000      x             x          
    01-04-95     Maintenance   30  30,000      x             x
    01-05-95     Acceptance    30  30,000      x             x
    01-06-95     Final invoice ..    ..        x
    Network/Activities
    Milestone    Estimate      Actual
    Assembly     01-03-95      01-03-95
    Maintenance  01-04-95     
    Acceptance   01-05-95
    For each billing date in a milestone billing plan, you can specify whether the billing
    date is:
    1.  fixed
    2.  always updated with the actual date of the milestone
    3.  updated with the actual date of the milestone, if the date is earlier than the
        planned billing date for the date
    Periodic Billing
    Some customers may require invoices to be processed periodically, so that all deliveries due for billing by a certain time are put into one collective invoice.
    Prerequisites
    To fulfill this requirement, a billing schedule must be defined for the customer:
    A factory calendar which contains special rules instead of working days must be created. These special rules refer to the days on which billing should be carried out. If, for example, an invoice is to be issued every last working day of the month, then this day must be entered as "valid from" day and "valid to" day. This day must be the only day defined as a working day in the calendar for each month.
    The ID-number of the factory calendar must be specified on the billing screen of the payer's customer master record in the Billing schedule field.
    Activities
    When a sales document is created, the system copies the invoice date from the factory calendar and enters it into the relevant document as follows:
    On the next billing date determined by the factory calendar, the system selects all sales orders and deliveries and puts them in a billing due list. They can now be billed.
    As a result of the ID-number of the factory calendar defined in the customer master record, all sales orders or deliveries for that customer over a particular period have the same billing date, and they can be combined in one collective invoice.
    The following figure shows how the system proceeds if a billing schedule has been defined for a customer.
    <a href="http://help.sap.com/saphelp_dimp50/helpdata/EN/59/54fc37004d0a1ee10000009b38f8cf/content.htm">Resource-Related Billing</a>
    http://help.sap.com/saphelp_46c/helpdata/en/dd/560fdd545a11d1a7020000e829fd11/content.htm

Maybe you are looking for

  • Images selected in iPhoto remain on screen and visible in other apps

    Running iPhoto '09 and quite often when we select multiple images to share via iMessage or email, those images then stay on the screen and are visible no matter application you have active.  iPhoto becomes unresponsive and the only resolution is a fu

  • How to I get rid of virus's on my mac book pro?

    is there any way to get rid of virus's on my macbook pro without making an appointment with apple?

  • Where the hell do the system.out.println s go ??

    I am using 9ifs 9.0.1 in windows accessing ifsservers through jsps. I am wondering where will the SOP 's be printed whil accessing the ifsserver through jsps 's. I guessed it was at the apachev jserv log files. I turned the log on and also checked al

  • Synch keeps telling me the computer is not authorized for the Ipod

    Synch keeps telling me the computer is not authorized for the Ipod  I have authorized again and again but this error still occurs. I am unable to synch and there is no option to not synch tunes from iTunes store. This occurred after an upgrade. ck

  • What has Mountain Lion done to iCal sync?

    I'm seeing lots of questions about iCal post-Mountain Lionon these forums, but far fewer answers on this one! I have four calendars on my iPhone 4 that run my life. Pre-Mountain Lion upgrade on my iMac they all synched perfectly well via iCloud with