- INSPCHARACTERISTIC
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 masterinspection 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 completelymaintained. In the parameter INSPCHARACTERISTIC you only have to supplythose fields that could not be copied from the master inspectioncharacteristic; 'C' for copy the data from the master inspectioncharacteristic into the inspection characteristic, 'N' for create alockable and unlockable reference to the master inspectioncharacteristic without a data transfer from the master inspectioncharacteristic. 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 itindividually 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 thefollowing 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 havedifferent 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 mandatorycharacteristic
You set "-" for: Limited to the rejection of the previous mandatorycharacteristic
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 thatthis has to be assigned to the operation in the PARAMETERPRODUCTIONRESOURCE.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 haveto 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 isrejected.
Description
In this parameter, the identifier of the generated routing is availablefor the succsssful transfer of the copied data. This identifier thenallows you to later access the routing.
By internal assignment the task list group is automatically determinedby the system, by external number assignment the task list group istransferred from the task list header data.
Description
By the successful transfer of the copied data, the group counter of thegenerated routing is available in this parameter. In connection withthe task list group returned in the parameter GROUP, you can lateraccess the generated routing.
When generating the first task list in a task list group '01' isnormally returned. If a new task list is added to an existing task listgroup, then the next available group counter is returned. If, in thetransferred task list header data, a group counter has already beenspecified, then this is used.
Description
You have to enter the BOM application if, when creating a routing,component assignments also have to be created.
In connection with the BOM usage, the BOM application controls theselection of the correct alternative BOMs with the componentassignment.
Description
You have to enter the BOM application if, when creating a routing,component assignments also have to be created.
The BOM usage controls the selection of the relevant BOM in thecomponent assignment.
Description
When entering a profile, you can define default values for specificattributes of the routing. The system always goes back to these if therelevant value has not been transferred. If the profile entry ismissing, the following attributes have to be supplied in the task listheader (structure TASK):
PLANT
TASK_MEASURE_UNIT
TASK_LIST_USAGE
TASK_LIST_STATUS
Likewise for task list header data, you can use the profile to definedefault values for the attributes of an operation. If there are nodefault values saved in the given profile or no profile has been given,then you have to supply the following attributes for the structureOPERATION:
CONTROL_KEY
BASE_QUANTITY
NOMINATOR
DENOMINATOR
The profile can be maintained in Customizing.
Description
With the help of this parameter, you define whether the transferreddata is just checked for consistency or whether it is also updated inthe database. However, an update is only possible if no inconsistenciesoccur.
Make sure, that when purely checking data, a new task list number isassigned from the internal number range. Afterwards, this is no longeravailable for the creation of a new routing.
Value range
Permitted values are:
' ' -> check and flag for update, provided there are noinconsistencies
'X' -> only check
Default
The default value is ' ',this means that provided no inconsistenciesoccur, the data is flagged for update.
Description
The data of the component assignments to be generated is copied intothis table.
The assignment takes place by entering the operation and item data.
To identify the operation, you have to enter its identifier in thefield OPERATION_ID. If this entry is missing, the system determines theoperation from the operation number (attribute ACTIVITY), if this ispossible.
The identification of the BOM item takes place using its identifier inthe field ITEM_ID in connection with entering the BOM (attributesBOM_TYPE, BOM_NO and ALTERNATIVE_BOM) and the header BOM. If the headerBOM is missing from the fields BOM_TYPE_ROOT, BOM_NO_ROOT andALTERNATIVE_BOM_ROOT, then the entry for the header material in thefield MATERIAL can not be determined.
You can only enter a task list group (attribute TASK_LIST_GROUP) in thecase of external number assignment. In the case of internal numberassignment the task list group is automatically assigned duringprocessing.
Information about the individual parameter fields can be found in therelevant data element documentation in the ABAP dictionary.
Description
The data of the inspection characteristics to be generated is copiedinto this table.
The identification of the operation occurs when entering its identifierin the field OPERATION_ID. If this is not available the system tries todetermine the operation using the operation number in the fieldACTIVITY.
The inspection characteristic can be created with reference to areleased master inspection characteristic.
You can only enter a task list group in the case of external numberassignment. In the case of internal number assignment the task listgroup is automatically assigned during processing.
Information about the individual parameter fields can be found in therelevant data element documentation in the ABAP dictionary.
Description
The data of the component assignments to be generated are copied intothis table.
You can only enter a task list group (attribute TASK_LIST_GROUP) in thecase of external number assignment. In the case of internal numberassignment the task list group is automatically assigned duringprocessing.
The following attributes have to have a value, otherwise, theconsistency of the task list can not be ensured:
MATERIAL (material)
PLANT (plant)
Information about the individual parameter fields can be found in therelevant data element documentation in the ABAP dictionary.
Description
The data of the operations to be generated is copied into this table.
To uniquely identify the operation particularly when being used insubordinated structures (such as component assignment) you can flageach operation in the field OPERATION_ID with a unique key. This has tocontain at least one character that is not a number (such as VORG0010)and not be changed for the entire life time of the operation.
The following attributes have to have a value, otherwise theconsistency of the oepration can not be ensured:
ACTIVITY (operation number)
CONTROL_KEY (control key) or
WORK_CNTR (work center) and PLANT (work center plant)
If a profile is entered, when calling up the BAPI, which defines adefault value for the control key, then the corresponding attribute inthe structure SUBOPERATION can be blank.
You can only enter a task list group (attribute TASK_LIST_GROUP) in thecase of external number assignment. In the case of internal numberassignment the task list group is automatically assigned duringprocessing.
Information about the individual parameter fields can be found in therelevant data element documentation in the ABAP dictionary.
Description
The data of the component assignments to be generated are copied intothis table.
The identification of the operation takes place when entering itsidentifier in the field OPERATION_ID. If this is not available, thesystem tries to determine the operation from the operation number inthe field ACTIVITY.
The following objects can be assigned to an operation as PRTs in whichthe entry of the corresponding object type occurs in the fieldPRT_CATEGORY:
- PRT (material)
The material is determined by the fields MATERIAL and PRT_PLANT.
- Equipment
You define the equipment to be assigned in the field EQUIPMENT.
- Documents
You define the documents to be assigned in the fields DOCUMENT_TYPE,DOCUMENT_NUMBER, DOCUMENT_PART and DOCUMENT_VERSION.
- Other
You define the PRT to be assigned in the field MISCELLANEOUS.
You can only enter a task list group in the case of external numberassignment. In the case of internal number assignment the task listgroup is automatically assigned during processing.
Information about the individual parameter fields can be found in therelevant data element documentation in the ABAP dictionary.Value range
The object type of the PRT to be assigned is defined in the fieldPRT_CATEGORY. The following values are permitted here:
'M' -> Material
'E' -> Equipment
'D' -> Documents
'S' -> Sonstiges
Description
The data of the reference operation set reference to be generated iscopied into this table.
To identify the reference operation set you can flag each reference inthe field OPERATION_ID with a unique key. This must contain at leastone character that is not a number (such as REF01) and not be changedfor the entire life time of the reference operation.
You enter the referenced reference operation set in the fieldsREFERENCED_TASK_LIST_GROUP (task list group) andREFERENCED_GROUP_COUNTER (group counter).
You have to enter the operation number of the reference operationwithin the routing, into the field ACTIVITY.
You can only enter a task list group in the case of external numberassignment. In the case of internal number assignment the task listgroup is automatically assigned during processing.
Information about the individual parameter fields can be found in therelevant data element documentation in the ABAP dictionary.
Description
All the messages that occur when creating a routing are cumulated inthis table. If inconsistencies occur, these messages can be used as thebasis for correction.
Description
The data of the sequences to be generated is copied into this table.
Note that you can only enter alternative or parallel sequences here.You are not permitted to enter standard sequences since these aregenerated automatically when creating the task list header.
You can only enter a task list group (attribute TASK_LIST_GROUP) in thecase of external number assignment. In the case of internal numberassignment the task list group is automatically assigned duringprocessing.
The following attributes have to have a value, otherwise theconsistency of the task list can not be ensured:
SEQUENCE_CATEGORY (sequence category)
REFERENCE_SEQUENCE (reference sequence)
RETURN_OPERATION (return operation) or RETURN_OPERATION_IDENT (returnoperation identifier)
If a routing sequence is entered (attribute SEQUENCE_NO), then this istaken into consideration when creating the sequence, otherwise the nextavailable routing sequence is automatically assigned.
Information about the individual parameter fields can be found in therelevant data element documentation in the ABAP dictionary.
Description
The data of the suboperations to be generated is copied into thistable.
To identify the suboperation you can flag each suboperation in thefield SUB_OPERATION_ID with a unique key. This has to include at leastone character that is not a number (such as UV0010/1) and not bechanged for the entire life time of the suboperation.
The assignment of the suboperation to its subordinated operation takesplace in the field OPERATION_ID by entering the identifier of theoperation. If there is no entry here, the system tries to determine thecorrect operation from the operation number in the field ACTIVITY.
The following attributes have to have a value, otherwise theconsistency of the suboperation can not be ensured:
SUB_ACTIVITY (suboperation number)
CONTROL_KEY (control key) or
WORK_CNTR (work center) and PLANT (work center plant)
If a profile is entered, when calling up the BAPI, which defines adefault value for the control key, then the corresponding attribute inthe structure SUBOPERATION can be blank.
You can only enter a task list group (attribute TASK_LIST_GROUP) in thecase of external number assignment. In the case of internal numberassignment the task list group is automatically assigned duringprocessing.
Information about the individual parameter fields can be found in therelevant data element documentation in the ABAP dictionary.
Description
The header data of the routing to be created is transferred into thisstructure.
Note that you can only enter a task list group (attributeTASK_LIST_GROUP) in the case of external number assignment. In the caseof internal number assignment, the task list group is automaticallydetermined during processing.
If a group counter (attribute GROUP_COUNTER) is entered, then this istaken into account when generating a new routing, provided this is notthe first task list in the group. If it is the first, then counter '01'is always used. If there is no group counter entry, then the nextavailable group counter is used to create the routing.
The following attributes have to have a value, because otherwise theconsistency of the header data can no be ensured:
TASK_LIST_USAGE (task list usage)
PLANT (plant)
TASK_LIST_STATUS (task list status)
TASK_MEASURE_UNIT (unit of measure)
Provided, when calling up the BAPI, a profile has been entered, whichdefines the default values for the named attributes, then thecorresponding attributes in the structure TASK can also be blank.
Information about the individual parameter fields can be found in therelevant data element documentation in the ABAP dictionary.
Description
Long texts to be processed when creating or changing routings aretransferred into this table line by line. This enables you to enter aformat parameter for each line.
Using both attributes LINE_FROM and LINE_TO from the tableTextAllocation you determine the long text lines assigned to an object.
Information about the meaning of individual parameter fields can befound in the relevant data element documentation in the ABAPdictionary.
Description
With the help of the data entered here, you can assign long texts whencreating or changing routings. Here, you first have to define therelevant object type in the attribute OBJECT_TYPE that thecorresponding long texts are assigned to. The following values areallowed here:
- '10' -> Task list header
- '12' -> Sequence
- '13' -> Operation
- '14' -> Suboperation
- '15' -> Reference operation set reference
- '16' -> Standard task
- '17' -> PRT
- '19' -> Inspection characteristics
According to each object type, you have to supply the other attributeswith the values necessary for the unique identification of the object.The attributes LINE_FROM and LINE_TO are pointers in the related texttables, into which the actual long text lines are to be transferred.LINE_FROM defines the first line of the long text and LINE_TO the last.
Information about the meaning of individual parameter fields can befound in the relevant data element documentation in the ABAPDictionary.
Description
The data for the standard tasks to be generated is copied into thistable.
In principle standard tasks presents a reference to a referenceoperation set. In contrast to this, for the standard task, thereference operation set operations are summarized in a referenceoperation, that means, all default values for the reference operationset operations are cumulated and stored in the corresponding attributesof the standard task.
For unique identification, you can flag each standard task in the fieldOPERATION_ID with a unique key. This has to include at least onecharacter that is not a number (such as STD01) and not be changed forthe entire life time of the standard task.
You enter the referenced reference operation set in the fieldsREFERENCED_TASK_LIST_GROUP (task list group) andREFERENCED_GROUP_COUNTER (group counter). You have to enter theoperation number of the standard task within the routing, in the fieldACTIVITY.
The following attributes have to be entered to generate a standardtask:
CONTROL_KEY (control key) or
WORK_CNTR (work center) and PLANT (work center plant)
CUMULATION_TYPE (cumulation type)
You can only enter a task list group (attribute TASK_LIST_GROUP) in thecase of external number assignment. In the case of internal numberassignment the task list group is automatically assigned duringprocessing.
Information about the individual parameter fields can be found in therelevant data element documentation in the ABAP dictionary.
Value range
The following values are permitted in the field CUMULATION_TYPE:
'1' -> Cumulation occurs in the task list and in the order
'2' -> Cumulation occurs in the order