Intercompany billing w/ PO: iDoc created, but no invoice receipt generated

Dear SAP Experts,
I am trying to implement an SAP intercompany billing from purchase order scenario (and I got good help from notes 109254 and 137686), but no invoice receipt occurs, even though the iDoc seems to have been correctly generated (in transaction BD87, I can see the iDoc number assigned to message type INVOIC under the node "Data passed to port OK").
Has any of you experienced a similar problem or know what to do to deal with this?
Thanks for helping.
Regards,
Nuno Ferreira

Check OSS Note 730853 - MRRL: M8283 Reverse value must be reset
Regards,

Similar Messages

  • IDOC created but not stored: No exception also

    Hi All,
    My scenario is that to upload the data from excel file and create inbound delivery. I am using the fm IDOC_INPUT_DESADV1. IBD and IDOC has been created but mot saved.
    if I goto vl32n, There is no IBD and if i goto WE02 then there is No IDOC. No exception also.
    Thanks with Regards,
    Vallamuthu M

    Hi,
    Thanks for all your updates. Not able to create IBD using IDOC_INPUT_DESADV1 in progran(SE38). I am using the following function modules. it's created IDOC and IBD. Now my problem is that how to create batch and serial number. I have given batch number in E1EDL24-CHARG and serial number E1EDL11-SERNR. It's create IBD with out the given batch number and serial number.
    call function 'IDOC_INBOUND_WRITE_TO_DB'
        TABLES
          t_data_records    = gt_idoc_data
    *     T_LINKED_OBJECTS  =
        CHANGING
          pc_control_record = gs_idoc_contrl
        EXCEPTIONS
          idoc_not_saved    = 1
          OTHERS            = 2.
      IF sy-subrc = 0.
        APPEND gs_idoc_contrl TO gt_idoc_contrl.
        CALL FUNCTION 'IDOC_START_INBOUND'
          EXPORTING
    *       PI_INBOUND_PROCESS_DATA       = ' '
            pi_called_online              = 'X'
    *       PI_DO_COMMIT                  = 'X'
    *       PI_START_EVENT_ENABLED        = 'X'
    *       PI_ORG_UNIT                   = ' '
            succ_show_flag                = 'X'
    *       PI_PARTNER_OPTION             =
          TABLES
            t_control_records             = gt_idoc_contrl
    *       T_DATA_RECORDS                =
          EXCEPTIONS
            invalid_document_number       = 1
            error_before_call_application = 2
            inbound_process_not_possible  = 3
            old_wf_start_failed           = 4
            wf_task_error                 = 5
            serious_inbound_error         = 6
            OTHERS                        = 7.
        IF sy-subrc <> 0.
    * Implement suitable error handling here
        ENDIF.
      ENDIF.

  • Create delivery automatically when sales order is created but not invoice??

    Hi,
    I have a requirement where in, it should create delivery (also issue) automatically when i create sales order, but it should not create the invoice automatically. I am going to do the invoice manually from the delivery document. Can you suggest me how to do this??
    Thanks
    Ghanesh

    Hi,
      If the sales document type is not relavant for Cash sale and the document type is used globally in the business then if for some specific conditions like distribution channel or plant or for division if u want to carry out the immediate delivery creation and PGI, use the below user exits and Bapi's
    The below user exit is used to export the sales order details to capture the required checking cond such as sal org,dist ch,div,plant,etc
    Include MV45AFZZ
    FORM USEREXIT_SAVE_DOCUMENT.
    Include MV45AFZA
    FORM -USEREXIT_REFRESH_DOCUMENT.
    BAPI_ISAORDER_GETDETAILEDLIST
    BAPI_OUTB_DELIVERY_CREATE_SLS
    SD_DELIVERY_UPDATE_PICKING
    BAPI_OUB_DELIVERY_CONFIRM_DEC
    Regards,
    Gopal.

  • Intercompany billing has 2 line items referring to the same salesorder item

    Hi All,
    I am posting Intercompany billing documents using Idocs. I am using the standard function module that creates INVOICE IDocs, but these Idocs are failing with error text "Document contains same order item more that once".
    The problem lies here, the PO that is been used is a STO (Scheduling Agreement) and the inter company billing the line item has the same material repeated twice but change in the quantity field. So, when I am posting document using Idocs we come across a segment E1EDP01 which has your quantity, weight, line item number and other fields. This segment is getting repeated twice with two different outbound deliveries.
    So, I think the solution is a mixture of both functional and technical....
    So, what I am planning to do here is for this particular material when ever it comes across duplicate entries add all the quantities fields and other numerical fields in the user exit and then refresh the internal table and then enter new entries. This could be done, but I don't know what could be the functional implications if these changes are made.
    Request you all to let me know what exactly needs to done in order to avoid these scenarios.
    Raghuram.

    Hi Raghuram,
    I found a very important SAP Note 103051, details are below.
    An IDoc processed by function module IDOC_INPUT_INVOIC_MM (of category INVOIC01) must not refer to the same purchase order item in several invoice items. This is also valid if for a goods receipt-related invoice verification several delivery notes belong to the same purchase order item.
    Depending on the system settings and the situation, various error messages can occur (for example, FD240 'Order item ... selected more than once' or M8050 'Balance not zero: & debits: & credits: &').
    In this situation module IDOC_INPUT_INVOIC_MRM generates error message M8321 'Document contains same order item more than once'.
    For example, this situation occurs if you work with individual batch valuation and the SD billing document executes a batch split for different batches which belong to the same purchase order item and delivery.
    Other terms
    INVOIC, SAPLIEDI,  M8047, M8, 321
    Reason and Prerequisites
    This is because of the program design.
    Solution
    There is no solution for IDOC_INPUT_INVOIC_MM.
    Module IDOC_INPUT_INVOIC_MRM (only as of Release 4.0) for the logistics invoice verification can distinguish different goods receipts by means of the delivery note number. For this purpose, GR-related invoice verification must be active.
    Owing to this symptom, billing documents for single batch valuation with batch split cannot be settled in MM-EDI inbound processing. The settlement generates exactly the situation described (several invoice items for the same purchase order item). In this case, the only solution is to deactivate the billing of the batch sub-items in SD Customizing and to calculate the main item only.
    Hope this helps.
    Reward if helpful.
    Thanks

  • Order and Third Party Related Intercompany Billing

    Dear All ,
    I am facing a problem in creation of third party order relevant intercompany billing .
    We have created commercial invoice from one co. code , but not able to create interco. invoice on the other co. code .
    Error message while creation of intercompany billing : No open Billing quantity has been determined .
    In our organisation , two co. codes are used because under one co. code sales is booked and under other co. code plant is entered .
    Hence , there is an involvement of commercial billing ( order related ) and intercompany billing ( which is also order - related ) .
    Help which customisation needs to be changed / amended to resolve the issue .
    Thanks .

    Hi
    Check item category  <b>TAS</b> as  billing relevance  <b>F</b>if you do MI<b></b>GO and <b>MIRO</b>, you can bill the quantity
    Rectify whether the line item Updated with Reason for Rejection

  • Intercompany billing (sales) not reflecting in sales account 410001

    Hi,
         I need some clarification regarding intercompany sales process.
    My client is having two company code named 8500 & 8700.
    we have to sell 8700 material eg 870000 through 8500 plant 8501. For this requirement i configured intercompany sales.
    i have assigned my deliverung plant 8501 and distribution channel  to 8700 . Created Internal customer representing 8700 in 8500/01/01 sales area and assigned to 8700 sales organisation. Ordertype OR assigned to billing type IV.
    I created a sales  order from sales area 8700/01/01 with a customer 1920 and the dispatch plant is 8501.
    I did delivery , PGI and i did  normal invoice from 8700 company code to 1920 customer . sales account is reflected in company code 8700 ( g/l account 410001 in FS10N)
    then i did intercompany billing from 8500 to internal customer. accounting document is generated. But i can,t see it in 8500 company code under G/L account 410001  eventhough it has created with accounting document in 410001.
      Please tell me where this account is moving
    Edited by: Mohamed.Naseem on Jun 22, 2010 12:53 PM
    Edited by: Mohamed.Naseem on Jun 22, 2010 12:54 PM
    Edited by: Mohamed.Naseem on Jun 22, 2010 12:54 PM

    So Mohamed, So it is posting to right account and you can see the Accounting document. But when you display the account balances, you don't see the Accounting Document there? Is that the issue?
    What T code are you using to display the account balances? Also describe briefly what you are doing after entering the transaction?

  • System is showing Bill Doc No in VF01 but in VF02 - No billing doc generate

    While creating invoice using Billing Plan, only for certain contacts,  we face an issue. In VF01-The system is saying Billing document XXXXXX123 is created but in VF02 , we are not able to see any document and the system says No billing document is generated for the same document no.
    The error message in Inbox says : Update was Terminated.
    Kindly tell me how to go about. Is this pertains to any authorization related issue. or is there anything which is wrong?
    Regards,
    Mahe

    In Output Procedure V10000 control - Requirement 62-Billing Doc : Release Post. is assinged to the Billing output type.
    Does this influence the Invoice creation  - When we are trying to create invoice , system is giving a billing doc no and in vf02 it is saying the bill doc does not exist. The error message in Inbox says : Update was Terminated.
    Is there any link between the two.
    Thanks,
    Mahe

  • Automate creation of Intercompany billing document

    Hello All,
    We have a requirement to automate the intercompany billing document to be created whenever F2 billing document is created ( without using VF04).
    Any input regarding this will be greatly appreciated.
    Thanks,
    Nagaraju

    After goods issue has taken place, you can process the delivery for billing. You can create the billing documents just like any other billing document on the Billing screen:
    for a single billing document with the menu path Billing document ---Create.
    for several billing documents with the menu path Billing document -
    Billing due list.
    The delivery may have to be processed for billing twice.
    The delivering plant processes the delivery to create an intercompany billing document (billing document type IV) for the selling company. This company code posts invoice entry for this billing document.
    The billing document is automatically billed to the internal payer that is assigned to the sales organization. The intercompany charges that appear in the intercompany billing
    document represent the actual amount that the delivering plant is charging the sales organization.
    If the selling company is selling the goods to a customer, it processes the delivery to create an invoice for this customer. The system can take the prices from the order or determine new prices. It takes the quantity to be invoiced from the delivery.
    The billing due list for the intercompany invoice is generated after the customer invoice has been created.

  • 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

  • Intercompany billing IDoc error

    while posting AP the IDoc was not processed and throws the below error:
    "No reversal possible. Reverse value must be reset
    Message no. M8283"
    intercompany invoice was created previously for the same delivery no. and was posted successfully. there wasnt any issue in cancelling the invoice as well. but when trying to create an IV invoice again, its throwing this error.
    please advice.

    Check OSS Note 730853 - MRRL: M8283 Reverse value must be reset
    Regards,

  • Create Intercompany billing without Good Issue

    Hi Gurus,
    I use Cross Company purchasing process with One step configuration. Normally it's used to be like this:
      1. Create Outbound delivery with reference to PO (t.code VL10B)
      2. Post good Issue --> automatic generate GI & Good Reciept document
      3. Create Intercompany billing with reference to the Delivery above.
    But now I want to go directly from step 1 to step 3 that means I want to create Inter. Billing with reference to Delivery which has not been post Good Issue. What should I do to solve this problem?
    Thank you very much,
        Hong Trinh

    Hi,
    You need to initially decide if you want to go with Cross company STO process through Purchasing or Intercompany Sales/Billing through Sales.
    Directly going from step 1 -3 is not possible.
    Only after you do a GI from the replenishment delivery and GR at the receiving plant will you be able to create an Invoice.
    If you are going with the Intercompany billing process, the sold to party/ship to party in your delivery should be the internal customer/plant and not the external customer. In this case you first need to create a F2 invoice and then IV invoice.
    Regards,
    Amit

  • IDoc created with status 03 checked via we02, but couldnt find in XI

    Hi all:
        Could you please do me a  favor?  implement a idoc to idoc issue. it has been created successfully .
    as It is found that the idoc created with status of 03 -
    data dispatched to  port ok (rather than 12 dispatch ok). however, I couldn't find  it via SXMB_MONI on XI,  there must be something wrong . coudl you please give me a hint ?
        Thank you very much!!!

    hi,
    you need to check transaction SM58 (remove the user from it) and F8
    it might be the reason that you didn't create a port in IDX1 on XI/PI
    but you will see that in SM58
    Regards,
    Michal Krawczyk

  • SD How to create IDoc once Sales Order Invoice (Billing) has been created ?

    Hi,
    How to create IDoc once Sales Order Invoice (Billing) has been created ?
    I.e Once you click on save button of Invoice , IDoc Should genrate Automatically.
    Thanks

    Hello,
    Go to T.code VV31 and select the billing output type and select the access sequence required and in the details screen of create condition records give all the required entries for eg: may be Billing Type, Sales Organsiation etc.and in the medium choose the option as 6(EDI) and time select as 4 that is immediately after saving the document.Also please ensure that particular partners for whom idoc should be generated they need to have partner profile setup with the billing message types. Hope this helps.

  • How to create IDoc once Sales Order Invoice (Billing) has been created

    Hi,
    How to create IDoc once Sales Order Invoice (Billing) has been created   ?
    I.e Once you click on save button of Invoice , IDoc Should genrate Automatically.
    Thanks.

    Hi,
    We need to do custom configuration for this scenario such that an output type will be attached when ever an INVOICE is created.
    Refer to application V3 in NACE. The Output type should contain an entry with transmission medium: Distribution (ALE).
    for example check the customization done for an output type in NACE.
    Goto NACE ---> Select an application V3 ---> Click on processing routines ---> select the output type (Eg: RD00) ---> Click on Details button  (CNTRL + SHFT + F2) which gives the configuration info.
    For example we can generate the IDOC based on the settings in partner profiles for the customer (Sold To)
    With Regards,
    Dwaraka.S
    Edited by: Dwarakanath Sankarayogi on Jan 29, 2009 8:16 AM

  • Employee created by Idoc. But Action 0000 IT not replicating in IT 302

    Hi Experts,
                   I need to create new employee using IDOC (HRMD_A06) IT 0000, 0001, 0002. Its getting created but its not upated completely I can not view in "overview" and the data is not reflecting in ADditional Actions and IT 302. If I create manully, its getting created completely in pa30.
                   Please respond ASAP.
    Regards,
    Jyoti Shankar
    Message was edited by:
            jyoti shankar

    I think you are using APEX4.0. So maybe this question is better asked in the APEX forum (Oracle Application Express (APEX) However it is also a PL/SQL question. So let me comment on that. I don't think your function has the problem. You mentioned that i worked before you made it into a dynamic action.
    This is the error message:
    ORA-06550: line 7, column 1: PLS-00372: In a procedure, RETURN statement cannot contain an expression
    So question 1 would be: Is your function valid? The error message indicates that you are calling a PROCEDURE and not a function. How do you reference the function in your Apex-Dynamic action? Should be something like:
    return d_date(:p8_priority);But maybe you need it without the RETURN
    d_date(:p8_priority)2. comment:
    you should try to avoid direct references to page items insider your procedure. Therefore I wouldn't call the IN parameter p8_priority but something else like "p_priority". Just to avoid confusions.
    3. What I don't understand is how you set the DUE_DATE field. Maybe the action is on the wrong field?
    4. You mentioned that the insert is not working. There is no database insert in the function. If you refere to the returned value, then don't say insert. Say something like: The item is not populated with the date value from the function.

Maybe you are looking for