Cross Company Customization

[Former Member]

Dear All,

Please let me know the customization part for Cross Company Scenario.

regards,

Ganesh Sabnis.

[Former Member]

Hi,

Go through the explanation given below with test cases.

Business case: -

Customer orders goods to company code/Sales organization A (Eg.4211/4211).Sales org 4211 will accept and punch the order in the system with sold to party as end customer code in the system. Company code/sales org B (Eg.4436) will deliver the goods to end customer and raise an intercom any billing on 4211 with reference to delivery. This can happen only after 4211 raises invoice to his end customer to whom the material has been delivered by 4436.

SPRO Customization required:-

1. Assign plant of delivering company code (Eg.SI81) to sales org/distribution channel combination of ordering company code (Eg.4211/RT)

2. Maintain intercom any billing type as IV for sales document type OR

3. Assign Organizational Units By Plant (Eg.SI81/4211/RT/11)

4.Define Internal Customer Number By Sales Organization (Eg.4436 will create customer master for 4211 company code and that number will be maintained in this relationship:-4211/231)

5. Automatic posting to vendor account (Optional)

6. Maintain pricing procedure determination for 4211/RT/A/1/RVAA01-For customer sales and billing

Maintain pricing procedure determination for 4436/RT/A/1/ICAA01-For intercompony billing

Master data to be maintained:-

1. Create end customer master in company code/sales org 4211/RT/11

2. Create customer master for 4211 company code/sales org in 4436/RT/11

3. Maintain PR00 as price for end customer-Active in RVAA01

4. Maintain PI01 as price which has to be paid to 4436-Statistical in RVAA01

5. Maintain IV01 as inter-company Price-Active in ICAA01

Process:-

1. Create OR with sold to party as end customer.

2. Plant to be selected is delivering plant belonging to different company code. With this selection system will treat this order as intercomany sales.

3. Pricing procedure is RVAA01

4. With reference to this order delivery will be created from the delivering plant and post the goods issue for this delivery.

5. Ordering sales org will create billing document F2 with reference to delivery for end customer.

6. Delivering sales org will create intercompany billing IV with reference to delivery document.

Inter-Company with Material Flow to Subsidiary:--

The main goal of this scenario is to offer small susidiaries/partners on demand the fast delivery of material centrally stored by the group. The ATP-check in the central distribution system provides the sales person selling locally with high delivery reliability. Therefore stock at the subsidiaries/partner sides can be reduced to the most frequently sold items.

Inter-Company with Material Flow to Subsidiary

SAP Business One at the subsidiaries / partners side is responsible for selling company products to the end customer. The availabilty of items, which are not located at the subsidiaries are being checked automatically in the central SAP R/3 system. The information about the stock situation of a central distribution center is stored in a central SAP R/3 system of the group.

In this scenario the customer is asking for a material, which is not available on stock at the subsidiary location. To provide the customer with a reliable information about the availabilty and the delivery date of the material, the sales person at the subsidiaries creates a quotation in SAP Business One. The quotation is automatically transferred to the SAP R/3 system in "real time". Here a quotation is created with reference to the SAP Business One quotation and an ATP check is executed. The result of the ATP check is transferred to SAP Business One system. Here the information is stored as an alert. In case the information leads to a sales process with the end customer, the sales person at the subsidiary creates a purchase order in SAP Business One to order the material from the central R/3 distribution center. This purchase order is being transferred to the SAP R/3 system, where a sales order is being created with reference. The process is continued with creating a delivery in SAP R/3, which leads to an Advanced Shipping Notification (in form of an alert) in SAP Business One. An outgoing invoice in R/3, which creates an incoming invoice with reference in SAP Business One closes the process. All changes on SAP R/3 or SAP Business One documents lead to changes in the reference document.

• = This business process is supported by Best Practices for SAP Business Suite. Best Practices for SAP Business Suite represent prepackaged business expertise in the form of methodology, documentation and reliable preconfiguration for SAP solutions. This helps you to start with a fully documented and reusable prototype for this scenario only days after you have installed the software. A prototype representing the results of a complete implementation project done up front and encapsulated in one single product that can rapidly turn into your productive solution. Best Practices for SAP Business Suite puts the power of SAP Business Suite in your hand.

http://www50.sap.com/businessmaps/iv_834CE219779E4642948985CF040F02E8.htm

http://www.iisales.com/sap/casestudies/balloon-2.pdf

Reward points if u helpful

Cheers,

Govind.

[Former Member]

Hi Ganesh,

Scenario – Cross Company Code Sales Order Processing

This scenario is made up of several building blocks, which contain the preconfiguration settings required for the Cross Company Code Sales Order Processing scenario. Building blocks can help you to implement the solution and put into production quickly.

Business View

The business view shows the business partners participating in the Cross Company Code Sales Order Processing scenario, the entire scope of the business processes, and the benefits for the parties involved.

A customer orders goods from the sales organization of his vendor. The vendor has a production/warehouse plant that belongs to a different company code. The goods are produced/contained in the different company code and delivered from the production/warehouse plant to the customer directly .

The delivery is billed twice: the first time, to create the customer invoice, and the second time, to carry out inter-company billing.

The customer pays his invoice by transferring the amount to the bank account. A manual account statement is posted, the open item on the customer’s account is cleared. The same occurs between the two company codes

Stock Transfer:

Purpose

In this scenario, a stock transfer is posted from one company code to another company code with delivery:

Function List

The following functions are provided to support the Stock Transfer - Cross-Company Code building block:

Stock transport order processing in receiving plant

Delivery processing in supplying plant

Picking batch determination in delivery

Goods issue processing in the supplying plant

Billing processing in supplying plant

Goods receipt processing in receiving plant

Invoice verification processing in receiving plant

Purchase order monitor processing in receiving plant

Key Points

You can control the stock in transit.

The issuing plant enters a delivery for the stock transport order and a billing document. This is an inter-company billing document (billing type IV).

During the stock transfer, two accounting documents are created in addition to the material document:

An accounting document for the removal from storage at the issuing company code

An accounting document for the placement into storage at the receiving company code.

http://help.sap.com/bp_bblibrary/500/Documentation/J62_Scen_Overview_EN_DE.ppt

Reward points if u helpful

Cheers,

Govind.

[Former Member]

Dear all,

I mean to say i want to know about intercompany Sales & Purchase Scenario.

regards,

Ganesh.