Intercompany billing between 3 companies

Hi SD gurus
i am facing problem in configuring a unique scenario i.e. intercompany billing between three companies. I have to configure the below scenario in SAP :
Company code A gets an order from Customer, product delivery is from company code B to direct customer. As per standard SAP process Billing is from Company code A to customer and there is a intercompany billing between Company code A and Company code B. but in my case there is one other company code C involve in this process. due to this now intercompany happens between B to C and C to A. do we configure this in SAP standard scenarios ? if not can anybody suggest how can we do this ?
Deepak

Hi Terry,
We have done a very similar kind of scenario for our client. We have done it for 4 company codes. Actually, standard SAP can handle intercompany sales between only 2 compnay codes. So, this requirement (with 3 companies) calls for an enhancement. You will have to create a couple of Z tables to achive this scenario. First Z table to update the partner function and the second one for the selection of sequence in which the companies need to be billed. And you can use a BAPI (BAPI_SALESDOCU_CREATEFROMDATA) to create intercompany invoices from company B to C further automatically. Hope this gives you an idea to start the work. Let me know if you need any further help.
Regards,
Raghav

Similar Messages

  • Billing between companies

    Dear all,
    I need to configure SAP in order to be able to bill some services that are invoiced from one company code to another. I would like to keep it simple and also avoid work duplication. We have: company A invoicing value X to company B. This means a debit note is created in company code A for customer B and in company code B that value is registered as a cost in a document.
    Can i reproduce this process through intercompany (because there are no materials or stock)? Should i use idocs? Can anyone give me some tips?
    Thank you!
    Best regards
    Joana Trigo

    Dear Murali,
    thank you very much for your answer. I've already looked for that option but these operations include VAT and that process doesn't work well: 1st, because it considers VAT amounts in a single company and afterwards we have to run a report (report RFBUST10); 2nd, because of the following: imagine that for company code A you want:
    50     profit account (7214000)                 u2013 net value
    50     VAT account (2433100)                  - vat
    01     Customer account (company B)        net value + vat
    that corresponds to a posting for company code B like the following:
    40     cost account (6221120)                     net value
    40     VAT account (2432300)                     vat
    31     Vendor account (company A)         - (net value + vat)
    If you do like mentioned the system will create 2 documents, one for A another for B like this:
    A:
    50     profit account (7214000)                 u2013 net value
    50     VAT account (2433100)                  - vat
    40     VAT account (2432300)                    vat
    01     Customer account (company B)        net value
    For company code B:
    40     cost account (6221120)                     net value
    31     Vendor account (company A)         -  net value
    So at the end, values posted to customer and vendor are net and not net+VAT as they should be.
    Best regards
    Joana Trigo

  • Intercompany Billing Credit & Debit Note

    Dear All,
    I have configured intercompany billing. Now i can able to create invoice for Supplying part to Ordering Party. This invoice creation without sales order na. So, if i want to create credit & Debite memo for supplying party to Ordering party how to create. Because here we are creating invoice wioth out sales order and creating with reference of delivery note. In this process sales order creation belongs to ordering party to customer. So where we can maintain Credit & Debit note for Supplying party to ordering party. I think when we create invoice can we maintain billing type as credit note? please suggest me to maintain Cr. & Dr Memo In Intercompany billing between Supplying company to Ordering company.
    Thanks & Regards,
    Anj

    Hithere,
    For intercompany stock transfer if you want to implement credit & debit memo in intercompany you need to reference credit & debit memo requests CR & DR or the returns order with delivery NL. You will define them in the sales area of the supplying plant. Then you maintain the copy controls from RE to G2 / D2 or CR / DR to G2 / D2.
    For intercompany sales, the customer returns the goods to the ordering plant. Not the supplying plant. Coz customer doesnot know from where the ordering plant brought the goods from. So in that case customer to ordering plant is standard returns process. Returns between the ordering & supplying plant is again like mentioned above.
    Regards,
    Sivanand

  • Intercompany billing issue

    Dear Experts,
    Intercompany billing between 2 company codes(existing under same company) in system. Let say, company 1100 is a customer to company 1600. Currently, when we create a billing in SD module (VF01) and posting to FI/CO, AR document will be created for Customer 1100 in company 1600. User for company code 1100 have to do manual entry for that incoming invoice in AP.
    Our requirement is , when we create billing and posted to FI, system have to create accounting document (AR) for company 1600 and AP document in company 1100 automatically for the same item and amount.
    Would appreciate if you could provide some suggestion on this requirement.
    Regards,
    N.C.Reddy

    Hi,
    It available in standard inter company scenario
    Configure Automatic vendor account posting  in
    IMG >> SD >> Basic function >> Billing >> Inter company billing
    Use out put type RD04
    Which will create IDOC document and post invoice verification
    http://wiki.sdn.sap.com/wiki/display/ERPLO/Inter-CompanyBilling-AutomaticPostingToVendorAccount%28SAP-EDI%29
    Kapil

  • Intercompany Billing -Error in Maintain Condition

    Dear All,
    When i am creating intercompany billing between Supplying company to Ordering Company....in invoice we have material price and marketing price....in pricing procedure Material price & Marketing price condition types also.....before creation invoive i have maintained condition records for IV01 Material Price and Zxyz condition for Marketing fees. After creation invoice i supposed to get both prices but marketing fees value is not coming in invoice. Even i maintained in condition types also. Please suggest me.
    Thanks & Regards,
    Vasu

    Hi Anjali
    The first thing is when u create Intercompany Invoice Why do u want the Marketing fees to appear.
    U must have maintained cond record for this in your customer's sales area. So when u create customer invoice i.e. delivery related, then I guess this cond type will appear.
    Hope u r using VF04 for creating Invoices.
    Hope this helps u.

  • Intercompany billing without many companies

    Hi,
    Is it possible to define intercompany billing without defining many Companies?
    How would that be done?
    We have a client request where they want intercompany billing within parts of their company. This for sure could be solved by defining many companies but that also would make things very complicated.
    At another client the intercompany flow is handled through CO but this is not applicable at this client.
    If anyone understand my question I really appreciate any feedback.
    Best regards
    Mattias

    Create 'Company B' as a customer in Company code A.(t-code FD01)
    To indicate that this is an inter company customer for Company code A, maintain the Trading partner field  in the control data of the customer master i.e 'Company B'. Here you give the Company ID of the Company code B.
    Similarly the vice versa i.e (create company A as a vendor in company code B + give the trading partner for vendor company A as the Company ID of company A.)
    Maintain 'Prepare Cross-company code transactions". Transaction OBYA for both company codes.
    The rest would be covered by regular transactions. Like the regular payment program would pick up any due and make payments.

  • Give me the Configuration steps  for intercompany billing and third party s

    Hi Gurus,
    Give me  the Configuration steps  for intercompany billing and third party sales and give me a brief description with examples.
    Regards,
    YSR

    Dear YSR
    Check the links
    [Cross Company Configuration|http://help.sap.com/bp_bblibrary/500/Documentation/J62_BB_ConfigGuide_EN_DE.doc]
    [Third Party Without Shipping Notification|http://help.sap.com/bestpractices/BBLibrary/html/J55_ThirdPartyWOSN_EN_US.htm]
    Third party order processing is as follows:
    Assume three companies X, Y and Z
    X - The company,
    y - The customer
    Z - Vendor
    When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.
    If he is procuring the goods, there are two methods that are generally followed:
    Method 1)
    After receiving the PO from Y, X creates a sales order against Y.
    Now at the same time he also creates a PO to a vendor Z to produce the goods
    Z produces the goods and supplies to X
    X receives the goods from Z
    Then X delivers the same goods to Y.
    After that X invoices Y and Z invoices X.
    Note : Here there is no direct/ Indirect relation between Z and Y.
    This process is known as Trading Process. and the Material here is created  with Material type HAWA.
    The other method is a Third party order processing method:
    Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.
    X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.
    Now Z supplies the material to Y and acknowledges the same to X.
    Z  will send a copy of delivery acknowledgement and invoice to X.
    After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.
    The next step for X  is to create an invoice and submit to Y
    Only after the invoice verification document is posted  then only X can create an invoice for Y.
    This is the business flow that is followed for third party order configuration.
    There are few steps that have to be configured to enable the system to function as mentioned above.
    Step1)
    If you are always followwing a third party process for a material then you have to create the material using item category group BANS.
    The procument type should be marked as External procurement (F) in MRP 2 view of the material master record.
    if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurment ( in house manufacturing and external procurement).
    Step 2)
    the item category in the order should be manually changed as TAS.
    For that you need to confugure the item category determination
    ord type + item cat grp + usge + Hiv level = Item cat + Manual item cat
    OR + NORM +      +       = TAN . + TAS
    OR + BANS +       +       = TAS
    Step 3)
    make sure that during the item category configuration for TAS  you need to mark relevnat for billing indicator as F
    Step 4)
    The schedule line cateogry for this type should be CS.
    make sure that you mark  subsequent type as NB - purchase requisition  in this schedule line category as this will trigger the purchase requision order immediately after the creation of the sales order and the PO to vendor is created against this purchase requiesion.
    thanks
    G. Lakshmipathi

  • Intercompany billing - Returns

    Hello All,
    I have a standard intercompany billing scenario: there are three companies A, B and C with different company codes. Company C orders goods at company B (order created at company B), whereas company B inputs supplying plant from company A, which ships directly to company C. Then we have internal billing (IV) between A and B) and normal billing F2 between B and C. This is OK.
    Normal return process for this intercompany billing is also standard and OK.
    What about when we have return first from C to B (I guess standard return process) and then from B to A (where A and B are on the the same SAP installation/system)??? I guess there cannot be standard return order (with reference to IV billing) with return delivery and credit memo from A to B, because we need goods issue and invoice receipt at B. We cannot have a STO with billing (as we need a reference to the original IV internal invoice).
    Anybody can help me with this scenario? Any help will be highly appreciated.
    Regards,
    Smoczek23

    Yes, we had tried that, and just to be sure I just re-tried it myself, changing the sales office at the header level of Sales order, but still nothing has changed against the Invoice. What we did not want to do was cancel all the documents back to the sales order and then re-create. We have about 500 document/items to be changed, so that would take simply ages.
    Are we up a creek without a paddle do you think?.
    Jas.

  • Intercompany Billing - the scenario

    Hi Gurus,
    What are the different situations and scenarios which lead to intercompany billing in real time...
    1. does shortage of a particular product - which incidentally also exists in supplying plant of another company code; -- lead to this scenario?
    or
    2. can a complete absence of a particular product can lead to this scenario of getting a particular product from another company which is not produced by ordering company?
    please explain to me as I want to understand the logic behind extending the material of the supplying company to the ordering company, to show as if the material also exists in ordering company code...
    Thanks in Advance,
    Nazim.

    Dear Nazim,
    Scenerios, for Inter-Company Billing:
    is it like the company had a similar material and the material is out of stock
    and
    is it that intercompany....is done when the material wanted by the customer does not exist in our company at all?
    Definitely, YES.
    Company A is selling own goods, but also goods from other companies. These materials are stored in plants linked to other company codes.
    So an order can contain both materials belonging to company A as materials belonging to company B, reside in one logical system in the same client.
    Normal sales works fine, because after the invoice is created, the system also creates an Intercompany Invoice (IV).
    Best Regards,
    Amit
    Note: When dealing with different company codes, one may find a need to transfer stock between two different company codes. In case the stock is transferred between different company codes, a transfer of value occurs and is an intercompany sale (customer belongs to one company, stock in the plant to another).
    Intercompany Transactions between two different SAP systems
    Setup Idocs (you might use XI or other middleware) to handle the communication to load the IC transactions to the other system and vice-versa.

  • Billing Document not gettting generated in Intercompany Billing Scenario

    Dear Experts,
    I am trying to create Intercompany Billing Document with Billing Type IV, but unable to create the same. I have done all the necessary config. I am getting error as Sales Organization is not defined.
    I have created normal billing document i.e. Invoice for End Customer but now i want to bill the supplying company code. So when i try to create Invoice wrt Delivery Doc., I get the above error i.e. Sales Org. not defined.
    I have also maintained ordering company code as internal customer and maintained it for Supplying Company code.
    Am I missing something plz let me know.
    Thnx in advance
    regards,
    Sagar

    Hi Abhijit,
    the customer for the internal invoice will be determined from the "delivering" sales organisation (as mentioned above). You need
    to create a customer with exactly the same address of the sales organization. Assign this customer no. to the delivering sales organisation (as mentioned above). Is your delivering plant in US? That's what I understood according to your explanation in the thread.
    Your example
    Sales organisation: 2000 Canada --> Cust.No. 5000 Canada
    Delivering plant 3000 US --> Sales organisation 3000 --> Customer 5001 US
    Customer: 6000 Canada
    Sales order
    Customer 6000
    Sales organisation for sales order: 2000 Canada
    Delivering plant: 3000 US
    Delivery & Invoice to the customer (normal procedure)
    Internal invoice
    Sales organistion 3000
    Customer 5000 Canada
    --> The System needs to have assigned the billing sales organisation for the plant in US. Did You assign
    the sales organisation? Futhermore the customer no 5000 (assigned to the sales organisation 2000) needs
    to be maintained in the sales area of 3000 for the internal billing.
    (the internal invoice is maybe complicated caused by tax requirments - internal invoicing between Canada und US)
    hopefully this helps you.
    Regards
    Reini

  • Account determination error during intercompany billing invoice

    Hi experts,
    I am getting 'Account Determination Error' shows in red during 'intercompany' billing.
    I tried to release to accounting but didn't help.
    Pls advise
    Br,
    Umesh

    Hi Sushant,
    The error during the invoice creation. This document is for intercompany billing.
    I checked in Account Determination Analysis --> Revenue Accounts
    When I click on the Item no., it shows as 'No G/L account found in KOFI' & messege 121.
    In VKOA, there are few tables but I am not sure how & what to compare between these two.
    Br,
    Umesh

  • Order Related Intercompany Billing - Third Party Order

    Dear all,
    I have configured intercompany billing that is based on the delivery and i have done that successfully, then I tried the third party process but after billing the third party order then the intercompany billing doesn't show up in the vf04, I have searched the SAP Notes especially SAP Notes 63459 but I really haven't got the clue how to do that clearly, if somebody can help me how to configure the intercompany billing for my requirement. I'm using SAP 5.0. I believe something missing in the copying control between sales document and billing document and also for the output type.Please help me very urgent.

    hi,
    Customizing settings are reported in notes 338922, 109254 and 308989.
    During delivery creation the LIKP fields VKOIV/VTWIV/SPAIV/FKAIV/PIOIV/FKDIV/KUNIV must be filled in program FV50XFLK_LIKP_FUELLEN_IV_UML. If you checkt this table and not all of these fields are filled, you have the wrong the customizing. If the error is in your pruduction there is a report with which you can correct the relevant deliveries (of course after correcting your customizing): see note 176476.
    Balazs

  • Cross company Stock Transport with Intercompany billing

    hi,
    I'm trying to use the standard cross company stock transport order process, however, when i create the initail purchase order in the ordering company, the shipping tab does not appear, preventing me from creating a delivery. The customers and vendors have been assigned correctly. Can anybody help ???

    dear govender
    refer this
    STO PROCESS
    Stock Transfer Orders comes into picture when the stock is moving / Transferring between two different plants with two Different Company Codes or Stock Transfer between two plants with One Company Code the Difference are given below:
    P.O Order types and Delivery Types
    STO: - Stock Transfer Order – Intra Company
    Stock Transfer between Two Plants with One Company code.
    The Purchase Order Type is Used in this case is "UB".
    And the Delivery Type Used here is "NL".
    Goods Movement type: 641
    Item Category in delivery is NLN
    STPO: - Stock Transfer Purchase Order – Inter Company
    Stock Transfer Purchase Orders between Two Plants with Two Different Company Codes.
    The Purchase Order Type is Used in this case is "NB".
    And the Delivery Type Used here is "NLCC".
    Goods Movement type: 643
    Item Category in delivery is NLC
    A. Configure Intercompany Stock Transport Order
    Material should exist in both the plants (Delivering & Ordering),
    Internal customer should be assigned to the ordering plant ( MM -> Purchasing -> Purchase Order -> Setup stock transport order -> assign the internal customer to the ordering plant and assign the Sales area of the internal customer.
    Assign its Sales area to the delivering plant
    Assign the document type and Delivery type NB and NLCC
    Assign the Supplying plant --> Receiving Plant --> NB
    Take the delivering plant and assign the sales area.
    Vendor master has to be created and assign the supply source (Delivering Plant).
    Create a purchase order ME21N ---> Save
    Delivery VL10 G ---> Calculation rule (appropriate) --> Assign the purchase order number here and execute.
    Select the Delivery creation line and do the back ground process.
    Start the log display and see the delivery document number by the documents button
    Goto VL02N --> do picking and PGI --> Then do the MIGO with respect to the delivery document.
    Billing (Intercompany pricing conditions should be set).
    AND
    1. Customer No. for the Goods Receiving Plant - OMGN
    2. Availability Check- Checking Rule (if necessary) - OMGN
    3. Assign a Delivery Type for the Delivering Plant - OMGN (for Stock Transport Orders, NLCC)
    4. PO type (which i believe you have done) - OMGN
    5. Assign Vendor No. to the Supplying Plant (done) - VK02
    6. Assign Customer No. to the Purchasing Plant for the Inter-Company Invoice (but you need to assign this to the Sales Organization pre-assigned to the Purchasing Plant),
    IMG-SD-Billing-InterCompany Billing-Define Internal Customer No. by Sales Org
    ***and by the way for the Invoice to work between Cross-Company Plants, you need also to have a Sales Org for the Supplying Plant and a Pricing Determination Procedure
    INTERCOMPANY PRICING:
    PI01 Intercompany: fixed amount per material unit
    PI02 Intercompany: percentage of the net invoice amount
    These condition types specify that the price charged by the delivering plant to the sales organization is shown as a statistical value in the sales order and an effective charge in the internal invoice.
    The condition records you create and maintain for intercompany billing are the same kind of records that you create for pricing in general.
    IV01 Inter-company Price ERLOS Revenue
    IV02 Inter-company % ERLOS Revenue
    STO CONFIG:
    The following steps have to be followed in order to configure stock transport order between two plants.
    1. Create a vendor for the Company code of the receiving plant using account group 0007 via T-Code XK01.
    2. In the purchasing data view assign the supplying plant and the schema group
    3. Create customer with the sales area of the vendor.
    4. The shipping conditions, the delivering plant and the transportation zone determine the route in the STO.
    5. In the pricing procedure determination relevant to the STO assign document pricing procedure and customer pricing procedure to get the pricing in the invoice.
    6. Maintain condition records for pricing condition.
    7. Maintain carrier as a partner in the customer master.
    8. In OMGN select the supplying plant and assign the company code and sales area. Similarly select the receiving plant and assign the company code and sales area (The company code to which the plant is assigned to).
    9. Assign the delivery type and checking rule to the document type.
    10. And finally, assign the purchasing document type to the supplying plant and the receiving plant.
    11. Create the STO using T-Code ME 21N and save.
    12. Check for release strategy if any and release using T-Code ME 28.
    13. Create delivery in background using VL10G.
    14. If delivery is created, it is an indication of correct configuration and master data creation.
    Stock transfer between two plants in different company codes is known as inter company stock transfer.
    Material should be maintained in both supplying and receiving plant MM01
    Stock should maintain only in supplying plant MB1C
    Create receiving plant as a customer in supplying plants company code and sales area XD01
    Assign this customer number in receiving plant details OMGN
    Assign supplying sales area in supplying plant details OMGN
    Assign delivery type NB for in combination of supplying/ receiving plants.
    Create STO ME21N
    As it is normal there in the item details we should get shipping date i.e. customer number
    Go for Delivery VL10B
    Shipping point *****
    Select PO go for execute
    then select the delivery then go for delvy ............create delvy,,,, delvy number generated.
    Goods Issue VL02
    Delvy doc **********
    Click on picking
    enter the picking qty
    Click on PGI
    in the mean time check in the PO history you will get the details
    Goods receipt MIGO
    Stock overview the stock will be updated....
    Check the below link
    http://help.sap.com/saphelp_47x200/helpdata/en/4d/2ba31643ad11d189410000e829fbbd/frameset.htm
    Stock transfers that include deliveries and billing documents/invoices are only possible between plants belonging to different company codes.
    If you want to carry out a cross-company-code stock transport order with delivery but without a billing document, you must set the Relevant for Billing (data element FKREL) indicator in Customizing of the item type to "blank" (Not relevant for billing).
    The following applications are involved in this type of stock transfer:
    • Purchasing (MM-PUR) in entering the order
    • Shipping (LE-SHP) in making the delivery from the issuing plant
    • Billing (SD-BIL) in creating the billing document for the delivery
    • Inventory Management (MM-IM) at goods receipt in the receiving plant
    Invoice Verification (MM-IV) at invoice receipt in the receiving
    Transfer of goods from one location to another location, it may be between plants within the same company code or in different company code's plants.
    within the company code, but plants,
    receiving plant will raise the STO in Supplying/issuing plant-ME21n,
    Supplying plant will deliver the goods to receiving plants ,
    then we need to pick n post the Goods Issue-VL02n,
    now when we can observe that the STO qty will be added into receiving plant and reduced in Delivering plant,
    To do this, we need do prior customization in SPRO-IMG,-
    material should be created in both plants( receiving & Supplying)
    -maintain the stock only in supplying plant
    -create a dummy customer in supplying plant's sales area(if u have one sales area, create in tat comp code n sales area)
    -assign this customer number to receiving plant's details along with the sales area,
    -Assign the STO doc type(UB) to Supplying plant, along with checking rule
    -Assign the Del type (NL/NLCC) to Supplying n receiving plant.
    *Del type=NL is not relevant for billing, where as NLCC is relevant for billing
    rewards if it helps
    siva

  • INTERCOMPANY BILLING & Contract

    Dear guru
    what is mean intercompany billing & Contract? and give me the steps to config. in sd module.
    regards
    Mohammedrenu
    [email protected]

    INTER COMPANY BILLING
    Definition:
    A company arranges direct delivery of the goods to the customer from the stocks of another company belonging to the same corporate group.
    To put in simple terms, Company code A orders goods through its sales organization A from Plant B belonging to Company code B.
    It is imperative that both Plants A & B should have the material. In other words, the material is created for both the Plants A & B + their respective storage locations.
    Sales Organizations and Plants are uniquely assigned to Company codes. It is not possible to assign either a plant or a sales organization to more than one company code.
    Sales organizations and plants assigned to each other need not belong to the same company code.
    In other terms, a plant belonging to Company code A & assigned to Sales Organization A can also be assigned to Sales Organization B of Company Code B. This enables cross company sales.
    PARTIES INVOLVED
    1) End Customer 2) Ordering Company code 3) Supplying Company Code.
    End customer:
    Customer who orders goods from the ordering company code.
    Ordering Company Code:
    Which orders goods from Plant belonging to Supplying Company code through its sales organization and bills the end customer.
    Supplying Company Code:
    Supplies goods from its plant to the end customer specified by the ordering company code and bill the ordering company code.
    CONFIGURATION SETTINGS
    Assign Delivery Plant of the supplying company code to Sales Org + Distribution channel of the Ordering company code in the Enterprise Structure.
    DEFINE ORDER TYPES FOR INTERCOMPNY BILLING:
    Menu path: IMG/ SD/Billing/Intercompany Billing/Define Order Types for Intercompany billing
    Assign Organizational units by Plant:
    Menu Path: IMG/ SD/Billing/Intercompany Billing/Assign Organizational units by Plant.
    Define Internal Customer Number By Sales Organization:
    Menu Path: IMG/ SD / Billing/ Intercompany Billing/ Define Internal Customer Number By Sales Organization:
    Creating / Showing Ordering Sales Organization as Internal Customer for Supplying Company code:
    Transaction Code: XD01
    The ordering sales organization is represented as Internal customer of Supplying company code.
    We need to create customer master in Account Group - Sold to Party and maintain minimum required financial & Sales Area data.
    This internal customer number has to be assigned to the ordering sales organization. Hence, the system automatically picks up this Internal customer number whenever there is Intercompany billing.
    PRICING:
    We need to maintain two pricing procedures RVAA01 & ICAA01. Pricing procedure RVAA01 represents condition type PR00 & any other discounts or surcharges that are meant for end customer.
    We assign Pricing procedure RVAA01 to combination of Sales area (Of Ordering company code) + Customer Pricing Procedure + Document Pricing Procedure of Sales document type.
    This pricing Procedure (RVAA01) is determined both at Sales Order level & Billing processing for the end customer.We maintain PR00 condition type to represent the ordering company code's price to the end customer.
    Condition records for PR00 are maintained using organizational elements of Ordering company code, end customer & the Material.
    Eg: Sales Org. of Ordering company code + End customer + Material.
    We also need to maintain PI01 condition type to represent costs to Ordering company code (in other words revenue to supplying company code). It is statistical condition type & meant for information purpose only.
    Condition records for PI01 are created with the following key combination:
    Ordering sales Org + Supplying Plant + Material
    Pricing Procedure ICAA01is determined at Intercompany billing processing level.
    Pricing Procedure ICAA01 - Pricing Procedure for Inter company billing is assigned to the combination of:Sales Area (of supplying company code) + Document pricing Procedure of Billing document type IV + Customer Pricing Procedure of the Internal customer.
    Pricing Procedure ICAA01 has condition type IV01 that represents revenues for Supplying company code in the intercompany billing.
    PR00 condition type also appears in Intercompany billing document. It is for information purposes only and does not have bearing on the value of the document.
    PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
    The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
    Condition Type VPRS in the intercompany-billing document indicates cost to the supplying company code.
    The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
    ILLUSTRATION:
    STEP 1: Create Sales Order
    Manually Enter the Delivery Plant of the Supplying Company Code:
    OBSERVE CONDITIONS SCREEN FOR ITEM:
    PR00 represents Price to the end customer (in other words, revenue for the ordering company).
    PI01 represents cost to ordering company (in other words, revenue for the supplying company). It is represented as statistical item only.
    DELIVERY:
    Delivery is carried out from the supplying point & hence we can observe that it is done from shipping point assigned to the supplying point.
    Subsequently, Picking & PGI are carried out.
    BILLING TO END CUSTOMER:
    T-Code: VF01
    Create Intercompany Billing:
    T-code: VF01
    OBSERVE THE CONDITIONS SCREEN OF THE INTERNAL INVOICE:
    IV01 Condition type represents revenue for the supplying company code.
    VPRS condition type represents cost to the supplying company code.
    PR00 in intercompany billing document displays amount billed to the end customer. It serves as just an information item and is inactive.
    If the ordering company enters the incoming invoice manually, the delivering company can print out an invoice document with the help of output type RD00, which is then sent to the Payer.
    If automatic invoice receipt has been agreed, we must use the SD output control functions to ensure that output type RD04 is found in internal billing. In R/3 system, output determination procedure V40000, which includes this output type, is assigned to Intercompany billing type IV.
    The automatic posting to the vendor account is initiated when output type RD04 is processed. The system uses the EDI output type INVOIC in the FI variant.
    To ensure that payables are posted in financial accounts of the ordering company, the delivery company must be created as a vendor.
    <b>Contracts</b>
    Follow the links
    http://help.sap.com/saphelp_47x200/helpdata/en/06/57683801b5c412e10000009b38f842/frameset.htm
    Master Contract:
    The master contract is a document under which you can group contracts as lower level contracts. It contains the general terms which apply for all the lower level contracts over a specified period.
    Use
    You group contracts as lower level contracts under a master contract to ensure that
    The terms in the master contract are granted in all the lower level contracts
    The data in all lower level contracts remains consistent
    You can group the following documents under a master contract:
    Quantity contracts
    Value contracts
    Service contracts
    The link between the master and lower level contracts is controlled by the referencing procedure which is assigned to the master contract type in Customizing. The referencing procedure determines which data is copied from the master contract into the lower level contracts
    Structure
    A master contract contains header data only. In the master contract, you can record:
    Business data
    Partner data
    Contract data
    Billing plan data
    On the overview screen of the master contract, there is a list of all the lower level contracts which refer to it. You can branch from this list into the individual contracts.
    Master Contract: The master contract is a document under which you can group contracts as lower level contracts. It contains the general terms which apply for all the lower level contracts over a specified period.
    Check these links on Master Contract
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/55fd0d545a11d1a7020000e829fd11/frameset.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/55fd34545a11d1a7020000e829fd11/content.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/55fd27545a11d1a7020000e829fd11/content.htm
    Details about contracts:
    Lets take standard CQ contract type:
    First maintain customer - material info record in VD51 T-code
    Secondly maintain pricing for customer / material or only material combination in VK31 / VK11 T-code
    Then use VA41 T-code to create a contract
    VA42 to change contract
    VA43 to display / view contract
    In VA41, enter the document type CQ, followed by the sales area details,
    Enter Sold to party.
    Enter PO number
    Enter PO Date
    Enter Validitiy from Date
    Enter Validity to Date
    Enter Material
    Enter Quantity say 999,999,999 or any other higher quantity as it is referred again and again
    Hit Enter.
    Save.
    For further info refer below
    : CONTRACTS
    Contracts
    Reward if Helpful...
    Regards,
    Praveen Kumar D

  • Intercompany billing , standard billing from same delivery possible - customization

    Dear Gurus,
    I have a query  where i couldn't manage to get a proper reply from my peers, hence pondering this to the forum kindly help out.
    In a normal O2C cycle , when  standard billing gets created from delivery  then the cycle is tend to be complete and  if we try to create another billing  document we get an error " The document has already been fully invoiced"  which is appropriate.
    But in case of an intercompany billing document if we try to create another billing document from the same delivery type then we get the billing document  "IV"  created .
    Can you please let me know where does this setting exist ?  An earlier reply is of great help.
    Br
    Krishna.K

    To my knowledge the below are the two settings are important along with other inter company sales settings.
    1. in VOV8( for order type OR you assign inter company billing IV)
    2. In VTFL we maintain copy control between LF and IV
    thanks,
    Srinu.

Maybe you are looking for