Import Order Master Data - Internal Orders
Application component: Overhead Orders
App type: SAP GUI
Description:  You can transfer orders automatically from external systems to the SAP system. Legacy data and external data is normally transferred to the SAP system as part of the implementation project in the IT department. 
Key features:  The system enters data from the external files into the data fields of the SAP internal orders that you wish to create. The procedure is similar to that for creating orders in the orders application. The option described in this section is an alternative to batch input. For the purpose of this data transfer, the SAP system includes the receiver structure OREXT. A corresponding sender structure must exist in the external system. All orders you want to create in the SAP system must exist in an external file with the same format as the sender structure. The external file must contain exactly one complete sender structure for each order (including up to three distribution rules). See also: Example of a Completed Sender Structure Order Settlement The field KONTY_n determines the settlement receiver (n=1,2,3). You can settle to the following receivers if you maintain KONTY_n as follows: Settlement ReceiversReceiver KONTY_n Conversion Exit Asset AN ALPHA Cost center KS  Cost object HP ALPHA Network NP ALPHA Order OR ALPHA Customer order VB ALPHA Project/WBS element PR KONPR G/L Account SK ALPHA  If you want to use fewer than three distribution rules, only maintain the KONTY_n fields you need. The company code (BUKRS) field in the distribution rule is not currently supported, but is present because it will be used in future releases. Therefore you need to leave it blank. The SCOPE field (object class) is two characters long in the OREXT (entries there are not language-dependent, for example, “OC” for overhead costs). For the purposes of the screen display, the system determines the language-dependent field content from the domain table for the SCOPE data element. The content is displayed with five characters (such as “GKOST” for overhead costs). In the case of order types for which the old order status management is active, you can use the ASTNR field to set the initial status. Otherwise, the system uses the default status. The same consistency checks are made for the automatic creation of internal orders as those made when you create or maintain internal orders in the SAP transactions. This means you must fill the same fields. The field names in the sender structure must be the same as the screen field names. Example Name on the screen: Plant Screen field name: WERKS Field name in sender structure: WERKS  You can display a field name by positioning the cursor on that field, then choosing F1 and F9.  Maintaining Order Types and Dependent Objects Many of the attributes of the order to be created are derived from the order type (for example, whether revenue postings are allowed or not). You need to specify the order type in the appropriate field in the sender structure. The data you transfer using the sender structure must fit the definitions of the corresponding order type in the SAP system. If you require a settlement rule, you need to enter a settlement profile in the order type. If you want to transfer a source assignment, you need to maintain the source structure. The SAP system must be able to recognize all the organizational units, settlement receivers, and so on. To settle one of the orders you want to create to a different order, you cannot create this in the same run as the order you want to settle, as it must already exist in the system. Note In contrast to the creation of orders in the application, you cannot use reference orders or model orders in the process of transferring old, or external data from external systems.