Issue of invoice with reference to service frame work order

Hi Gurus,
i am creating service framework purchase order for a service material. in item detail of service framework po in condition tab i maintain vat % condition. then i create service entry sheet with reference to that po and post the entry. when i go to maintain invoice for that material with ref to po the system shows two line items first line item shows amount and quantity to be invoice and second line item shows no amount or quantity but shows po number and po text which mentions vat% .
please tell me what customizing mistake has taken place
regards

Hi Suresh
go to OLMSRV > taxes at individual service level
then check box against country code.
Best Regards
Nishant Shende

Similar Messages

Create sales order with reference to service order

Hi
I need to create sales order based on the service order . Is there any BAPI function module available for this ?
Please help...
Regards
Sujith

**　プログラムＩＤ　　　　　　 ： ZBAPI_SALESORDER_CREATE               *
**　プログラム名称　　    　　 ： Upload Sales Order Creation                   *
**　処理概要　　　　　　　   　：                                       *
**　作成者　　　　　　　　　　 ： Karthik.P                             *
**　作成日　　　　　　　　　　 ： 2006/08/10                            *
REPORT ZBAPI_SALESORDER_CREATE LINE-SIZE 132 MESSAGE-ID ZMMBAPI .
       Internal table definition                                     *
****<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>>>
DATA: GT_ORDER_HEADER_IN LIKE BAPISDHD1,
*******<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>
      GT_ORDER_HEADER_INX LIKE    BAPISDHD1X,
*****<<<<<Return Parameter>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
      GT_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE, " Return Messages
*********<<<Communication Fields: Sales and Distribution Document Item<>>>>>
      GT_ORDER_ITEMS_IN LIKE BAPISDITM OCCURS 0 WITH HEADER LINE, " Item Data
*********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>
      GT_ORDER_ITEMS_INX LIKE BAPISDITMX OCCURS 0 WITH HEADER LINE, "Item Data Checkbox
*********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>
      GT_SALESDOCUMENT LIKE BAPIVBELN-VBELN , "Number of Generated Document
*********<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
      GT_ORDER_PARTNERS LIKE BAPIPARNR OCCURS 0 WITH HEADER LINE, "Document Partner
********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
      GT_ORDER_SCHEDULES_IN LIKE BAPISCHDL OCCURS 0 WITH HEADER LINE, "Schedule Line Data
****<<<<<<<<Checkbox List for Maintaining Sales Document Schedule Line>>>>>>>>
      GT_ORDER_SCHEDULES_INX LIKE BAPISCHDLX OCCURS 0 WITH HEADER LINE, " Checkbox Schedule Line Data
*******Communication Fields for Maintaining Conditions in the Order
      GT_ORDER_CONDITIONS_IN LIKE BAPICOND OCCURS 0 WITH HEADER LINE,
******Communication Fields for Maintaining Conditions in the Order
      GT_ORDER_CONDITIONS_INX LIKE BAPICONDX OCCURS 0 WITH HEADER LINE.
       Data definition                                               *
DATA: BEGIN OF GT_FT_SALES OCCURS 0,
       DOC_TYPE(4) ,        "Sales Document Type
       SALES_ORG(4) ,        "Sales Organization
       DISTR_CHAN(2) ,      "Distribution Channel
       DIVISION(2)   ,       "DIVISION(2)
       SALES_DIST(6) ,      "Sales district
       INCOTERMS1(3) ,      "Incoterms (part 1)
       INCOTERMS2(28) ,     "Incoterms (part 2)
       PMNTTRMS(4) ,        "Terms of payment key
       PRICE_DATE(8) ,       "Date for pricing and exchange rate
       PURCH_NO_C(35) ,     "Customer purchase order number
       PURCH_NO_S(35) ,     "Ship-to Party's Purchase Order Number
       EXCHG_RATE(8) ,      "Directly quoted exchange rate for pricing and statistics
       CURRENCY(5) ,         "SD document currency
       MATERIAL(18),         "MATERIAL
       TARGET_QTY(13) ,     "Target quantity in sales units
       ITEM_CATEG(4) ,      "Sales document item category
       MATL_GROUP(8) ,      "Material Group
       PURCH_NO_C1(35),      "Customer purchase order number
       SALES_DIST1(6) ,     "Sales district
       INCOTERMS11(3) ,     "Incoterms (part 1)
       INCOTERMS21(28),     "Incoterms (part 2)
       PMNTTRMS1(4) ,     "Terms of payment key
       EXCHG_RATE1(8) ,    "Directly quoted exchange rate for pricing and statistics
       PRICE_DATE1(8) ,    "Date for pricing and exchange rate
       TRG_QTY_NO(5)    , "Factor for converting sales units to base units (target qty)
       DIVISION1(2)     ,                                   "DIVISION1
       SALQTYNUM(5)     , "Numerator (factor) for conversion of sales quantity into SKU
       GROSS_WGHT(3)    , "Gross Weight of the Item
       NET_WEIGHT(15)    , "Net Weight of the Item
       UNTOF_WGHT(3)    ,"Weight Unit
       PARTN_ROLE(2)   ,"Partner function
       PARTN_NUMB(10)   ,"Customer Number 1
********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
       ITM_NUMBER(6) ,"Item number of the SD document
       REQ_QTY(8) , "Schedule line date
       DLV_DATE(8) , "Schedule line date
       MS_DATE(8) , "Material availability date
       LOAD_DATE(8) , "Loading time (local time with reference to a shipping point)
       GI_DATE(8), "Time of goods issue (local DATE, with reference to a plant)
       TP_DATE(8) , "Transportation planning -time (local w/ref. to shipping pnt)
       ITM_NUMBER2(6) , "Condition item number
END OF GT_FT_SALES,
       MSG(240) TYPE C, " Return Message
       E_REC(8) TYPE C,    " Error Records Counter
       REC_NO(8) TYPE C, " Records Number Indicator
       S_REC(8) TYPE C,   " Successful Records Counter
       T_REC(8) TYPE C.   " Total Records Counter
selection block for EXCEL UPLOAD FILE>>>>>>>>>>>>>>>>>>>>>>>>
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.
PARAMETERS FILE TYPE IBIPPARMS-PATH OBLIGATORY.
SELECTION-SCREEN END OF BLOCK B1.
*<<<<AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .>>>>>>>>>>>>
AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      PROGRAM_NAME = SYST-CPROG
      DYNPRO_NUMBER = SYST-DYNNR
    IMPORTING
      FILE_NAME     = FILE.
**<<<<<<<<<<<<<<<<<START-OF-SELECTION.>>>>>>>>>>>>>>>>>>>>>>>>>>>
START-OF-SELECTION.
CALL FUNCTION 'WS_UPLOAD'                                 "#EC *
    EXPORTING
      FILENAME                = FILE
      FILETYPE                = 'DAT'
    TABLES
      DATA_TAB                = GT_FT_SALES
    EXCEPTIONS
      CONVERSION_ERROR        = 1
      FILE_OPEN_ERROR         = 2
      FILE_READ_ERROR         = 3
      INVALID_TYPE            = 4
      NO_BATCH                = 5
      UNKNOWN_ERROR           = 6
      INVALID_TABLE_WIDTH     = 7
      GUI_REFUSE_FILETRANSFER = 8
      CUSTOMER_ERROR          = 9
      NO_AUTHORITY            = 10
      OTHERS                  = 11.
IF SY-SUBRC <> 0 .
    MESSAGE E000.
ENDIF.
SKIP 3.
FORMAT COLOR COL_HEADING INVERSE ON.
    WRITE 40 TEXT-001.
FORMAT COLOR COL_HEADING INVERSE OFF.
SKIP 1.
FORMAT COLOR COL_NEGATIVE INVERSE ON.
    WRITE :/ TEXT-002, 13 SY-MANDT , 104 TEXT-003, 111 SY-UNAME,
              / TEXT-004, 13 SY-DATUM , 104 TEXT-005, 111 SY-UZEIT.
FORMAT COLOR COL_NEGATIVE INVERSE OFF.
SKIP 3.
LOOP AT GT_FT_SALES.
      PERFORM SLALE_UPLOAD_DATA.
ENDLOOP.
T_REC = E_REC + S_REC.
SKIP 3.
FORMAT COLOR COL_TOTAL INVERSE ON.
    WRITE: /38 TEXT-007, T_REC.
FORMAT COLOR COL_TOTAL INVERSE OFF.
FORMAT COLOR COL_NEGATIVE INVERSE ON.
    WRITE: /38 TEXT-008, E_REC.
FORMAT COLOR COL_NEGATIVE INVERSE OFF.
FORMAT COLOR COL_TOTAL INVERSE ON.
    WRITE: /38 TEXT-009, S_REC.
FORMAT COLOR COL_TOTAL INVERSE OFF.
*&      Form SLALE_UPLOAD_DATA
      text
--> p1        text
<-- p2        text
FORM SLALE_UPLOAD_DATA .
*******<<<<<<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>
    GT_ORDER_HEADER_IN-DOC_TYPE =    'TA'.
    GT_ORDER_HEADER_IN-SALES_ORG = GT_FT_SALES-SALES_ORG . "'0001'
    GT_ORDER_HEADER_IN-DISTR_CHAN = GT_FT_SALES-DISTR_CHAN. "'01'
    GT_ORDER_HEADER_IN-DIVISION =   GT_FT_SALES-DIVISION. " '01'
    GT_ORDER_HEADER_IN-SALES_DIST = GT_FT_SALES-SALES_DIST ."'000001'
    GT_ORDER_HEADER_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1. "'CFR'
    GT_ORDER_HEADER_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'
    GT_ORDER_HEADER_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS .    "'0001'
    GT_ORDER_HEADER_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE ."'20060818'
    GT_ORDER_HEADER_IN-PURCH_NO_C = '32'.
    GT_ORDER_HEADER_IN-PURCH_NO_S =   '32'.
    GT_ORDER_HEADER_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE ."'1.00000'
    GT_ORDER_HEADER_IN-CURRENCY = GT_FT_SALES-CURRENCY . " 'EUR'
********<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>
    GT_ORDER_HEADER_INX-DOC_TYPE   = 'X'.
    GT_ORDER_HEADER_INX-SALES_ORG = 'X'.
    GT_ORDER_HEADER_INX-DISTR_CHAN = 'X'.
    GT_ORDER_HEADER_INX-DIVISION   = 'X'.
    GT_ORDER_HEADER_INX-SALES_DIST = 'X'.
    GT_ORDER_HEADER_INX-INCOTERMS1 = 'X'.
    GT_ORDER_HEADER_INX-INCOTERMS2 = 'X'.
    GT_ORDER_HEADER_INX-PMNTTRMS =   'X'.
    GT_ORDER_HEADER_INX-PRICE_DATE = 'X'.
    GT_ORDER_HEADER_INX-PURCH_NO_C = 'X'.
    GT_ORDER_HEADER_INX-PURCH_NO_S = 'X'.
    GT_ORDER_HEADER_INX-EXCHG_RATE = 'X'.
    GT_ORDER_HEADER_INX-CURRENCY = 'X'.
*****<<<<<<Communication Fields: Sales and Distribution Document Item>>>
    GT_ORDER_ITEMS_IN-ITM_NUMBER = '000010'.
    GT_ORDER_ITEMS_IN-MATERIAL = GT_FT_SALES-MATERIAL .
    GT_ORDER_ITEMS_IN-PO_ITM_NO = '32'.
    GT_ORDER_ITEMS_IN-CUST_MAT22 = 'AGNI-IV'.
    GT_ORDER_ITEMS_IN-BILL_DATE = '20060808'.
    GT_ORDER_ITEMS_IN-PLANT = '0001'.
*GT_ORDER_ITEMS_IN-STORE_LOC = '0001'.
    GT_ORDER_ITEMS_IN-TARGET_QTY = GT_FT_SALES-TARGET_QTY . "'1000'
    GT_ORDER_ITEMS_IN-ITEM_CATEG = GT_FT_SALES-ITEM_CATEG . "'TAN'
    GT_ORDER_ITEMS_IN-MATL_GROUP = GT_FT_SALES-MATL_GROUP . "'01'
    GT_ORDER_ITEMS_IN-PURCH_NO_C = GT_FT_SALES-PURCH_NO_C . "'32'
    GT_ORDER_ITEMS_IN-SALES_DIST = GT_FT_SALES-SALES_DIST . "'000001'
    GT_ORDER_ITEMS_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1 . "'CFR'
    GT_ORDER_ITEMS_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'
    GT_ORDER_ITEMS_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS .    "'0001'.
    GT_ORDER_ITEMS_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE . "'1.00000'
    GT_ORDER_ITEMS_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE . "'20060808'
*GT_ORDER_ITEMS_IN-SALES_UNIT = 'DZ'.
    GT_ORDER_ITEMS_IN-TRG_QTY_NO = GT_FT_SALES-TRG_QTY_NO . "'23'
    GT_ORDER_ITEMS_IN-DIVISION = GT_FT_SALES-DIVISION   .   "'01'
    GT_ORDER_ITEMS_IN-SALQTYNUM = GT_FT_SALES-SALQTYNUM .   "'32'
    GT_ORDER_ITEMS_IN-GROSS_WGHT = GT_FT_SALES-GROSS_WGHT. " ' 25272000'
    GT_ORDER_ITEMS_IN-NET_WEIGHT = GT_FT_SALES-NET_WEIGHT. "'24464000'
    GT_ORDER_ITEMS_IN-UNTOF_WGHT = GT_FT_SALES-UNTOF_WGHT . " 'KG'
*GT_ORDER_ITEMS_IN-CURRENCY = 'EUR'.
    APPEND GT_ORDER_ITEMS_IN.
****<<<<<<Communication Fields: Sales and Distribution Document Item>>>
    GT_ORDER_ITEMS_INX-ITM_NUMBER = '000010'.
    GT_ORDER_ITEMS_INX-MATERIAL = 'X'.
*GT_ORDER_ITEMS_INX-PO_ITM_NO = 'X'.
    GT_ORDER_ITEMS_INX-CUST_MAT22 = 'X'.
    GT_ORDER_ITEMS_INX-BILL_DATE = 'X'.
    GT_ORDER_ITEMS_INX-PLANT = 'X'.
*GT_ORDER_ITEMS_INX-STORE_LOC = 'X'.
    GT_ORDER_ITEMS_INX-TARGET_QTY = 'X'.
    GT_ORDER_ITEMS_INX-ITEM_CATEG = 'X'.
    GT_ORDER_ITEMS_INX-MATL_GROUP = 'X'.
    GT_ORDER_ITEMS_INX-PURCH_NO_C = 'X'.
    GT_ORDER_ITEMS_INX-SALES_DIST = 'X'.
    GT_ORDER_ITEMS_INX-INCOTERMS1 = 'X'.
    GT_ORDER_ITEMS_INX-INCOTERMS2 = 'X'.
    GT_ORDER_ITEMS_INX-PMNTTRMS = 'X'.
    GT_ORDER_ITEMS_INX-EXCHG_RATE = 'X'.
    GT_ORDER_ITEMS_INX-PRICE_DATE = 'X'.
*GT_ORDER_ITEMS_INX-SALES_UNIT = 'X'.
    GT_ORDER_ITEMS_INX-TRG_QTY_NO = 'X'.
    GT_ORDER_ITEMS_INX-DIVISION = 'X'.
    GT_ORDER_ITEMS_INX-SALQTYNUM = 'X'.
    GT_ORDER_ITEMS_INX-GROSS_WGHT = 'X'.
    GT_ORDER_ITEMS_INX-NET_WEIGHT = 'X'.
    GT_ORDER_ITEMS_INX-UNTOF_WGHT = 'X'.
*GT_ORDER_ITEMS_IN-CURRENCY = 'x'.
    APPEND GT_ORDER_ITEMS_INX.
*****<<<<<<Communications Fields: SD Document Partner: WWW
    GT_ORDER_PARTNERS-PARTN_ROLE =   'WE'.
    GT_ORDER_PARTNERS-PARTN_NUMB = '0000000057'.
***GT_ORDER_PARTNERS-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER . " '000010'.
    APPEND GT_ORDER_PARTNERS.
*********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
    GT_ORDER_SCHEDULES_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER." '000010'
    GT_ORDER_SCHEDULES_IN-REQ_QTY = GT_FT_SALES-REQ_QTY .   "'234'
    GT_ORDER_SCHEDULES_IN-DLV_DATE = GT_FT_SALES-DLV_DATE ." '20060824'.
    GT_ORDER_SCHEDULES_IN-MS_DATE = GT_FT_SALES-MS_DATE . "'20060808'
    GT_ORDER_SCHEDULES_IN-LOAD_DATE = GT_FT_SALES-LOAD_DATE. " '20060822'
    GT_ORDER_SCHEDULES_IN-GI_DATE = GT_FT_SALES-GI_DATE . " '20060823'
    GT_ORDER_SCHEDULES_IN-TP_DATE = GT_FT_SALES-TP_DATE .   "'20060821'
    APPEND gt_ORDER_SCHEDULES_IN.
*********<<<<Communications Fields: SD Document Partner: WWW FLAG>>>>>>>>>>>>>>>>>>
    GT_ORDER_SCHEDULES_INX-ITM_NUMBER = '000010'.
    GT_ORDER_SCHEDULES_INX-REQ_QTY = 'X'.
    GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.
    GT_ORDER_SCHEDULES_INX-MS_DATE = 'X'.
    GT_ORDER_SCHEDULES_INX-LOAD_DATE = 'X'.
    GT_ORDER_SCHEDULES_INX-GI_DATE = 'X'.
    GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.
    APPEND gt_ORDER_SCHEDULES_INX.
********Communication Fields for Maintaining Conditions in the Order
    GT_ORDER_CONDITIONS_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER ." '000010'
    APPEND GT_ORDER_CONDITIONS_IN.
***Communication Fields for Maintaining Conditions in the Order
    GT_ORDER_CONDITIONS_INX-ITM_NUMBER = '000010'.
    APPEND GT_ORDER_CONDITIONS_INX.
    CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
      EXPORTING
   SALESDOCUMENTIN               =
        ORDER_HEADER_IN               = GT_ORDER_HEADER_IN
        ORDER_HEADER_INX              = GT_ORDER_HEADER_INX
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
     IMPORTING
       SALESDOCUMENT                  = GT_SALESDOCUMENT
      TABLES
       RETURN                         = GT_RETURN
        ORDER_ITEMS_IN                = GT_ORDER_ITEMS_IN
        ORDER_ITEMS_INX               = GT_ORDER_ITEMS_INX
        ORDER_PARTNERS                = GT_ORDER_PARTNERS
       ORDER_SCHEDULES_IN            = GT_ORDER_SCHEDULES_IN
       ORDER_SCHEDULES_INX           = GT_ORDER_SCHEDULES_INX
       ORDER_CONDITIONS_IN           = GT_ORDER_CONDITIONS_IN
       ORDER_CONDITIONS_INX          = GT_ORDER_CONDITIONS_INX
ORDER_CFGS_REF                =
ORDER_CFGS_INST               =
ORDER_CFGS_PART_OF            =
ORDER_CFGS_VALUE              =
ORDER_CFGS_BLOB               =
ORDER_CFGS_VK                 =
ORDER_CFGS_REFINST            =
ORDER_CCARD                   =
ORDER_TEXT                    =
ORDER_KEYS                    =
EXTENSIONIN                   =
PARTNERADDRESSES              =
    IF GT_RETURN-TYPE EQ 'E' .
      E_REC = E_REC + 1.
      READ TABLE GT_RETURN WITH KEY ID = 'V1'.
      FORMAT COLOR COL_NEGATIVE INVERSE ON.
      REC_NO = E_REC + S_REC.
          CONCATENATE TEXT-006 REC_NO ':'
          GT_RETURN-MESSAGE INTO MSG SEPARATED BY SPACE .
          CONDENSE MSG.
          WRITE: / MSG.
      FORMAT COLOR COL_NEGATIVE INVERSE OFF.
ELSEIF GT_RETURN-TYPE EQ 'S'.
      S_REC = S_REC + 1.
      FORMAT COLOR COL_POSITIVE INVERSE ON.
          MSG = GT_RETURN-MESSAGE.
          CONDENSE MSG.
          WRITE: / MSG .
      FORMAT COLOR COL_POSITIVE INVERSE OFF.
     PERFORM COMMIT_MM.
ENDIF.
      CLEAR: GT_RETURN[], MSG.
ENDFORM.                    " SLALE_UPLOAD_DATA
*&      Form COMMIT_MM
      text
--> p1        text
<-- p2        text
FORM COMMIT_MM .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT   = 'X'
      IMPORTING
        RETURN = GT_RETURN.
clear:      GT_ORDER_ITEMS_IN[],GT_ORDER_CONDITIONS_IN[].
ENDFORM.                    " COMMIT_MM

Creating a Invoice with reference to another invoice with new pricing proce

Hi People,
I want to raise a supplimentary excise invoice for the differential price.
I want to do it by raising a supplimentary commercial invoice with reference to the old invoice but with a new pricing procedure assigned to it.later on raise the supplimentary excise invoice with Tcode j1iin wrt the new commercial invoice.
Although i have done all the necessary configurations such as determination of new pricing procedure, Doc pricing Procedure and changing the pricing type at the copy control settings of the item category to "B".
i am unable to get the new pricing procedure when i am creating the supplimentary commercial invoice.
Can u people suggest me in this regard

Dear Nagabhushan
Normally for price difference, there is an order type RK for "Invoice Correction Request" which should be created in reference to F2 billing document. Based on this, you can issue credit memo (document type G2).
This being the case, you cannot create supplimentary invoice with reference to original invoice. Moreover, for all excise related adjustments, you should not use j1iin. You should run j1ih - Other adj.
thanks
G. Lakshmipathi

ERP invoice with reference to SRM Basic Contract?

Hi
In SAP SRM you can create a shopping cart or a PO with reference to a SRM Basic Contract by setting the item number to 0 like: 4700000107/0
But with the new Ehp1 SAP states that ERP invoices can be created with reference to a SRM central contract (via SRM_SERVICE_PROC_1). But can you create the invoice with reference to contract item 0?
The idea is to have the non PO related invoices registrered on the basic contract in SRM along with the PO's. A basic contract can't be copied to ERP, as there is no lines on it, but is the ERP contract copy needed for this scenario?
So two questions:
- is the ERP contract copy from SRM needed to use the Ehp1 functionality of creating invoices with reference to a SRM contract?
- can the ERP invoice be created with reference to a basic SRM contract by giving the contract item as 0 or in another way?
BR
Jacob

Hello,
With SRM 70 EHP1 you can create ERP invoice against your SRM Central Contract distributed to ERP.
To enable this you need to do few settings in ERP, for the same you can refer to the config guides available at Service market place for SRM701 releases.
Configuring Contract Handling for Invoices : You use this procedure to configure contract handling for invoices in the SAP ERP system. You have activated the Procurement - SRM Integration 2 (LOG_MM_P2PSE_2) business function in the SAP ERP system.
Steps :
1. In Customizing for SAP ERP, perform the activity under : Materials Management -- Logistics Invoice Verification -- Incoming Invoice -- Activate Direct Posting to Contracts , to allow direct references to contracts when creating invoices and parking documents.
2. In Customizing for SAP ERP, perform the activity under : Materials Management -- Logistics Invoice Verification -- Invoice Block -- Set Tolerance Limits , to set the tolerance key for contracts (PC: Price variance for contract).
The feature is termed as Invoice Reconciliation here.
Best Regards,
Rahul

Excise Invoice with reference to Commercial Invoice

Hello Experts
My client has third party software. In SD- Order to Invoice cycle is done in that software.
After Invoice is created the data is interfaced and Invoice is received in SAP.
Now my doubt is that will it be possible to create the excise invoice with reference to this commercial invoice.and if so, what should I assign in config- Assign Del types to Invoice Types.
Please advice.
Best Regards
Raghu

Hi
Your scenario is not very clear to me although i am trying to attempt for the solution. Generally F2 invoice will take care of commercial *** excise invoice requirement. If material is excisable & attracts commercial taxes like CST or VAT you can geit through F2 invoice. You can have print programme developed for the invoicing where heading print will be like "Commercial *** excise invoice".

Single Invoice with reference to 2 Sales Order

Hi,
How can i make a single billing invoice no (vf01) with reference to 2 sales order?
billing plan has been maintained from each sales order,we dont have any pgi process.
so process is sales order->billing plan-> invoice
my user want to generate single invoice with reference to 2 sales order - same customer no.

For processing billing due list (VF04) - The system combines documents with the same customer number, proposal billing type and sales organization, and attempts to include them all in the same billing document. If the preconditions are met, then a single invoice is created for the deliveries and/or orders.
To do a collective billing. Collective Billing Documents
The selected documents in the billing due list are billed. The system tries to combine them as much as possible. Processing of the selected documents is carried out in the background. After processing of the documents, you return to the billing due list. The sysytem will indicate whether or not a document has been billed successfully.
If successful, then Save
You can also carry out a simulation of billing. In this case, select Simulate. The system simulates the collective billing / online function described above.
-After the collective run you can display a log for the collective run. This displays possible errors during billing.
-You can also branch to the resulting billing documents, in order to carry out a split analysis.
-The billing documents of a collective run can also be canceled.
Re: VF04
Hope it assist you.
Thanks & Regards
JP

How to create excise invoice with reference thorugh credit memo

Hi All,
Please provide any solution for the following qurey:
How to create excise invoice with reference thorugh credit memo

Hi murali,
i am unable to understand your requirement i think there is no like this scenario requirement for any client
if any requirement is there kindly explain detail
cheers

How to create excise invoice with reference delivery document

hi all sd guru
please guide me how to create excise invoice by taking reference of delivery no.
thankx in advance
san

HI
FACTORY SALES
IN CASE OF FACTORY sales you have to create a billing document either Proforma or Commercial.
Then you can reference the billing doc i9n J1IIN for creation
DEPOT SALES
In case of depot sales you can create a excise invoice with reference to delivery document.
For this after creation of delivery goto J1IJ and slect the rg23d from menu
you can create an excise invoice with delivery in depot sales.
In factory it is not possible to create a excise invoice with delivery doc.
regards
Prashanth

Problem in generating excise invoice with reference to commercial invoice

Hi,
I could able to generate excise invoice with reference to STO ( jex ) invoice but unable to generate with reference to commercial invoice ( F2) .System is show 'error in creating FI document'. Am i missing some configuration.
Please advice
Thanks
satya

Hi
Check the G/L accounts assignments for Excise transaction types DLFC,
Also check the NUmber ranges in OBA7, and also the accounting doc type for excise invoice
regards
Prashanth
Edited by: Prashanth@SD on Feb 3, 2011 8:27 AM

Excise invoice with reference to credit memo/debit memo

Normally we create Excise Invoice with reference to Inter company Invoices . Is it possible to create Excise invoice w.r.t. Credit Memo/ Debit Memo. If Yes , then what are the settings that needs to be maintained and where?

Excise JV thru J1IH transaction is one option. It gives you 6 options.
1.Material Doc for written off
2.materail doc for non production
3.Additional Excise
4.Other adjustments
5 TR6 Challan
6.Cacel Excise Invoice

Excise Invoice with Reference to Delivery

Hi,
i want to create Excise Invoice with reference to Delivery *without creating "JEX"*(Proforma Invoice)
OR->LF->J1IIN->F2 ie. Commercial Invoice after Excise Invoice. is it possible?
Regards,
Amol

Hello Amol,
you can create with reference of the deliveyr document. in J1iin trnsaction you have the option in the header tabs of create from delivery
enter the delivery and create the excise invocie
Hope this helps
Thanks
akasha

Sales order with reference to Service Notification

Hi Freinds,
I have to create a sales order with reference to Service notification (IW51). can someone sugggest me BAPI or Function module to perform this task.
Appriciate your help.
Best regards
Pravin

no std bapi's as far as i know..when you hit create create repair order(in iw51) system calls QM06_RMA_ORDER_CREATE
..whick internally calls SD_ORDER_CREATE..may be this should give some pointers..
Regards
Siva

Invoice with reference to SalesOrder

Hi,
in SQL Table INV1 i can see information like BaseRef=10000, BaseType = 17, BaseEntry = 1 etc.
How can I Import invoice via XML structure with a BaseRef?
In our scenario we have invoices with reference to order.
Thank
Kay

I solved it:
BaseRef will be filled automatically.
in XML I defined only <BaseEntry> and <BaseLine>
Another important Point: <CardCode> <LineNum> and <ItemCode> in invoice sould be the same as in order!
Best regards,
Kay

How to create item wise invoice with reference to sales order.

Hi ,
Please let me know how to create item wise invoice with reference to sales order.
Ex : Sales order has 2 line items .
When creating invoice system should create two invoices for each line items.
I have tried with copy control but I am not able to do it.
Please advise.
Regards

Hi,
Please let us know your exact requirement. Whether you want it to be fixed like only one line item to be billed every time ot it to be based on selection you do every time.
As per my understanding it should not be fixed and in that case it should like as follows,
In VF01 you will select Del. document/S.O. number and click on selection list and will take you to next screen as mention below,
and select desire line item to be billed and click on copy and will take you to billing screen.
Regards,
Ajit K Singh

Repair order with reference to service nitification.

Hello,
I want to create repair order with reference to service notification S1. but when I click create repair order in action box nothing happens. could any one of you help me in sloving this. where is the link missing in customizing. can you help.
thanks in advance

Hi
Check out the config in Action box
Plant Maintenance and Customer Service - Master Data in Plant Maintenance and Customer Service - Maintenance and Service Processing - Maintenance and Service Notifications - Notification Processing - Additional Functions - Define Action Box
execute it
Select and execute
Define Follow-Up Functions (Generated Tasks/Activities)
Select your notification type, and go for activities, maintain the fields notification type (S1), Fk (0031), scenario, sort no and description.
- Pithan

Issue of invoice with reference to service frame work order

Similar Messages

Maybe you are looking for