An intra-company-code delivery can only take place when the selling organization at header level of a sales document is assigned to a different profit center node from the delivering organization at item level, and the company code does not change. In this case you should perform a profit center settlement between the two profit centers. The intra-CC transfer price should by displayed in the sales order.

In this scenario, intra-company-code deliveries can become cross-system deliveries when the supplying plant is managed at item level in a different system than the sales system.

• SAP R/3 Enterprise Core
• PlugIn 2001.2
• SAP APO Rel. 3.0A

The following diagram shows a cross-system delivery (intra-company-code) between two SAP R/3 systems with a joint SAP APO.

1. You create a sales order in the sales order system. On the initial screen, choose the order type and organizational data.
2. On the order entry screen, enter the header data followed by the item data. You have two options:

1. Enter you own plant (plant in the sales order system)
2. Enter an external plant (from another SAP R/3 System within the business system group).

• To process items with external plants, you require an active integration model. There is an additional input option for external plants when you maintain the CIF model.
• You cannot use any discounts in kind.
• Configuration with external plants is not possible.
• You cannot use valuated or non-valuated sales order stock.
• Make-to-order production is not supported.
• You cannot make account assignments of costs or revenue from the sales order.
• Scheduling agreements for the component supplier industry (see also in the SAP menu: Logistics → Sales and Distribution → Sales → Scheduling Agreement → Create; with type LZ) and customer requirements (see also in the SAP menu: Logistics → Production → Production Planning → Demand Management → Customer Requirements → Create) are not supported for external plants.
• The indirect document flow is not available for any self-programmed evaluations. The SAP standard system is not affected by this.
• Immediate order are not possible for items with external plants.
• The batch management requirement must be defined across plants.
• Business area determination from plant-division (rule 001 in Customizing for business area account assignment) is not possible for external plants.
• Region, county, and city of the external plant are not used in rules-based ATP.
• Shipping points and storage locations cannot be defined for external plants, and can therefore not be made default values in the sales order.
• The factory calendar is not recognized for external plants in the sales order system. Within shipment and transportation scheduling (that can also be performed in SAP APO), the system takes into account the SAP APO calendar for the issuing location (plant). The work times/shifts of the shipping point are also not recognized. These can be mapped using the part-day maintainable SAP APO calendar.
• The customer number is not known for external plants, and can therefore not be used for material groups and any related pricing.
• The MRP type is not known for materials in external plants, and can therefore not be used for assigning and checking schedule line categories in the sales order.
• The item in the order must also have a requirements type for external plants (determination using the item category and the initial MRP type).
• The requirements from external plants are not visible in the sales order system (stock/requirements view).

4. When the order is saved in the sales order system, the order is transferred to the SAP APO system using the SAP APO Core Interface. In the SAP APO order network, requirements are also created for the items in this order that have external plants (no requirements are created for these items in the sales order system).

6. You save the order in the sales order system.

• The credit limit check in the order is only possible if the relevant data from the supplying system exists, i.e. goods issue data, statistics and so on. Cross-system statistics can only be realized using customer exits.
• Shipment and transportation scheduling must be active. Otherwise, you must subsequently maintain this data manually in the sales order.

14. An availability check is performed in SAP APO for the delivery. Any relevant changes are saved in the SAP APO system. Depending on the available quantity reported by SAP APO to the shipping system, the following processes can result in the delivery:

• Everything available
• Reduced quantity

15. The delivery confirms the delivery quantities to the sales order. The system then updates the status and document flows for the sales order.

16. You can perform all the follow-on functions, such as picking, packing, and goods issue as you would in the integrated scenario. All changes to the delivery are automatically reported to the sales order system.

17. The billing document is created with reference to the order. The billing document index is written from the confirmation of the delivery to the order, when the delivery is posted for goods issue. If information is required from the delivery in order to create the billing document, where this information cannot be determined from the document flow of the relevant order, a BAPI is called synchronously for the billing document in the shipping system. This BAPI determines the data relevant for the billing document. The system determines the delivery data or values from accounting, or defines conditions.

If you set your system up in such as way that the different plants are also in different company codes, then the delivery is relevant for intercompany billing.

The process described above changes, at the latest, when you post the goods issue in the shipping system and intercompany billing is triggered and sent to the sales order system for comparison.

The following scenarios will still be supported:

• Rule-Based ATP Check (SAP R/3 and SAP APO)