Inbound IDoc to generate Billing Document - t.code VF01

Hi,
which is the inbound idoc to trigger Billing Document.
pls suggest
thanks in advance...
Regards,
Balaji

Hi,
>IDOC name- INVOIC.INVOIC02
INVOIC02 can only be used as outbound from VF01 not as inbound (at least in standard)
unless you know a process code that can be used for inbound?
in general sales invoice can only be created via interface with the use of ERS (selfbilling) scenario
but I'm not sure if this is what you need
Regards,
Michal Krawczyk

Similar Messages

Billing document( T code:VF01) number range interval error

Hi Guru,
While Creating Billing document i.e (VF01) I got an error. But apart from that I already maintain the Number range Interval in FBN1 as well as SNUM. But that number ranges I assigned in Billing document type also. Then also facing the same error.
So please give me some solution Asap
Regards,
Sukdev.

Dear Neel,
Please find the Screen shot for VN01
and please find my Sales document type Number range assignment.
and please find my billing document type number range assignment.
Regards,
Sukdev.

IDOC for Invoice/Billing document

Hi Experts,
Some of our customers want us to send electronic but no paper invoice to them in the coming week.
I've investigated the process, steps are:
1. Do some configs for message type of billing document
2. Create KU partner profile and set outbound parameters, include Port / Basic type / Message type / Process code.
If you have experience about this (IDOC for Invoice/Billing document) ? please kindly share the detail for me.
Thanks in advance.
Regards
Sam

Hi,
Please check [https://supplier.intel.com/static/ap/forms/imp_gid2.doc|https://supplier.intel.com/static/ap/forms/imp_gid2.doc] this.
This might help you.
Thanks,
Abhijit

Reset a pricing condition type value when generating billing document

Hi experts,
I have a delivery-related billing type. In sales order, there is a pricing condition type Z001, with value = 100, I would like to reset it to zero when generating billing document. Is there any configuration or user exits can do this? Thanks.

Hello,
You can do this in BILLING provided , if the Condition type is Manual condition type
To achieve this you have to do some configuration in the condition types as,
Goto transaction code V/06 and select your condition type and maintain the MNAUAL ENTRIES as C which means you can process it manually and in the V/08 chose your pricing procedure and against your condition type check the Manal entry .
Now you can change the value of the condittion type to 0 in the Billing document.
Hope this is clear,
regards,
santosh

Relating outbound idoc to inbound idoc to create a document

We have a requirement to relate the outbound idoc to inbound idoc , transfer the data and create a document.
Kindly let me know the tcode / configuration steps of how can we relate the idocs.
Thanks,
Nalini S.

Hi Juan,
Check the IDOC: WMATGRP01. Hope it will be helpful for you.
BR,
Lokeswari.

Inbound IDOC error 51 Application Document not posted

Inbound IDOC error 51: Item: 002 Goods/Service number not entered So application document not posted.
Please help me out

hi
check whether service number is available in the idoc if not check the field mapping

System dump whiling testing Inbound IDoc for BOMMAT(Bill of material)

HI Experts,
I m testing Inbound IDoc from T-Code 'we19' using logical system 'BOMMAT' .System is giving a dump with error"Field Symbol has not yet been assigned". while testing t_code 'we02' A IDoc is genreted with warning with status 64 with error 'No filters , No conversion , No version change . Please suggest some solution.
Thanks
Ravinder Singh

Hi,
Check the data in the idoc.
This dump might happen due to numeric field you might have passed the character value. check throughly.
Regards,
Shanmugavel chandrasekaran

Delete IDOC before cancelling Billing Documents

Hi Gurus,
I want to Cancel Billing Documents , for this billing documents Idoc are already created with status "03" Data passed to Port OK.
For this First shall i need to delete Idoc and then cancel the Billing documents or first i can cancel billing documents and then delete Idoc?
Let me know which one i should do first.
Regards,

Hi,
Are you refering to the outbound idoc send from Billing doucment.
If yes, then fist check if the idoc has posted in the target system.
Many times it happnes that even if outbound idoc is in 03 status, it might have actually posted in target system.
And if it has not posted in target system, then delete the idoc and then delete the billing document.
Also I suggest, after deletion ask the target system guys to have a look for the idoc data, if they receive it ask them to take no action on it.
Let us know..
Regards,
SB.

Error while creating Billing Document in Tcode VF01

Hi all,
When i want to create a Billing document with single document number i'm able to move on to the overview of billing items.....for instance if 9000004568 is a document with 10 and 20 as items and when i try an create a billing document for the concern document with VF01 t-code its populating only one item in the overview of billing document screen....why is it sooo
And most importantly when i give two documents like 9000004568 and 6700000000 in the first screen and process them to see the overview of this then it populates Information message 'Reference document 9000004568 000020 (Error during INSERT)' .This is for the second item of the corresponding document number ie item 20 and when processed with single document number it shows only one item number 10 in the preceding screen......Why this is happing...
Thanks in Advance.

Younis
are you trying to create 1 single billing document?
If yes, you need have to same payer, payment terms and invoice date.
if you are planning to create separate billing documents, you need to make sure that "billing type" is same.
let me know if you need more info.
pl reward points if u find this info useful.
thx
ramesh

Unable to view the billing document created through vf01 tcode

Hi,
i'm unable to view the billing document which was created through vf01. when i want to display the document through vf03 it say document not created. As an abaper i'm not able to find any error..
Is there any configuration missed by the fn guy.

Hi,
While you are saving billing document i think you got Express document (please check in Transaction code SBWP :- Business work place of particular user). As per me the number range has completed for the particular document type(might be excise invoice also, if u have excise invoice auto generation functionality) that is why system is not able to update the invoice.
Hope this will be helpful
Regards
bvdv

Smartform output to be sent as pdf when billing document is saved(VF01)

Hello all,
I`m facing a problem in transaction VF01.The requirement is,when user will save the newly created billing document in VF01 transaction ,the corresponding smartform (attached to respective output type ) should be converted and sent as pdf to ship-to party e-mail address.
I`ve done the coding so that smartform is converted and sent through transaction VF02/VF03.
But I`m facing problem in understanding how the program is automatically triggered when billing document is created.In VF02/VF03 it can be understood that on "Issue output To" and selecting respective output type,driver program is triggered and processing starts for mentioned routine in NACE.
waiting for your valuable inputs...

I hope process will go like this...
1) when you use VF01 / VF02 & save, automatically RSNAST00 standard program will be triggered.
2) This program will fetch the driver program & form from NACE transaction & it will execute the driver program.

File to IDOC:how do i relate inbound idoc with generated idoc in the R/3

hi experts;
can any body tell me how can i relate the IDOC number genrated in the PI with the generated IDoc number in the SAP R/3 system for file to IDOC scenario?
in SAP PI for tcade idx5, idoc no is:12002
but in SAP R/3 in tcode WE05, idoc no is:846915
how can i know a particular message (in SAP PI) created a particular idoc in the backend SAP R/3 System.
thanks in advance,
kumar

Hi Kumar
at the time of testing you have to note down a time at what ur file got picked up ok
then go to we05
-> give the date on CREATED ON field.
-> then in BASIC TYPE field select your particular IDOC CREMAS05 or whatever, see the TIME field that you have noted down at the time of testing, if that is matching means that is ur latest IDOC you have tested.
-> one more thing, tha last IDOC showing in the list means that is your latest IDOC you have tested.
Hope i have helped you, points plz
Warm Regards
Dheeraj Kumar

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

IDOC and Billing Document relation

Hi All,
I want to know that is there any table where we can find IDOC for a Billing Document.
Please advice.
Thanks!
Regards,
Vivek Srivastava

Hi,
Check these tables
EDID4
EDIDC
EDIDD
Thanks and regards
Praveen.J

User exit trigerred after billing document is generated

The objective is to set the Sales Order Item Level System Status. Using a line item that is created in VA01, I have to create a reference item in VA02. For both the line items created I have to generate billing document in VF01. After the billing document is created (when I give save in VF01), using the billing document number I have to set the Billing and delivery system status to completed.
The functional specification provided me with a user exit USEREXIT_NUMBER_RANGE in RV60AFZZ. But the exit is getting triggered before the billing document number is generated. So I am unable to set the status. Can you suggest me a user exit that would be triggered after the billing document is generated?

if your invoice is relevant for accounting posting - you may use one of SD/FI exits (check RV_ACCOUNTING_DOCUMENT_CREATE and search for call customer-function).
OR you may define new output type for your invoice and put your logic there, nast-objkey will have invoice number.

Inbound IDoc to generate Billing Document - t.code VF01

Similar Messages

Maybe you are looking for