RefSetOfOperations

The business object reference operation set is a description of
a production process that occurs when producing different plant materials.

Structure

The reference operation set contains operations. An operation describes
how a work step is carried out. The cumulation of operations into a
reference operation set enables you to display ever recurring standard
procedures. These standard procedures can be referenced in a routing.

An operation can be split into suboperations for detailed descriptions.
An operation or a suboperation can refer to a work center where it is
carried out. An operation or a suboperation contains the necessary
activities. In addition, an operation can require a specific quantity of material components or PRTs.

Integration

A reference operation set can be used for the production of several plant materials in any number of routings.

Available Methods

• Create : Creation of a reference operation set [ BAPI_REFSETOFOPERATIONS_CREATE ]
  
• ExistenceCheck : Check existence of reference operation set [ BAPI_REFSETOFOPR_EXISTENCE_CHK ]
  

Create

This method serves to create reference operation sets with all their subordinated objects.

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

Example

You want to create a reference operation set with its 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.

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). You only 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 an
inspection characteristic number in the field INSPCHAR. You can createinspection characteristics with or without reference to a masterinspection characteristic. In the field CHA_MASTER_IMPORT_MODUS (Modusfor the reference to the master inspection characteristic) enter the
reference to the master inspection characteristic: 'L' for reference.In this case, the master inspection characteristic has to be completelymaintained. 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 inspection
characteristic into the inspection characteristic, 'N' for create a lockable and unlockable reference to the master inspectioncharacteristic without a data transfer from the master inspection characteristic. In this case manually fill out all fields in the
parameter 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 forthe 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: Specified 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

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 reference operation set. To secure the data in the database, you now have to carry out a COMMIT WORK.

All errors that occur are logged in the external paramter RETURN. Inthe case of inconsistencies, the entire reference operation set to be generated is rejected.

ExistenceCheck

This module checks whether the reference operation set specified by thetask list group (GROUP) and the group counter (GROUPCOUNTER) exists. Asadditional criteria you can enter the selection period to be used. Inthis case, the system checks whether the specified reference operation set exists in the given selection period.

Notes

Note that the function module merely provides information about whetherthe specified reference operation set exists in the selection period ornot. It does not say anything about the effectivity of the reference operation set within this period