Activity profile for shipment- create billing document

Hi Expert,
Few days ago, I discovered in some posts the functionality of "Activity Profile". As we want to automate the creation of invoices wheh a shipment  is planed, I try this functionality. I create the variant and link it with the activity "For Planning". I tested it and invoices are well created.
But, because there is always a "but", the invoice that is automaticaly created is of type F2 - Billing Documents however we want that F8 - Proforma invoice type will be used. Any idea where to configure the billing document type to be use when creating invoices with an activity profile ?
kind regards,
yannick

Yannick
To decide if a proforma or a F2 is created you have
to define this in the item category type of the sales order items (VOV7)
For the case they have invoice relevance 'D' then the activity
profile would create a proforma invoice.
Within function module SD_SHIPMENT_CREATE_INVOICE it is checked which delivery is relevant for
invoicing and which invoice type has to be created (call transaction
VF01).
Best regards,david

Similar Messages

  • Setting for VF01 create billing documents

    Hi,
             We have one scenario,  we have made one package material concept  just like BOM for header material  we have created one material for which we have maitain BOM and for that item category as ZBOM,  when we enter this parent material in Sales order all child items as per BOM coming in the SO  after that we are making delivery with VL01N  and in VL01N  for header material i.e parent material pick qty. is 0 as we want to dispatch only child items parent material is made only to get all BOM items  but after VL01N if we go for J1IJ or VF01  there also that parent material is coming delivery qty 0  but we want that is delivery qty. is zero that material should not come in J1IJ  and VF01.
           How to do this .
    regards,
      zafar

    Hi,
    Setting in VTFL is OK , when I remove the the material from VTFL for delivery to billing process that materail is not coming in VF01 when creating billing document ref. to delivery  , but before VF01 we have to do J1IJ capture excise details ,  and in J1IJ i want that material with Item category ZBOM should not come or material with delivery picked qty. : 0 should not come in J1IJ.
    regards,
      zafar

  • SAp standard Activity profile for shipment.

    Hi Expert,
    I am working on transortation module.
    WE have requirmrnt that in shipment creation measn vt01n transaction when user will tick the shipment status that is shipment start,shipment loading......etc. automatic PGI happend or automatic billing document created in background.
    for this as per my knowledge SAP activity profile is the solution but no idea.
    Can someone help me & help me to clear my view.
    Thanks in Advance.
    Dev

    Hi
    Thanks for your reply.
    I know the path , but I want what is activity profile?
    Which activity profile have to use for PGI & which for Billing document.?
    Please suggest or send me any document which provide me a complete set of information.
    Thanks & reply ASAP.
    Dev

  • Require bapi for create billing document

    Hi,
    Guru.....
    Please provide the Bapi for Backgournd create Billing document with refrence to Delivery.
    Thanks
    Arun

    HI
    Try with T-Code VF06 for automatic back- ground billing document creation based on delivery with PGI
    Check the Below link
    [Re: automatic delivery and billing|automatic delivery and billing;
    Regards,
    Prasanna
    Edited by: prasanna_sap on Feb 1, 2012 12:09 PM

  • Creating Billing document for WBS Element(Transaction: CJ02 )

    Hi Guys,
    I am using FM BILLING_SCHEDULE_MAINTAIN to create billing document with milestone data,
    it is giving sy-subrc eq 0. but billing document is not saving in  FPLA table,
    I am using FM GRSV_UPDATE_GRPGA_FROM_CJDW to update project.
    and more over iam using COMMIT WORK.
    Thansk in advance
    Regards
    Peram Srinivas

    Kindly refer following Links:
    Excise modvat accounts not defined for DLFC transaction and  excise group
    STO Account Determination
    j1iin error message
    Accounting document for Excise Invoice
    Regards,
    Ashutosh

  • Please help with this bapi for creating billing document

    I want to create a billing document using the bapi:  BAPI_BILLINGDOC_CREATEMULTIPLE from a delivery number and NOT A SALES ORDER.
    Please tell me what  details to be passed to table  BILLINGDATAIN . Please don't provide me function module documentation because it does n't help me create billing document from delivery. A sample source code or suggestion to what to pass would be really great!
    Thanks,
    Krishen
    P.S. Points assured for helpful answers and thanks for your time.

    Hi,
    Try this..
    DATA: s_vbap TYPE vbap.
    TABLES: vbak,vbap,likp, lips.
    DATA: t_billing TYPE STANDARD TABLE OF bapivbrk WITH HEADER LINE.
    DATA: t_conditions TYPE STANDARD TABLE OF bapikomv WITH HEADER LINE.
    DATA: t_return TYPE STANDARD TABLE OF bapireturn1 WITH HEADER LINE.
    DATA: t_ccard  TYPE STANDARD TABLE OF bapiccard_vf WITH HEADER LINE.
    DATA: t_errors TYPE STANDARD TABLE OF bapivbrkerrors WITH HEADER LINE.
    DATA: t_success TYPE STANDARD TABLE OF bapivbrksuccess WITH HEADER LINE
    PARAMETERS: p_vbeln TYPE vbeln.
    select single * from likp
                    where vbeln = p_vbeln.
    SELECT SINGLE * from lips where
                    vbeln = likp-vbeln.
      t_billing-salesorg   = likp-vkorg.
      t_billing-ref_doc     = likp-vbeln.
      t_billing-ref_item    = lips-posnr.
      t_billing-doc_number     = p_vbeln.
      t_billing-itm_number    = lips-posnr.
      t_billing-ordbilltyp  = 'ZINV'.
      t_billing-price_date = sy-datum.
      t_billing-ref_doc_ca  = likp-vbtyp.
      t_billing-material    = lips-matnr.
      t_billing-plant       = lips-werks.
      APPEND t_billing.
    CALL FUNCTION 'BAPI_BILLINGDOC_CREATEMULTIPLE'
      TABLES
        billingdatain         = t_billing
        return                = t_return
        success               = t_success
    commit work.
    Thanks,
    Naren

  • VF06 - Create billing documents separately for each delivery order

    Hi gurus,
    Just as subject, I want to create billing documents for each delivery order in batch job.
    Can anybody tell me how can this be achieved.
    thank you.

    Hi,
    The steps to create a background job is mentioned below:
    1. Go to transaction SM36.
    2. Then give the Job name & job class.
    3.If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
    4.Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
    Reward me if you find this helpful
    Regds.......
    Sumit
    Edited by: Sumit Rayaguru on Jul 22, 2008 9:01 PM

  • Activity profiles in Shipment

    Hi All,
    Kindly explain me about Activity Profiles assigned for the Shipment activities.
    In our company, In the Shipment, during Check in, GTS documents are created, during Shipment PGI will be done and some ASN Outputs are triggered only after PGI.
    Is this standard SAP or it can customized. I checked all the Activity profiles, those are all just Variants. But how are these variants performing all these activities. Can anyone explain.
    Kindly explain in detail about Activity Profiles in Shipment.
    Regards,
    Mullairaja

    Hello
    you firstly create variants according your business needs (eg. PGI, billing, output) to report RV56ABST and then,
    assign them to the required status into shipment type ( at check-in, at completion...)
    spro > le> transportation>shipments> define and assign activity profiles
    Whenever you press on deadlines button, activities defined will be carried out.
    Very easy..
    regards, david

  • Error while creating billing documents

    Hi,
      While creating billing documents I am getting error message as 
    Maintain customizing for excise and series group determination
    Message no. 8I619
    I have check the setting for CIN it is OK excise and series group are maintain properly so what can be the proble,
    regards,
    zafar

    Hi,
    Check once again customizing
    Maintain Series Group - In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents. Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
    - Define excise series groups based on type of outgoing document
    - Assign series group to excise registration ID
    - If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    - If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' Iindicator. Example - You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
    - No account postings for CENVAT in sales cycle
    - No utilization Flag
    If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
    If the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
    Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
    If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
    Thanks
    Chidambaram

  • Ff759 during creating billing document

    hi guys
    During  sales order process with Customer Down Payment (for Poland) I'm getting an ff759 error when I'm creating  billing document .
    Message no. FF759.
    Cannot post document: tax base in local currency is zero.
    You tried generating a document in which the tax base in local currency is zero although the tax amount and tax base in foreign currency is not zero
    System is not creating an accounting document.
    The billing document that I'm creating in that case  is a regular invoice (type F2) that uses a downpayment invoice (type FAF) for clearing.
    Both invoices are in local currency.
    I'm sure the error is  because of some tax rounding isuess.
    We have implented every note relating to Down Payment  for Poland and to FF759 error.
    My system SAP ECC 6.03 , SP04
    Any ideas??
    thx
    Raf

    Alex, thank you for your answer, but it didnu2019t solve my problem, most of the notes that you wrote about are relating to invoice correction,
    and like I wrote before our problem is happening only during  sales order process with Customer Down Payment (Down payment process for Poland is different than in other countries) when weu2019re creating  billing document.
    Error  is being trown from  infunction FI_TAX_SV_TAXITEM.
    Prüfung: Steuer <> 0 und Steuerbasisbetrag = 0
        IF ( i_bset-hwbas = 0 AND i_bset-hwste != 0 ) OR
           ( i_bset-fwbas = 0 AND i_bset-fwste != 0 ) OR
           ( i_bset-h2bas = 0 AND i_bset-h2ste != 0 ) OR
           ( i_bset-h3bas = 0 AND i_bset-h3ste != 0 ).
    no error in case of external system is active             "N515047
    AND  billing document AND bas-amount = 0                  "N515047
    prerequisite: note 549712                                 "N515047
          IF  ext_activ IS INITIAL                              "N515047
         OR  i_bkpf-awtyp NE 'VBRK'.               "N515047   "N1174393
           or ( i_bkpf-awtyp NE 'VBRK' and                      "N1174393
                i_bkpf-awtyp NE 'WBRK' ).                       "N1174393
            message_store 'FF' 'E' '759' blank blank blank blank.
          ENDIF.                                                "N515047
        ENDIF.
    btw. != means different
    Beside that I would like to let you know that thanks to substitution described in note 872449 point 5c I was able to avoid ff759 error when I was creating billing document, but unfortunately in that case  posting document was incorrect.

  • Error while creating billing document using VF04 transaction

    Hi All,
    User is trying to create billing document using VF04 with ference to delivery number. When pressing save in invoice creation system SAP gives invoice document number (No accouting document generated). but no documents are actually created. When user trying for second time log is showing this sales order is currently processed by the user(user is same who is trying to create invoice)
    Please let us know what is causing this issue since this issue is happening in production and we can not debug this.
    We checked for number range also but its not.
    Waiting for your inputs.
    Regards,
    Jyothi CH.

    When pressing save in invoice creation system
    SAP gives invoice document number (No accouting document generated).
    but no documents are actually created
    Check there is any clash with internal number range of billing type vs other billing types ?
    Try to create billing document using VF01,see any messages were poping while saving ?
    Check for abap dump in ST22 ?
    Edited by: Jeyakanthan A on Feb 9, 2011 9:52 PM

  • How to block creating Billing document if no accounting doc generated

    Hi,
    In Brazil, after create Billing Document a new document called Nota Fiscal is also created.
    But I can't allow creating Billing Document and Nota Fiscal if i have a problem during the releasing process of the Accounting Document.
    How Could I to do for block the creation of those documents if i had a problem in releasing the accounting document ?
    Best Regards.
    Kleyson Rios.

    HI,
    with out creating a billing document we can not expect accounting document details.
    once u create a billing document then we come to know whether accounting doc is created or not. if not created then we hav top analyze why it is not created.
    do one thing u have to check all configuration settings before creating a billing document.
    Srini

  • 'update was terminated' while creating billing document VF01

    Hi all,
             i need a solution urgently ..except for paticular document no all documents that i post using VF01 create successfully document no.
    but for a paticular document no(may be it is of some type that i am unable to) while creaing billing document no it gives a message 'document created successfully' ,but when i try to click any button after that e.g BACK it shows a messge 'Update was terminated  for author ....' in my inbox. and vf03 shows the documentdoesn't exist.
    in st22 i checked one dump . when i gave a break point at that point the cursor never reached the code.
    I also checked SM13 and it showed all fms as init. and one fm 'RV_MESSAGE_UPDATE ' as error . i aws unable find the fm in the main program .
    one more thing when i create bill document for other document type it shows messge 'Document saved ....(no accounting document created)' but for this one i am getting messge 'document saved.......' .
    I asked one collegue he told me might be some OSS notes required for it . i am working on a unicoded system ECC 6.0  version.but he is not sure .
    Has any body faced the same problem..and what was the soln....if oss notes are required than how could i find it..and what was the no...........
    THANKS IN ADVANCE ...................

    THANKS  for the reply.
    i am new to sap .can u tell me in detail where actually i can check for number range of the document . one more when i checked the sm13 and  started debugging it gave me for a certain character set  (may be in chineses) present in the table ,the transfer command gives a dump. now the problem is it is too long 132 and don't no forwhich character it gives an  dump.how can i check the characters maintained in the system. it gives a dump   CX_SY_CONVERSION_CODEPAGE   ,At the conversion of a text from codepage '4102' to codepage '4110':      
    i am not sure this causes the mesages 'Updation was terminated' . what u people think.
    thanks ..

  • Create Excise invoice(J1IIN) document while creating billing document using bapi BAPI_BILLINGDOC_CREATEMULTIPLE

    Dear Experts,
    My scenario is:
    We have batch split scenario, where the parent line item of billing document has 0 quantity and its subsequent item (item with batch number) holds actual quantity data.
    When we create billing document using VF01 against delivery document, system creates billing document along with excise invoice document (J1IIN Document). And in excise document contain same number of line items that of billing document. Please see the below attachment: 
    Biiling document screen shot:
    While creating billing document, the J1IIN Document created automatically. Below is the screen-shot for the same.
    Now the issue is:
    When we create billing document using BAPI: BAPI_BILLINGDOC_CREATEMULTIPLE system creating only billing document and not creating excise invoice document.
    When we create excise document manually using J1IIN the zero quantity line items are excluded in excise invoice document.
    Please see the below screen-shot for the same; The z quantity line items are missing.
    We want excise document to be created while creating billing document using BAPI BAPI_BILLINGDOC_CREATEMULTIPLE. Or is there any other BAPI for the same purpose.
    Customization is also maintained for creating excise invoice document automatically.
    Regards,
    Rajesh Sadula.

    HI
      Pricing will be carried basing on the pricing
    procedure.
    Case1: Prices will be carried out automatically if
    necessary condition records are maintained for the
    condition type.
      For this you can go to Sales Order-> Item Conditions
    In the screen you can click on command button Analysis,
    which gives you the list of condition types associated
    to the pricing procedure. By clicking on the condition
    type you can know the action that has taken place.
    Case2: Manually forcing prices for Items.
      To do this, you have to populate ORDER_CONDITIONS_IN &
    ORDER_CONDITIONS_INX. Also note to identify the item
    numbers, you manually pass the item number for each item
    in the sales order, use the same item number for
    populating conditions.
      Parameters required:
    ORDER_CONDITIONS_IN:
      ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
    ORDER_CONDITIONS_INX:
      ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
       Hope the above info helps you. Do revert back if you
    need more info.
    Kind Regards
    Eswar

  • Create billing document from IDOC INVOIC01

    Hi Experts,
    I created a function module to extend IDOC_INPUT_INVOIC_MRM. After created successfully the invoice from this inbound idoc, I tried to create a billing document by code below:
    get sale order number from purchase order *****************************
        CALL FUNCTION 'BAPI_PO_GETDETAIL'
          EXPORTING
            PURCHASEORDER                    = lw_tfrseg-ebeln
            ACCOUNT_ASSIGNMENT               = 'X'
         TABLES
            PO_ITEM_ACCOUNT_ASSIGNMENT       = lt_acc_***
    ****get sale order details*******************************************************
         CALL FUNCTION 'BAPISDORDER_GETDETAILEDLIST'
          EXPORTING
            I_BAPI_VIEW                   = lw_order_view
          I_MEMORY_READ                 =
          TABLES
            SALES_DOCUMENTS               = lt_sales_key
            ORDER_HEADERS_OUT             = lt_ord_headers
            ORDER_ITEMS_OUT               = lt_ord_items
            ORDER_SCHEDULES_OUT           = lt_ord_schedules
            ORDER_BUSINESS_OUT            = lt_ord_business
            ORDER_PARTNERS_OUT            = lt_ord_partners
            ORDER_ADDRESS_OUT             = lt_ord_address
          ORDER_STATUSHEADERS_OUT       =
          ORDER_STATUSITEMS_OUT         =
            ORDER_CONDITIONS_OUT          = lt_ord_cond
    ****Fill billing data in*******************************************************
               lt_bill_data-SALESORG = lt_ord_headers-sales_org.
             lt_bill_data-DISTR_CHAN = lt_ord_headers-DISTR_CHAN.
             lt_bill_data-DIVISION   = lt_ord_headers-DIVISION.
             lt_bill_data-DOC_TYPE   = lt_ord_headers-DOC_TYPE.
             lt_bill_data-ORDBILLTYP    = lt_ord_headers-ORDBILLTYP.
             lt_bill_data-BILL_DATE    = lt_ord_business-bill_date.
             lt_bill_data-SOLD_TO    = lt_ord_headers-SOLD_TO.
             lt_bill_data-ITEM_CATEG    = lt_ord_items-ITEM_CATEG.
             lt_bill_data-ACCTASGNMT    = lt_ord_business-ACCNT_ASGN.
             lt_bill_data-PRICE_DATE    = lt_ord_business-PRICE_DATE.
             lt_bill_data-COUNTRY    = 'US'.
             lt_bill_data-PLANT    = lt_ord_items-PLANT.
             lt_bill_data-BILL_TO    = lw_partner_bp-customer.
             lt_bill_data-PAYER    = lw_partner_py-customer.
             lt_bill_data-SHIP_TO    = lw_partner_sh-customer.
            REF_DOC    = lt_sales_orders-DIVISION.
             lt_bill_data-MATERIAL    = lt_ord_items-material.
             lt_bill_data-REQ_QTY    = lt_ord_items-req_qty.
             lt_bill_data-CURRENCY    = lt_ord_items-currency.
             lt_bill_data-SHORT_TEXT    = lt_ord_items-short_text.
             lt_bill_data-TAXCL_1MAT    = lt_ord_items-TAX_CLASS1.
            REF_ITEM    = lt_sales_orders-DIVISION.
            STAT_GROUP    = lt_sales_orders-DIVISION.
             lt_bill_data-NO_MATMAST    = 'X'.
             lt_bill_data-ADDR_NO    = lt_ord_address-ADDRESS.
            lt_bill_data-TITLE    = lt_ord_address-DIVISION.
             lt_bill_data-NAME    = lt_ord_address-NAME  .
             lt_bill_data-NAME_2    = lt_ord_address-NAME_2.
             lt_bill_data-POSTL_CODE    = lt_ord_address-POSTL_CODE.
             lt_bill_data-CONSUMCTRY    = lt_ord_address-COUNTRY.
             lt_bill_data-CITY    = lt_ord_address-CITY.
             lt_bill_data-DISTRICT    = lt_ord_address-DISTRICT.
             lt_bill_data-STREET    = lt_ord_address-STREET.
             lt_bill_data-REGION    = lt_ord_address-REGION.
             lt_bill_data-PROD_HIER    = lt_ord_items-PROD_HIER.
             lt_bill_data-SALES_UNIT    = lt_ord_items-SALES_UNIT.
             lt_bill_data-PROFIT_CTR    = lt_ord_items-PROFIT_CTR.
            TAXJURCODE    = lt_sales_orders-DIVISION.
             lt_bill_data-PURCH_ORD    = lt_ord_headers-PURCH_NO.
             lt_bill_data-DOC_NUMBER    = lt_ord_items-DOC_NUMBER.
             lt_bill_data-ITM_NUMBER    = lt_ord_items-ITM_NUMBER.
            ORIGINDOC    = lt_sales_orders-DIVISION.
            lt_bill_data-ITEM    = lt_sales_orders-DIVISION.
             lt_bill_data-CREATED_BY   = sy-uname.
            MATERIAL_EXTERNAL = lt_sales_orders-DIVISION.
            MATERIAL_GUID = lt_sales_orders-DIVISION.
            MATERIAL_VERSION = lt_sales_orders-DIVISION.
             lt_bill_data-INCOTERMS1  = lt_ord_business-INCOTERMS1.
             lt_bill_data-INCOTERMS2  = lt_ord_business-INCOTERMS2.
             lt_bill_data-EXCHANGE_RATE = lt_ord_business-EXCHG_RATE.
             lt_bill_data-PAYMENT_TERMS  = lt_ord_business-PMNTTRMS.
             lt_bill_data-HG_LV_ITEM   = lt_ord_items-HG_LV_ITEM .
    ******call bapi function to create billing document********************
      CALL FUNCTION 'BAPI_BILLINGDOC_CREATEMULTIPLE'
       EXPORTING
         CREATORDATAIN         = lw_creator
         TESTRUN               = lc_testrun
         POSTING               = lc_posting
        TABLES
          BILLINGDATAIN         = lt_bill_data
        CONDITIONDATAIN       =
        CCARDDATAIN           =
        TEXTDATAIN            =
          ERRORS                = lt_bill_errs
          RETURN                = lt_bill_retu
          SUCCESS               = lt_bill_succ
    A return message in the table lt_bill_retu:
    "This item is not relevant for billing!"
    Anyone can tell me why? I think this problem be generated from the step "fill billing data" but I don't know where.
    Pls help me!!!
    Thanks,
    Gy

    Hi,
    In the condition data, I want to add new condition type as below:
    <<  Add new condition type
        CLEAR: lt_cond_data.
        lt_cond_data-COND_TYPE = 'ZHD0'.
        lt_cond_data-COND_VALUE = mrm_ship_charge-summe.  " amount of shipping charge
        lt_cond_data-COND_CURR = mrm_ship_charge-waerq. " USD
        append lt_cond_data.
    *>>
    But I created successfully billing document, this condition type is not appear in the billing view by transaction VF03.
    Could you help me to find out the fault?
    Thanks,
    Gy

Maybe you are looking for