Intercomany Sale

[Former Member]

hi all

i want to know what is Intercomany Sale and in what scenerio it is used and how to to config for this scenerio.Plz explain the SPRO settings also.

cheers

shalsa007............

[Former Member]

Hi

An inter company sales tranction occours when a sale occurs and selling sales orgnisation belongs to different company code then that of the deliverring plant.

1) first you have maintain two legal entites under one company. which means under company two company codes.

2) each company code maintain sales area customer material and do the pricing determination.

3) material must exist both the plants sold and delivering plants.

4) copy control you have to do such OR and F2and OR and IV.

5) now you go to the path spro -sd- billing intercompany billing .

6) assign order type to inter company blling.

7) assignorg units by plants .

😎 assign internal customer by sales orgnisation

9)special condition types have to be maintained PI01 or PI02 in delivering sales orgnisation.

i hope you have understood.

if your doubts is clear don't forget to reward.

thanks

surya

[Former Member]

hi

here is the required configration settings

Cross-Company Sales

1.) Assignment of a sales area to intercompany billing for the delivering plant

--> Sales and Distribution --> Billing --> Intercompany Billing --> Assign Organizational Units by Plant

2.)Maintenance of assignment between sales organization, distribution channel, and supplying plant

--> Enterprise Structure --> Assignment -->Sales and Distribution -->Assign Sales Organization - ->Distribution Channel ---> Assign Plant

3.)Assignment of a customer to the sales organization

--> Sales and Distribution --> Billing  Intercompany Billing -->Define Internal Customer Number by Sales Organization

4.)Maintenance of billing type for intercompany billing in the sales document

--> Sales and Distribution --> Billing --> Intercompany Billing --> Define Order Types for Intercompany Billing

5.) Maintenance of settings required for automatic posting to vendor account

--> Sales and Distribution --> Billing --> Intercompany Billing --> Automatic Posting to Vendor Account (SAP-EDI)

hope this will make u understand

reward points if helpful

thanks and regards

ravikant dewangan

[Former Member]

hi

see the senario below :

company code 1000 : ( sales org 1000 and plant 1200)

company code 2200: ( sales org 2200 ) .

customer 2500 .

 When the goods in the purchase order have been ordered by the customer, you enter a sales order in sales organization 2200. This belongs to the so-called ordering company code (company 2200).

 The plant from which the goods to be delivered are taken is referred to as the delivering company code (company 1000).

 As soon as the order is due for delivery, the delivering company creates the outbound delivery. The goods issue is posted at the end of the shipping activity, and the goods are delivered to the customer.

 Afterwards, the invoice for the end customer is created in sales organization 2200, that is, in the ordering company code.

 In order for inter-company billing to take place between the two companies involoved, the delivering company issues an internal invoice, through ist sales organization 1000, to the ordering company.

 Depending on the agreement between the two connected companies, the entry of receipt of invoice may take place automaticaly. If not, the received invoice is entered manually in the financial accounting system of the ordering company.

1 .) create sales order :

 The process for cross-company sales processing is initated when standard sales order is created.

 In a sales order, the system determines the delivering plant for each order item, or this data is entered manually by the processor.

The system can propose the delivering plant from the following master records (sequence according to priority):

 Customer-material info record

 Customer master for goods recipient

 Material master

 If the delivering plant in the order item belongs to a company that is not in the sales organization creating the order, the system recognizes that this is a cross-company sales activity.

 When you create the order, the system checks whether the combination of sales organization, distribution channel and delivering plant is allowed.

 Depending on the sales organization, the plants allowed for sales activities are defined in connection with the distribution channel. Here it is possible for a sales organization to sell goods from several plants. Conversely, a plant can be assigned to several sales organizations.

 In Customizing, a plant is uniquely assigned to one company code. A sales organization, too, belongs to exactly one company code.

 Sales organizations and plants assigned to one another do not have to belong to the same company code. Otherwise, cross-company sales activities would not be possible.

 The distribution channel provides a further means of differentiation of plants in a sales organization from a sales viewpoint. A distribution channel, for example, can be allowed for certain plants within a sales organization, but not for others.

 In the order itself, the system automatically executes pricing, whereby the stored condition master data is evaluated.

 Condition type PR00 specifies the price that is billed to the customer. This price appears, possibly with surcharges and discounts, in the invoice for the customer, provided no change has taken place in the meantime. This price, therefore, stands for the revenue.

 For information purposes, instead of the moving average price for the material you have the price that the ordering company has to pay to the delivering company (price for intercompany billing). It will be relevant for intercompany billing and represents the costs of the ordering company.

 To represent the internal price, there are 2 condition types in the standard system:

­ PI01 (quantity-dependent)

­ PI02 (percentage)

­ Condition records are entered in connection with the sales organization entering the order, the delivering plant, and, if necessary, the material.

 The amount for intercompany billing appears on the condition screen of the sales order as a statistical value (it is only displayed, and has no effect on the pricing results for the customer).

2.) excute shiping activety :

 The shipping activity is initiated as soon as the outbound delivery has been created. This can take place with the help of the standard collective processing function for delivery of orders due,or with explicit reference to the sales order.

 As a rule, the outbound delivery is created as soon as the first workstep in the shipping process is imminent.

 The individual worksteps in the shipping process (picking, packing, printing the delivery note, and so on) are executed on the basis of the outbound delivery and also documented in the delivery.

 The outbound delivery is created and the shipping activities executed in the shipping point specified in the order. This shipping point is assigned in Customizing to the delivering plant.

 For picking purposes, a transfer order with reference to the outbound delivery is created. The list printout of the transfer order is given to the picker so that he/she can pick the required goods from the warehouse.

 Depending on the settings in Customizing, the pick may have to be confirmed (confirmation requirement). During this confirmation of the transfer order, you can enter possible quantitiy differences.

 If the goods are to be packed in shipping into larger boxes or placed onto pallets, for example, the appropriate information can be stored in the outbound delivery.

 Using the output control and output processing functions, you can print out delivery notes.

 The goods issue posting is the closing activity in the shipping process. Here a quantity and value update of the stock takes place.

3. ) create invoice invoice for end customer :

 The invoice for the end customer is created in the sales organization that created the sales order.

 Invoicing includes a reference to the outbound delivery. Here it is not of importance that the outbound delivery was taken from another company code.

 With the goods issue posting, the outbound delivery is automatically entered into the billing due list. The invoice is created either right away, or in a billing collective processing run.

 The goods issue date of the outbound delivery is the relevant billing date for the billing due list.

 The invoice for the end customer is a u201Cnormalu201D invoice. In the standard version, you can use billing types F2 or F1, whereby in the case of standard orders (sales document type OR) the system automatically used billing type F2 as the default type.

 In contrast to an internal invoice, the payer as well as the sales units and the company code are taken directly from the order.

 In the order, the company code was derived from the sales organization that entered the order. This is, therefore, called the ordering company.

4.) create internal invoice :

 For intercompany billing for the services rendered to the customer in sales organization 2200, the delivering company issues an invoice to the ordering company.

 The internal invoice is created by sales organization 1000. In customizing, you assign the sales organization responsible for inter-company billing to the delivering point.

 Likewise, in the case of an invoice to the end customer, the billing has a reference to the outbound delivery. You set the indicator u201Cintercompany billingu201D during the selection of the documents for billing.

 The outbound delivery is only entered in the billing due list of the respective sales organization of the delivery company when the invoice is issued to the end customer.

 In the standard version, billing type IV is used for the internal invoice. This is automatically proposed on the basis of the order.

 The payer of the internal invoice is usually the ordering company, which is like a customer with respect to the delivering company. For this you create a customer master record in the delivering company in which you enter the data relevant for billing. Afterwards, you assign the respective customer number to the sales organization of the ordering company in Customizing (field "Customer intercompany").

 The company code in the internal invoice comes from the company code to which the delivering plant belongs. It is therefore the same as the delivering company.

 In Customizing, you assign the sales area required for creating the internal invoice to the delivering plant (fields u201CSales organization IVu201D, u201CDistribution channel IVu201D, u201CDivision IVu201D). Make sure that the same settings are also used for stock transfer activities.

 The sales organization in the company code in which the sales order is generated takes on the role of the payer for intercompany billing.

 A customer master record must exist for the payer, in order that an intercompany invoice can be generated. This is assigned to the sales organization in the company code which delivers the order.

 A minimum of information must be contained in the customer master record. This information includes data that is relevant for the role of the payer (for example, address, reconciliation account). Also, you should store here the currency in which the intercompany billing is to take place.

 The company code data is created in the delivering company.

 The sales area data is entered in connection with the sales area for intercompany billing (sales organization IV, distribution channel IV, division IV).

 Condition type PR00 in the internal invoice displays the amount billed to the end customer. It serves as an information item and is inactive.

 The active price for internal billing is given by condition type IV01. It is determined by reference to condition type PI01 and therefore is the value that the delivering company has to receive from the ordering company.

 For the delivering company, condition type IV01 stands for the revenue. The costs are given by the moving average price of the material.

 In the internal invoice, the system uses a pricing procedure (standard version ICAA01) different from that in the sales order and the customer billing documents. Utilizing this, condition type PI01 is replaced by condition type IV01.

IV01, in contrast to PI01, is not marked as a statistical value.

 Through the reference to condition type PI01 defined in the definition of condition type IV01, you finally get the same condition values for both condition types. Here condition PI01 stands for the costs of the ordering company, and IV01 for the revenue of the delivering company. The use of different condition types for intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (component CO-PA).

 The determination of the pricing procedure in the internal invoice takes place in connection with the document procedure defined in the billing type, the sales area, and the customer pricing procedure stored in the customer master.

With the sales area you refer to the sales area assigned to the delivering plant.

5.) post invoice recipt :

 The invoice issued by the delivering company (company code) to the ordering company must be entered in the financial accounting of the ordering company code in order for payment to take place. This can be done manually.

 Cross-company sales processing can be set up so that the creation of an internal invoice in the delivering company automatically generates the creation of an incoming invoice in the ordering company.

 It is possible, for example, to have an agreement between the two parties involved that for invoices issued by sales organization 1000 to sales organization 2200 there is immediately a posting to the vendor account in the ordering company (company code 2200).

 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 upon, you must use the SD output control functions to ensure that output type RD04 is found in internal billing. In the R/3 System, output determination procedure V40000, which includes this output type, is assigned to billing type IV.

 The automatic posting to the vendor account is initiated when output type RD04 is processed. The technical conversion is carried out using the EDI technology. The EDI output category INVOIC is used in the F1 variant. For specifications on the required system settings (partner profiles, and so on), refer to the Implementation Guide for Intercompany Billing.

 So that the payable can be posted in financial accounting of the ordering company, the delivering company must be created as a vendor (vendor 10000).

regards

ravikant dewangan

[Lakshmipathi]

Please go thru this link

[Inter Company Billing|http://www.sapcustomization.com/document/InterCompany_Billing_IDoc.pdf]

thanks

G. Lakshmipathi

[former_member204513]

Hi 007,

Please go through this link it will help you about Intercomany Sale in SAP.

http://help.sap.com/saphelp_47x200/helpdata/en/dd/5614cd545a11d1a7020000e829fd11/frameset.htm

I hope it will help you,

Regards,

Murali.