Inter company billing, client and company code

Hello,
In inter co billing, the selling sales org and the delivery plant both belong to different company codes.
my questions are :-
1) Assuming my sap  production  system id is XBI, do  both the company codes need to exist in the same production system Id  XBI  for inter co billing ?
2) if the delivery plant system id is different than XBI, then the delivery of goods from the delivery plant will qualify for inter co billing or third party sale ?
3) Can two different companies  working on SAP have the same clients  (for eg if Hindustan Unilever and Colgate Palmolive) on SAP)
regds

1) Assuming my sap production system id is XBI, do both the company codes need to exist in the same production system Id XBI for inter co billing ?
YES
2) if the delivery plant system id is different than XBI, then the delivery of goods from the delivery plant will qualify for inter co billing or third party sale ?
Can be inter company provided Delivery Plant is also in XBI. Else I think Third Party scenario gets applicable
3) Can two different companies working on SAP have the same clients (for eg if Hindustan Unilever and Colgate Palmolive) on SAP)
YES
Regards
Sai

Similar Messages

  • Inter company billing use and steps?

    Inter company billing use and steps?

    INTERCOMPANY 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:
    1)     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.
    Configure Intercompany Stock Transport Order
    Material should exist in both the plants (Delivering  & Ordering),
    Internal customer should be assaigned 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 assaign the supply source ( Delivering Plant).
    Create a puchase order ME21N ---> Save
    Delivery VL10 G ---> Calculation rule (appropriate) --> Assaign 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

  • Can we create two different Segments at client and company level

    We have a particular requirement in segments reporting. we have to provide product wise segments reporting at client level and for income tax purpose one of our manufacturing plant has to maintain a separate books of accounts for this purpose we want to create a separate geographically at company level of this plant which is in different state. can we create this type of segments for separate books at company level.
    If there is any other process where we can get separate books of accounts.

    Dear,
    Of course you can do this but only worrysome thing will business users will be confused between the Plant and product line business segment.
    You must have Product Line (for e.g. segment 1000) is manufacture at plant 1000 (segment 2000), so when any expense occur in Plant 1000 for Product Line 1000 which segment should be used???
    So give precedence to segment whichever you want......and costantly monitor entries being posted to thses segment...
    Regards,
    Chintan Joshi

  • Inter company Billing - for service

    Dear SD Experts,
    My client has 2 company; that are,
               Company 1000 with sales org 1000      and
               Company 2000 with sales org 2000
    A customer placed order by company 1000. How can I create an order by company 1000 and an invoice it directly to Customer; however, I would like SAP create inter-company billing automatically between company 1000 and company 2000?
    <u>P.S.</u> Our client's business are service, he dose not has any sell stock.
    Great Thank for any idea and configuration document,
    [email protected]
    Prach

    Dear Prasanth,
             Sorry for make you confused. Clearly customer placed an order in company code 1000. However, company 2000 will take this service. Thus, customer will recieved invoice from company 1000. And company 1000 will recieved invoice from company 2000.
              Actually, "I don't have any problem in crated order by company code 1000"; but <u>how can I get other invoice automatically</u> (invoice from company code 2000 send to company code 1000) after I create invoice from company code 1000 to customer.
    Best Regards,
    Please share an idea or any configuration document about inter-compnay
    Prach

  • Inter company Billing for service industry

    Hi,
    I never workded over inter company billing.Please suggest me what to do? I am in a service industry project where no delivery takes place.So how should i go about for intercompany billing configuration?
    Thanx in advance.
    Regardds,
    Satya

    Dear Satya,
    You can create the inter company bill with refrence to the service order
    To do inter company billing settings go through this IMG path
    IMG>Sales and Distribution>Billing-->Intercompany billing
    Process steps for normal inter company process with delivery.
    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.
    In your requirenment there will not be delivery process in between service sales order and the intercompany bill so do the settings accordingly in the copy controls between service sales order type and inter company billing type.
    I hope this will help you,
    Regards,
    Murali.
    I hope this will help you,

  • Client Level & Company Code Level Settings.

    Hi
    Which are the Settings in SD are At Client Level & At Company Code Level.???
    I know that Batch management & Serial number profile is at Client Level.
    Regards,
    Amol

    Hi
    SD strat with Sales Organization assign to company code, next is Distribution channel and Divisions, combination these 3 called as sales area. next is sales offcie and sales groups.
    Client and company codes top most level in SAP and Company code defined in FI.
    Batch mangement activate at Plant level and warehouse level, settings need to done on Material master and plant level not at company code level, but plant assigned to company code.
    Same as Serial number profiles related to Plant and Material master, again here plant is link to company code and material created under plant.
    So, no where direct link to Company codes.
    hopes it helps
    thanks
    Satish

  • Inter company billing - how to post to GL accounts and not sub-ledger

    Hi,
    During Inter company billing, instead of creating Inter company customer and vendor invoice, there is requirement to post to Inter company GL accounts. How do we tweak the system to post to Inter company GL accounts instead of IC Customer/ Vendor?
    Thanks,
    Mukul

    Use t-code OBYA and instead of vendor/customer accounts use GL Accounts.  This should help you post directly to GL versus Customer/Vendors. 
    Dan

  • Inter company stock transfer and billing

    Dear all,
    can anyone please tell me the process steps of inter company billing and stock transfer?
    plzz provide the links if possible.
    thanx...
    Deepak....

    Dear deepak,
    Stock transport order config settings:
    .Create a vendor for the company code of receiving plant, using account group :0007 using T-Code XK01.
    2 Assign this vendor to Delivering plant
    Go to XK02 >Purchasing view>Extras>Add. Purchasing data>Plant
    3. Create internal customer with the sales area of the vendor. Go To XD01
    4.In Pricing procedure determination relevant to STO, assign document Pricing Procedure and customer pricing procedure appropriate for STO to get the pricing in the invoice.
    5.Maintain condition records for the relevant pricing condition.
    6. Some more setting for STO: Go to MM> Purchasing > Purchase Order > Set up STO> define shipping data for plants > Go to Receiving plant >assign customer here & Supplying SA (for billing) to Receiving plant here
    7. Go to MM> Purchasing > Purchase Order > Set up STO> define shipping data for plants > Go to Supplying plant and assign the sales area of receiving plant.
    8. Go to MM> Purchasing > Purchase Order > Set up STO> assign delivery Type & Checking rule
    Assign the delivery type to document type. In this case, Delivery type NLCC is assigned to Document type NB
    9. Go to MM> Purchasing > Purchase Order > Set up STO>Assign document Type, One step Procedure, Under delivery tolerance
    Assign the document type NB to supplying plant and receiving plant
    10. After all settings , Create the STO using T-Code:ME21n and Save.
    11. Create Delivery :VL10G
    Click on the Background Button after selecting line item
    A message is flashed : See log for information> next Click on Log for delivery creation Button >click on line item>click on document button to get Delivery document No
    12. Picking, PGI:[VL02n
    13. Billing:VF01n
    Save the document and its done
    Hi
    Follow the below steps to to make STO between two plants ( different company codes).It is also called as Inter Company STO.....
    1)Create one Customer Master in XD01 with respect to Supplying Plant Sales Area and assign this Customer no with Receiving Plant in OLME->PO-> set up STO->Define shipping data for plant and for the supplying Plant assign the above sales area.( Make sure,In Customer Master,sales Area Tab: you are
    2) For Receiving Plant Pur. Org and Co.Code Combination create Vendor master in XK01 and in this vendor master assign the Supplying plant in Pur.Org.Data screen->Extras--> Add.Pur.data
    3) OLME->PO-> Set up STO------>For your supplying plant assign document type NB, Delivery type NLCC and Checking Rule RP
    4)then For your supplying Plant and receiving Plant assign Document type NB
    5)Make sure you are maintaining Sales View for the material at supplying Plant and in Sales /Gen plant Data view maintain Availability check, Loading group and Transportation group.
    6) In SPRo-->Logistics execution> Shipping->Basic shipping functions->Shipping point Determination>assign shipping points-> For your Loading group,Shipping Condition and Supplying plant combination,Assign shipping point
    these are the configuration settings you have to do in background.
    Then Create STO from Receing Plant in ME21N with document type NB.
    Based on that STO, Create Delivery in VL10B from supplying Plant
    Do PGI in VL02N from Supplying plant
    Do GR in MIGO at Receiving Plant keeping Outbound delivery as a ref. document.
    Now your STO bet. two plants belongs to diff. Co.Codes will be completed.
    2)Follow the below steps to to make STO between two plants belongs to same company codes).It is also called as Intera- Company STO.....**
    1)Create one Customer for Supplying Plant Sales area and assign this Customer no with Receiving Plant in OLME---> PO -
    > Set up STO -
    > define Shipping Data for plants. and maintain the same sales area in your Supplying plant.
    2) In OLME---> PO -
    > Set up STO.....for your Document Type: UB and Suppying plant Combination assign Del. Type NL and Checking rule RP
    3) In OLME---> PO -
    > Set up STO...for your Supplying Plant and Receiving Plant combination Maintain Doc. Type : UB
    Make sure you are maintaining Sales View for your Material at Supplying Plant.
    4) Maintain Shipping point at, SPRO----> Logistics Execution -
    > Shipping -
    > Basic Shipping Functions -
    > Shipping Point Determination for Plants.....there for your Loading group,Shipping Condition, Shipping Plant combination maintain Shipping plant..
    Now Create STO in ME21N with Doc.type: UB at Receiving Plant.
    Then Create Delivery in VL10B from Supplying Plant...
    Then Do PGI in VL02N from supplying Plant.
    Then do GR at Receiving Plant based on Outbound Delivery at Receiving Plant...

  • Inter Company Billing and automatic booking to Vendor master.

    Hi,
    Wish you a Happy New year,,,,,,,
    We have done all the necessary configuration for generating Inter Company billing including the Cost booking to vendor Automatically.
    There are certain points where I need some help,
    1) During Idoc genration we are getting error related to Payment terms of Internal Customer.
    If the payment terms is immidiate then only an Idoc is getting generated,,,,,,,,, else it is throwing an error message " status 51", but according to our business requirements it may be for any days and this may also impact our aging analysis and cash flows.
    2) We have configured upto Third level of product hierarchy but while creating a contract if user maintains only upto first level, then release to account is not happening for inter company billing. Where as if user maintain upto third level there is no issue in the whole process of inter comapny billing.
    Kindly suggest us how to restrict user to maintain product hierarchy pto third level during the creation of contract.
    3) during the Inter company billing generation, if the internal customer is eligible for Tax exemption or tax booking, that is how to book the tax details to internal customer and also to vendor while booking the cost.Please let us know the logic for tax processign in Inter company billing and Idoc generation.
    Awaiting for a favourable reply and thanks in Advance.
    Regards,
    Upendra.

    Hello,
    Did you assign the internal customer to the ordering sales organisation? If not, then create a customer in Delivering Sales org + DC+ Div + Plant and assign the same in the ordering sales organisation.
    You can maintian the same in SPRO --> Enterprise structure --> Defenition --> Sales organisation (Enter internal customer).
    Or
    SPRO--> Sales and  Distribution --> Billing ---> Intercompany billing --> Define internal customer
    Prase

  • Client level setting and company code level setting

    Hi Friends,
    Can you tell me the client level settings and company code level settings in Configuration and master data?
    Ex : Material type configuration - client level
    Thanks in advance
    Rgds
    Madhavan

    Dear,
    For complete detailed information about SAP MM configuration, you can find on first thread or self exploration through net search.
    Please have a look at: http://help.sap.com/SAPHelp_46c/helpdata/EN/e0/71369adc56d11195100060b03c6b76/frameset.htm
    Regards,
    Syed Hussain.

  • Inter company and intra company billing

    Hi Dina,
    Can you please explain the difference between inter and intra company billing and under what condition which one can be used?
    Thank you.
    Deborah
    Edited by: user4461879 on Mar 2, 2011 7:16 AM

    Hi
    Intercompany billing is done when both organizations, the provider and receiver organizations, are within the same operating unit.
    If organizations are in different operating units, you would be using intercompany billing.
    Oracle Projects cross charge functionality is quite different with those two scenarios.
    Cross charge within the same operating unit is called Borrow-and-Lent. This process generates journal entries for both organizations, sent to the same SOB. There are no AP and AR internal invoices involved with that.
    When you need to cross operating units, there are additional setup steps, like creating an inter-company projects for each one of the parties.
    Dina

  • Error while creating Inter-company billing document

    Hi All,
    Help me to solve below error while creating inter-company billing document with ref to delivery document.
    " 1190984113 000000 Company code is not defined"
    Thanks for your help.

    Hi
    Please check wheather Customer has been extended to both company codes.Also check wheather 1190984113 is a G/L account.If it is a G/L account please check wheather it has been maintained in the company code or not.If it is not maintianed then kindly maintain the G/L account and then create the Intercompany billing document
    Regards
    Srinath

  • Inter company billing problem

    Dear All
    I need have get the favour from any expert..Please help me.
    I tried to Create one inter company billing  but not possible and showing the below problem ...
    "No billing documents were generated, see log."
    I had made Sales order: 9440010232, Delivery note: 9600011258, Invoice: 9800010604(VF03).
    Now, I need to create this by also VF01. Mentioned the problem I can not perform to create the Intercompany billing.
    Please any body help me.
    Thanks & B.Rgds
    Bishnu
    2906

    Hi,
    please check the inter company  config settings ..... assign ur order type to ur inter comapny  billing type ...  check one by one here is the notes.....
    In SAP sales & distribution module, an intercompany sales occurs when the selling organization belongs to a different company code than the delivering plant. The transaction path for accessing intercompany sales billing is:
    IMG >> Sales and distribution >> Billing >> Intercompany billing
    Let us take an example to understand intercompany sales better. Suppose there are two company codes namely 1000 and 2000. A customer may place an order for goods in sales organization belonging to company code 3000. However, the goods may be manufactured by a delivering plant belonging the company code 1000. A sales order is created indicating delivering plant of company code 1000. The sales organization then invoices the customer for the materials purchased. SAP R/3 automatically creates an intercompany billing document at the same time as the customeru2019s billing document is created. This intercompany invoice is sent from the delivering plant to the selling sales organization.
    As a rule of thumb, when dealing with different company codes, one may find a need to transfer stock between two different company codes. However, if the stock be transferred within the same company code, there is no need for an intercompany transaction. But in case the stock is transferred between different company codes, a transfer of value occurs and is an intercompany sale.
    Best regards,
    venkataswamy

  • Currency error during Inter Company Billing

    Hi,
    While doing Inter Company Billing I'm getting the error "Error determining local currency: ER type 'M' date 02.10.2009 from INR to  RC 4
    Message no. M2802"
    The error is coming only during Inter Company Billing. I have checked in transaction OB08 and correct exchange rate are maintained there.
    Any solution for the above error ?

    Hi
    You need to use  T.code OB08 and Maintain exchange rates with ER type M with starting date 02.10.2009 between currencies INR & RC4 .Then the problem will be solved.
    Regards
    Srinath

  • Inter company billing issue

    Hi,
    We have plant A and plant B. Plant A belongs to sales org  A and company code A and Plant B belongs to sales org B and company code B.
    we will book the sales order in sales org A but we want the  delivery plant to be B in sales order. My questions are:-
    1) In the config step of "organisational units by plant" for inter co billing, Do I need to assign the sales org A to plant B ??
    2) For determining plant B in sales order( to be booked uner sales org A), I will maintain plant B in customer master. Do I need to do some additional settings in config of  enterprise structure for determining plant B in sales order .i.e. in assigment of  enterprise structure , do i need to assign sales org A to plant B...? (in enterprise structure sales org A in any case will be assigned to plant A)
    3) In the config step , define " internal cust no by sales org". Which is the sales org for which i assign the internal customer   and under which sales org should I create the internal customer for plant ?
    regds
    Edited by: sapsd73 on Aug 23, 2010 12:29 PM

    Hi,
    Check the following links
    [IC1|Re: Inter-company sales process;
    [IC2|http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBIL/SDBIL.pdf]
    [IC3|http://help.sap.com/printdocu/core/print40b/EN/pdf/sdbil/sdbil.pdf]
    [IC4|Re : Problem with InterCompany Sales Configuration;
    Hope this helps.
    Regards,
    Amit

Maybe you are looking for