How to create Billing Plan in sales order using Function module /BAPI

hi,
How to create Billing Plan in sales order using Function module /BAPI
i hv check few FM such
BILLING_SCHEDULE_READ
BILLING_SCHEDULE_GET_NUMBER
BILLING_SCHEDULE_SAVE
But unable to create billing plan for a sales order.....any other method to create???

Hi,
Use this link.
Create sales order with billing plan via LSMW and BAPI BUS2032
BAPI or Function to update Billing Plan in Sales Order Items
Hope this will help you.
Regards,
Vijay

Similar Messages

How to Create RMA Based on Sales order using OE_ORDER_PUB api

Hi,
Can any one pls help me how to create a RMA based on the sales order using oe_order_pub.process_order APi.
Thanks.

Creating RMA is very similar to creating an Order. You need to make sure you're passing the correct order_type, line_type which'll be setup as 'RETURN' (or 'MIXED') category in transaction type definition.
For the API to automatically create a reference on your RMA lines to the original Order lines, you need to pass the following
l_line_tbl (l_line_tbl.COUNT).return_reason_code := 'RETURN'; -- Mandatory for RMA
l_line_tbl (l_line_tbl.COUNT).reference_line_id := v_ref_line_id; -- Original order line_id
l_line_tbl (l_line_tbl.COUNT).reference_header_id := v_ref_header_id; -- Original order header_id
l_line_tbl (l_line_tbl.COUNT).return_context := 'ORDER';
l_line_tbl (l_line_tbl.COUNT).return_attribute1 := v_ref_header_id; -- Original order header_id
l_line_tbl (l_line_tbl.COUNT).return_attribute2 := v_ref_line_id; -- Original order line_id
Once the RMA gets created, query the order and navigate to Lines>Returns tab. You can see the original order number and line number.
Thanks
Gopal

Configuration is not updating in sales order using function module SD_SALESDOCUMENT_CREATE

Hello Experts,
we are using SD_SALESDOCUMENT_CREATE function module to create sales order.
Sales order is creating successfully but the configuration for the items are not updating.
Could any one help me out on this ....we tried in different ways but couldn't ....
Here is the code....
*---Filling Configuration data
*--- Filling Configuration Reference Item / Instance
     w_sales_cfgs_refinst-posex     = w_items-itm_number.
     w_sales_cfgs_refinst-config_id = '000001'.
     w_sales_cfgs_refinst-inst_id   = '00000001'.
     APPEND w_sales_cfgs_refinst TO t_sales_cfgs_refinst.
     CLEAR w_sales_cfgs_refinst.
*---Filling Configuration Reference Data SALES_CFGS_REF Table
     w_sales_cfgs_ref-posex      = w_items-itm_number.
     w_sales_cfgs_ref-config_id = '000001'.
     w_sales_cfgs_ref-sce        = '1'.
     w_sales_cfgs_ref-root_id    = '00000001'.
     w_sales_cfgs_ref-complete   = 'T'.
     w_sales_cfgs_ref-consistent = 'T'.
     APPEND w_sales_cfgs_ref TO t_sales_cfgs_ref.
     CLEAR w_sales_cfgs_ref.
*---Filling Configuration Instances SALES_CFGS_INST Table
     w_sales_cfgs_inst-config_id       = '000001'.
     w_sales_cfgs_inst-inst_id         = '00000001'.
     w_sales_cfgs_inst-obj_type        = 'MARA'.
     w_sales_cfgs_inst-class_type      = '001'.
     w_sales_cfgs_inst-obj_key         = w_sales_items_in-material.
     w_sales_cfgs_inst-quantity        = w_items-target_qty.
     w_sales_cfgs_inst-quantity_unit   = 'EA'.
     w_sales_cfgs_inst-complete        = 'T'.
     w_sales_cfgs_inst-consistent      = 'T'.
     w_sales_cfgs_inst-OBJECT_GUID     = 'T'.
     w_sales_cfgs_inst-PERSIST_ID_TYPE = w_sales_items_in-material.
     APPEND w_sales_cfgs_inst TO t_sales_cfgs_inst.
     CLEAR w_sales_cfgs_inst.
*---Filling Configuration Characteristic Values SALES_CFGS_VALUE Table
     LOOP AT w_items-itm_config INTO wa_itm_config.
       w_sales_cfgs_value_in-config_id = '000001'.
       w_sales_cfgs_value_in-inst_id   = '00000001'.
       w_sales_cfgs_value_in-charc     = wa_itm_config-charc_name.
       w_sales_cfgs_value_in-value     = wa_itm_config-charc_value.
       APPEND w_sales_cfgs_value_in TO t_sales_cfgs_value.
*---Filling Configuration Variant Condition Key SALES_CFGS_VK
       w_sales_cfgs_vk-config_id = '000001'.
       w_sales_cfgs_vk-inst_id   = '00000001'.
       w_sales_cfgs_vk-vkey      = wa_itm_config-charc_name.
       APPEND w_sales_cfgs_vk TO t_sales_cfgs_vk.
       CLEAR : w_sales_cfgs_value_in,w_sales_cfgs_vk.
     ENDLOOP.
Regards,
Harsha P

Hello All,
Actually there was a bug in my code to update configuration for an item in sales order
Below is my Updated Code with that i can updated configuration successfully....
*---Filling Configuration data
*---Filling Configuration Reference Data SALES_CFGS_REF Table
     w_sales_cfgs_ref-posex      = w_items-itm_number.
     w_sales_cfgs_ref-config_id = '000001'.
     w_sales_cfgs_ref-sce        = '1'.
     w_sales_cfgs_ref-root_id    = '00000001'.
     w_sales_cfgs_ref-complete   = 'T'.
     w_sales_cfgs_ref-consistent = 'T'.
     APPEND w_sales_cfgs_ref TO t_sales_cfgs_ref.
     CLEAR w_sales_cfgs_ref.
*---Filling Configuration Instances SALES_CFGS_INST Table
     w_sales_cfgs_inst-config_id       = '000001'.
     w_sales_cfgs_inst-inst_id         = '00000001'.
     w_sales_cfgs_inst-obj_type        = 'MARA'.
     w_sales_cfgs_inst-class_type      = '300'.
     w_sales_cfgs_inst-obj_key         = w_sales_items_in-material.
     w_sales_cfgs_inst-quantity        = w_items-target_qty.
     w_sales_cfgs_inst-quantity_unit   = 'EA'.
     w_sales_cfgs_inst-complete        = 'T'.
     w_sales_cfgs_inst-consistent      = 'T'.
     w_sales_cfgs_inst-object_guid     = w_sales_items_in-material.
     w_sales_cfgs_inst-persist_id_type = 'G'.
     APPEND w_sales_cfgs_inst TO t_sales_cfgs_inst.
     CLEAR w_sales_cfgs_inst.
*---Filling Configuration Characteristic Values SALES_CFGS_VALUE Table
     LOOP AT w_items-itm_config INTO wa_itm_config.
       w_sales_cfgs_value_in-config_id = '000001'.
       w_sales_cfgs_value_in-inst_id   = '00000001'.
       w_sales_cfgs_value_in-charc     = wa_itm_config-charc_name.
       w_sales_cfgs_value_in-value     = wa_itm_config-charc_value.
       APPEND w_sales_cfgs_value_in TO t_sales_cfgs_value.
*---Filling Configuration Variant Condition Key SALES_CFGS_VK
       w_sales_cfgs_vk-config_id = '000001'.
       w_sales_cfgs_vk-inst_id   = '00000001'.
       w_sales_cfgs_vk-vkey      = wa_itm_config-charc_name.
       APPEND w_sales_cfgs_vk TO t_sales_cfgs_vk.
       CLEAR : w_sales_cfgs_value_in,w_sales_cfgs_vk.
     ENDLOOP.
     CLEAR : w_sales_items_in,wa_mara,w_items,w_sales_schedules_in,
             w_items-itm_number.
   ENDLOOP.
Cheers,
Harsha

Create Billing Document from Sales Order (Without Delivery)

Dear Experts,
Pls note, presently we are creating Billing Document (VF01) from Outbound Delivery Number after Post Good Issue. All sales Document like Billing Document, Output Type, Invoice Type has been configured for this process and we are doing this without any error. Fyki, we have configured lots of Z Order, Billing & Delivery type to do this processes.
But for one of this order type we need not do any delivery. We want to create Billing Documents from sales order directly (without doing any Outbound Delivery).
So, would u pls advise the steps how can we configure and assign Order Type, Billing Type or any other type to meet above requirement.
Thanks in advance.
Best Regards.
Ripon

Hi
There are two most important configuration:-
1) In VOV8 for your Order Type maintain the Order Related Billing Document
2) Maintain the Copy control setting in VTFA betwwen your Order Type and billing Type.
Also note that if your line item is not require to be delivered then for your Item category maintain (in VOV7) not relevant for delivery and not relevant for scedule line.
Regards
Amitesh Anand
Edited by: Amitesh Anand on May 24, 2010 5:09 PM

To add Billing Plan at Sales Order Header Level

Dear All,
Our requirement is such that for a project, we need to define a billing plan at header level of sales order.
As of now we are defining billing plan at sales order line item which are having accunt assignment to WBS elements.
Pl. let me know whether we can add billing plan at SO header level and if it is possible then how to do it. Because right now there is no tab available for "Billing Plan" at SO header level.
If we can add it then will it be valid for all item levels?
Need your help.
Regards
Ratna Palit

SPRO - SD - Billing - Billing Plan - the first 5 config nodes (Define Billing Plan types / Define Date descriptions / Assign Date categories / Maintain Date Proposals / Assign Billing Plan types to Sales Doc types) are applicable to you.
this is pretty tranparent for a reference.
What else is required?

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

Change in document type while creating billing document from sales order

While creating billing document from Sales order it is creating with document type RV which is standerd one but i want to change Document type.
How can i change it?
Regards
Raj

Hi
If you use another existing document type, check that it has a number range suitable to you. Else create a new 'z' type and assign an entirely new number range, not used in the other doc types.
It is useful to make the FI document number the same number. If I understand from the forums, the FI number range must be external. Search the forum for this. It is very useful for the Finance people.
Kind regards
Dawn
Edited by: Dawn Verrell on Sep 9, 2010 4:10 PM

How to Send Internal table to SAP Spool using Function Modules or Methods?

Hi Experts,
How to Send Internal table to SAP Spool using Function Modules or Methods?
Thanks ,
Kiran

This is my code.
I still get the no ABAP list data for the spool, even tho I can see it sp01?
REPORT Z_MAIL_PAYSLIP.
* Declaration Part *
tables: PERNR, PV000, T549Q, V_T514D, HRPY_RGDIR.
infotypes: 0000, 0001, 0105, 0655.
data: begin of ITAB occurs 0,
MTEXT(25) type C,
PERNR like PA0001-PERNR,
ABKRS like PA0001-ABKRS,
ENAME like PA0001-ENAME,
USRID_LONG like PA0105-USRID_LONG,
end of ITAB.
data: W_BEGDA like HRPY_RGDIR-FPBEG,
      W_ENDDA like HRPY_RGDIR-FPEND.
data: RETURN like BAPIRETURN1 occurs 0 with header line.
data: P_INFO like PC407,
      P_FORM like PC408 occurs 0 with header line.
data: P_IDX type I,
      MY_MONTH type T549Q-PABRP,
      STR_MY_MONTH(2) type C,
      MY_YEAR type T549Q-PABRJ,
      STR_MY_YEAR(4) type C,
      CRLF(2) type x value '0D0A'.
data: W_CMONTH(10) type C.
data: TAB_LINES type I,
      ATT_TYPE like SOODK-OBJTP.
data: begin of P_INDEX occurs 0,
        INDEX type I,
end of P_INDEX.
constants: begin of F__LTYPE, "type of line
   CMD like PC408-LTYPE value '/:', "command
   TXT like PC408-LTYPE value 's',   "textline
end of F__LTYPE.
constants: begin of F__CMD, "commands
NEWPAGE like PC408-LINDA value '',
end of F__CMD.
data: P_LIST like ABAPLIST occurs 1 with header line.
*data: OBJBIN like SOLISTI1 occurs 10 with header line,
data: OBJBIN like LVC_S_1022 occurs 10 with header line,
      DOCDATA like SODOCCHGI1,
      OBJTXT like SOLISTI1 occurs 10 with header line,
      OBJPACK like SOPCKLSTI1 occurs 1 with header line,
      RECLIST like SOMLRECI1 occurs 1 with header line,
      OBJHEAD like SOLISTI1 occurs 1 with header line,
      it_mess_att LIKE solisti1 OCCURS 0 WITH HEADER LINE,
      gd_buffer type string,
      l_no_of_bytes TYPE i,
      l_pdf_spoolid LIKE tsp01-rqident,
      l_jobname     LIKE tbtcjob-jobname.
data: file_length type int4,
      spool_id     type rspoid,
      line_cnt     type i.
*-------------------------------------------------------------------* * INITIALIZATION *
OBJBIN = ' | '.
append OBJBIN.
OBJPACK-HEAD_START = 1.
data: S_ABKRS like PV000-ABKRS.
data: S_PABRP like T549Q-PABRP.
data: S_PABRJ like T549Q-PABRJ.
* SELECTION SCREEN                                                  *
selection-screen begin of block BL1.
parameters: PAY_VAR like BAPI7004-PAYSLIP_VARIANT default 'ESS_PAYSLIPS' obligatory.
selection-screen end of block BL1.
START-OF-SELECTION.
s_ABKRS = PNPXABKR.
S_PABRP = PNPPABRP.
s_pabrj = PNPPABRJ.
w_begda = PN-BEGDA.
w_endda = PN-ENDDA.
get pernr.
*                                 "Check active employees
rp-provide-from-last p0000 space pn-begda pn-endda.
CHECK P0000-STAT2 IN PNPSTAT2.
*                                 "Check Payslip Mail flag
rp-provide-from-last p0655 space pn-begda pn-endda.
CHECK P0655-ESSONLY = 'X'.
rp-provide-from-last p0001 space pn-begda pn-endda.
*                                 "Find email address
RP-PROVIDE-FROM-LAST P0105 '0030' PN-BEGDA PN-ENDDA.
if p0105-usrid_LONG ne ''.
    ITAB-PERNR      = P0001-PERNR.
    ITAB-ABKRS      = P0001-ABKRS.
    ITAB-ENAME      = P0001-ENAME.
    ITAB-USRID_LONG = P0105-USRID_LONG.
    append itab.
    clear itab.
endif.
"SY-UCOMM ='ONLI'
END-OF-SELECTION.
*------------------------------------------------------------------* start-of-selection.
write : / 'Payroll Area        : ', S_ABKRS.
write : / 'Payroll Period/Year : ',STR_MY_MONTH,'-',STR_MY_YEAR. write : / 'System Date : ', SY-DATUM.
write : / 'System Time         : ', SY-UZEIT.
write : / 'User Name           : ', SY-UNAME.
write : / SY-ULINE.
sort ITAB by PERNR.
loop at ITAB.
    clear : P_INFO, P_FORM, P_INDEX, P_LIST, OBJBIN, DOCDATA, OBJTXT, OBJPACK, RECLIST, TAB_LINES.
    refresh : P_FORM, P_INDEX, P_LIST, OBJBIN, OBJTXT, OBJPACK, RECLIST.
*                                                  Retrieve Payroll results sequence number for this run
    select single * from HRPY_RGDIR where PERNR eq ITAB-PERNR
                                    and FPBEG ge W_BEGDA
                                    and FPEND le W_ENDDA
                                    and SRTZA eq 'A'.
*                                                  Produce payslip for those payroll results
    if SY-SUBRC = 0.
      call function 'GET_PAYSLIP'
        EXPORTING
          EMPLOYEE_NUMBER = ITAB-PERNR
          SEQUENCE_NUMBER = HRPY_RGDIR-SEQNR
          PAYSLIP_VARIANT = PAY_VAR
        IMPORTING
          RETURN          = RETURN
          P_INFO          = P_INFO
        TABLES
          P_FORM          = P_FORM.
      check RETURN is initial.
*                                                 remove linetype from generated payslip
      loop at p_form.
        objbin = p_form-linda.
        append objbin.
        line_cnt = line_cnt + 1.
      endloop.
      file_length = line_cnt * 1022.
*                                                 create spool file of paylsip
      CALL FUNCTION 'SLVC_TABLE_PS_TO_SPOOL'
        EXPORTING
          i_file_length = file_length
        IMPORTING
          e_spoolid     = spool_id
        TABLES
          it_textdata   = objbin.
      IF sy-subrc EQ 0.
        WRITE spool_id.
      ENDIF.
      DESCRIBE table objbin.
      DATA PDF LIKE TLINE OCCURS 100 WITH HEADER LINE.
      CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
        EXPORTING
          SRC_SPOOLID                    = spool_id
          NO_DIALOG                      = ' '
          DST_DEVICE                     = 'MAIL'
*      PDF_DESTINATION                =
*    IMPORTING
*      PDF_BYTECOUNT                  = l_no_of_bytes
*      PDF_SPOOLID                    = l_pdf_spoolid
*      LIST_PAGECOUNT                 =
*      BTC_JOBNAME                    =
*      BTC_JOBCOUNT                   =
        TABLES
          PDF                            = pdf
        EXCEPTIONS
          ERR_NO_ABAP_SPOOLJOB           = 1
          ERR_NO_SPOOLJOB                = 2
          ERR_NO_PERMISSION              = 3
          ERR_CONV_NOT_POSSIBLE          = 4
          ERR_BAD_DESTDEVICE             = 5
          USER_CANCELLED                 = 6
          ERR_SPOOLERROR                 = 7
          ERR_TEMSEERROR                 = 8
          ERR_BTCJOB_OPEN_FAILED         = 9
          ERR_BTCJOB_SUBMIT_FAILED       = 10
          ERR_BTCJOB_CLOSE_FAILED        = 11
          OTHERS                         = 12
      IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
*Download PDF file C Drive
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      filename = 'C:\itab_to_pdf.pdf'
      filetype = 'BIN'
    TABLES
      data_tab = pdf.
* Transfer the 132-long strings to 255-long strings
* LOOP AT pdf.
*    TRANSLATE pdf USING ' ~'.
*    CONCATENATE gd_buffer pdf INTO gd_buffer.
* ENDLOOP.
* TRANSLATE gd_buffer USING '~ '.
* DO.
*    it_mess_att = gd_buffer.
*    APPEND it_mess_att.
*    SHIFT gd_buffer LEFT BY 255 PLACES.
*    IF gd_buffer IS INITIAL.
*      EXIT.
*    ENDIF.
* ENDDO.
      OBJHEAD = 'Objhead'.
      append OBJHEAD.
* preparing email subject
      concatenate W_ENDDA(6)
                ' Payslip-'
                ITAB-ENAME+0(28)
                ITAB-PERNR+4(4) ')'
             into DOCDATA-OBJ_DESCR.
      DOCDATA-OBJ_NAME = 'Pay Slip'.
      DOCDATA-OBJ_LANGU = SY-LANGU.
      OBJTXT = 'Pay Slip.'.
      append OBJTXT.
*prepare email lines
      OBJTXT = DOCDATA-OBJ_DESCR.
      append OBJTXT.
      OBJTXT = 'Please find enclosed your current payslip.'.
      append OBJTXT.
* Write Attachment(Main)
* 3 has been fixed because OBJTXT has fix three lines
      read table OBJTXT index 3.
*    DOCDATA-DOC_SIZE = ( 3 - 1 ) * 255 + strlen( OBJTXT ).
      clear OBJPACK-TRANSF_BIN.
      OBJPACK-HEAD_START = 1.
      OBJPACK-HEAD_NUM = 0.
      OBJPACK-BODY_START = 1.
      OBJPACK-BODY_NUM = 3.
      OBJPACK-DOC_TYPE = 'RAW'.
      append OBJPACK.
* Create Message Attachment
      ATT_TYPE = 'PDF'.
      describe table OBJBIN lines TAB_LINES.
      read table OBJBIN index TAB_LINES.
*    OBJPACK-DOC_SIZE = ( TAB_LINES - 1 ) * 255 + strlen( OBJBIN ).
      OBJPACK-TRANSF_BIN = 'X'.
      OBJPACK-HEAD_START = 1.
      OBJPACK-HEAD_NUM = 0.
      OBJPACK-BODY_START = 1.
      OBJPACK-BODY_NUM = TAB_LINES.
      OBJPACK-DOC_TYPE = ATT_TYPE.
      OBJPACK-OBJ_NAME = 'ATTACHMENT'.
      OBJPACK-OBJ_DESCR = 'Payslip'.
      append OBJPACK.
* Create receiver list refresh RECLIST.
      clear RECLIST.
      RECLIST-RECEIVER = itab-USRID_long.
      translate RECLIST-RECEIVER to lower case.
      RECLIST-REC_TYPE = 'U'.
      append RECLIST.
* Send the document
*SO_NEW_DOCUMENT_ATT_SEND_API1
      call function 'SO_DOCUMENT_SEND_API1'
        exporting
          DOCUMENT_DATA = DOCDATA
          PUT_IN_OUTBOX = 'X'
          COMMIT_WORK = 'X'
* IMPORTING
*   SENT_TO_ALL =
*   NEW_OBJECT_ID =
        tables
          PACKING_LIST = OBJPACK
          OBJECT_HEADER = OBJHEAD
          CONTENTS_BIN = pdf
          CONTENTS_TXT = OBJTXT
*   CONTENTS_HEX =
*   OBJECT_PARA =
*   OBJECT_PARB =
          RECEIVERS = RECLIST
        exceptions
          TOO_MANY_RECEIVERS = 1
          DOCUMENT_NOT_SENT = 2
          DOCUMENT_TYPE_NOT_EXIST = 3
          OPERATION_NO_AUTHORIZATION = 4
          PARAMETER_ERROR = 5
          X_ERROR = 6
          ENQUEUE_ERROR = 7
          others = 8.
      if SY-SUBRC NE 0.
        ITAB-MTEXT = 'Message Not Sent to : '.
      else.
        ITAB-MTEXT = 'Message Sent to : '.
      endif.
*    else.
*      ITAB-MTEXT = 'Message Not Sent to : '.
*    endif.
    else.
      "SY-SUBRC Not = 0
      ITAB-MTEXT = 'Payroll data not found : '.
    endif.
    "end of SY-SUBRC = 0.
    modify ITAB.
endloop. "end loop at ITAB
sort ITAB by MTEXT PERNR.
loop at ITAB.
    at new MTEXT.
      uline.
      write : / ITAB-MTEXT color 4 intensified on.
      write : / 'Emp. Code' color 2 intensified on,
             12 'Emp. Name' color 2 intensified on,
             54 'Email ID' color 2 intensified on.
    endat.
    write : / ITAB-PERNR, 12 ITAB-ENAME, 54 ITAB-USRID_LONG.
endloop.

Bill Plan with Sales Order item rejected

Milestone Billing Plan created.
IMG Config Sales Order Item Reason for Rejection = BIC checked (Not Relevant for Billing)
Add material on the (Billing Plan) Sales Order Item.
Set the Item Reason For rejection (same reason as set in IMG config for BIC above)
Create some Billing Plan dates (at the sales order header).
[F3] back. You get an info message "Value-based differences in the billing plan cannot be allocated"
Save the Order.. All is fine.
If I do not set a reason for rejection on the item all is fine.
Can anyone explain this ?

Hi Friends
I have resolved the problem myself. I have used sap note : 97272 and downloaded the utility/ correction program ZZUNREJE and ran it for rejected sales line item.
The reason for rejection was successfully reversed without touching any of the associated POs.
Regards

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.

Can the project status be influenced by billing plan in sales order?

I am facing the following problem:
I linked the WBS Element to a sales order billing plan (in header: account assignment).
Now, is there a possibility to prevent changing the status of the project to close technically, while there are still some invoices of the billing in the sales order not billed?
I want to make sure that a project can only be closed once all the invoices related to the project were billed.
Thanks in advance
Maike

Hello Maike,
I have different view here:
System status is set to FNBL automatically when all the items in the sales orders are billed. So user does not really need to set it.
TECO is a status which should follow FNBL generally speaking. And it has to be put manually.
Now, if the requirement is to throw an error when FNBL or TECO is put manually if not all the sales orders items are billed- it can be done by using validation.
A validation can be activated which will check for any open billing item for that WBS when status is set to TECO. If there is any, it will throw an error while saving WBS with TECO.So it will not allow to set TECO. T code for validation is OPSI.
Thanks,
Sourabh

How to create PR automatically by sales order?

Dear experts,
I want to create PR automatically with sales order, and then create delivery from this sales order, and goods issue. I know third party order, however it can't create delivery.
thanks
Lance

Hi,
Go to VOV7 T code,
You will find one check box Create PO automatic. Check that.
It will create automatically PO.
Hope this will help.
Reward Point if helpful.
Thanks,
Raja

How to ChangePlantfor each item of Sales order using User Exit SAVE_DOCUMEN

Hi All,
I have to change plant for Each line item of sales order using (MV45AFZZ) (USEREXIT_SAVE_DOCUMENT) based on first Schedule line.
if Confirmed Quantity is Less than Ordered Quantity.
based on first Schedule line.
it has to select other Plant and need to populate it in line item of sales order.Please see the below code and let me knoe if any changes required... Thanks in Advance.
data : wa_vbep like xvbep,
       Lv_matnr type mara-matnr,
       lv_werks type marc-werks.
DATA: it_vbap TYPE STANDARD TABLE OF vbap,
      wa_vbap TYPE vbap.
field-symbols: <wa_vbap> type VBAPVB.
clear wa_vbap.
*loop at xvbap into wa_vbap.
loop at xvbap assigning <wa_vbap>.
read table xvbep into wa_vbep with key posnr = <wa_vbap>-posnr.
if wa_vbep-ETENR = '0001'.
if sy-subrc = 0.
IF wa_VBEP-BMENG LT wa_VBEP-WMENG.
    SELECT SINGLE DWERK
                 INTO lv_werks
                 FROM MVKE WHERE matnr = <wa_VBAP>-matnr
                            and DWERK ne <wa_VBAP>-werks.
if not Lv_werks is initial.
if lv_werks EQ 1033.
move '1002' to <wa_vbap>-werks.
if sy-subrc eq 0.
xvbap-werks = <wa_vbap>-werks.
modify xvbap from <wa_vbap> .
endif.
elseif lv_werks EQ 1003.
move '1003' to <wa_vbap>-werks.
elseif lv_werks EQ 1010.
move '1010' to <wa_vbap>-werks.
endif.
endif.
endif.
endif.
endif.
endloop.
endif.
Regards,
Sudhakar Reddy.A

You have to use the form routine "USEREXIT_SAVE_DOCUMENT_PREPARE"
regards
Vinod

WES element is disable with billing plan in sales order?

Hi experts,
I have problem, when I create a sales order with item category billing plan, then the WBS element in this line become disable,so I can't input the WBS, How can I solve this issue?
Thanks
Best regards
Lance

done

Maintaining Billing Plan in Sales Order

Hello Expert
Where can i restrict that all billing plan mantain in Sales Order-> item level-> billing plan should not exceed the Sales Order Amount?
Our process is only create SO, maintain billing plan and create billing document.
We are not using Delivery, PGI etc.
Thanks

I am only maintaining the following field in the line item-> billing plan
Billing Date,DCategory,Bill Value, Currency
My question is how to control that the amount maintain in the billing value will not be more than the Selling Amount (SO->Line item->Amount)
At the moment, the user can bill up to 1M even the sales order amount is only 100K

How to create Billing Plan in sales order using Function module /BAPI

Similar Messages

Maybe you are looking for