Service Contract Billing plan

Dear Guru's,
           As per my clinet Requirement we configured the Service Contract with Periodic Billing Plan on Monthly basis.Now After Saving the Service Contract when i go to change mode in Item Level Billing Plan Tab Page it is showing GREY or DISPLAY MODE only. But when i realize the Button HDR it is showing CHANGE MODE.
           Now what is my Requirement is The Billing Plan Tab page Should always be in Change mode only .So how to do this could anybody help me.
Thank you
suribabu

Dear All,
                Thank you. i solved the problem. i have maintain the Billing plan in Both Header and Item level.Now Remove at Header level. Do run the cycle.
Thank you.
suribabu

Similar Messages

  • Service Contract Billing

    Hi,
    I am trying to bill a service contract with periodic billing plan. but when it is executing it is showing all the dates based on the period(monthly). But after saving it, its showing me only last date. I am not getting whats wrong?? I want to bill only for a particular period not for all. plz guide me .
    Thanks
    Ipsit

    Hi ,
    As per my Knowledge  you need to configure your fiscal year in your system  then after creation your billing it will calculate  into  period.
    For example     : if you set up your project   November month  then onwards after completion of project it will calculate period  to the back   .   if your project has completed  in june      your peariod would  08 .
    if you give me brief i can help you out more.
    if helpful REWARD points
    Thank you .
    Regards
    Ramana

  • Service contract - Billing block

    Dear Guru's
                 i am doing  the service contract with standard document type  WV.But my client requirment is,he wants to block the individual line item wise in VA41 and Release in VA42 by individual line item and do billing in VF01.
               could anybody tell me how to configure the same. i am using the Billing plan Periodic .
    Thank you
    suribabu

    Hi,
    You can achieve same using status profile conifg at item level, i did same for my service contract for order creation block ( IW31) and Billing block,
    try with status profile , i hope its help you to block Service items in sales contract.
    Regards
    Nishad

  • Service Contracts Billing Schedule Creation Error

    Hi,
    I have a requirement of creating service contracts from back-end for which I am using the oks_contracts_pub.create_contract_header, create_service_line, and create_bill_schedule. I am creating my contracts with active status and renewal type of EVN (Header level), FUL(Line Level). My contract is of type subscription. The contract header and line are creating fine but the Bill schedule API is throwing an UNEXPECTED ERROR. The billing schedules need to be created based on accounting rule which can be quarterly or monthly. I have included the bill schedule code (hard coded values) for review. Any help is greatly appreciated.
    Also the version I am working on is R12
    ________________________________________________CODE___________________________________________________________________
    CREATE OR REPLACE PROCEDURE BILLING_SCHEDULE AS
    l_strm_level_tbl OKS_BILL_SCH.STREAMLVL_TBL;
    v_bill_qtrs NUMBER := 0;
    v_bill_mths NUMBER := 0;
    v_bill_days NUMBER := 0;
    v_net_amount NUMBER := 468;
    v_acct_rule_name VARCHAR2(50) := 'QUARTERLY';
    v_amt_per_day NUMBER;
    x_error_locator VARCHAR2(2000);
    v_start_date DATE := '04-MAY-2010';
    v_end_date DATE := '25-MAY-2010';
    x_return_status VARCHAr2(3);
    x_msg_count NUMBER;
    x_msg_data VARCHAR2(2000);
    v_billing_sequence NUMBER;
    x_chr_id NUMBER := 17000;
    x_line_id NUMBER := 223248604345353294444923586786456728480;
    g_day_uom VARCHAR2(10) := 'DAY';
    g_month_uom VARCHAR2(10) := 'MTH';
    g_quarter_uom VARCHAR2(10) := 'QTR';
    v_amt NUMBER;
    v_invoicing_rule_id NUMBER := -2;
    BEGIN
    --Create Billing Schedule based on accounting rule
    okc_context.set_okc_org_context;
    MO_GLOBAL.INIT('OKS');
    MO_GLOBAL.SET_POLICY_CONTEXT('S', 83);
    v_bill_qtrs := 0;
    v_bill_days := 0;
    v_bill_mths := 0;
    SELECT NVL(v_net_amount, 0)/(v_end_date - v_start_date)
    INTO v_amt_per_day
    FROM dual;
    dbms_output.put_line('Calculated amt per day ' || v_amt_per_day);
    IF v_acct_rule_name LIKE '%QUARTERLY%' THEN
    --Quarterly billing schedule
    SELECT FLOOR(MONTHS_BETWEEN( v_end_date,
    v_start_date)/3),
    v_end_date - ADD_MONTHS(v_start_date, (FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)/3)*3))
    INTO v_bill_qtrs,
    v_bill_days
    FROM dual;
    dbms_output.put_line('Calculated the qtrs and days');
    IF v_bill_qtrs > 0 THEN
    SELECT (ADD_MONTHS(v_start_date, (FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)/3)*3)) - v_start_date)*v_amt_per_day
    INTO v_amt
    FROM dual;
    dbms_output.put_line('Calculated qtr amt');
    SELECT NVL(MAX(sequence_no), 0) + 1
    INTO v_billing_sequence
    FROM oks_stream_levels_b
    WHERE dnz_chr_id = x_chr_id
    AND cle_id = x_line_id;
    --Populating the stream line variables
    l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
    l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
    -- l_strm_level_tbl(v_billing_sequence).id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).uom_code := g_quarter_uom;
    l_strm_level_tbl(v_billing_sequence).uom_per_period := 1;
    l_strm_level_tbl(v_billing_sequence).level_periods := v_bill_qtrs;
    l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
    l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
    l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
    l_strm_level_tbl(v_billing_sequence).amount := v_amt/v_bill_qtrs;
    l_strm_level_tbl(v_billing_sequence).level_amount := v_amt/v_bill_qtrs;
    l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
    l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
    dbms_output.put_line('Before calling the Bill Sch API for QTR');
    OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
    p_strm_level_tbl=>l_strm_level_tbl,
    p_invoice_rule_id=>v_invoicing_rule_id,
    x_return_status=>x_return_status);
    dbms_output.put_line('After calling the Bill Sch API for QTR');
    IF x_return_status <> 'S' THEN
    x_msg_count := 1;
    dbms_output.put_line('Quarterly schedule creation error ' || x_msg_data);
    ---DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
    -- RETURN;
    END IF;
    END IF;
    IF v_bill_days > 0 THEN
    SELECT NVL(MAX(sequence_no), 0) + 1
    INTO v_billing_sequence
    FROM oks_stream_levels_b
    WHERE dnz_chr_id = x_chr_id
    AND cle_id = x_line_id;
    dbms_output.put_line('sequence '||v_billing_sequence);
    --Populating the stream line variables
    l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
    l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
    --l_strm_level_tbl(v_billing_sequence).id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).uom_code := g_day_uom;
    l_strm_level_tbl(v_billing_sequence).uom_per_period := v_bill_days;
    l_strm_level_tbl(v_billing_sequence).level_periods := 1;
    l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
    l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
    l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
    l_strm_level_tbl(v_billing_sequence).amount := v_net_amount;--v_amt_per_day*v_bill_days;
    l_strm_level_tbl(v_billing_sequence).level_amount := v_net_amount;--v_amt_per_day*v_bill_days;
    l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
    l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
    dbms_output.put_line('Before calling the Bill Sch API for QTR days');
    OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
    p_strm_level_tbl=>l_strm_level_tbl,
    p_invoice_rule_id=>v_invoicing_rule_id,
    x_return_status=>x_return_status);
    dbms_output.put_line('After calling the Bill Sch API for QTR days ' || v_bill_days || ' ' || x_return_status);
    IF x_return_status <> 'S' THEN
    x_msg_count := 1;
    dbms_output.put_line('Day schedule, for quarterly accounting rule, creation error ' || x_msg_data);
    --DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
    --RETURN;
    END IF;
    END IF;
    ELSE
    --Monthly billing schedule
    SELECT FLOOR(MONTHS_BETWEEN( v_end_date,
    v_start_date)),
    v_end_date - ADD_MONTHS(v_start_date, FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)))
    INTO v_bill_mths,
    v_bill_days
    FROM dual;
    dbms_output.put_line('Calculated the mths and days');
    IF v_bill_mths > 0 THEN
    SELECT (ADD_MONTHS(v_start_date,FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date))) - v_start_date)*v_amt_per_day
    INTO v_amt
    FROM dual;
    dbms_output.put_line('Calculated the mths amt');
    SELECT NVL(MAX(sequence_no), 0) + 1
    INTO v_billing_sequence
    FROM oks_stream_levels_b
    WHERE dnz_chr_id = x_chr_id
    AND cle_id = x_line_id;
    --Populating the stream line variables
    l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
    l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
    --l_strm_level_tbl(v_billing_sequence).id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).uom_code := g_month_uom;
    l_strm_level_tbl(v_billing_sequence).uom_per_period := 1;
    l_strm_level_tbl(v_billing_sequence).level_periods := v_bill_mths;
    l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
    l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
    l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
    l_strm_level_tbl(v_billing_sequence).amount := v_amt/v_bill_mths;
    l_strm_level_tbl(v_billing_sequence).level_amount := v_amt/v_bill_mths;
    l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
    l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
    dbms_output.put_line('Before calling the Bill Sch API for MTHS');
    OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
    p_strm_level_tbl=>l_strm_level_tbl,
    p_invoice_rule_id=>v_invoicing_rule_id,
    x_return_status=>x_return_status);
    dbms_output.put_line('After calling the Bill Sch API for MTHS');
    IF x_return_status <> 'S' THEN
    x_msg_count := 1;
    dbms_output.put_line('Monthly schedule creation error ' || x_msg_data);
    --DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
    --RETURN;
    END IF;
    END IF;
    IF v_bill_days > 0 THEN
    SELECT NVL(MAX(sequence_no), 0) + 1
    INTO v_billing_sequence
    FROM oks_stream_levels_b
    WHERE dnz_chr_id = x_chr_id
    AND cle_id = x_line_id;
    --Populating the stream line variables
    l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
    l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
    --l_strm_level_tbl(v_billing_sequence).id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).uom_code := g_day_uom;
    l_strm_level_tbl(v_billing_sequence).uom_per_period := v_bill_days;
    l_strm_level_tbl(v_billing_sequence).level_periods := 1;
    l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
    l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
    l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
    l_strm_level_tbl(v_billing_sequence).amount := v_amt_per_day*v_bill_days;
    l_strm_level_tbl(v_billing_sequence).level_amount := v_amt_per_day*v_bill_days;
    l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
    l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
    dbms_output.put_line('Before calling the Bill Sch API for MTH days');
    OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
    p_strm_level_tbl=>l_strm_level_tbl,
    p_invoice_rule_id=>v_invoicing_rule_id,
    x_return_status=>x_return_status);
    dbms_output.put_line('After calling the Bill Sch API for MTH days');
    IF x_return_status <> 'S' THEN
    x_msg_count := 1;
    dbms_output.put_line('Day schedule, for monthly accounting rule, creation error ' || x_msg_data);
    --DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
    --RETURN;
    END IF;
    END IF;
    END IF;
    COMMIT;
    EXCEPTION
    when others then
    dbms_output.put_line('Error ' || sqlerrm);
    END;
    Thanks,
    Yash.

    Hi There,
    I have a similar requirement to create rental service contracts and create billing schedules.
    Can you please pass on your functional docs so that i can refer to them.
    Thanks,
    Raidu

  • Contract , billing plan issue

    Hello
    I am having issue where I have cancelled billing document corresponding to a contract, then also I canu2019t rebill the contract. I found in the header billing plan the status is showing is B(Partially processed) which is partially processed and for a line item it is showing C(Completely  processed), though I have cancelled all the invoices. Can some one help.
    David

    David
    Try running reports SDVBUK00 and RVV05IVB  to correct the status and/or billing index after carefully reading their documentation.
    Hope this helps.

  • 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

  • Pricing in contract/billing plan

    Hai ,
    I have a contract with a billing plan. On header level I use a pricing condition. Example: at header level I have a net value of 400 euro.  In the periodic billing plan I have 13 periods, each period gets 400 euro.
    I want that the 400 euro  will be divided over the periods. In this case, 13 periods so each period has to get 400/13= 33,77.
    Can you help me to accomplish this?

    Hello Balazs,
    Thanks for your reply.
    I use an condition with a fixed amount at header level. this amount/rate must be divided over number of settlement periods.
    Whe use a routine for this and it works, but when I save a contract and go back to change a discription, the rate is no longer  divided by the number of periods. It looks like the routine is in conflict with standaard SAP.
    Is it possible to customize this without a routine, so that the amount at header level divided over the number of periods.
    Fixed amount 400 euro at header level. in billing plan 13 periods so each period has to get 400/13= 30.77
    Thanks!

  • Item billing plan lines not appearing in billing due list ...

    Hello Team ,
    I have one question on service contract billing plan. Contract has status released.
    I have one contract which has header billing plan that is applicable at line item also.
    1. At line item level billing plan two items are due for billing but in billing due list this line item does not appear. Some of the lines in Item billing plan are already billed.
    Also at item billing plan there is no check (tick mark) for Header Billing Plan.
    Can some one suggest what are the possible checks for item billing plan not appearing in billing due list.
    Thanks ,
    Nitn Patki

    Hi Nitin,
    Check the status of the line items.
    Regards
    Narayana

  • How to link Sales Order with Service Contract and then with Install Base?

    Hi Friends,
    1) I would like to know the integeration process from sales order to Service Contract and then with Install Base.
    2) I couldn't see anything enabled in Service Tab in Order Lines, its grayed out. Is there any set up/profile option to get it enabled?
    3) How can we create AR invoice from Service Contract?
    Please let me know if anyone has idea on this.
    Thanks in Adavance,
    Vara

    Dear Sid,
    Thanks for your promt response.
    Let me explain you what I did.
    1) I have booked a Bill Only sales order which has one order line, mentioned it as Service Item and provided the same details in Service Tab in Order lines. Now Line status is "Fulfilled"
    2) Then Submitted Workflow Back Ground Process for OM Order Lines and it has created an AR Invoice and closed the line
    3) And then submitted "Service Contracts Order Capture Integration Program" from SErvice Contracts Responsibility and it completed normal.
    4) Now I went in to Launch Contracts Window and queried with the sales order but couldn't see any contract created
    5) Then I went in to Reprocess Order Window and found this order shows an error message as "Referenced Product not present in the Installed Base", then I tried to reprocessed it, but the same error message again.
    Here I have few doubts:
    1) Are the AR invoice and Service Contract Billing Invoices same?
    2) In above scenario AR Invoice has been created, I would like to do the billing from SErvice Contracts and need to create an Invoice in AR? how can I do that?
    because as you explained in one of my questions earlier, A Single Invoice can be created for the whole duration of the contract. I want to do that and trying for the same.
    3) Regarding the above error message, how can I resolve it and create the service contract against that Order?
    Thank you so much for your helpful answers.
    Regards,
    Vara

  • Billing Plan Flow

    Hello,
    Suppose we have a contract with a sales plan that comprises a milestone plan (3 invoices with different percentages 30%, 40% and 40%).
    Is it possible to split the billing plan in different sales orders wichi will end up in one of those invoices mentioned above?
    Contract (Billing Plan)   --> Sales order 1   --> 30%  --> F2
                                         --> Sales order 2   --> 40%  --> F2
                                         --> Sales order 3   --> 30%  --> F2
    OR the billing plan only supports this scenario:
    Contract (Billing Plan)   --> Sales order 1   --> 30%  --> F2 30%
                                                                                    --> F2 40%
                                                                                    --> F2 30%
    Kind Regards.

    Hi,
    The billing plan only supports the second scenario.
    We cannot create different sales orders for different billing plan items in contract.
    The name itself tells us that it is a plan for billing.
    So it supports only this case:
    Contract (Billing Plan) --> Sales order 1 --> 30% --> F2 30%
    --> F2 40%
    --> F2 30%.
    For creating the first billing document,we have to maintain the billing block for other two items.
    Regards,
    Krishna.

  • Service Contracts  with billing plan not updating debit memo request in ECC

    For service contracts with billing plan, we cancel the line items and set the user status at header to "cancelled" and also set the cancellation date (under Cancellation Tab) at the header as well as item level which delete all items in the “DMR” in ECC (which are not yet billed). When we do this, it works perfect for most of the time and in some cases DMR items are not updated in ECC and it is billing. When I checked in CRM, the billing plan items are updated based on the cancellation date.
    Experts appreciate your help on this issue.
    Thanks,
    George.

    This is resolved by the note 1008663

  • 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 Service Contracts per order instead of a billing plan

    Is it possible, with standard config, to disconnect the billing plan from a service contract and bill the service order itself with a fixed labor charge.
    Where the fixed labor charge amount comes from the contract.
    In other words, we want to bill service contract orders by billing a fixed labor charge on the orders instead of billing the fixed amount on a billing plan.
    We need to bill like this to make sure the service is complete prior to billing the contract.  Since the billing plan is independant of the service order being complete, we found that we were billing the billing plan when the service order never completed.  So we're looking for a way to sell a service contract that schedules service orders, but bills the labor as a fixed "contracted" amount on the service order.

    Hi Paul,
    I hope in service contract you have material which has the billing plan.
    Don't enter this material in service contract.Create the other material which helps to create the service order (i.e service order only created with reference to this material.)In service order you create the material for fixed price.
    I hope you know how to control the billing plan.
    Thanks,
    Senthil vadivelan.R

  • Billing Plan Start Date not copied to Sales order from Service Contract

    Hi
    We are developing a process of Creation of Service Contract and then a order confirmation.
    Now based on the Order Confirmation will bill based on the Bill Plan.
    The Bill plan start date in contract header is not flowing to Sales Order header while creating with reference.
    Then navigating to Header Billing plan and if we input the date the billing plan dates are displayed.
    We checked the copy control settings and seems like the date is not copied.Is this a standard behaviour.
    If so then do we have any work arounds to achieve the same. Because the contract start date can change before confirmation.
    So business wants a sales order confirmation to be created after contract creation and bill periodically as per the Sales order instead of contract.

    Hi,
    Appreciate ur quick response. But instead of FKDAT i need the FPLA-BEDAT to be flowed to Billing Plan.Right now iam entering the following date manually at header.Instead if it copies from Contract header then manual entry could be neglected.
    Is it possible with the same routine to code with the above mentioned FPLA-BEDAT.

  • Periodic Billing Plan in Contract

    Hi
    I am  trying to configure periodic billing plan in service contract scenario but when I assign it to Sales Doc. and item category, and create contract, the value in contract overview screen ( Net Document Value) does not match with Net header value . when I remove Billing plan then they match.Billing is to be done quarterly in this scenario.Please guide.

    Hi,
    for Contract end rule 10
    In T.Code: OVBZ
    maintain baseline date as 01= Todays date
    time period as 1
    time unit as 4= year.
    Alternately maintain  Contract Validity period as 1 year and check. It looks the contract end and validity are not uniform.
    Hope this will help.
    Regards,
    sharan

Maybe you are looking for