PLM - FSPEC.016 - Create-Update Article From Specification

INSIGHT Program
Functional Specification
Create / Update Article Master and

Cost from Specification
Version: 1.0
Last Revision Date: December 4, 2014
257012361.doc
Page 1 of 161
1/12/2015
INSIGHT Program
Document Statistics
Document Identification
The following is current information about this document:
Object ID
Title
PLM.FSPEC.16
Create / Update Article Master and Cost from
Specification
1.0
Version
Team Which Owns the Object
Creation Date
Author
System Version
Development Type
Document Status
Consulting Team
Approver(s) & Date
Limited Brands Approver(s) & Date
20-Jun-13
Pranav Patel
ECC 6.0 EhP 6
Enhancement
Draft
Revision
History
The following is a history log of revisions to the document:
Version
Author Of Revision
Creation
Date
Comments
1.0
1.1
Pranav Patel
Pranav Patel
20-June-13
17-Jul-14
2.0
Suresh Billa
11/26/2014
Initial version
CR for Turnkey BOM Transfer Total
Product Cost instead of VLC / Total
Unit Cost to ZC01 PIR for Turnkey
Finished Goods
UoM measure update on all existing
PIRs
Change
Request
Impact
The following is a summary of the hours impact of the change requests against
this functional specification:
Change
FSPEC Hours TSPEC Hours
Request # Impact
Impact
257012361.doc
Page 2 of 161
DEV Hours
Impact
Other Specs Impacted
1/12/2015
INSIGHT Program
Table of Contents
1
GENERAL REQUIREMENTS....................................................................................5
1.1
1.2
1.3
1.4
1.5
1.6
1.7
REQUIRED DATA......................................................................................................6
2.1
2.2
2.3
2.4
2.5
GENERAL.......................................................................................................... 12
DEPENDENCIES..................................................................................................13
SCHEDULING CONSIDERATIONS..........................................................................13
ENHANCEMENT / MODIFICATION DESIGN.........................................................13

5.1
5.2
5.3
GENERAL............................................................................................................ 9
SELECTION CRITERIA...........................................................................................9
OUTPUT LAYOUT..................................................................................................9
INTERFACE DESIGN................................................................................................9
4.1
4.2
4.3
INPUT DATA.........................................................................................................6
OUTPUT DATA......................................................................................................7
DATA MAPPING.................................................................................................... 8
LEGACY FILE DETAILS..........................................................................................9
LEGACY FILE LAYOUT:..........................................................................................9
FORM / REPORT DESIGN........................................................................................9

3.1
3.2
3.3
BUSINESS DRIVER.................................................................................................5
CURRENT FUNCTIONALITY....................................................................................5
DESIRED FUNCTIONALITY.....................................................................................5
ASSUMPTIONS..................................................................................................... 5
PROJECT / DEVELOPMENT CONSTRAINTS..............................................................6
PERFORMANCE CRITERIA.....................................................................................6
APPLICATIONS AFFECTED.....................................................................................6
GENERAL.......................................................................................................... 13
REQUIRED SCREENS..........................................................................................13
SCREEN LAYOUTS..............................................................................................14
ADDITIONAL INFORMATION.................................................................................14
6.1
6.2
6.3
6.4
6.5
TEST PLAN........................................................................................................14
BACKUP / RECOVERY.........................................................................................14
SECURITY PROFILE & AUTHORIZATION................................................................14
AUDIT / CONTROL..............................................................................................14
ERROR LOGS.....................................................................................................14
257012361.doc
Page 3 of 161
1/12/2015
INSIGHT Program
1
1.1
General Requirements
Business Driver
Description:
The purpose of this document is to develop an enhancement to create / update Article
Master and Cost from Specification automatically on a status change. Currently, this
functionality exists in Optiva through two interfaces (one for Article Master and second for
Cost update). As part of Optiva replacement, SAP PLM should provide the same
automation.
1.2
Current Functionality
Refer to functional specification for Optiva to Article Master Interface.
Old version
RXC 05 02_FSPEC 08
- Inbound Article Master Data FromOptiva (2).doc
Latest version
RXC 05 02_FSPEC 08
- Inbound Article Master Data FromOptiva.doc
Refer to functional specification for Optiva to SAP Cost Interface
ATP.06_IC.FSPEC.0
5[ATP.06.05.A_FSPEC.15]_Optiva cost interface.doc
1.3
Desired Functionality
Create / Update Article Master
The enhancement is required to synchronize specification data in SAP PLM and Article
Master Data. The process of synchronizing data will always be triggered by status change
on the specification. The enhancement will synchronize data from Specification to Article
Master i.e. unidirectional. In other words, data updated directly on Article Master will not
be synchronized back to Specification (Note: When a new Article Master is created, SAP
assigns Article Master Number automatically and EAN number (for Finished Goods only),
which should be received back and stored on the specification). The enhancement will be
used for both, creating new and updating existing Article Master records.
As SAP PLM is not able to provide all the information which is required to create an Article
Master, additional data will be determined from the Merchandise Category Reference
Articles and Sites, which will populate default fields. The Master Data Team will be
responsible for creating these Reference Articles and Sites.
The enhancement will be called from user exit C10Y0002 that is called when status on
specification is being saved. However, changing the specification data is not possible in
257012361.doc
Page 4 of 161
1/12/2015
INSIGHT Program
this user exit, which may require implementation of method AT_SAVE_CHECK of BADI
EHSS_SPEC_CHECKS to change specification data to update it with newly created
Article Master Number and EAN Number for Finished Goods. Any error during the
program logic should provide appropriate error messages, change the status back to its
original status and should not allow user to save the status change. User will take
necessary steps based on the error and change the status to trigger this enhancement
again.
A custom table should be created that will allow functional consultant to configure
specification types and status transition combination that should trigger Article creation /
update. If an entry for specification type and status transition combination does not exist
in this table, it should not create / update Article Master. For example, specification type
like LIST_SUB will not have any Article Master.
Specification Type
ESTRH-SUBCAT
ZFG_VAR
ZFG_VAR
ZFRM
ZFRM
ZGIFT_SET
ZING
ZING
Packaging (Multiple types e.g.
bottle, label etc)
Packaging (Multiple types e.g.
bottle, label etc)
Status From
EHSBT_APPL_SCOPESUBSTAT
170
175
170
175
175
170
175
170
Status To
EHSBT_APPL_SCOPE- SUBSTAT
175
270
171
270
171
270
270
171
270
171
Following table has list of all specification types that are considered Packaging. That
means Packaging entries in the table above will be maintained for every packaging
specification type in the table below.
Spec Type
ZACTUAT
ZAERO
ZAPPLIC
ZBAG_ENVEL
ZBSE_PLG
ZBTL_JAR
ZBRUSH
ZCAN_DRM
ZCAPASMBLY
ZL_CLOSURE
ZCLS_DISP
ZCLS_OVRCP
ZCLS_THRD
ZCLS_RODAPP
257012361.doc
Page 5 of 161
Description
Actuator (Packaging)
Aerosol Valve (Packaging)
Applicator/Sponge/Brush (Packaging)
Bag/Envelop (Packaging)
Base/Plug (Packaging)
Bottle / Jar (Packaging)
Brush (Packaging)
Canister/Drum (Packaging)
Cap Assembly (Packaging)
Closure (Packaging)
Closure Dispensing (Packaging)
Closure Overcap (Packaging)
Closure Threaded (Packaging)
Closure-Rod/Applicator (Packaging)
1/12/2015
INSIGHT Program
Spec Type
ZCOLLOR
ZCOMPCT
ZCONTNR
ZL_DDEVICE
ZDST_CVR
ZCRTN_FOLD
ZCRTN_LIN
ZHANG_TAG
ZL_LBL
ZLIPST_BSE
ZORF_RED
ZPCK_UDIV
ZPACKETTE
ZPAD
ZPAN
ZPARTITION
ZPENCIL
ZPOLYBAG
ZPOUCH
ZPMP_ACT
ZRIB_BOW
ZSEAL_DISC
ZSETP_BOX
ZSHIPPER
ZSHRINK
ZSIFT_SPT
ZSLEEVE
ZLSUB_ASSY
ZTISSUE
ZTUBE
ZCLS_TBE
ZVAC_PLAT
ZVIAL
ZWICK
ZL_OTHERPG
Description
Collar (Packaging)
Compact (Packaging)
Container (Packaging)
Device (Packaging)
Dust Cover (Packaging)
Folding Carton (Packaging)
Folding Carton Liner (Packaging)
Hangtag (Packaging)
Label (Packaging)
Lipstick/Base (Packaging)
Orifice Reducer (Packaging)
Packer U Divider (Packaging)
Packette (Packaging)
Pad (Packaging)
Pan (Packaging)
Partition (Packaging)
Pencil (Packaging)
Polybag (Packaging)
Pouch (Packaging)
Pump Actuator (Packaging)
Ribbon/Bow (Packaging)
Sealing Disc (Packaging)
Set-up Box (Packaging)
Shipper (Packaging)
Shrink (Packaging)
Sifter/Spout (Packaging)
Sleeve (Packaging)
Sub Assembly (Packaging)
Tissue (Packaging)
Tube (Packaging)
Tube with Closure (Packaging)
Vacform/Platform (Packaging)
Vial (Packaging)
Wick (Packaging)
OTHER or MISCELLANEOUS (Packaging)
This will allow functional consultant to determine if Article should be created / updated for
the same status depending on which status it is coming from. For example, Article Master
should be updated if the status on Specification is changed from Complete to Submitted
for Approval, but not if it is coming from Non-critical Change to Submitted for Approval.
257012361.doc
Page 6 of 161
1/12/2015
INSIGHT Program
The program will first check if the Article Master is already assigned to the specification
(Table ESTMJ). A new Article Master will be created if no assignment exists, otherwise
and existing Article Master will be updated. When a new Article Master in created, it
should be linked back to the specification. See Article Assignment tab in screenshot below
(The PLM Web UI screenshot was taken from non-retail system, so it says Material
Assignment, but it is same functionality).
Here is an example of Article Assignment screenshot from SAPGUI.
For Finished goods, in addition to Article Number, EAN number is also generated. The
specification should be updated with this information as well. The EAN number will be
stored in the property tree VAT ZFG_VARIANT Characteristic ZFG_EAN_NUMBER.
257012361.doc
Page 7 of 161
1/12/2015
INSIGHT Program
This enhancement will create following Article Types with appropriate Article Category
based on the specification type and Article Setup Type from Specification. This
information should be maintained in a custom table instead of hardcoding in the program.
Specification
Type
ESTRH-SUBCAT
ZFG_GEN
ZFG_VAR
ZGIFT_SET
ZFG_GEN
ZFG_VAR
ZGIFT_SET
ZFRM
Packaging
(Multiple types
e.g. bottle, label
etc)
Raw Material
ZING
Article Setup Type
Article Type
VAT
MARA- MTART
ZFG_PROJECT_INFO
Characteristic
ZFG_PI_ARTSETUP
Finished_Good
Finished
Goods (FERT)
Finished_Good
Finished Goods
(FERT)
Finished_Good
Finished Goods
(FERT)
Trading_Good
Trading Goods
(HAWA)
Trading_Good
Trading Goods
(HAWA)
Trading_Good
Trading Goods
(HAWA)
Formulas
(ZFRM)
Raw Materials
(ROH)
Raw Materials
(ROH)
Constituents
(ZCON)
Article
Category
MARAATTYP
Sub Type for

ZXPARAM
Generic (01)
Not
Applicable
VARIANT
Variant (02)
Sales Set
(10)
Generic (01)
Variant (02)
Sales Set
(10)
Single Article
(00)
Single Article
(00)
Single Article
(00)
Single Article
(00)
SALES_SET
Not
Applicable
VARIANT
SALES_SET
FORMULA
COMPONENT
CONSTITUEN
Refer to table above for the list of all Packaging specification types.
257012361.doc
Page 8 of 161
1/12/2015
INSIGHT Program
Note: The Generic Articles are created from cProjects. Refer to functional specification
PLM_FSPEC.001 - cProjects to RD Project Interface for more details. Overall logic
including the fields that will be created for Generic Articles is still part of this enhancement.
It will just be called from cProjects instead of on save of specification.
Currently, Article Masters of type ROH exist in SAP system for Raw Materials in Optiva
(SAP equivalent of LIST_SUB). However, business has change practice to create
Constituents for every Raw Material (100% of itself) if used in a formula. That means
Article Masters for Ingredients will created only as ZCON going forward, not as ROH. This
does not affect program logic as it will be controlled via entry in the table above.
Here is the number range used for each Article type (copied from existing functional
specification. For reference only).
Article
Type
Description
NR
from
NR to
FERT
Internally
Developed
10 000
000
HAWA
Trading
Goods
70 000
000
10
999
999
70
999
999
90 000
000
90
999
999
20 000
000
24
999
999
ZPLH
257012361.doc
Page 9 of 161
Placeholders
FERT or
HAWA
Variants of
Generic
Article
Comment
Number Ranges used for Generic
Articles
Number Range currently allows
the creation of 1 million Generic
Articles (Styles). Currently JDA
can only handle article numbers
of 6 characters
-> 10 as prefix in SAP to denote
internally developed products
JDA deals with the last 6
characters, POS can only deal
with 8 digits
Prefix will go to 1 if JDA goes to 7
digits
No prefix will be used if JDA goes
to 8 digits
Need to add more than 8 digits if
both JDA and POS system can
handle more than 8 digits
-> 70 as prefix in SAP to denote
third party developed products
For reference only. This
enhancement will never use this.
-> 90 as prefix in SAP to
denote placeholder or planning
products.
8 digit sequential number range
(NR) used for Variants of Generic
Articles
NR allows the creation of 10
million variants
1/12/2015
INSIGHT Program
FERT or
HAWA GIFT
SETS
25 000
000
ROH
Raw
Materials
30 000
000
VERP
Components
40 000
000
ZCON
Constituents
50 000
000
ZFRM
Formulas
60 000
000
NLAG
None
Merchandise
80 000
000
ABF
Waste
85 000
000
ZGFT
Gift Cards
86 000
000
ZPRE
Prepacks
87 000
000
29
999
999
34
999
999
44
999
999
54
999
999
64
999
999
84
999
999
85
999
999
86
999
999
89
999
999
Used for Gift Sets (Generic Gift

Set gets number of FERT or
HAWA range, real Gift Sets get
number of this range
Used for Raw Materials
Packaging Components
enhancement will never use this.
Used for Packaging Components
Used for Constituents
Used for Formulas
enhancement will never use this
number range as it will not enter
the Non Merchandise articles.
Waste Articles (manually created
in SAP)
Used for Gift Cards (manually
created in SAP)
Used for Prepacks (manually
created in SAP)
When a particular variant Article Master is created (i.e. small/strawberry Hand Crme)
using Size and Fragrance, the characteristics of the variant (small/strawberry) must not
change. An inconsistency will occur otherwise.
A generic Article Number must be passed while creating Variant Article Number (Article
Category 02). To find the generic Article Number for Variant Article being created, go to
Relationships sub view and find inherited specification with template ZGEN_VAR. The
name of the template should not be hardcoded in the program, but it should be read from
Environment Parameter ZPLM_GEN_VAR_TEMPLATE.
257012361.doc
Page 10 of 161
1/12/2015
INSIGHT Program
Environment parameters are stored in table TCGENV. Refer to function module

C1I0_TCGENV_READ for more details.
The Article Master assigned to this source specification is the Generic Article.
Following mandatory fields must be provided to create Article Master.
257012361.doc
Page 11 of 161
1/12/2015
INSIGHT Program
Article Number will be determined based on the number range for the Article Type / Article
Category being created. The program will use standard SAP function module to get next
number from the number range and use it to create new Article Master.
Program will use following ZXPARAM table entries to determine appropriate number
range.
Note: The Generic Articles are created from cProject. The cProjects program will pass
actual Generic Article number that should be created i.e. the logic to get next number for
Generic Articles is part of cProjects development.
Article Type and Article Category are determined based on the table shown above.
Program will use ZXPARAM table entries to determine appropriate Merchandise Category.
Note: The Generic Articles are created from cProject. The cProjects program will pass
actual Merchandise Category that should be created i.e. the logic to get Merchandise
Category for Generic Articles is part of cProjects development. Variant Article
automatically uses Merchandise Category from Generic.
For Gift Sets, the program should use the Merchandise Category from Generic associated
with the Gift Set. Find the inheritance relationship for the Gift Set specification. The
source specification in Inherits from section with template ZGEN_VAR is the Generic
Specification associated with Gift Set. The Article master linked to this Generic
Specification is Generic Article. Use the same Merchandise Category this is used in this
Generic Article.
257012361.doc
Page 12 of 161
1/12/2015
INSIGHT Program
In addition to these fields, characteristic profile is needed for Generic Article. The
cProjects program will pass appropriate sub type to determine profile based on following
ZXPARAM table entries.
The enhancement should create following Article Master views.
Basic Data
Classification
Listing
Sales
Logistics Distribution Center
Logistics Store
POS
The enhancement will populate following Article Master fields.

Standard SAP Retail Fields
Table
Name
Field
Name
MARA
MATNR
MARA
MAKT
MARA
Description
Type
Length
Article Number
CHAR
18
MTART
MAKTX
Article Type
Article Description
CHAR
CHAR
4
40
MATKL
Class (Merchandise
Category)
CHAR
MARA
ATTYP
Article Category
CHAR
MARA
MEINS
Base Unit of Measure
CHAR
MARA
SATNR
Generic Article Number
CHAR
18
EINA
LIFNR
257012361.doc
Page 13 of 161
Vendor Number
CHAR
10
Comments
SAP Retail system
generated Article number.
FERT, ROH, VERP etc.
Article Description
Lowest level of article
grouping in SAP Retail
Merchandise
Classification System.
Generic, Variant, Single
etc.
Article Base Unit of
Measure
The Generic Article that
the variant belongs to.
Will be blank when
passing Generic Articles.
External party supplying
the merchandise or
performing the service
Update
allowed
No
No
Yes
No
No
No
No
Yes
1/12/2015
INSIGHT Program
EINA
IDNLF
Vendor Article Number
CHAR
35
Vendors number for this

particular item
Yes
EINE
NETPR
Article Cost
CURR
11
Article cost or the labor

cost for a service
Yes
MARA
SAISO
Season Code
CHAR
Yes
MARA
MARA
SAISJ
MSTAE
Season Year
Article Status
CHAR
CHAR
4
2
Yes
Yes
CABN
ATNAM
Characteristic Type #1
CHAR
30
Fragrance Type
AUSP
ATWRT
Characteristic Value #1
CHAR
30
Value
CABN
ATNAM
CHAR
30
Color Type
AUSP
ATWRT
CHAR
30
Value
CABN
ATNAM
CHAR
30
Packaging Type
AUSP
ATWRT
CHAR
30
Value
CABN
ATNAM
CHAR
30
Size Type
AUSP
ATWRT
CHAR
30
Value (Default to NA)
Field Name
Description
Type
Length
ZZ_PLMID
PLM Number
CHAR
50
ZZ_SUBRAND
Sub-Brand
CHAR
ZZ_SUBCLASS Subclass
CHAR
No
No
No
No
No
No
No
No
Comments
Update
allowed
This number is generated in the

No
PLM system and passed to SAP.
A line of merchandise or
services produced and sold that
are similar or related in nature
(e.g., those developed by a
No
designer, or sourced from a
particular vendor or can be a
trademark). Typically it is the
primary differentiating factor.
This field stores the subclass the
style belongs to. Usually
consists of the predominate
attribute of the class or category.
No
Extend Table MARA (Refer RXC.05.02_FSPEC.05 for enhancement)

257012361.doc
Page 14 of 161
1/12/2015
INSIGHT Program
ZZARTMAS Table Fields (Refer RXC.05.02_FSPEC.05 for enhancement)

Field Name
Description
Type
Length
Comments
Update
allowed
Yes
ZZ_LSTYLE
Lifestyle
CHAR
15
The event, action, function,

occasion or point in time that is
associated with the product with
the intent of describing the
function/features for
marketing/purposes
ZZ_FORMNR
Formula
Number
Number 15
SAP PLM Specification Number

for Formula Specification
No
ZZ_PRANGE
Price Point
Range
CHAR
Provides initial price range for

which the style falls into
Yes
10
Dimension fields to be added to MARM based on future Article Design Options:

Field Name
Description
Type
Length
Comments
Update
allowed
HOEHE
Height
QUAN
13
Height
Yes
LAENG
Length
QUAN
13
Length
Yes
BREIT
Width
QUAN
13
Width
Yes
MEABM
Unit of
dimension
UNIT
Unit of dimension
Yes
NTGEW
Net weight
QUAN
13
Net weight
Yes
BRGEW
Gross weight
QUAN
13
Gross weight
Yes
GEWEI
Weight Unit
UNIT
Weight Unit
Yes
INHAL
Net contents
QUAN
13
Net contents
Yes
INHME
Content unit
UNIT
Content unit
Yes
VOLUM
Volume
QUAN
13
Volume
Yes
VOLUN
Volume Unit
UNIT
Volume unit
Yes
257012361.doc
Page 15 of 161
1/12/2015
INSIGHT Program
In order to provide Manugistics with Brand information as early as possible, the following
fields will be maintained when a FERT / HAWA Generic or Variant gets created:
Table Name
Field Name
Description
Type
Length Comments
MARA
PRDHA
Product
Hierarchy
Basic view
CHAR
18
MVKE
PRODH
Product
Hierarchy
Sales view
CHAR
18
ZZARTMAS
ZZ_ZZ_PLANORG6
CHAR
MARA
ZZ_PLANSTAT
CHAR
ZZARTMAS
ZZ_PLANORG2
CHAR
ZZARTMAS
ZZ_PLANORG10)
CHAR
Planning Org
- BBWD
Planning Org
- BBW
Planning Org
- VSB
Planning Org
- LZB
Product hierarchy
based on Brand
from cProjects:
BBW = Blank
LZB = 709LZB
VSB = 706VSB
Same as MARAPRDHA for the
following
Sales org / Distr
channel:
BBW = 1117/50,
1004/10
LZB = 1117/50,
1268/10
VSB = 1117/50,
1108/10
A when Brand =
BBW
A when Brand =
BBW
A when Brand =
VSB
A when Brand =
LZB
Update
allowed
No
No
No
No
No
No
Custom Data Mapping Table(s) will be created that will allow functional consultant to
configure which Specification field maps to which Article Master field for each Article Type /
Article Category. If Article Category is left blank, the mapping applies to all categories for
that Article Type. The mapping table will use Table Names / Field Names used by
BAPI_MATERIAL_MAINTAINDATA_RT. The table also have sequence number that
allows us to configure multiple rows / records for a particular table parameter. Please
make sure to use a different sequence number for each record.
257012361.doc
Page 16 of 161
1/12/2015
INSIGHT Program
Note: Article Master fields may be different for different Article Type. This table will also
allow using default values / constants for certain fields that are not stored in Specification
e.g. Any site specific views will be created for site ZC01 only.
257012361.doc
Page 17 of 161
1/12/2015
INSIGHT Program
Article
Type
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
257012361.doc
Page 1 of 161
Category
Seq
Table Name
Field Name
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
10001
10001
10001
10001
10001
10001
10001
11001
11001
11001
12001
12001
12001
30001
30001
30002
30002
15001
20001
20001
20001
20001
20001
20001
20001
20001
20001
20001
20002
20002
20002
20002
20002
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
ZAMARA
ZAMARA
ZAMARA
ZZARTMAS
ZZARTMAS
ZZARTMAS
SALESDATA
SALESDATA
SALESDATA
SALESDATA
PLANTDATA
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
BASE_UOM
CONT_UNIT
NET_CONT
NET_WEIGHT
PROD_HIER
SAESON_YR
SEASON
ZZ_PLANSTAT
ZZ_SUBCLASS1
ZZ_SUBRAND1
ZZ_PLANORG10
ZZ_PLANORG2
ZZ_ZZ_PLANORG6
DISTR_CHAN
SALES_ORG
DISTR_CHAN
SALES_ORG
PLANT
ALT_UNIT
EAN_CAT
GROSS_WT
HEIGHT
LENGTH
UNIT_DIM
UNIT_OF_WT
VOLUME
VOLUMEUNIT
WIDTH
ALT_UNIT
GROSS_WT
HEIGHT
LENGTH
NUMERATOR
Type
TX
TX
PK
PK
PK
PK
VAT
Characteristic
Val Typ
ZFG_GENERAL
ZFG_GENERAL
ZFG_EACH_A
ZL_COMR_MCS
ZFG_GENERAL
ZFG_GENERAL
ZL_COMR_MCS
ZL_COMR_MCS
ZL_COMR_MCS
ZL_COMR_MCS
ZL_COMR_MCS
ZL_COMR_MCS
ZFG_GEN_PRD_SIZEUOM
ZFG_GEN_PRD_SIZE
ZFG_EACH_WT_NET
ZSL_COMR_MCS_BRAND
ZFG_GEN_YEAR
ZFG_GEN_SEASON
ZSL_COMR_MCS_BRAND
ZSL_COMR_MCS_SUBCLASS
ZSL_COMR_MCS_SUBBRAND
ZSL_COMR_MCS_BRAND
ZSL_COMR_MCS_BRAND
ZSL_COMR_MCS_BRAND
CHAR_
CHAR_
NUM_V
NUM_V
CHAR_
CHAR_
CHAR_
CHAR_
CHAR_
CHAR_
CHAR_
CHAR_
CHAR_
ZL_COMR_MCS
ZL_COMR_MCS
ZSL_COMR_MCS_BRAND
ZSL_COMR_MCS_BRAND
CHAR_
CHAR_
PK
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_WT_GROSS
ZFG_EACH_HEIGHT
ZFG_EACH_LENGTH
ZFG_EACH_WIDTH
ZFG_EACH_WT_GROSS
ZFG_EACH_VOLUME
ZFG_EACH_VOLUME
ZFG_EACH_WIDTH
ZFG_PKVALUE_A
ZFG_PKVALUE_A
ZFG_PKVALUE_A
ZFG_PKVALUE_A
ZFG_PKVALUE_WT_GROSS
ZFG_PKVALUE_HEIGHT
ZFG_PKVALUE_LENGTH
ZFG_PKVALUE_EA_P_PK
PK
1/12/2015
CHAR_
CHAR_
NUM_V
NUM_V
NUM_V
MEAS_
MEAS_
NUM_V
MEAS_
NUM_V
CHAR_
NUM_V
NUM_V
NUM_V
NUM_V
INSIGHT Program
Article
Type
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
257012361.doc
Page 2 of 161
Category
Seq
Table Name
Field Name
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
10
10
10
10
10
10
10
10
10
10
10
10
20002
20002
20002
20002
20003
20003
20003
20003
20003
20003
20003
20003
20003
20004
20004
20004
20004
20004
20004
20004
20004
20004
15001
20001
20001
20001
20001
20001
20001
20001
20001
20001
20001
20002
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
PLANTDATA
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
SUB_UOM
UNIT_DIM
UNIT_OF_WT
WIDTH
ALT_UNIT
GROSS_WT
HEIGHT
LENGTH
NUMERATOR
SUB_UOM
UNIT_DIM
UNIT_OF_WT
WIDTH
ALT_UNIT
GROSS_WT
HEIGHT
LENGTH
NUMERATOR
SUB_UOM
UNIT_DIM
UNIT_OF_WT
WIDTH
PLANT
ALT_UNIT
EAN_CAT
GROSS_WT
HEIGHT
LENGTH
UNIT_DIM
UNIT_OF_WT
VOLUME
VOLUMEUNIT
WIDTH
ALT_UNIT
Type
VAT
Characteristic
ZFG_PKVALUE_A
ZFG_PKVALUE_A
ZFG_PKVALUE_A
ZFG_PKVALUE_WIDTH
ZFG_PKVALUE_WIDTH
ZFG_CASE_A
ZFG_CASE_A
ZFG_CASE_A
ZFG_CASE_A
ZFG_CASE_WT_GROSS
ZFG_CASE_HEIGHT
ZFG_CASE_LENGTH
ZFG_CASE_EA_P_CSE
ZFG_CASE_A
ZFG_CASE_A
ZFG_CASE_A
ZFG_CASE_WIDTH
ZFG_CASE_WT_GROSS
ZFG_CASE_WIDTH
ZFG_PALPATDIM_A
ZFG_PALPATDIM_A
ZFG_PALPATDIM_A
ZFG_PALPATDIM_A
ZFG_PALPAT_WT_GROSS
ZFG_PALPAT_HEIGHT
ZFG_PALPAT_LENGTH
ZFG_PALPAT_EAPPAL
ZFG_PALPATDIM_A
ZFG_PALPATDIM_A
ZFG_PALPATDIM_A
ZFG_PALPAT_WIDTH
ZFG_PALPAT_WT_GROSS
ZFG_PALPAT_WIDTH
PK
PK
PK
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
ZFG_EACH_A
PK
1/12/2015
ZFG_EACH_WT_GROSS
ZFG_EACH_HEIGHT
ZFG_EACH_LENGTH
ZFG_EACH_WIDTH
ZFG_EACH_WT_GROSS
ZFG_EACH_VOLUME
ZFG_EACH_VOLUME
ZFG_EACH_WIDTH
Val Typ
CHAR_
MEAS_
MEAS_
NUM_V
CHAR_
NUM_V
NUM_V
NUM_V
NUM_V
CHAR_
MEAS_
MEAS_
NUM_V
CHAR_
NUM_V
NUM_V
NUM_V
NUM_V
CHAR_
MEAS_
MEAS_
NUM_V
CHAR_
CHAR_
NUM_V
NUM_V
NUM_V
MEAS_
MEAS_
NUM_V
MEAS_
NUM_V
CHAR_
INSIGHT Program
Article
Type
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
257012361.doc
Page 3 of 161
Category
Seq
Table Name
Field Name
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
20002
20002
20002
20002
20002
20002
20002
20002
20003
20003
20003
20003
20003
20003
20003
20003
20003
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
UNITSOFMEASURE
GROSS_WT
HEIGHT
LENGTH
NUMERATOR
SUB_UOM
UNIT_DIM
UNIT_OF_WT
WIDTH
ALT_UNIT
GROSS_WT
HEIGHT
LENGTH
NUMERATOR
SUB_UOM
UNIT_DIM
UNIT_OF_WT
WIDTH
Type
VAT
Characteristic
Val Typ
ZFG_PKVALUE_A
ZFG_PKVALUE_A
ZFG_PKVALUE_A
ZFG_PKVALUE_A
ZFG_PKVALUE_HEIGHT
ZFG_PKVALUE_LENGTH
ZFG_PKVALUE_EA_P_PK
ZFG_PKVALUE_A
ZFG_PKVALUE_A
ZFG_PKVALUE_A
ZFG_PKVALUE_WIDTH
ZFG_PKVALUE_WIDTH
ZFG_CASE_A
ZFG_CASE_A
ZFG_CASE_A
ZFG_CASE_A
ZFG_CASE_WT_GROSS
ZFG_CASE_HEIGHT
ZFG_CASE_LENGTH
ZFG_CASE_EA_P_CSE
ZFG_CASE_A
ZFG_CASE_A
ZFG_CASE_A
ZFG_CASE_WIDTH
ZFG_CASE_WT_GROSS
ZFG_CASE_WIDTH
NUM_V
NUM_V
NUM_V
NUM_V
CHAR_
MEAS_
MEAS_
NUM_V
CHAR_
NUM_V
NUM_V
NUM_V
NUM_V
CHAR_
MEAS_
MEAS_
NUM_V
PK
1/12/2015
INSIGHT Program
Article Type: Article type being created / updated
Category: Article Category. If this field is blank, the entry applies to all categories
for that Article Type.
00
01
02
10
Single article
Generic article
Variant
Sales set
Seq: Unique record number for the row. This record number will help the user to
create multiple rows in the same table. See SALESDATA and UNITOFMEASURE
entries above.
Table Name: Target Table Name. This is the table name used by
BAPI_MATERIAL_MAINTAINDATA_RT.
Field Name: Target Field Name. The field name from the table name defined
above.
Type: Target Field Type

PK
Primary Key for the Table
TX
Use Phrase Code for

Transformation
PT
The field is Primary Key

AND use Phrase Code for
Transformation
This will help program identify the field as

primary key in the table
The value coming from Specification is
Phrase. Use Phrase Code instead of Phrase
Key. This will help us avoid maintaining
thousands of transformation entries, more
importantly when new phrases are created
and added to phrase sets.
The field is both PK and TX above
VAT: Value Assignment Type from source Specification
Characteristic: Characteristic Name from Value Assignment Type of Source

Specification
Val Type: Value Type that should be used from Characteristic

CHAR_VALUE
NUM_VAL_FM
MEAS_UNIT1
257012361.doc
Page 1 of 161
Use CHAR Value from the Characteristic

Use From Value from numeric Characteristic
Use Unit of Measure from numeric Characteristic
Default: Default Value. When specification source is provided in this configuration

table, it will be used as source for the Article Master field, otherwise default value
1/12/2015
INSIGHT Program
should be used. When both (specification source and default value) are populated
in the configuration table, default value will be used only when specification source
is blank.
Sys Default: System variable for default value e.g. sy-datum. The program will
automatically interpret values of these variables at runtime. Only one of the default
field should be populated.
Update: Flag to indicate if the field should be updated in subsequent update. If it

is blank, the field is updated only during initial create.
The above table will be populated when the source is property from Specification.
Article
Type
Category
FERT
Seq
Table Name
Field Name
Typ
10001
CLIENTDATA
PUR_STATUS
Source
Table
Name
APPLSCP
Source Field
Name
Default
Sys
Default
SYS_STATUS
The above table will be populated when the source is table value from Specification e.g.
Status. The table name field name are referenced from BAPI_BUS1077_GETDETAIL.
Article
Type
FERT
Category
FERT
Seq
Table Name
Field Name
20001
MATERIALDESCRIPTION
LANGU
20001
MATERIALDESCRIPTION
MATL_DESC
ID
Type
ID Cat
NAM
PROD
Default
Sys
Default
SYLANGU
The above table will be populated when the source is Identifier from Specification.
It will be functional consultants responsibility to maintain all required entries in these
tables to avoid any program errors.
The program will also support a transformation table that will allow functional consultant to
configure transformation rules before updating the value in Article Master.
Article
Type
FERT
FERT
Table Name
Field Name
Spec Value
Transform Value
CLIENTDATA
CLIENTDATA
CONT_UNIT
PROD_HIER
OZA
FERT
FERT
CLIENTDATA
CLIENTDATA
PROD_HIER
PROD_HIER
FERT
FERT
CLIENTDATA
CLIENTDATA
PROD_HIER
PROD_HIER
FERT
FERT
FERT
CLIENTDATA
CLIENTDATA
CLIENTDATA
PROD_HIER
PROD_HIER
PROD_HIER
FOZ
BATH & BODY
WORKS
BBW CANADA
BBW
INTERNATIONAL
LA SENZA
LSZ
INTERNATIONAL
VSB
VSB CANADA
VSB
INTERNATIONAL
257012361.doc
Page 2 of 161
Category
709LZB
709LZB
706VSB
706VSB
706VSB
1/12/2015
Updat
INSIGHT Program
Article
Type
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
FERT
Table Name
Field Name
Spec Value
Transform Value
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
CLIENTDATA
SALESDATA
PUR_STATUS
PUR_STATUS
PUR_STATUS
PUR_STATUS
PUR_STATUS
PUR_STATUS
PUR_STATUS
PUR_STATUS
PUR_STATUS
PUR_STATUS
PUR_STATUS
PUR_STATUS
PUR_STATUS
DISTR_CHAN
17
79
17
99
Z1
17
27
61
71
68
88
68
61
10
FERT
FERT
SALESDATA
SALESDATA
DISTR_CHAN
DISTR_CHAN
FERT
FERT
SALESDATA
SALESDATA
DISTR_CHAN
DISTR_CHAN
FERT
FERT
FERT
SALESDATA
SALESDATA
SALESDATA
DISTR_CHAN
DISTR_CHAN
DISTR_CHAN
FERT
SALESDATA
SALES_ORG
FERT
FERT
SALESDATA
SALESDATA
SALES_ORG
SALES_ORG
FERT
FERT
SALESDATA
SALESDATA
SALES_ORG
SALES_ORG
FERT
FERT
FERT
SALESDATA
SALESDATA
SALESDATA
SALES_ORG
SALES_ORG
SALES_ORG
FERT
ZAMARA
ZZ_PLANSTAT
FERT
FERT
ZAMARA
ZAMARA
ZZ_PLANSTAT
ZZ_PLANSTAT
FERT
ZZARTMAS
ZZ_PLANORG10
FERT
FERT
ZZARTMAS
ZZARTMAS
ZZ_PLANORG10
ZZ_PLANORG10
FERT
FERT
ZZARTMAS
ZZARTMAS
ZZ_PLANORG10
ZZ_PLANORG10
E0001
E0002
E0003
E0004
E0005
E0006
E0007
E0008
E0009
E0010
E0011
E0012
E0013
BATH & BODY
WORKS
BBW CANADA
BBW
INTERNATIONAL
LA SENZA
LSZ
INTERNATIONAL
VSB
VSB CANADA
VSB
INTERNATIONAL
BATH & BODY
WORKS
BBW CANADA
BBW
INTERNATIONAL
LA SENZA
LSZ
INTERNATIONAL
VSB
VSB CANADA
VSB
INTERNATIONAL
BATH & BODY
WORKS
BBW CANADA
BBW
INTERNATIONAL
BATH & BODY
WORKS
BBW CANADA
BBW
INTERNATIONAL
LA SENZA
LSZ
257012361.doc
Page 3 of 161
Category
10
10
10
10
10
10
10
1004
1004
1004
1268
1268
1108
1108
1108
A
A
A
A
A
1/12/2015
INSIGHT Program
Article
Type
Category
Table Name
Field Name
FERT
FERT
FERT
ZZARTMAS
ZZARTMAS
ZZARTMAS
ZZ_PLANORG10
ZZ_PLANORG10
ZZ_PLANORG10
FERT
ZZARTMAS
ZZ_PLANORG2
FERT
FERT
ZZARTMAS
ZZARTMAS
ZZ_PLANORG2
ZZ_PLANORG2
FERT
FERT
ZZARTMAS
ZZARTMAS
ZZ_PLANORG2
ZZ_PLANORG2
FERT
FERT
FERT
ZZARTMAS
ZZARTMAS
ZZARTMAS
ZZ_PLANORG2
ZZ_PLANORG2
ZZ_PLANORG2
FERT
ZZARTMAS
ZZ_ZZ_PLANORG6
FERT
FERT
ZZARTMAS
ZZARTMAS
ZZ_ZZ_PLANORG6
ZZ_ZZ_PLANORG6
FERT
FERT
ZZARTMAS
ZZARTMAS
ZZ_ZZ_PLANORG6
ZZ_ZZ_PLANORG6
FERT
FERT
FERT
ZZARTMAS
ZZARTMAS
ZZARTMAS
ZZ_ZZ_PLANORG6
ZZ_ZZ_PLANORG6
ZZ_ZZ_PLANORG6
Spec Value
Transform Value
INTERNATIONAL
VSB
VSB CANADA
VSB
INTERNATIONAL
BATH & BODY
WORKS
BBW CANADA
BBW
INTERNATIONAL
LA SENZA
LSZ
INTERNATIONAL
VSB
VSB CANADA
VSB
INTERNATIONAL
BATH & BODY
WORKS
BBW CANADA
BBW
INTERNATIONAL
LA SENZA
LSZ
INTERNATIONAL
VSB
VSB CANADA
VSB
INTERNATIONAL
A
A
A
A
A
A
Create / Update Cost

This section explains how Purchasing Info Record for Article Master should be created
(ME11) / updated (ME12) and how additive cost will be created (CK74N). Any cost
attributes maintained directly on Article Master e.g. MBEW-ZPLP1 will be handled as part
of Article Master create / update described above.
SAP PLM Specification maintains the complete planned Cost information which shall be
passed over to costing. This data will form the basis for Variance analysis against Base
SAP PLM cost estimates.
SAP PLM being the development system, every time a new approved BOM is passed
over, other cost information shall also be passed on.
It is required to collect the cost component information from specification and pass it over
to SAP Costing .The process of synchronizing data will always be triggered by
Specification (based on status of finished goods).The data update will be uni-directional
from SAP PLM to SAP costing.
257012361.doc
Page 4 of 161
1/12/2015
INSIGHT Program
Following is the type of values which will be available from Specification.
Total Product Cost

Labor Cost
Custom Brokerage Admin (%)
Custom Brokerage Admin ($)
Duty Fixed $ Amount
Duty Rate
Freight Fixed $ Amount
Freight Rate
Royalty Fee Fixed $ Amount
Following is the list of values which need to be passed over for each type of update:
1. Additive Cost (CK74N):
a. Freight
b. Import Duty
c. Royalty
d. Dutiable agency fees
e. Non dutiable agency fee
The header information for this transaction code shall be defaulted as follows:
Article number = from Specification
Costing Variant = ZOPT
Site = ZC01
Costing version = 1
Costing lot size = 1
257012361.doc
Page 5 of 161
1/12/2015
INSIGHT Program
The item level information is populated based on the data from Specification and data
mapping.
Item Category: defaulted as V
Description: from Specification
Total Price: from Specification
Cost Element: Defaulted based on description.
This will not be called for the components in the gift sets even if the components
themselves are finished product.
2. Purchasing Info Record (ME11 / ME12)
Note: Use BAPI_INFORECORD_GETLIST to check whether info-record exists or not
a. For Article Type FERT will have sub-contracting type of info record
i. Vendor = Default Vendor for Site ZC01
ii. Article = From Specification
iii. Purchasing Org = Default 1117
iv. Site = Default ZC01
v. Standard Quantity = From Specification
vi. Net Price = From Specification (labor cost + (total product cost *
(overhead pct / 100) + overhead fixed + total bulk cost) From
257012361.doc
Page 6 of 161
1/12/2015
INSIGHT Program
Specification VLC / Total Unit Cost (Value Assignment Type

ZFG_COST_PARAM, characteristic ZFG_COST_TOTUNIT_VLC).
If the property Turnkey? (Value Assignment Type
ZFG_COST_PARAM, Characteristic ZFG_COST_TURNKEY) is set
to Yes (Phrase ID LTDPL-IHS_GEN_0014010), use property Total
Product Cost (Value Assignment Type ZFG_COST_PARAM,
charactersitc ZFG_COST_PRODCOST_TOT) instead.
257012361.doc
Page 7 of 161
1/12/2015
INSIGHT Program
vii. Purchase Price UOM = From Specification

b. For Article Type HAWA will have sub-contracting type of info record
i. Vendor = Default Vendor for Site ZC01
ii. Article = From Specification
iii. Purchasing Org = Default 1117
iv. Site = Default ZC01
v. Standard Quantity = From Specification
vi. Net Price = From Specification (labor cost + (total product cost *
(overhead pct / 100) + overhead fixed + total bulk cost) From
Specification VLC / Total Unit Cost (Value Assignment Type
ZFG_COST_PARAM, characteristic ZFG_COST_TOTUNIT_VLC).
If the property Turnkey? (Value Assignment Type
ZFG_COST_PARAM, Characteristic ZFG_COST_TURNKEY) is set
to Yes (Phrase ID LTDPL-IHS_GEN_0014010), use property Total
Product Cost (Value Assignment Type ZFG_COST_PARAM,
charactersitc ZFG_COST_PRODCOST_TOT) instead.
vii. Purchase Price UOM = From Specification
257012361.doc
Page 8 of 161
1/12/2015
INSIGHT Program
This will not be called for the components in the gift sets even if the components
themselves are finished product.
[Feb 2015 Enhancement]: Update Order unit on all existing PIRs (Tcode ME12)
a) Get list of all existing PIRs for the articles Use BAPI_INFORECORD_GETLIST.
i.
Article = From Specification
b) Gen PO_Unit from specification. (use same logic that used to update PO_Unit for
article master)
Update PIR order unit EINA- MEINS with PO_UNIT for all PIRs from step-a.
Note: This enhancement should update only PIR order unit. Please exclude costing
PIR (ZC01 site PIR) as it is already getting updated with right unit of measure.
257012361.doc
Page 9 of 161
1/12/2015
INSIGHT Program
Existing condition for PIR creation or updation should be applicable for this
enhancement also. PIR should be updated only for FERT and HAWA articles with
Article Type 02 or 10.
3. Planned Price 1 in Article Master in the costing view (will be handled as part of
Article Master create / update described above)
a. Planned Price 1 = (Extended Cost / total Qty) * conversion Factor (if Uom
from Specification and Article are different). Total Qty = Quantity * (1 + non
std waste factor / 100). Use waste factor if non std waste factor is blank.
b. Planned Price Date 1 = System Date
Compare component unit of measure in specification to base unit of measure in
Article Master; if different, convert calculated total price per specification unit of
measure to Article unit of measure prior to populating Planned Price 1. These
fields should be updated only for Article Types other than FERT and HAWA.
1.4
Assumptions
The data synchronization is unidirectional i.e. from Specification to Article Master

The required configuration and master data for Article Master creation is already
completed
Note that the scope for this functional specification does not include Physical
Deletion and Re-classification of articles
All the property checks are already carried out successfully as part of another
enhancement when this is triggered. In other words, all mandatory / required
property values are maintained when this enhancement is triggered.
1.5
Project / Development Constraints
1.6
The complexity and timeline for this development may be impacted if the
configuration for Article Master, BOM or Costing is changed.
Performance Criteria
Real-time
1.7
Applications Affected
SAP Module
Impact/Change Description
NON-SAP
System
Impact/Change Description
257012361.doc
Page 10 of 161
1/12/2015
INSIGHT Program
2
2.1
2.2
Required Data
Input Data
From System Name
Structure or Table Name
Field Name
Field Description
Destination System Name
Structure or Table Name
Structure or Table Location
Field Name
Field Description
Format
Data Mapping
2.4
Legacy File Details

N/A
2.5
Legacy File Layout:

N/A
Length
Form / Report Design

N/A
3.1
General
N/A
3.2
Selection Criteria
N/A
3.3
Output Layout
N/A
Format
Output Data
2.3
Length
Interface Design
257012361.doc
Page 11 of 161
1/12/2015
INSIGHT Program
4.1
General
4.1
Dependencies
4.2
Scheduling Considerations
Enhancement / Modification Design
5.1
General
5.2
Required Screens
5.3
Screen Layouts
Additional Information
6.1
Test Plan
FEB-2015 Release UTC
FSPEC.16_FEB2015
UTC.xlsx
6.1.1
Related Business Scenario and Business Transactions
Business Scenario
Create Article Master for each type
Update existing Article Master
Test Article Master is not created for Spec types that are not configured in Z table
Test Specification Status Change is not allowed and Application Log is created in case of error
Test Cost update
6.1.2
Test Data
Finished Goods Generic and Variant

Project is created in cProjects with following details.
257012361.doc
Page 12 of 161
1/12/2015
INSIGHT Program
Note that the Style number (Generic Article Number) is not created in SAP yet.
257012361.doc
Page 13 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 14 of 161
1/12/2015
INSIGHT Program
Similarly, no Generic Specification is created or linked to the project.
The project has following Choice specific Tasks.
And those choice specific tasks have following fields populated.

257012361.doc
Page 15 of 161
1/12/2015
INSIGHT Program
Change status of project to Released and save.
257012361.doc
Page 16 of 161
1/12/2015
INSIGHT Program
Now the Generic Specification is created and linked to the project.
The specification has following details.
257012361.doc
Page 17 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 18 of 161
1/12/2015
INSIGHT Program
Please note the specification data is used as source for Article create / Update.
Following Article is created and linked to specification.
Go to MM43 and verify all fields are created / updated as per the functional specification.
257012361.doc
Page 19 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 20 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 21 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 22 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 23 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 24 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 25 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 26 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 27 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 28 of 161
1/12/2015
INSIGHT Program
The cProjects enhancement has also created following variant specifications and linked to
Generic specification.
The variant specification has following details.
257012361.doc
Page 29 of 161
1/12/2015
INSIGHT Program
Enter values in Brokerage Admin, Duty, Freight and Royalty Fee. These costs are
transferred to Additive Cost CK74N.
257012361.doc
Page 30 of 161
1/12/2015
INSIGHT Program
Enter values in some of the labor cost fields to make sure VLC / Total Unit Cost has some
value calculated in it. This is the price that will be transferred to PIR.
257012361.doc
Page 31 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 32 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 33 of 161
1/12/2015
INSIGHT Program
Populate Dimension data for Each and save.
257012361.doc
Page 34 of 161
1/12/2015
INSIGHT Program
There is no Article created / assigned to the variant specification.
Change Specification status to 171 and save.

Note: As of 2/6/2014, there is an open OSS message with SAP because the user exit on
status save is not called appropriately from PLM Web UI. Hence, the following status
change is performed using SAPGUI transaction CG02BD.
257012361.doc
Page 35 of 161
1/12/2015
INSIGHT Program
The Variant Article is created and linked back to specification.
The EAN code is also updated in Specification.
257012361.doc
Page 36 of 161
1/12/2015
INSIGHT Program
Go to MM43 and verify all fields are created / updated as per the functional specification.
257012361.doc
Page 37 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 38 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 39 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 40 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 41 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 42 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 43 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 44 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 45 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 46 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 47 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 48 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 49 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 50 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 51 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 52 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 53 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 54 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 55 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 56 of 161
1/12/2015
INSIGHT Program
The Generic Article is also updated appropriately.
257012361.doc
Page 57 of 161
1/12/2015
INSIGHT Program
Go to ME13 and verify PIR is created with appropriate values.
257012361.doc
Page 58 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 59 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 60 of 161
1/12/2015
INSIGHT Program
Go to CK74N and verify Additive Costs are created appropriately.
257012361.doc
Page 61 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 62 of 161
1/12/2015
INSIGHT Program
Trading Goods Generic and Variant

Similarly, following specification was created from cProjects. It also created a HAWA
Generic Article.
257012361.doc
Page 63 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 64 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 65 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 66 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 67 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 68 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 69 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 70 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 71 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 72 of 161
1/12/2015
INSIGHT Program
Following Variant Specification is created and linked the Generic Specification.
257012361.doc
Page 73 of 161
1/12/2015
INSIGHT Program
Update Cost Parameters to have values for PIR and Additive Cost.
257012361.doc
Page 74 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 75 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 76 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 77 of 161
1/12/2015
INSIGHT Program
There is no Article created yet.
Change the status of Specification to create Article and save.
257012361.doc
Page 78 of 161
1/12/2015
INSIGHT Program
The Article is created and linked to specification.
257012361.doc
Page 79 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 80 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 81 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 82 of 161
1/12/2015
INSIGHT Program
Following PIR is created for the Article.
257012361.doc
Page 83 of 161
1/12/2015
INSIGHT Program
Following Additive Costs are created for the Article.
Finished Goods Generic and Gift Set

Following Specification is created from cProjects.
257012361.doc
Page 84 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 85 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 86 of 161
1/12/2015
INSIGHT Program
And following Article is created from it.
257012361.doc
Page 87 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 88 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 89 of 161
1/12/2015
INSIGHT Program
Following Variant is created.
257012361.doc
Page 90 of 161
1/12/2015
INSIGHT Program
Add some cost details.
257012361.doc
Page 91 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 92 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 93 of 161
1/12/2015
INSIGHT Program
There is no Article created yet.
Change the status of the specification and save.
257012361.doc
Page 94 of 161
1/12/2015
INSIGHT Program
The Article is created and linked back to Specification.
257012361.doc
Page 95 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 96 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 97 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 98 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 99 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 100 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 101 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 102 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 103 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 104 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 105 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 106 of 161
1/12/2015
INSIGHT Program
Following PIR is created.
257012361.doc
Page 107 of 161
1/12/2015
INSIGHT Program
Following Additive Costs are created.
Formula
Following specification is created.
257012361.doc
Page 108 of 161
1/12/2015
INSIGHT Program
Article is not created yet.
Change specification status and save.
Article is created and linked back to specification.
257012361.doc
Page 109 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 110 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 111 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 112 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 113 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 114 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 115 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 116 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 117 of 161
1/12/2015
INSIGHT Program
Ingredient
Following Specification is created.
257012361.doc
Page 118 of 161
1/12/2015
INSIGHT Program
Change Specification Status and Save.
257012361.doc
Page 119 of 161
1/12/2015
INSIGHT Program
Article is created and linked back to Specification.
257012361.doc
Page 120 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 121 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 122 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 123 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 124 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 125 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 126 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 127 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 128 of 161
1/12/2015
INSIGHT Program
Packaging Component
Following Specification is created.
257012361.doc
Page 129 of 161
1/12/2015
INSIGHT Program
Change Specification status and save.
257012361.doc
Page 130 of 161
1/12/2015
INSIGHT Program
Article is created and linked back to Specification.
257012361.doc
Page 131 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 132 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 133 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 134 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 135 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 136 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 137 of 161
1/12/2015
INSIGHT Program
257012361.doc
Page 138 of 161
1/12/2015
INSIGHT Program
6.2
Backup / Recovery
6.3
Security Profile & Authorization
6.4
Audit / Control
6.5
Error Logs
257012361.doc
Page 139 of 161
1/12/2015

PLM - FSPEC.016 - Create-Update Article From Specification

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

PLM - FSPEC.016 - Create-Update Article From Specification

Caricato da

Copyright:

Formati disponibili

INSIGHT Program

Create / Update Article Master and

The following is current information about this document:

The following is a history log of revisions to the document:

Other Specs Impacted

ENHANCEMENT / MODIFICATION DESIGN.........................................................13

FORM / REPORT DESIGN........................................................................................9

Refer to functional specification for Optiva to SAP Cost Interface

Here is an example of Article Assignment screenshot from SAPGUI.

Article Setup Type

Sub Type for

Used for Gift Sets (Generic Gift

Environment parameters are stored in table TCGENV. Refer to function module

Following mandatory fields must be provided to create Article Master.

The enhancement should create following Article Master views.

The enhancement will populate following Article Master fields.

Base Unit of Measure

Generic Article Number

Vendor Article Number

Vendors number for this

Article cost or the labor

Value (Default to NA)

This number is generated in the

Extend Table MARA (Refer RXC.05.02_FSPEC.05 for enhancement)

ZZARTMAS Table Fields (Refer RXC.05.02_FSPEC.05 for enhancement)

The event, action, function,

SAP PLM Specification Number

Provides initial price range for

Dimension fields to be added to MARM based on future Article Design Options:

Article Type: Article type being created / updated

Type: Target Field Type

Primary Key for the Table

Use Phrase Code for

The field is Primary Key

This will help program identify the field as

VAT: Value Assignment Type from source Specification

Characteristic: Characteristic Name from Value Assignment Type of Source

Val Type: Value Type that should be used from Characteristic

Use CHAR Value from the Characteristic

Default: Default Value. When specification source is provided in this configuration

Update: Flag to indicate if the field should be updated in subsequent update. If it

Create / Update Cost

Following is the type of values which will be available from Specification.

Total Product Cost

Specification VLC / Total Unit Cost (Value Assignment Type

vii. Purchase Price UOM = From Specification

Article = From Specification

The data synchronization is unidirectional i.e. from Specification to Article Master

Project / Development Constraints

Structure or Table Name

Destination System Name

Structure or Table Name

Structure or Table Location

Legacy File Details

Legacy File Layout:

Form / Report Design

Enhancement / Modification Design

FEB-2015 Release UTC

Related Business Scenario and Business Transactions

Finished Goods Generic and Variant

Similarly, no Generic Specification is created or linked to the project.

The project has following Choice specific Tasks.

And those choice specific tasks have following fields populated.