Regarding Billing for STPO Order

Dear All,
We are creating Stock transport purchase orders using outbound deliveries is there any transaction code which will tell me that i need to create invoice for the outbound deliveries created  for stock transport purchase orders.
In other words if i have completed my delivery document any tcode in SAP after giving inputs will let me know that I have to complete billing for these documents.
Regards
Atul
Edited by: Atul Keshav on Jun 20, 2008 9:53 AM

hi
for intera company STO :
Create the STO using T-Code:ME21n and Save.
Create Delivery :VL10G
Click on the Background Button after selecting line item
A message is flashed : See log for information> next Click on Log for delivery creation Button >click on line item>click on document button to get Delivery document No
Picking, PGI:[VL02n
Billing:VF01n
Save the document and its done
for inter company STO:
Create STO in ME21N with Doc.type: UB at Receiving Plant.
Then Create Delivery in VL10B from Supplying Plant...
Then Do PGI in VL02N from supplying Plant.
Then do GR at Receiving Plant based on Outbound Delivery at Receiving Plant...
regards
ravikant dewangan

Similar Messages

  • Regarding Billing for STPO Orders

    Dear All,
    We are creating Stock transport purchase orders using outbound deliveries is there any transaction code which will tell me that i need to create invoice for the outbound deliveries created for stock transport purchase orders.
    In other words if i have completed my delivery document, any tcode in SAP after giving inputs will let me know that I have to complete billing for these documents.
    Regards
    Atul

    Hi
    You can enter the details like
    Sold-To Party - The customer numebr of the Receiving Plant.
    Destination country
    Shipping point
    Select the Intercompany billing check box also.
    Thsi will get you the list for the Outbound deliveries
    Thanks & Regards
    Kishore

  • Quotation Creation and Billing for Service Orders--node details needed

    Hi ,
    I need to work on node "Quotation Creation and Billing for Service Orders" ....I see lot of integration with SD and FICO . Can any one give details about integrations required and what is done in this node ....
    Regards
    NPB

    There are different steps to be done for that.
    1. Create DIP Profile in ODP1 & check the consistency in ODP2 - DIP will be used to bill the customer based on resource (labor & material) usage. Creation of DIP profile has been discussed many times in this forum. Please check.
    2. Assign the Quotation document type & Billing type used in DIP profile to your sales area - Your document type should be assigned to your sales organisation, distribution channel & division combination.

  • How  to  generate  Billing   for   Service Order   ?

    how  to  generate  Billing   for   Service Order   ?

    Hello,
    You may do a resource related billing from the service order,  but you need to maintain Resource Related billing profile in Service order --> Control tab. Once it is set you may generate the billing document (debit memo) from service order through DP90, provided the config is right.
    Prase

  • Delivery related billing for repair order

    Hi sdn,
    Could you please explain how to do the delivery related billing for repair orders.
    Earlier we my client was using order related billing for repair orders. Instead of that he wants delivery related billling.
    We have done all configuratin settings
    While doing the delivery the system is going to termination.
    In earlier process IRPA IRRP IRRE IRAL item categories are determining in the repair order.
    IRPA is relavent for price and billing
    IRRE and IRRP relavant for returns delivery
    IRAL item category relavant for delivery and not relavan for pricing
    We changed the config settings for IRPA item category .we changed the IRPA item category relavan for delivery
    When enter the VL01n the syetem is terminating program.
    Due to this include L1PWF46 system going to terminate
    Please advice how i will change the process into delivery related billing instead of order related billing.
    Thanks
    KV

    I have done all configuration settings which were related to delivery related billing but still the program was terminated.This process related repair and service.
    please suggest needful answer.
    Thanks
    KV

  • Billing for service orders

    I need to be able to bill for some of the service orders as a requirement of my client.
    Has anyone done the config in SD for this before?
    If I do not want to use SD is there another option to use?
    Any help would be great and will award points.
    Thanks,
    AD

    Hi AD
    There are two options provided by SAP for billing custmer service
    1. One way I earlier explained is by creating Sales Order .In this u can create service order automatically & Bill the Custmer
    2. Second way is to use DP90 in which u have to create a billing request which can be used for RRB(Resource Related Billing) using DIP profile
    So in summary it can be processes with Sales /Service Order as per your need
    For more help , refer [here |http://help.sap.com/erp2005_ehp_03/helpdata/EN/99/0fad3cf7ca0855e10000000a114084/frameset.htm]
    Regards
    Jignesh

  • Regarding bapis for sales order creation and modification

    Hi,
    I am trying to create a syncbo for sales order creation, modification and display. The bapis that I am using are
    1.BAPI_SALESORDER_GETLIST
    2.BAPISDORDER_GETDETAILEDLIST
    3.BAPI_SALESORDER_CREATEFROMDATA1
    4. BAPI_SALESORDER_CHANGE
    Am I using the correct bapis. When I tried to create a syncbo it gave the following errors
    BAPISDORDER_GETDETAILEDLIST does not have RETURN parameter in export or tables parameter
    RETURN parameter in Create BAPI Wrapper should refer to structure BAPIRET2
    RETURN parameter in GetList BAPI Wrapper should refer to structure BAPIRET2
    GetDetail BAPI Wrapper does not have RETURN parameter in export or tables parameter
    No Export parameter referring to header structure exists in GetDetail BAPI Wrapper
    No Import parameter referring to header structure exists in Create BAPI Wrapper
    No Import parameter referring to header structure exists in Modify BAPI Wrapper
    No Import parameter referring to a field of header structure exists in GetDetail BAPI Wrapper
    No Export parameter referring to a field of header structure exists in Create BAPI Wrapper
    No Tables parameter referring to item structure exists in Create BAPI Wrapper
    No Tables parameter referring to item structure exists in Modify BAPI Wrapper
    I am informed that the above bapis are standard bapis.
    I am not sure as to why I am getting the errors.
    Does the syncbo require the  bapi's to be in a specific format.
    What would be the header and item structures for sales order bapis
    Regards
    Raja Sekhar

    Hi Raja,
      ya , for creating Sync BOs ,our BAPI wrappers must satisfy certain conditions..
    just go through this link.
    u can use the standard BAPIs of SALES Order in ur Custom BAPI Wrapper
      http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/what_is_a_bapi_wrapper.html
    the RETURN must be of type BAPIRET2..
                    Regards
                    Kishor Gopinathan

  • Table for parked and posted vendor bills for purchase order.

    Gurus
    In which table purchase order histroy data is stored? Is there any standard report for viewing following
    po no,PO date,line item no.,material code,ordered quantity,GRN date,GRN qty,GRN amount,parked qty,parked amount,posted qty, posted amount.
    Atul Kulkarni.

    Hi,
    PO history could be seen from table EKBe.
    Rest of the details can be seen in EKKO (header table for purchasing document) and EKKO (line item for purchasing doc).
    Regards,
    Ashwini.

  • Regarding fields for Purchase order

    can any body help what are the fields reqiured to develop a p.o report to display the change date,user name,time,p.o name and vendor code.

    Hi
    see the sample report for the fieldnames and other logic
    all the PO info is there here.
    *& Report  ZMM_PO_REPORT
    REPORT  ZMM_PO_REPORT message-Id yb
           NO STANDARD PAGE HEADING
           LINE-COUNT 60(1)
           LINE-SIZE 230.
           D A T A B A S E  T A B L E S   D E C L A R A T I O N
    TABLES: lfa1,           " Vendor Master
            t161,           " PO Doc Types
            t024,           " Purchase Groups
            ekko.           " PO Header
                   T Y P E S  D E C L A R A T I O N S
    Purchase Orders Main Structure
    TYPES: BEGIN OF s_po,
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            bstyp TYPE bstyp,           " PO Category
            bukrs TYPE bukrs,           " Company Code
            bsart TYPE bbsrt,           " PO Type
            lifnr TYPE lifnr,           " Vendor No
            ekgrp TYPE bkgrp,           " Purchase Group
            waers TYPE waers,           " Currency
            bedat TYPE etbdt,           " PO Date
            txz01 TYPE txz01,           " Material Text
            werks TYPE ewerk,           " Plant
            lgort TYPE lgort_d,         " Storage Location
            matkl TYPE matkl,           " Material Group
            menge TYPE bamng,           " PR Quantity
            meins TYPE bamei,           " UOM
            bprme TYPE bbprm,           " Price Unit
            netpr TYPE netpr,           " Net price
            peinh TYPE peinh,           " Price Unit UOM
            pstyp TYPE pstyp,           " Item Category
            knttp TYPE knttp,           " Account Assignment Category
           END OF s_po.
    Purchase Orders History Structure
    TYPES: BEGIN OF s_account,
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            gjahr TYPE mjahr,           " Fiscal Year
            belnr TYPE mblnr,           " PO Invoice No
            menge TYPE menge_d,         " PR Quantity
            wrbtr TYPE wrbtr,           " Price in Local Currency
            dmbtr TYPE dmbtr,           " Price in Foreign Currency
            waers TYPE waers,           " Currency
            shkzg TYPE shkzg,           " Dr/Cr Indicator
           END OF s_account.
    Purchase Orders History Structure(Item Sum)
    TYPES: BEGIN OF s_inv_sum,
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            menge TYPE menge_d,         " PR Quantity
            wrbtr TYPE wrbtr,           " Price in Foreign Currency
            waers TYPE waers,           " Currency
           END OF s_inv_sum.
    Purchase Orders Main Structure
    TYPES: BEGIN OF s_rep,
            lifnr TYPE lifnr,           " Vendor No
            ebeln TYPE ebeln,           " PO No.
            ebelp TYPE ebelp,           " PO Item
            bstyp TYPE bstyp,           " PO Category
            bsart TYPE bbsrt,           " PO Type
            ekgrp TYPE bkgrp,           " Purchase Group
            waers TYPE waers,           " Currency
            bedat TYPE etbdt,           " PO Date
            txz01 TYPE txz01,           " Material Text
            werks TYPE ewerk,           " Plant
            lgort TYPE lgort_d,         " Storage Location
            matkl TYPE matkl,           " Material Group
            menge TYPE bamng,           " PR Quantity
            meins TYPE bamei,           " UOM
            bprme TYPE bbprm,           " Price Unit
            netpr TYPE netpr,           " Net price
            peinh TYPE peinh,           " Price Unit UOM
            pstyp TYPE pstyp,           " Item Category
            knttp TYPE knttp,           " Account Assignment Category
            name1 TYPE name1,           " Plant
            orewr TYPE netpr,           " To be Invoiced Price
            curr  TYPE waers,           " Inv Doc Currency
           END OF s_rep.
               D A T A  D E C L A R A T I O N S
    DATA: gv_title1 TYPE sylisel,            " Report title
          gv_dial.                           " Color flag
                C O N S T A N T S  D E C L A R A T I O N S
    CONSTANTS: c_x                VALUE 'X',   " Flag X
               c_h                VALUE 'H',   " Debit
               c_vgabe TYPE vgabe VALUE '2'.   " Transaction Type
         I N T E R N A L  T A B L E S  D E C L A R A T I O N S
    DATA: i_po    TYPE STANDARD TABLE OF s_po WITH HEADER LINE,
                                 " Purchase Order
          i_inv   TYPE STANDARD TABLE OF s_inv_sum WITH HEADER LINE,
                                         " PO Invoice Values
          i_rep   TYPE STANDARD TABLE OF s_rep WITH HEADER LINE,
                                     " PO Invoice Values
          i_ekbe  TYPE STANDARD TABLE OF s_account WITH HEADER LINE.
                               " PO Invoice Values
                     S E L E C T I O N  S C R E E N                      *
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    SELECT-OPTIONS: s_lifnr FOR lfa1-lifnr MATCHCODE OBJECT kred,
                    s_ebeln FOR ekko-ebeln MATCHCODE OBJECT mekk,
                    s_bsart FOR t161-bsart,
                    s_ekgrp FOR t024-ekgrp,
                    s_bedat FOR ekko-bedat.
    SELECTION-SCREEN END OF BLOCK b1.
                      I N I T I A L I Z A T I O N                        *
    INITIALIZATION.
                  A T  S E L E C T I O N - S C R E E N                   *
    AT SELECTION-SCREEN.
    Validate the screen fields
      PERFORM validate_screen.
                   S T A R T - O F - S E L E C T I O N                   *
    START-OF-SELECTION.
    Fetch main data
      PERFORM fetch_data.
                   T O P - O F - P A G E                                 *
    TOP-OF-PAGE.
    Header of the List
      PERFORM header.
                   E N D - O F - P A G E                                 *
    Footer
    END-OF-PAGE.
      ULINE.
                   E N D - O F - S E L E C T I O N                       *
    END-OF-SELECTION.
    Display the Report Output data
      PERFORM display_data.
    At Line-Selection
    AT LINE-SELECTION.
    When double clicked on EBELN display the details of Purchase Doc
      PERFORM line_sel.
    *&      Form  validate_screen
    Validation of Selection Screen fields
    FORM validate_screen .
    Validation of Vendor Number
      CLEAR lfa1-lifnr.
      IF NOT s_lifnr[] IS INITIAL.
        SELECT lifnr UP TO 1 ROWS
            INTO lfa1-lifnr
            FROM lfa1
            WHERE lifnr IN s_lifnr.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Vendor'(002).
        ENDIF.
      ENDIF.
    Validation of PO Number
      CLEAR ekko-ebeln.
      IF NOT s_ebeln[] IS INITIAL.
        SELECT ebeln UP TO 1 ROWS
            INTO ekko-ebeln
            FROM ekko
            WHERE ebeln IN s_ebeln.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Document Number'(003).
        ENDIF.
      ENDIF.
    Validation of PO Document Type
      CLEAR t161-bsart.
      IF NOT s_bsart[] IS INITIAL.
        SELECT bsart UP TO 1 ROWS
            INTO t161-bsart
            FROM t161
            WHERE bsart IN s_bsart.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Purchase Document Type'(004).
        ENDIF.
      ENDIF.
    Validation of Purchasing Group
      CLEAR t024-ekgrp.
      IF NOT s_ekgrp[] IS INITIAL.
        SELECT ekgrp UP TO 1 ROWS
            INTO t024-ekgrp
            FROM t024
            WHERE ekgrp IN s_ekgrp.
        ENDSELECT.
        IF sy-subrc <> 0.
          MESSAGE e000 WITH 'Invalid Purchasing Group'(005).
        ENDIF.
      ENDIF.
    ENDFORM.                    " validate_screen
    *&      Form  fetch_data
    Fetching the PO related data from Database Tables
    FORM fetch_data .
      CLEAR i_po.
      REFRESH i_po.
      SELECT a~ebeln            " PO No.
             b~ebelp            " PO Item
             a~bstyp            " PO Category
             a~bukrs            " Company Code
             a~bsart            " PO Type
             a~lifnr            " Vendor No
             a~ekgrp            " Purchase Group
             a~waers            " Currency
             a~bedat            " PO Date
             b~txz01            " Material Text
             b~werks            " Plant
             b~lgort            " Storage Location
             b~matkl            " Material Group
             b~menge            " PR Quantity
             b~meins            " UOM
             b~bprme            " Price Unit
             b~netpr            " Net price
             b~peinh            " Price Unit UOM
             b~pstyp            " Item Category
             b~knttp            " Account Assignment Category
        INTO TABLE i_po
        FROM ekko AS a JOIN ekpo AS b
        ON a~ebeln = b~ebeln
        WHERE a~ebeln IN s_ebeln AND
              a~lifnr IN s_lifnr AND
              a~ekgrp IN s_ekgrp AND
              a~bsart IN s_bsart AND
              a~bedat IN s_bedat.
      SORT i_po BY ebeln ebelp.
      break-point.
      IF NOT i_po[] IS INITIAL.
    Fetch the PO History/Invoice Details from EKBE Table
        CLEAR i_ekbe.
        REFRESH i_ekbe.
        SELECT ebeln           " PO No.
               ebelp           " PO Item
               gjahr           " Fiscal Year
               belnr           " PO Invoice No
               menge           " PR Quantity
               wrbtr           " Price in Local Currency
               dmbtr           " Price in Foreign Currency
               waers           " Currency
               shkzg           " Dr/Cr Indicator
         INTO TABLE i_ekbe
         FROM ekbe
         FOR ALL ENTRIES IN i_po
         WHERE ebeln = i_po-ebeln AND
               ebelp = i_po-ebelp AND
               vgabe = c_vgabe.
        IF sy-subrc = 0.
          SORT i_ekbe BY ebeln ebelp.
          LOOP AT i_ekbe.
            IF i_ekbe-shkzg = c_h.
              i_ekbe-wrbtr = i_ekbe-wrbtr * -1.
            ENDIF.
            MODIFY i_ekbe.
          ENDLOOP.
      break-point.
    Sum up the Item wise Invoice totals
          LOOP AT i_ekbe.
            AT END OF ebelp.
              READ TABLE i_ekbe INDEX sy-tabix.
              SUM.
              MOVE-CORRESPONDING i_ekbe TO i_inv.
              APPEND i_inv.
            ENDAT.
            CLEAR i_inv.
          ENDLOOP.
          SORT i_inv BY ebeln ebelp.
            break-point.
        ENDIF.
      ENDIF.
    Move the Vendor Name and Invoice Values to I_rep Internal Table
      LOOP AT i_po.
        MOVE-CORRESPONDING i_po TO i_rep.
        CLEAR i_inv.
        READ TABLE i_inv WITH KEY ebeln = i_po-ebeln
                                  ebelp = i_po-ebelp.
        IF sy-subrc = 0.
          i_rep-orewr = ( i_po-menge - i_inv-menge ) * i_po-netpr.
          i_rep-curr  = i_inv-waers.
        ELSE.
          i_rep-orewr = i_po-menge * i_po-netpr.
          i_rep-curr  = i_po-waers.
        ENDIF.
      break-point.
    Get the Vendor Name
        CLEAR lfa1-name1.
        SELECT SINGLE name1 FROM lfa1 INTO lfa1-name1
          WHERE lifnr = i_po-lifnr.
        IF sy-subrc = 0.
          i_rep-name1  = lfa1-name1.
        ENDIF.
        APPEND i_rep.
        CLEAR  i_rep.
          break-point.
      ENDLOOP.
      SORT i_rep BY lifnr ebeln ebelp.
      DELETE i_rep WHERE orewr LE 0.
      break-point.
    ENDFORM.                    " fetch_data
    *&      Form  display_data
    Display the Report Output data
    FORM display_data .
      DATA: lv_flag,               " New Flag
            lv_rec TYPE i.         " No of Records
      CLEAR lv_rec.
      IF i_rep[] IS INITIAL.
        MESSAGE e000 WITH 'No Data found'(022).
      ELSE.
        LOOP AT i_rep.
    Toggle Color
          PERFORM toggle_color.
          IF lv_flag <> space.
            NEW-LINE.
          ENDIF.
    At New Purchase Document
          AT NEW ebeln.
            WRITE:/1 sy-vline, 2(10) i_rep-ebeln INTENSIFIED OFF.
            lv_flag = c_x.
            lv_rec = lv_rec + 1.
          ENDAT.
          WRITE: 1 sy-vline,
                12 sy-vline,13(4)   i_rep-bsart,
                17 sy-vline,18(10)  i_rep-lifnr,
                28 sy-vline,29(35)  i_rep-name1,
                64 sy-vline,65(4)   i_rep-ekgrp,
                69 sy-vline,70(10)  i_rep-bedat,
                80 sy-vline,81(5)   i_rep-ebelp,
                86 sy-vline,87(40)  i_rep-txz01,
               127 sy-vline,128(9)  i_rep-matkl,
               137 sy-vline,138(1)  i_rep-pstyp,
               139 sy-vline,140(1)  i_rep-knttp,
               141 sy-vline,142(4)  i_rep-werks,
               146 sy-vline,147(4)  i_rep-lgort,
               151 sy-vline,152(13) i_rep-menge UNIT i_rep-meins,
               165 sy-vline,166(3)  i_rep-meins,
               169 sy-vline,170(15) i_rep-netpr CURRENCY i_rep-waers,
               185 sy-vline,186(4)  i_rep-waers,
               190 sy-vline,191(5)  i_rep-peinh,
               196 sy-vline,197(4)  i_rep-bprme,
               201 sy-vline,202(15) i_rep-orewr CURRENCY i_rep-curr,
               217 sy-vline,218(4)  i_rep-curr,
               222 sy-vline,223(7)  i_rep-bstyp centered,
               230 sy-vline.
          NEW-LINE.
          hide: i_rep-ebeln.
        ENDLOOP.
        ULINE.
        FORMAT COLOR OFF.
        WRITE : /2 'Total Number of Purchasing Documents:'(025) COLOR 3,
                    lv_rec COLOR 3.
      ENDIF.
    ENDFORM.                    " display_data
    *&      Form  header
    Write the Report Header
    FORM header .
      FORMAT RESET.
    header
      WRITE:/1(230) 'LIST OF PURCHASE DOCUMENTS PER VENDOR'(006) CENTERED.
      SKIP.
      FORMAT COLOR COL_HEADING.
      ULINE.
      WRITE:/1 sy-vline,2(10)   'Pur.Doc.No'(006) CENTERED,
            12 sy-vline,13(4)   'Type'(007),
            17 sy-vline,18(10)  'Vendor'(008) CENTERED,
            28 sy-vline,29(35)  'Name'(009) CENTERED,
            64 sy-vline,65(4)   'PGrp'(010) CENTERED,
            69 sy-vline,70(10)  'Doc.Date'(012) CENTERED,
            80 sy-vline,81(5)   'Item'(011),
            86 sy-vline,87(40)  'Material Short Text'(024) CENTERED,
           127 sy-vline,128(9)  'Mat.Group'(013),
           137 sy-vline,138(1)  'I',
           139 sy-vline,140(1)  'A',
           141 sy-vline,142(4)  'Plnt'(014),
           146 sy-vline,147(4)  'SLoc'(015),
           151 sy-vline,152(13) 'Quantity'(016) CENTERED,
           165 sy-vline,166(3)  'UoM'(017),
           169 sy-vline,170(15) 'Net Value'(018) CENTERED,
           185 sy-vline,186(4)  'Curr'(019),
           190 sy-vline,191(5)  'Per'(020),
           196 sy-vline,197(4)  'Unit'(021),
           201 sy-vline,202(15) 'To be Invoiced'(023) CENTERED,
           217 sy-vline,218(4)  'Curr'(019),
           222 sy-vline,223(7)  'Doc.Cat'(026),
           230 sy-vline.
      ULINE.
    ENDFORM.                    " header
    *&      Form  toggle_color
    This routine alters the color of the records in the list
    FORM toggle_color.
      IF gv_dial = space.
        FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
        gv_dial = c_x.
      ELSE.
        FORMAT COLOR 1 INTENSIFIED OFF.
        CLEAR gv_dial.
      ENDIF.
    ENDFORM.                    " toggle_color
    *&      Form  LINE_SEL
    *When double clicked on EBELN field display the details of Purchase Doc
    FORM line_sel.
      CASE sy-lsind.
        WHEN '1'.
          DATA: lv_field(20),
                lv_value(10),
                lv_bstyp like i_rep-bstyp.
          clear: lv_bstyp,lv_value, lv_field.
          GET CURSOR FIELD lv_field VALUE lv_value.
          IF lv_field = 'I_REP-EBELN'.
            IF NOT lv_value IS INITIAL.
              READ LINE sy-index FIELD VALUE i_rep-bstyp
                                       INTO  lv_bstyp.
             READ CURRENT LINE FIELD VALUE i_rep-bstyp INTO lv_bstyp.
              if lv_bstyp = 'F'.
                SET PARAMETER ID 'BES' FIELD lv_value.
                CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
              elseif ( lv_bstyp = 'K' or lv_bstyp = 'L' ).
                SET PARAMETER ID 'VRT' FIELD lv_value.
                CALL TRANSACTION 'ME33' AND SKIP FIRST SCREEN.
              elseif lv_bstyp = 'A'.
                SET PARAMETER ID 'ANF' FIELD lv_value.
                CALL TRANSACTION 'ME43' AND SKIP FIRST SCREEN.
              endif.
            ENDIF.
          ENDIF.
      ENDCASE.
    ENDFORM.                    " line_sel
    Regards
    Anji

  • BAPI for resource related billing for service order

    Hi,
    I want to generate billing based on cost spent on service in transaction DP90.
    i searched and tried the BAPI DIPCOL_COLLECTIVE_RRB. But this one is for collective processsing i.e DP96.
    Is there any BAPI or FM which is for DP90 which i can use in my program.
    Thanks
    Sree

    Hi all,
    Solved myself.
    Use call txn to generate sales order. I gave  input as service order and saved, it will generate sales order which is collected via set / get parameter. eg: set parameter id 'AUN' field fl_sales_order.
    Then used 'BAPISDORDER_GETDETAILEDLIST' to get sales order details and 'BAPI_SALESORDER_CHANGE' and finally 'BAPI_TRANSACTION_COMMIT'.

  • Regarding Priority for Sales Order

    HI Gurus
    In a Make to Order scenario based on sales order say the customer wants it immediatly to go into production 
    It  needs to set priority for that corresponding production order how to do that
    Thanks in advance
    Rajesh

    HI  Thanks for the Info
    I have checked in the production order priority in help they have given that priority from sales order will be fetched in case of assembly order
    i am using strategy group 70 in material master
    but i am not getting
    how to do that
    Thanks in advance
    Rajesh

  • URGENT: REGARDING TABLE FOR SALES ORDER STOCK

    Hi,
    I making a report in which i have to display the material's minimum ,maximum and reorder point levels and its stock level too.
    but 1 problem i am facing is that if the stock is present in the sales order theni have to use the MSKA table but it contains different fields such as :-
    1.) Unrestricted stock
    2.) Block Stock
    3.) Quality stock
    I want to know that table which stoers the sum of all the values given above.
    plzz help me out how to solve this problem.it is really urgent to me as i have to complete the report right now.

    Hello,
    I think you have to sum up all the values (You can request the requirement from functionals) also you can always cross check with transaction MB52.

  • Milestone Billing  for third party order process

    hai Gurus
                 Pls help me in understanding of milestone billing with example.
                 Is it possible to link the milestone billing for Thirdparty order process?
                 pls send me documents to my Id [email protected]
    I will reward points for the helpfull answers
    Regards
    SaravananS
    Message was edited by:
            Saravanan Sevuga perumal

    Hello Saravanan,
    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
    <b>**REWARD IF THIS HELPS**</b>
    Regards
    AK

  • User exit for Production Order status

    Hi all ,
    Pl tell me about the : user exit for Production Order status
    ( i want CLSD status after settlement of the Production order .)
    regards,

    Hi,
    for production order you have exits PPCO0001 - PPCO0023. In transaction SMOD you can see the documentation for all this exits. Actually I think exit PPCO0007 could be a possiblity for you. This exit is called by saving the order.
    But maybe it would be better for you to use a special status profile? A user status is set if settlement status is set.
    Also BADI WORKORDER_UPDATE could be interessting for you.
    Regards,
    Sabine

  • User exit for production order settlement

    Hi Experts,
    Can anybody tell me if there is any user exit which will make GR and settlement of Production Orders at the same time i. e. as soon as production order is confirmed ( movement type 101 happens) the same production order will be settlelled immediately.............
    Thanks on advance for your answer.
    Regards,
    Bijay

    Hi,
    for production order you have exits PPCO0001 - PPCO0023. In transaction SMOD you can see the documentation for all this exits. Actually I think exit PPCO0007 could be a possiblity for you. This exit is called by saving the order.
    But maybe it would be better for you to use a special status profile? A user status is set if settlement status is set.
    Also BADI WORKORDER_UPDATE could be interessting for you.
    Regards,
    Sabine

Maybe you are looking for