Professional Documents
Culture Documents
Split Tags
Unpublished – rights reserved under the copyright laws of the United States.
Intergraph Corporation
Huntsville, Alabama 35894-0001
Trademarks
Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, INtools, MARIAN, and PDS are registered
trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation.
Other brands and product names are trademarks of their respective owners
Table of Contents
Table of Contents
Introduction ........................................................................................................................4
What does it mean to split a tag? ..................................................................................4
Appendix C – CIPs...........................................................................................................29
Index ..................................................................................................................................31
Introduction
This document explains how to set up and use the split tags feature.
The Split Tag feature has been implemented for these cases. It allows you to create
sub-parts for a tagged item at different stages within the procurement and site control
module.
Splitting is available only on one level; in other words, a further splitting of the
sub-parts of a tagged item is not possible.
This kind of splitting is not to be confused with the already known and still available
features of splitting a quote detail in screen P.30.22 using the ‘Create Split’ button
and creating additional item shipments in the expediting screens. These two
functionalities are intended only for splitting quantities whereas the functionality
described in this document allows you to create a kind of assembly for an ident.
Creating Splits
Where can you create splits?
When a screen allows you to split a tag you will find a Split Tag button on that
screen.
• In the inquiry cycle for the detail of a quote summary -> screen P.30.22
• In the order cycle for the line item of an order -> screen P.50.07
• In expediting for an item shipment -> screens P.70.31, P.70.62, P.70.72
and P.70.74
• In traffic for an item shipment -> screens P.80.11 and P.80.51
• In site for an item shipment -> screens C.20.01, C.20.01.02, C.20.04 and
C.20.05
Appendix A includes a list of the screens that contain the Split Tag button.
• The item rule of the item type of the commodity code is either ‘TAB,’
‘TFM,’ ‘TOM,’ ‘TWM’, or SWT.
• The item has a valid tag number, not ‘---‘ or ‘UNTAGGED’.
Some screens have additional restrictions. These will be pointed out in the individual
chapters of the different modules.
A new ident is created for the detail tags. The commodity code of this ident is taken
over from the commodity code of the master tag enlarged by a sequential number.
To change the description of this new ident / commodity code in any screen, click
the Split Tag button to display screen S.80.25 Tag Description and History. Open
this screen by double-clicking the tag number. For the item-rule ‘TAB,’ the tab
page ident layout displays. For other tags, the for TAG Description displays. The
tag number of a detail tag is takenfrom the master tag and enlarged by a
sequential number.
You can update the tag number. When doing so, you are asked whether you want to
use screen S.80.24 Rename Tagged Items for this change, or if you want to update the
tag number immediately.
On Screen S.80.24, you can check all documents in which the tag number is used
prior to changing it. You can also update only the commodity code, only the tag
number, or both commodity code and tag number in the case of item rule TFM, TOM,
and TWM.
For idents of rule TAB, you can only update the tag number itself.
With an immediate update, both the commodity code and tag number are altered for
item rules TFM, TOM, and TWM. For idents of rule TAB or SWT, only the tag
number is changed.
No matter how you update the tag number and the commodity code, you must still
commit your changes to the database.
A detail tag is inserted as an additional line item, for example, as an additional quote
detail, an additional order line item, an additional item shipment, an additional MR
line item, and so on.
Attributes that are attached to the master tag are copied to the detail tag.
If the master tag can be found clearly without ambiguity on the BOM, the detail tags
will be inserted on the BOM. This requires that you have set the ZB_SPLNODE
project default. With this project default, you define the BOM node below which you
want the detail tags of your master tags to be placed. For each master tag a node will
be created below the node specified by ZB_SPLNODE. The node type of the newly
created node will be taken from the node that you have selected for the
ZB_SPLNODE project default. The new node is named like the tag number of the
master tag. The list positions of this node are the detail tags of the master. These
positions will not be taken into account by the MTO and are needed for the site
module. Thus, the issue of material against the BOM or the forecast and reservation
runs can also include the detail tags. The list position of the master tag will be linked
with the BOM node for the master tag. This BOM link is kept if you import BOM
data for a higher issue status. Although all these entries are made in the BOM, they
are not available for the user. They are not displayed in any BOM tree, but you can
see the linked data using B.20.01.18 Show BOM Link.
We strongly recommend that you do not apply any modifications to these nodes and
positions that are created automatically. Updating, for example, the quantities of the
list positions, has no effect on the data stored in procurement.
Only root nodes without child nodes are available for the ZB_SPLNODE project
default. After a node has been assigned to this project default, it is not displayed any
longer in any BOM tree (with the exception of screen C.30.02 Reserved Nodes).
Once detail tags have been created, the value of this project default cannot be
changed any longer.
To limit the scope in which the procedure looks for the tag-number in the BOM,
there exists a project default named ZB_SPLI_WP. With this project default you
define a B.40.12 Workpackage with one or more BOM-Start-Nodes.
Detail tags are displayed just below their master tag. The letters are shown in a light
blue color. If a detail tag is added later on, it may occur in the traffic screens that
because of the order sequence, detail tags do not appear just below their master tag.
The use of different colors is not restricted to the screens that contain the Split Tag
button. In all screens that display the master and detail tags, colors are used for the
visualization.
The newly created ident and commodity code are deleted (if they have not been used
somewhere else in the meantime).
A master tag always consists of at least two detail tags. Therefore, when you select
the second to last detail tag, the remaining detail tag is automatically deleted.
If no more detail tags exist, the master tag is no longer regarded as a master tag but as
regular material. In other words, it will be displayed with black letters again.
The Split Tag button is active only when setting the focus in the corresponding
block.
Once detail tags have been created, the quoted quantity cannot be changed any
longer.
The quoted quantity of a new detail tag is 0 and should be set to the correct value.
Sequence, engineering requisition, and position of master and detail tags are
identical; the released quantity of a detail tag is always 0.
The Unit Price, Extended Price, Discount %, and Discount Amount fields are only
updateable for regular material and master tags, not for detail tags. Other costs can be
entered for detail tags.
The Alternates button is not available for master or detail tags. Detail tags can be
deleted, whereas you cannot delete regular material or master tags.
If the tag number of the master tag cannot be found on the BOM, you can split the
same tagged item (differently if you wish) on several quote summaries.
If the master tag can be found on the BOM, only one supplier can create splits for this
quote detail.
If this supplier is not selected at the end of the bid evaluation but you want to create
splits for the supplier you have finally selected, you first have to delete the other
detail tags. If you have not created the order so far, you can then create the new splits
on the quote detail level. If you have already created an order, you will be able to
create splits in P.50. 07 only if you have previously deleted the splits of the other
supplier.
If you have to create splits for another supplier, you must first delete the detail tags of
the other supplier in screen P.30.22.
Note that these assertions refer to each individual master tag. In other words, you will
have no problems if you have an inquiry for two suppliers with two tagged items on
the BOM when one of these tagged items is split by the first supplier and the other
tagged item is split by the second supplier.
If the master tag is not included in the BOM, each supplier can split a tagged item.
On screen P.30.22, Commercial Evaluation, you can select only the master tag, not
the detail tags in the ‘Awarding’ folder.
When creating an order based on a bid evaluation in screen P.50.01, master and detail
tags will be copied over to the purchase order.
Detail tags can be created only for orders of types ‘Purchase Order’ and ‘Notice of
Commitment’ and their change orders. The feature of splitting tags is not available
for blanket orders.
Splits must not exist on the item shipment level. This can occur if either the order was
approved, expediting created splits, and then the approval was reversed; or you are
dealing with a change order of a purchase order for which splits were created by
expediting before the change order was created.
The position of master and detail tags is identical. If possible, the sub-position of the
master tag is set to 0, and the sub positions of the detail tags are increased by 1 for
each detail tag. (It is not possible to set the sub-position of the master tag to 0 if sub
line item position 0 already exists for another position, or if you create the first detail
tag on a change order.)
Once detail tags have been created, the quantity of the master tag cannot be changed
on a purchase order or a notice of commitment. The quantity of a master tag on a
change order can only be 0 or 1.
The quantity of a new detail tag is 0 and should be set to the correct value. The
quantity of a detail tag on a change order can only be updated if the quantity of the
master tag is 1. Updating the quantity of a detail tag implies a corresponding update
of the quantity of its item shipment.
When setting the quantity of a master tag on a change order to 0, the quantities of all
its detail tags are automatically set to 0, too.
An order line item is also regarded as a master tag if detail tags have been created on
the item shipment level. In other words, if you have approved an order, and
expediting has created detail tags on the item shipment level but then the approval of
the order is taken back, you will not be allowed to update the quantity of the order
line item for the detail tags that have been created by expediting.
The Update Quantity button is not available for master or detail tags.
The Unit Price and Extended Price fields can be updated only for regular material
and master tags, not for detail tags. Other costs can be entered for detail tags.
Detail tags can be deleted from purchase orders or notices of commitment if they
have not been approved. The sub-position of the master is reset to 1 if the last two
detail tags are deleted. Detail tags cannot be deleted from a change order unless they
were created on that change order.
Detail tags can be deleted from a purchase order or a notice of commitment even after
approval if the detail tag has been created after the order was approved. In other
words, if the detail tag was created by expediting, traffic, or site.
If you create a change order and place a master tag on it, all detail tags will be
automatically inserted, too. If you select a detail tag, the master tag and all remaining
detail tags are inserted as well. This is valid for both the automatic creation of a
change order via the Create Supplement button on the P.30.01 screen and the
manual creation of a change order via the Create CO button available on screen
P.50.07.
When you delete a master tag, all its detail tags are deleted as well. However, the
detail tags are kept on the original order and/or any other previously created change
orders when you delete a master tag from a change order. If the order was created
based on a bid evaluation, the splits are kept on the quote summary.
If an order is based on a bid evaluation, you may be unable to create splits for a
tagged item. In this case, the following error message displays: MAR-30124: “Master
tag cannot be split a second time.”
You will encounter this problem if one of the suppliers who was involved in the bid
evaluation, but not selected, has already created splits. You will then be able to create
splits in P.50.07 only if you have previously deleted the splits of the other supplier in
screen P.30.22 Quote Details.
This problem occurs only for tagged items that can be found on the BOM.
Expediting
Splits can be created only if the item has not been split (quantity split). In other
words, a split is possible only if exactly one item shipment with a quantity of 1 exists
for an order line item (apart from already possibly created detail tags). Apart from
this, the general restrictions apply, such as that the item rule of the item type of the
commodity code must be ‘TAB’, ‘TFM’, and so forth.
If detail tags are created by expediting, they are either created on the order line item
or on the item shipment level. Which level is chosen depends on two factors: the
setting of the ZP_SP_POLI project default and the first occurrence of a split.
If the ZP_SP_POLI project default has been set to Y, detail tags are always created
on the order line item level independent from the time/stage/level the first split
occurs. If ZP_SP_POLI has been set to N, detail tags are created on the order line
item level if some detail tags have already been created during the inquiry or the
order cycle because splitting is only possible on one level. If splits are created for the
first time by expediting (or later on by traffic or site), these detail tags will be created
on item shipment level.
Splits are created on the order line item level, and although the order has already been
approved, an additional line item and a corresponding item shipment are added.
Whether splits have been created on the order line item or on the item shipment level
can again be recognized by the color visualization. If splits are created on the order
line item level, the Pos, Sub, IS Pos, and IS Sub fields are displayed in blue letters.
If splits are created on the item shipment level, only the IS Pos and IS Sub fields are
shown in blue letters.
If splits are created on the order line item level, you are asked whether you want the
changes to be taken over to the order line item as well when updating the quantity or
the quantity unit of the item shipment of a detail tag. Otherwise, you have no
possibility to update this information on the order line item.
The position of master and detail tags is identical. If possible, the sub-position of the
master tag is set to 0, and the sub-positions of the detail tags are increased by 1 for
each detail tag. Depending on which level detail tags are created, this refers either to
the position / sub-position of the order line item or of the item shipment. If all detail
tags have been deleted, the sub-position of the master is reset to 1.
Unlike all other item shipments, the quantity unit of detail tags can be modified.
Once detail tags have been created, an additional item shipment cannot be created for
the master tag, and its quantity cannot be changed any longer (independent from the
level on which detail tags were created).
The item shipment quantity of a new detail tag is 1 and should be set to the correct
value. The split must be inserted with a quantity of 1 because in the screens of the
basic expediting module, item shipments are displayed only if their quantity is greater
than 0. If the split is performed on the order line item level, the quantity of the order
line item is 1 as well.
For most of the date fields and some other fields of the master tag, when committing
the entries, you are asked whether you wish to take over these data to the detail tags.
This feature is not available for the following fields:
These fields have been taken out because it either makes no sense to populate them
(weight, volume, dimensions), the validations that have to be performed are too
complex (delivery designation and routing method must match), or the automatic
calculation of further date fields is triggered taking into account the transit days of the
routing methods that can differ for each detail tag (Curr/Rev Prom Ship, Pred Ship,
Actual Ship).
The population of values from a master tag to its detail tags works for both splits
created on the order line item level and splits created on the item shipment level.
Import split tags from screen P.70.72. Click Print to File in the toolbar. Click the
Import tab. Upload the Microsoft Office Excel spreadsheet to the application server
and click Start. On screen P.70.71, click Export to create a Microsoft Office Excel
spreadsheet.
In the spreadsheet, all details that you marked with D in SP Materials will be marked
with an X.
In screen P.70.31 Shipment Groups, the population only works in the third block.
Changes are not populated when applied in the second block (Shipment Groups).
When setting one of the following dates for the last detail tag (i.e., there are no more
detail tags for which this date is NULL), the latest date of all detail tags is taken over
to the master tag:
Traffic
Splits can be created only if the item shipment quantity is 1. If the MR/traffic quantity
is not 0, it will be reset to 0.
The selected item shipment must be the only one for the corresponding order line
item or must already be a master tag.
In screen P.80.11 Material Receipts, detail tags can be created only for material
receipts of revision 0 that have not been closed.
When you click the Split Tag button on a traffic screen, detail tags are created on
either the order line item or item shipment level (depending on the setting of the
ZP_SP_POLI project default or the occurrence of the first split; see also the previous
chapter). In addition, these new detail tags are taken up as an additional MR/traffic
line item.
Detail tags created by traffic are created in the same way as those created by
expediting. The only difference is that in addition, they are inserted on the material
receipt and the BOL or container, respectively. Therefore, all explanations given in
the previous chapter are valid here, too.
The detail tag gets the sequence of the master tag increased by .001 or a multiple of
this.
If, for example, a sequence number of 2 has been assigned to a master tag, its detail
tags will have the sequences 2.001, 2.002, 2.003, and so on. Thus, it is ensured that
detail tags are always shown directly below their master tag.
Again, you are asked whether you want your changes to be taken over on the order
line item level and – in this case additionally on the item shipment level – when
updating the MR/traffic quantity. Thus, you do not have to call any expediting screen
just to change the item shipment quantity for newly (by traffic) created detail tags.
After opening the screen, you are only asked once to make a decision. This decision
is then valid as long as you stay in the screen. Only after closing and re-opening the
screen are you asked again how the system is to act.
You can receive either the master tag or its detail tags, but not both of them. This
refers not only to an individual material receipt (referring to a BOL or a container in
the case of screen P.80.51), but also to all receipts. In other words, if you have started
a master receiving, you can receive only the master tag on any other material receipt;
if you have started a detail receiving, the details can be received only on any other
material receipt.
By default, the system assumes a detail receiving. Therefore, whenever possible, the
MR/traffic quantity of the master tag is set to 0 and the corresponding quantities of
the detail tags are set to the expected quantity.
To switch from detail to master receiving, you have to set the MR/traffic quantity of
all detail tags to 0, and commit these changes. Afterwards, you will be able to enter
an MR/traffic quantity for the master tag.
If you want to receive only the master tag, you can delete all its detail tags, but this is
not required. If you want to receive only the detail tags, the master tag must remain
on the material receipt / BOL / container, nevertheless. When you delete a master tag,
all its detail tags will be automatically deleted as well. You do not have to include all
detail tags of a master tag.
If you select a master tag from a list of values or a multi-selection screen, all its detail
tags will be inserted, too. If you select a detail tag, the corresponding master tag will
be inserted, too, if not already present.
If you delete an MR/traffic line item that represents a detail tag, you do not delete the
corresponding order line item or the item shipment, only this MR/traffic line item. If
you want to delete the real detail tag, you have to call an expediting screen to do so.
When updating any of the date fields for a master tag in screen P.80.51, you are asked
whether you want these changes to be taken over on the detail tags, too. This is not
valid for Actual Ship field.
This population of values from a master tag to its detail tags works for splits created
on both the order line item level and the item shipment level.
When setting one of the following dates for the last detail tag (i.e., there are no more
detail tags for which this date is NULL), the latest date of all detail tags is taken over
to the master tag:
• Actual Ship
• Actual Stage Ready
• Actual Loaded
• Actual On Site
Site Control
Splits can be created only if the item shipment quantity is 1. If the received quantity
of the master tag is not 0, it will be reset to 0.
The selected item shipment must be the only one for the corresponding order line
item or must already be a master tag.
Detail tags can be only created for MRRs of revision 0 that have not been posted.
When you click the Split Tag button on a site screen, detail tags are created on either
the order line item or the item shipment level (depending on the setting of the
ZP_SP_POLI project default or the occurrence of the first split; see also the
Expediting chapter). In addition, these new detail tags are taken up as additional
inventory receipts.
Detail tags created by site are created in the same way as those created by expediting.
The only difference is that in addition they are inserted on the MRR. Therefore, all
explanations given in the Expediting chapter are valid here, too.
When updating the received quantity, you are asked whether you want your changes
to be taken over on the order line item level or on the item shipment level –
depending on what level the detail tags were created. Thus, you do not have to call
any expediting screen just to change the item shipment quantity for newly (by site)
created detail tags.
After opening the screen, you are only asked once to make a decision. This decision
is then valid as long as you stay in the screen. Only after closing and re-opening the
screen are you asked again how the system is to act.
You can receive either the master tag or its detail tags, but not both of them. This
refers not only to an individual MRR, but also to all MRRs (including direct receipts).
In other words, if you have started a master receiving, you can only receive the
master tag on any other MRR; if you have started a detail receiving, only the details
can be received on any other MRR.
By default, the system assumes a detail receiving. Therefore, whenever possible, the
received quantity of the master tag is set to 0, and the corresponding quantities of the
detail tags to the expected quantity (if the ZC_QTYRECV project default is set to Y).
To switch from detail to master receiving, you have to set the received quantity of all
detail tags to 0 and commit these changes. Afterwards, you will be able to enter a
received quantity for the master tag.
If you want to receive only the master tag, you can delete all its detail tags. But you
do not have to do this. If you want to receive only the detail tags, the master tag must
remain on the MRR nevertheless. When you delete a master tag, all its detail tags will
be automatically deleted as well. You do not have to include all detail tags of a
master tag.
If you select a master tag from a list of values or a multi-selection screen, all its detail
tags will be inserted, too. If you select a detail tag, the corresponding master tag will
be inserted, too, if not already present.
If you delete an inventory receipt that represents a detail tag, you do not delete the
corresponding order line item or the item shipment, only this inventory receipt. If you
want to delete the real detail tag, you have to call an expediting screen to do so.
MRR by Traffic
In screen C.20.02 Prepare MRR by Traffic, the Split Tag button is not provided
because MRRs are created here based on traffic items. If master or detail tags can be
found on a traffic item, these will be taken over on the MRR. If further splits are
needed, you have to go to screen C.20.01 where all other updates of the created
MRRs have to be performed, too.
OPI
The open procurement interface allows you to create detail tags, too. The restrictions
that have to be respected when splitting a tag also apply here. For example, you
cannot create a detail tag if the selected order line item is not a tagged item .
To create a detail tag on the order line item level, you have to include the
<POLI_SPLIT_TAG> tag in your xml-file. For the creation of a detail tag on the item
shipment level, the <ISH_SPLIT_TAG> tag is needed. These tags have to be
included below the LINES and SHIPMENTS elements/tags, respectively. The system
will then create a detail tag for the order line item or item shipment determined by
PO_NUMBER, …, POLI_POS, POLI_SUB_POS (and possibly ITEM_SHIP_POS
and ITEM_SHIP_SUB_POS).
More details can be found in the documentation for the open procurement interface.
Attached Attributes
If you call screen A.50.21 Attached Attributes for a master tag, the Insert for Detail
Tags, Delete for Detail Tags, and Update Detail Tags buttons are enabled. This
allows you to add, delete, or update attributes on the master tag level and to populate
these changes to all detail tags.
This feature works in the same way as the corresponding Insert on Line Items,
Delete on Line Items, and Update Line Items buttons that are active when calling
this screen for a header.
API
Detail tags can also be created using the inquiry and order APIs.
To create a detail tag for an order line item, you have to use the ins_detail_poli
procedure provided in the m_api_poli package. For the creation of a detail tag on the
item shipment level, you need the ins_detail_ish procedure in the m_api_ish package.
These procedures will only create a detail tag if the Split Tag button is enabled in the
corresponding SmartPlant Materials screen. In other words, the procedures will not
create detail tags if, for example, the quantity of the order line item or item shipment
is not 1 or if the item rule of the item type of the commodity code is not ‘TAB,’
‘TFM,’ ‘TOM,’ ‘TWM’, or ‘SWT’
CIPs
The hierarchical structure of master and detail tags is also saved internally as an
assembly. To prevent these assemblies from being exploded on the BOM or by the
MTO, the sub_line_ident_ind column has been added in the m_idents table.
You should make sure that your CIPs also consider this column if assemblies are to
be exploded.
Apart from these screens on which the button is provided, you can split tags via
screen OPI 10.01 OPI – Import Jobs or using the inquiry and order API.
Appendix C – CIPs
M_PCK_STD_CUSTOM.NEW_IDENT_CODE Used to define the newly created
ident code by a rule defined by the customer.
Index
API, 22 order line items, 12
attached attributes, 22 project defaults, 27
attributes, attached, 22 quote details, 11
CIPs, 23 reservation run, 21
colors, 8 site control, 20
commodity code, 5 split tag, 4
creating splits, 5 Split Tag button, 5, 6, 9, 11, 18, 20, 21, 25
defaults, project, 27 splits
deleting detail tags, 9 creating, 5
detail tag, 5 splitting
deleting, 9 tags, 4
expediting, 14 tag
Forecast, 21 split, 4
hierarchical structure, 23 tag number, 5
inquiry cycle, 11 tagged items, 4
items tags
tagged, 4 detail, 5
master tag, 5 master, 5
MIR by BOM commodity, 21 terminology, 5
MRR by traffic, 21 traffic, 18
OPI, 22 visualization, 8
order cycle, 12