Routing

The business object Routing is a description of the process used
to manufacture plant materials or provide services in the production industry.

Structure
A routing contains sequences of operations. An operation describes how
a workstep is to be performed. Operations can be combined into
sequences to show parallel or alternative processes. One operation can occur in several sequences.

Several similar routings and their operations can be combined in one group.

An operation can be divided into sub-operations to provide more detail
of the operation. An operation or sub-operation refers to a work center
where it is performed. An operation or sub-operation contains the
required activity information. In addition, an operation can require a
certain quantity of material components or production resources/tools.

Integration
A routing can be used to produce several materials. It is used as a
reference to create production orders or run schedule headers.

Available Methods

• Create : Creation of a routing [ BAPI_ROUTING_CREATE ]
  
• ExistenceCheck : Check existence of object [ BAPI_ROUTING_EXISTENCE_CHECK ]
  

Create

This method serves to create routings with all their subordinated objects.

Here, you can generate a key date view as well as the complete historyof a routing. The latter is particularly useful for data transfers from non-SAP systems.

Example

You want to create a routing with its sequences, operations and inspection characteristics on the key date 01.01.2000.

You generate an entry for each object in the following table by always entering the date 01.01.2000 in the attribute VALID_FROM:

Enter the relevant task list header data here. The attributesTASK_LIST_GROUP and GROUP_COUNTER only have to be supplied if you workwith external number assignment. For internal number assignment thetask list group and the group counter are determined automatically.

Here, only entries for alternative or parallel sequences are allowed.The standard sequence of a routing is always generated automaticallyand therefore does not have to be entered. Here also, the attributesTASK_LIST_GROUP and GROUP_COUNTER need only be supplied in the case of external number assignment.

You generate an entry for each operation in this table. To identify theoperations, you have to enter an external operation identifier in thefield OPERATION_ID. This identifier has to contain at least one character that is not a number (such as VORG0010). This external
identifier is used by the definition of the alternative or parallelsequences to identify the corresponding branch or return operation. Youonly have to supply the TASK_LIST_GROUP and GROUP_COUNTER in the case of external number assignment.

You generate an entry for each inspection characteristic in this table.To identify the inspection characteristics you have to enter aninspection characteristic number in the field INSPCHAR. You can createinspection characteristics with or without reference to a master
inspection characteristic. In the field CHA_MASTER_IMPORT_MODUS (Modusfor the reference to the master inspection characteristic) enter thereference to the master inspection characteristic: 'L' for reference.In this case, the master inspection characteristic has to be completely
maintained. In the parameter INSPCHARACTERISTIC you only have to supplythose fields that could not be copied from the master inspection characteristic; 'C' for copy the data from the master inspectioncharacteristic into the inspection characteristic, 'N' for create a lockable and unlockable reference to the master inspection
characteristic without a data transfer from the master inspection characteristic. In this case manually fill out all fields in theparameter INSPCHARACTERISTIC.

You can either transfer the inspection characteristic control indicatordirectly from the master inspection characteristic, enter it individually or in the field PRESET_CTRL_INDS_KEY you enter a key for
the control indicator if you have stored this key in Customizing.

If you have individually entered a control indicator, note the following special features:

SCOPE_IND: Inspection scope. This indicator can have different
characteristics:

You set " " for: Free inspection scope
You set "<" for: Smaller inspection scope permitted
You set ">" for: Larger inspection scope permitted
You set "=" for: Defined inspection scope

RESULT_RECORDING_TYPE: Record entry type. This indicator can have different characteristics:

You set "-" for: No record entry
You set "*" for: Classified record entry
You set "+" for: Single record entry
You set " " for: Summarized record entry

DOCU_REQU: Documentation required for check results. This indicator can
have different characteristics:

You set " " for: No documention required
You set "." for: Documentation for rejection
You set "+" for: Document all check results
You set "+" for: Document all check results.

CONFIRMATION_CATEGORY Characteristic category
You set " " for: Optional characteristic

You set "+" for: Limited to the acceptance of the previous mandatory characteristic
You set "-" for: Limited to the rejection of the previous mandatory characteristic

You set "X" for: Mandatory characteristic
PRINT_IND: Print control

This indicator can have different characteristics:
You set " " for: Print
You set "x" for: Do not print
You set "*" for: Do not print at skip

If you want to assign an inspection equipment to the inspectioncharacteristic in the field ITEM_NO_OF_PRODUCTION_RESOURCE, note that this has to be assigned to the operation in the PARAMETER
PRODUCTIONRESOURCE.

Notes

Provided that during the data transfer no errors can be found, theexport parameters GROUP and GROUPCOUNTER contain the key for thegenerated task list. To secure the data in the database, you now have to carry out a COMMIT WORK.

All error that occur are logged in the external parameter RETURN. Inthe case of inconsistencies, the entire routing to be generated is rejected.

ExistenceCheck

This module checks whether the routing specified by the task list group(GROUP) and the group counter (GROUPCOUNTER) exists. As additionalcriteria you can enter the selection period to be used. In this case,the system checks whether the specified routing exists in the given selection period.

Notes

Note that the function module merely provides information about whetherthe specified routing exists in the selection period or not. It doesnot say anything about the effectivity of the routing within this period.