Description
The program RCPTRA01 creates a batch input session for transferringexternal routing data to the SAP system. The data transfer is carriedout in the following steps:
Transfer of external routing data to the SAP system
The user must first write a program that selects and collects theexternal routing data and writes it into a sequential file before it isready to be transferred to the SAP system.
If the external system is also an SAP system, use program RCPBTCO1.
In any case, write the required program yourself.
Create Batch Input Sessions
The program, RCPTRA01 takes the data from the sequential file and makesbatch input session for creating routings. The following applicationtransactions are available currently:
CA01 Create routing
CA11 Create reference operation set
QP01 Create inspection plan
Posting the data
The routings are posted to the SAP system when the batch input sessionis run.
Note the following when transferring data in the sequential file:

• Test report: You can use the RCPTRA00 program to create a
sequential file for test purposes. To do this, you must enter the thatshould be transferred to the sequential file.

• Data Structures:There are three different types of data
structures:
Session record:
This data structure contains the data that are valid for the session youwant to create. In this data structure you can enter the session name,client key and the user name. You can use the lock date to see how longthe session will be locked and when you can run the session again.
Header record per transaction
This data structure contains the transaction code for the transactionwhich starts the batch input session.
Application data
These data structures contain data for the routings to be created in theSAP System. For each object (for example, header, sequence, operation)there is a unique structure.

• Record types: The various data structures in the input file are
identified by record types. The record type is in the first position ofthe data structure with the format CHAR 2.
Record type,,Struc.Name,,Comment
00,,BI000,,Session record; it contains information on the
,,,,session to be created
01,,BIMPL,,Material-task list allocation
03,,BIPKO,,Header
04,,BIPTX,,Header long text
05,,BIPFL,,Sequence
06,,BIPTX,,sequence long text
09,,BIPPO,,Operation
10,,BIPTX,,Operation long text
11,,BIPFH,,PRT assignment
12,,BIPTX,,PRT assignment long text
13,,BIPMZ,,Material component allocation
18,,BIPMK,,Inspection characteristic
20,,BIPTX,,Inspection characteristic long text
99,,BI001,,Header record per transaction; it contains
,,,,the code for the transaction which
,,,,starts the session
,,,,CA01 - Create routing
,,,,CA11 - Create reference operation set
,,,,OP01 - Create inspection characteristic

• Sequence of data records in the input file: Keep the following
sequence when creating the input file:
Enter a session record for each session with appropriate data (recordtype "00"). Because posting occurs for each session, no more thanapprox. 10,000 routing records should be processed between two sessions.Several transaction header records can be made by two session records.
Enter a header record for each transaction (Record type "99"). Allsubsequent data records up to the next transaction header refer to thisapplication transaction. A planner group is always used in everytransaction (and not a material). All records in a transaction headerrecord (all record types besides "00" and "99") must therefore have thesame task list type and same group number (often left blank). The groupcounter (task list alternative) can be changed.
Enter application data. Within a transaction call no particular sequencemust be followed for the application data (All record types except "00"and "99")

• Preparation of the data records in the input file

BI000 - Session record
BI000-TYPE,,Record type = "00"
BI000-GOUP,,Session name
BI000-MANDT,,Client
BI000-USNAM,,User name
BI000-START,,Start date; the session cannot be started
,,prior to this date
BI000-XKEEP,,Save session after it is read in
BI000-NODATA,,Special character, that controls that no
,,value is transferred to the SAP System for
,,this field (for example, default values)
BIMPL - Material-task list allocation
For every material that is allocated to a task list of type "N" or "Q",you must create a data record for the material-task list allocation(Structure BIMPL).
BIMPL-RECTY,,Record type = "01"
BIMPL-MATNR,,Number of the allocated material
BIMPL-WERKS,,Plant of the assigned task list
BIMPL-PLNTY,,Task list type of the allocated material
BIMPL-PLNNR,,Group of the assigned task list (See A)
BIMPL-PLNAL,,Group counter of the assigned task list
...
BIMPL-VBELN,,Sales document
BIMPL-POSNR,,Sales document item
BIPKO - Header
For every task list to be created (identified by a group and a groupcounter) you must create a data record for the task list header(Structure BIPKO).
BIPKO-RECTY,,Record type = "03"
BIPKO-PLNTY,,Task list type
BIPKO-PLNNR,,Group (See A)
BIPKO-PLNAL,,Group counter
BIPKO-DATUV,,Valid from date, required entry, valid for all objects
BIPKO-AENNR,,Change number
BIPKO-VERWE,,Usage
BIPKO-WERKS,,Plant
BIPKO-STATU,,Status
BIPKO-PLNME,,Unit of measure
BIPKO-LOSVN,,Lot size from
BIPKO-LOSBS,,Lot size to
BIPKO-VAGRP,,Responsible planner group
BIPKO-KTEXT,,Task list description
BIPKO-TXTSP,,Language key for long text
,,This field must have a value that is not
,,blank if a long text is to be created for
,,this header.
BIPKO-PROFIDNETZ,,Profile
,,The profile must have the
,,"Entry tool" activated.
BIPKO-QDYNREGEL,,Dynamic modification rule
BIPKO-QDYNHEAD,,Level at which dynamic
,,modification parameters are defined
BIPKO-EXTNUM,,Indicator: external numbering
BIPKO-PLNNR_ALT,,Old task list number
BIPKO-SLWBEZ,,Description for the inspection point field combination
BIPKO-PPKZTLZU,, Indicator: Partial lot assignment for inspection
,,during production
BIPKO-QPRZIEHVER,, Sample-drawing procedure
BIPKO-LIEFKZ,, Indicator: Take vendor into account during dynamic
,,modification
BIPKO-HERSTKZ,, Indicator: Take manufacturer into account during
,,dynamic modification
BIPKO-KUNDKZ,, Indicator: Take customer into account during
,,dynamic modification
BIPTX - Header long text
A long text can be created for each routing to be created (StructureBIPTX).
BIPTX-RECTY,,Record type = "04"
BIPTX-PLNTY,,Task list type
BIPTX-PLNNR,,Group (see A)
BIPTX-PLNAL,,Group counter
...
BIPTX-TEXT,,Long text line (see B)
BIPTX-TXPARGRAPH,,Format column
BIPFL - Sequence
For each routing to be created, you must create at least one data recordfor a sequence (Structure BIPFL). You do not have to create a sequencerecord for reference operation sets.
BIPFL-RECTY,,Record type = "05"
BIPFL-PLNTY,,Task list type
BIPFL-PLNNR,,Group (See A)
BIPFL-PLNAL,,Group counter
BIPFL-PLNFL,,Sequence
BIPFL-FLGAT,,Sequence type
,,"0" = Standard sequence
,,"1" = Parallel sequence
,,"2" = Alternative sequence
BIPFL-LTXA1,,Sequence short description
BIPFL-TXTSP,,Language key for long text
,,This field must have a value that is not
,,blank if a long text is to be created
,,for this sequence.
BIPFL-LOSVN,,Lot size from in alternative sequences
BIPFL-LOSBS,,Lot size to in alternative sequences
BIPFL-AUSCHL,,Scheduling alignment key
,,With parallel or alternative sequences,
,,you must also maintain the following
,,fields:
BIPFL-VORNR1,,Branch operation
BIPFL-VORNR2,,Return operation
BIPTX - Sequence long text
You can create a long text for every sequence to be created (StructureBIPTX).
BIPTX-RECTY,,Record type = "06"
BIPTX-PLNTY,,Task list type
BIPTX-PLNNR,,Group (See A)
BIPTX-PLNAL,,Group counter
BIPTX-PLNFL,,Sequence
...
BIPTX-TEXT,,Long text line (see B)
BIPTX-TXPARGRAPH,,Format column
BIPPO - Operation
Individual operations can be created for each sequence (Structure BIPPO)
BIPPO-RECTY,,Record type = "09"
BIPPO-PLNTY,,Task list type
BIPPO-PLNNR,,Group (See A)
BIPPO-PLNAL,,Group counter
BIPPO-PLNFL,,Sequence
BIPPO-VORNR,,Operation number
BIPPO-STEUS,,Control key
BIPPO-WERKS,,Plant
BIPPO-KTSCH,,Standard text key
BIPPO-LTXA1,,Operation description: 1st line
,,If both fields are filled, the 1st text line
,,is overwritten with the standard text in the
,,standard text key.
BIPPO-TXTSP,,Language key for long text
,,This field must have a value that is not
,,blank if a long text is to be created for
,,this operation.
BIPPO-MEINH,,Operation unit of measure
BIPPO-UMREN,,Numerator for conversion of
,,unit of measure to base unit
BIPPO-UMREZ,,Denominator for conversion of
,,unit of measure to base unit
BIPPO-BMSCH,,Base quantity
BIPPO-ZMERH,,Break
BIPPO-ZEIER,,Unit for breaks
BIPPO-LAR01,,Activity type 1
BIPPO-VGE01,,Unit of standard value 1
BIPPO-VGW01,,Standard value 1
BIPPO-LAR02,,Activity type 2
BIPPO-VGE02,,Unit of standard value 2
BIPPO-VGW02,,Standard value 2
...
BIPPO-ZERMA,,Standard value determination type
BIPPO-ZGDAT,,Date of standard value determination
BIPPO-ZCODE,,Reference number for standard value
BIPPO-ZULNR,,Standard value determination reference
BIPPO-RSANZ,,Number of confirmation slips
BIPPO-LOANZ,,Number of time tickets
BIPPO-LOART,,Wage type
BIPPO-QUALF,,Suitability
BIPPO-ANZMA,,Number of employees
BIPPO-RFGRP,,Setup group category
BIPPO-RFSCH,,Setup group key
BIPPO-RASCH,,Setup group key
BIPPO-AUFAK,,Scrap
BIPPO-LOGRP,,Wage group
BIPPO-UEMUS,,Indicator: Required overlapping
BIPPO-UEKAN,,Indicator: Optional overlapping
BIPPO-FLIES,,Indicator: Continuous flow
BIPPO-ZEIMU,,Unit of minimum overlap time
BIPPO-ZMINU,,Minimum overlap time
BIPPO-MINWE,,Minimum send-ahead quantity
BIPPO-SPMUS,,Indicator: Required splitting
BIPPO-SPLIM,,Number of splits
BIPPO-ZEIMB,,Unit of minimum processing time
BIPPO-ZMINB,,Minimum processing time
BIPPO-ZEILM,,Unit of maximum wait time
BIPPO-ZLMAX,,Maximum wait time
BIPPO-ZEILP,,Unit of minimum wait time
BIPPO-ZLPRO,,Minimum wait time
BIPPO-ZEIWN,,Unit of normal queue time
BIPPO-ZWNOR,,Normal queue time
BIPPO-ZEIWM,,Unit of minimum queue time
BIPPO-ZWMIN,,Minimum queue time
BIPPO-ZEITN,,Unit of normal move time
BIPPO-ZTNOR,,Normal move time
BIPPO-ZEITM,,Unit of minimum move time
BIPPO-ZTMIN,,Minimum move time
BIPPO-ABLIPKZ,,Indicator: teardown and queue
,,occur in parallel
BIPPO-RSTRA,,Reduction strategy per operation
BIPPO-BZOFFB,,Sub-operation reference to start
BIPPO-OFFSTB,,Offset to reference date PRT
,,start
BIPPO-EHOFFB,,Unit of sub-operation offset
BIPPO-BZOFFE,,Sub-operation reference to finish
BIPPO-OFFSTE,,Offset to reference date PRT finish
BIPPO-EHOFFE,,Unit of sub-operation offset
BIPPO-SORTL,,Sort string
BIPPO-LIFNR,,Vendor account number
BIPPO-PLIFZ,,Planned delivery time in days
BIPPO-PREIS,,Net price in purchasing info record
BIPPO-PEINH,,Price unit
BIPPO-SAKTO,,Cost element
BIPPO-WAERS,,Currency key
BIPPO-INFNR,,Number of purchasing info record
BIPPO-EKORG,,Purchasing organization
BIPPO-EKGRP,,Purchasing group
BIPPO-KZLGF,,Indicator: ext. processing lot-size
BIPPO-MATKL,,Material group
BIPPO-SLWID,,Key word ID for user-defined fields
BIPPO-USR00,,User field 20 characters
BIPPO-USR01,,User field 20 characters
BIPPO-USR02,,User field 10 characters
BIPPO-USR03,,User field 10 characters
BIPPO-USR04,,User field quantity
BIPPO-USE04,,User field quantity unit
BIPPO-USR05,,User field quantity
BIPPO-USE05,,User field quantity unit
BIPPO-USR06,,User field value
BIPPO-USE06,,User field value unit
BIPPO-USR07,,User field value
BIPPO-USE07,,User field value unit
BIPPO-USR08,,User field date
BIPPO-USR09,,User field date
BIPPO-USR10,,User field indicator
BIPPO-USR11,,User field indicator
BIPPO-ARBPL,,Work center
BIPPO-UVORN,,Sub-operation
BIPPO-UENICHT,,Indicator: No overlapping
BIPPO-CKSELKZ,,Indicator for costing relevance
BIPPO-VPLFLG,,Flag: Reference to ref. operation set
BIPPO-VPLNNR,,Group of reference operation set
BIPPO-VPLNAL,,Group counter of ref. operation set
BIPPO-VINTV,,Operation interval
,,If in addition to BIPPO-VPLFLG,
,,BIPPO-KTSCH or BIPPO-LTXA1 is filled,
,,they are valid as text elements for reference
BIPPO-VERDRT,, Cumulation type
BIPPOI-UAVO_AUFL,, Indicator: Sub-operations not in order
BIPPO-FRDLB,,Indicator: External operation with subcontracting
BIPPO-QPART,,Inspection type
BIPPO-ERFSICHT,,Recording view
BIPPO-QPPKTABS,,Flow variants for inspection point completion
BIPPO-QKZPRZEIT,,Indicator: Takt = time (time reference)
BIPPO-QKZPRMENG,,Indicator: Takt = quantity (quantity reference)
BIPPO-QKZPRTREI,,Indicator: Takt without reference to time or quantity
BIPPO-QRASTZFAK,,Time factor for inspection points (batch input)
BIPPO-QRASTZEHT,,Time unit for inspection points (batch input)
BIPPO-QRASTMENG,,Quantity between two inspections
BIPPO-QKZTLSBEST,,Ind.: Operation with partial lot assignment relevant,,to stock
BIPPO-QKZZTMG1,,Indicator: Quantity confirmation for each partial lot
BIPPO-PRZ01,,Business process number
BIPPO-EBELN,, Purchasing document number
BIPPO-EBELP,,Item number of the purchasing document (batch input field)
BIPTX - Operation long text You can create a long text for everyoperation to be created (Structure BIPTX).
BIPTX-RECTY,,Record type = "10"
BIPTX-PLNTY,,Task list type
BIPTX-PLNNR,,Group (See A)
BIPTX-PLNAL,,Group counter
BIPTX-PLNFL,,Sequence
BIPTX-VORNR,,Operation number
...
BIPTX-TEXT,,Long text line (see B)
BIPTX-TXPARGRAPH,,Format column
BIPFH - Production resource/tool assignment
PRTs can be assigned to every operation (Structure BIPFH).
BIPFH-RECTY,,Record type = "11"
BIPFH-PLNTY,,Task list type
BIPFH-PLNNR,,Group (See A)
BIPFH-PLNAL,,Group counter
BIPFH-PLNFL,,Sequence
BIPFH-VORNR,,Operation number
BIPFH-PSNFH,,PRT item number
BIPFH-STEUF,,Control key PRT management
...
BIPFH-MGEINH,,Unit of PRT quantity
BIPFH-MGVGW,,Standard value PRT quantity
...
BIPFH-TXTSP,,Language key for long text
,,This field must have a value that is
,,not blank if a long text is to be
,,created for this PRT assignment.
BIPFH-KTSCH,,Standard text key PRT
BIPFH-TXTZ1,,PRT text
BIPFH-FHMAR,,PRT category
BIPFH-FHMNR,,PRT number
BIPFH-FHWRK,,PRT value
BIPFH-MATNR,,Material number
BIPFH-SFHNR,,PRT
BIPFH-DOKAR,,Document type
BIPFH-DOKNR,,Document number
BIPFH-DOKTL,,Document part
BIPFH-DOKVR,,Document version
BIPFH-EQUNR,,Equipment number
BIPTX - PRT long text
You can create a long text for each PRT allocation (Structure BIPTX):
BIPTX-RECTY,,Record type = "12"
BIPTX-PLNTY,,Task list type
BIPTX-PLNNR,,Group (See A)
BIPTX-PLNAL,,Group counter
BIPTX-PLNFL,,Sequence
BIPTX-VORNR,,Operation number
BIPTX-PSNFH,,PRT item number
...
BIPTX-TEXT,,Long text line (see B)
BIPTX-TXPARGRAPH,,Format column
BIPMZ - Material component allocation
You can allocate material components to every operation
(Structure BIPMZ ).
BIPMZ-RECTY,,Record type = "13"
BIPMZ-PLNTY,,Task list type
BIPMZ-PLNNR,,Group (See A)
BIPMZ-PLNAL,,Group counter
BIPMZ-PLNFL,,Sequence
BIPMZ-VORNR,,Operation number
BIPMZ-STLTY,,Bill of material type
BIPMZ-STLNR,,Bill of material number
,,If the bill of material number remains
,,empty, the system determines a number
,,automatically from bill of material BIPMZ-BOMAT
,,and plant BIPMZ-WERKS for the key date of the header record.
,,The BOM type and the BOM alternative
,,BIPMZ-STLTY, -STLAL are used as selection criteria.
,,BIPMZ-STLNR and BIPMZ-STLAL are copied for
,,the first bill of material found.
BIPMZ-STLAL,,Bill of material alternative
BIPMZ-STLKN,,BOM level number
...,,If the system automatically searches for
,,the BOM level number, the field BIPMZ-STLKN
,,must have the constant "*POS" in its first
,,four places. The last four places of this
,,field contain the BOM item number. You have
,,to enter leading zeros or it becomes initial.
,,If you enter a BOM item number, the system
,,searches for the BOM by this item number.
,,The first entry found determines the level number.
,,The component is copied in BIPMZ-MATNR.
,,If you do not enter an item number, the system
,,searches for the BOM by the component BIPMZ-MATNR.
,,The first entry found determines the level number.
,,The key date used to search is the key date
,,of the header record (BIPKO-DATUV).
BIPMZ-ZUDIV,,Whole numbers
BIPMZ-ZUMS1,,Cutting measure 1
BIPMZ-ZUMS2,,Cutting measure 2
BIPMZ-ZUMS3,,Cutting measure 3
BIPMZ-ZUMEI,,Cutting measure unit
BIPMZ-IMENG,,Component quantity
BIPMZ-IMEIN,,Component unit of measure
BIPMZ-MATNR,,Material number of material component
BIPMZ-WERKS,,Plant
BIPMZ-BOMAT,,BOM material, for multi-level BOMS always the top material
BIPMZ-RGEKZ,,Indicator: backflush
BIPMK - Inspection characteristics
You can assign characteristics to every operation
BIPMK-RECTY,,Record type = "18"
BIPMK-PLNTY,,Task list type
BIPMK-PLNR,,Group key
BIPMK-PLNAL,,Group counter
BIPMK-PLNFL,,Sequence of operations within a task list
BIPMK-VORNR,,Operation number
BIPMK-MERKNR,,Inspection characteristic number
BIPMK-KURZTEXT,,Inspection characteristic description
BIPMK-TXTSP,,Language key
BIPMK-VSTEURKZ,,Default for control indicator for inspection charact.
BIPMK-TOLERANZSL,,Tolerance key
BIPMK-QUANTITAT,,Indicator: Quantitative characteristic
BIPMK-MESSWERTE,,Indicator: Measurement reading must be confirmed
BIPMK-PRUEKAT,,Indicator: Reference to characteristic value required
BIPMK-TOLEROBEN,,Indicator: Upper specification limit
BIPMK-TOLERUNTEN,,Indicator: Lower specification limit must be entered
BIPMK-SOLLPRUEF,,Indicator: Check target value
BIPMK-PUMFKZ,,Indicator: Inspection scope
,,This indicator can have various values:
,,Set " " for:,,scope not fixed
,,Set "<" for:,,smaller scope
,,Set ">" for:,,larger scope
,,Set "=" for:,,fixed scope
BIPMK-LZEITKZ,,Indicator: Long-term inspection
BIPMK-ESTUKZ,,Indicator: Original value recording
,,This indicator can have various values:
,,Set "-" for: ,,No characteristic recording
,,Set "*" for: ,,Class recording
,,Set "+" for: ,,Individual recording
,,Set " " for: ,, Collective recording
BIPMK-DOKUKZ,,Indicator: Documentation required for inspection results
,,,This indicator can have various values:
,,Set " " for:,, No documentation necessary
,,Set "." for:,, Documentation for rejection
,,Set "+" for:,, Documentation necessary
BIPMK-RZWANG,,Indicator: Results recording required
,,This indicator can have various values:
,,Set " " for:,, Optional characteristic
,,Set "+" for:,, After acceptance
,,Set "-" for:,, After rejection
,,Set "X" for:,, Required characteristic
BIPMK-SYNCRO,,Indicator: Synchronization active
BIPMK-ADDPRO,,Indicator: Sample quantity added together
BIPMK-ZERSTPRF,,Indicator: Destructive testing
BIPMK-FORMELMK,,Indicator: Formula characteristic
BIPMK-STICHPR,,Indicator: Sampling procedure necessary
BIPMK-AUSSLOS,,Indicator: Characteristic scrap proportion
BIPMK-FIXIERT,,Indicator: Proposed control indicator cannot be changed
,,(only assigned internally)
BIPMK-BEWFHLZHL,,Indicator: Confirmation of number of defects
BIPMK-LSTKZ,,Control of characteristic results QM subsystem (not
,,supported at the moment)
BIPMK-VORGAEND,,Requirements can be changed (indicator) (not
,,supported at the moment)
BIPMK-PMMZWANG,,Assignment of test equipment
BIPMK-FEHLREC,,Indicator: Automatic call up of defects recording
BIPMK-AENDBELEG,,Create change documents when entering results
BIPMK-QSPCMK,,Indicator: SPC characteristic
BIPMK-KEINDRUCK,, Indicator: Printing
,,This indicator can have various values:
,,Set " " for:,, Printing
,,Set "x" for:,, No printing
,,Set "*" for:,, Documentation required
BIPMK-VERWMERKM,, Inspection characteristic identification of the ,,
master inspection characteristic
BIPMK-QPMK_REF,, Indicator: reference to master inspection character.
BIPMK-QPMK_ZAEHL,,Plant of the master inspection characteristic
BIPMK-MKVERSION,,Version number of the master inspection characteristic
BIPMK-PMETHODE,,Inspection method
BIPMK-QMTB_WERKS,,Plant of the inspection method
BIPMK-PMTVERSION,,Version number of the inspection method
BIPMK-PROBENR,,Partial sample number of the inspection method
BIPMK-PRUEQUALI,,Inspector qualification
BIPMK-MERKGEW,,Weighting of the characteristic
BIPMK-EEANTVERF,,Share calculation
BIPMK-PSNFH,,Item number PRT (batch input)
BIPMK-DUMMY10,,Text line for additional information
BIPMK-DUMMY20,,Text line for additional information
BIPMK-STICHPRVER,,Sampling procedure in inspection characteristic
BIPMK-PROBEMGEH,,Sample unit of measure
BIPMK-PRUEFEINH,,Sample quantity factor for sample (sample: multiple of
,,PME)
BIPMK-SPCKRIT,,SPC criterion
BIPMK-DYNMERKREF,,Characteristic (in task list) whose quality level is
,,copied
BIPMK-QDYNREGEL,,Dynamic modification rule
BIPMK-LIEFKZ,,Vendor taken into account for dynamic modification
BIPMK-HERSTKZ,,Manufacturer taken into account for dynamic modification
BIPMK-KUNDKZ,,Customer taken into account for dynamic modification
BIPMK-STELLEN,,Number of decimal places (accuracy)
BIPMK-MASSEINHSW,,6 character unit of measure, for maintaining
,,quantitative data
BIPMK-SOLLWERT,,Target value for a quantitative characteristic
BIPMK-TOLERANZOB,,Upper specification limit
BIPMK-TOLERANZUN,,Lower specification limit
BIPMK-KLASANZAHL,,Number of inspection results value classes
BIPMK-KLASBREITE,, Class width
BIPMK-KLASMITTE,, Class mid-point
BIPMK-GRENZEOB1,,First upper specification limit
BIPMK-GRENZEUN1,,First lower specification limit
BIPMK-GRENZEOB2,,Second upper specification limit
BIPMK-GRENZEUN2,,Second lower specification limit
BIPMK-PLAUSIOBEN,,Upper plausibility limit
BIPMK-PLAUSIUNTE,,Lower plausibility limit
BIPMK-TOLERWEIOB,,Upper tolerance change
BIPMK-TOLERWEIUN,,Lower tolerance change
BIPMK-TOLERWAB,,Date from which the tolerance change is valid
BIPMK-TOLERWBIS,,Date up to which the tolerance change is valid (BI)
BIPMK-FORMELSL,,Indicator: Check and calculate formula in QM
BIPMK-FORMEL1,, Formula field
BIPMK-FORMEL2,, Formula field
BIPMK-CODEGRQUAL,,Defect code group for rejection in general
BIPMK-CODEQUAL,,Defect code for rejection in general
BIPMK-CODEGR9U,,Defect code group for rejection due to lower tolerance
BIPMK-CODE9U,,Defect group for rejection due to lower tolerance
BIPMK-CODEGR9O,,Defect code group for rejection due to upper tolerance
BIPMK-CODE9O,,Defect group for rejection due to upper tolerance
BIPMK-KATAB1,, Indicator,, Catalog entry is a selected set
BIPMH-KATALGART1,,Catalog of the assigned code group or selected set
,, (only 1 allowed)
BIPMK-AUSWMENGE1,,Assigned selected set
BIPMK-AUSWMGWRK1,,Plant of the assigned selected set
BIPMK-KATAB2,, Indicator,, Catalog entry 2 is a selected set
BIPMH-KATALGART2,,Catalog of the assigned code group or selected set
BIPMK-AUSWMENGE2,,Assigned selected set 2
BIPMK-AUSWMGWRK2,,Plant of the assigned selected set 2
BIPMK-KATAB3,, Indicator,, Catalog entry 3 is a selected set
BIPMH-KATALGART3,,Catalog of the assigned code group or selected set
BIPMK-AUSWMENGE3,,Assigned selected set 3
BIPMK-AUSWMGWRK3,,Plant of the assigned selected set 3
BIPMK-KATAB4,, Indicator,, Catalog entry 4 is a selected set
BIPMH-KATALGART4,,Catalog of the assigned code group or selected set
BIPMK-AUSWMENGE4,,Assigned selected set 4
BIPMK-AUSWMGWRK4,,Plant of the assigned selected set 4
BIPMK-KATAB5,, Indicator,, Catalog entry 5 is a selected set
BIPMH-KATALGART5,,Catalog of the assigned code group or selected set
BIPMK-AUSWMENGE5,,Assigned selected set 5
BIPMK-AUSWMGWRK5,,Plant of the assigned selected set 5
BIPTX - Long text for inspection characteristics
You can enter a long text (structure BIPTX) for every inspectioncharacteristic in the task list. Note that the description is also thefirst line in the long text.
BIPTX-RECTY,,Record type = "20"
BIPTX-PLNTY,,Task list type
BIPTX-PLNNR,,Key of the task list group
BIPTX-PLNAL,,Group counter
BIPTX-PLNFL,,Sequence of operations within a task list
BIPTX-VORNR,,Operation number
BIPTX-PSNFH,,Item number PRT (batch input)
BIPTX-ZAEHL,,Consecutive counter (batch input)
BIPTX-TEXT,,Text editor text line
BIPTX-TYPARGRAPH,,Format column
BIPTX-MERKNR,,Inspection characteristic number
BI001 - Header record per transaction
BI001-TYPE,,Record type = "99"
BI001-TCODE,,Transaction code
A: If you use internal number assignment and let the system assign thenumber, you must set the group to the initial value.
B: The transfer of the long text depends on the language with which youare logged into the system. Note when long texts are copied that a longtext line has 72 places. Formatting indicators in the format columns aretaken into account.
The data fields that are to be maintained are determined using thescreens in the routing transaction.
The field names of the data structures in the input file can bedistinguished from the field names in the application transactions bytheir prefix. For example, the field for the sequence alignment key inthe routing transaction is PLFLD-AUSCHL and in the input file it iscalled BIPFL-AUSCHL.
You can display the field names in the application transaction bypressing F1 on the entry field and then clicking on the pushbutton"Technical info".

• Initialization and identification of empty fields

You can make an entry for every field in the batch input structure. Youcan enter the following:
An explicitly entered field value (for example when the control key ofthe operation is transferred)
A blank (for example, when the field contents should be deleted)
A special character, used to tell the batch input program that no valuesshould be transferred.
Fields for which no values should be transferred because they are notused (for example) must be identified by a special character. Thisspecial character is interpreted to mean that the current value of thefield in the SAP System should remain the same. This value can be aninitial value, an explicitly entered value or a value determined by theSAP System. Generally "/" is the special character used. If you want touse a different character, you must define it in the field BI000-NODATA.

• Data format

Data transferred from an external system into the SAP System must havefields that are compatible with those of the SAP System. The data mustbe in character format. The contents of the external fields may not belonger than the corresponding SAP fields.

• Number assignment

If you want the system to assign the numbers, that is internal numberassignment for the newly added groups, you must set the field "Group" tothe initial value. A unique group will be created every time thetransaction is called (identified by a unique transaction header).
If you want to assign the numbers yourself, that is using externalnumber assignment - from a source other than the system - you can createa task list for an existing group by calling the transaction again.