Hon Hai PCEBG SiP Project

“Functional Spec” (SA document) :

VPN Allocation function between SAP and ePO

Sign:
SAP:____________ Prepared by: YI-Fong Wang
ePO:____________ Date: Aug 24, 2009
Local BU:_________
 Table of Changes

No Topic Page Date

1 Job Scheduled period 4 2009/08/24
2 Rule & Policy modify, such as 有需求的 BOM / VPN 處理方式 5~6 2009/08/24
3 First Time Go-Live need 6 2009/8/25
4 VPN number 第五碼識別是否有 allocation 群組 6 2009/8/25
5 第一次 ePO 上線 data migration 規則變更 6 2009/9/4
6 上傳 VPN to ePO 時，SAP 須同時提供使用到該組 VPN 的上層物料 6 2009/9/4
目錄
Catalog......................................................................................................................................................3
1. Business Flow......................................................................................................................................4
1.1 Functional description.................................................................................................................4
1.2 SAP/ePO Terms and Definition..................................................................................................5
1.3 Flow Chart...................................................................................................................................5
1.4 Rule & Policy...............................................................................................................................5

3. Related Process Detail........................................................................................................................7

2.1 Program......................................................................................................................................7
2.1.1 ZRPP_PCE_0106....................................................................................................................7
2.2 RFC.............................................................................................................................................7
2.2.1 ZRFC_PP_PCE_0051.............................................................................................................7
2.2.2 ZRFC_PP_PCE_0052.............................................................................................................8

SiP Project Page 3 of 10

1 Business Flow
1.1 Functional description

(1).In the B2B(Foxconn vs ASUS) real case, Foxconn SAP will create the material master and BOM(FCST &
Production) automatically as the edi 832 comes from ASUS, the group id(1,2,3,…) and allocation(100% and
0%) of alternative group will keep in SAP in the same time, then Foxconn SAP will schedule a periodical job,
generate the VPN number of the alternative group within SAP Demanded BOM components, and keep the
VPN data in the Foxconn SAP addon tables, then Foxconn ePO will call SAP RFC to get all the VPN data in
SAP Demanded BOM.
(2).Foxconn Sourcer will logon to ePO system in order to maintain the info record and allocation (usage%) of
VPN alternative part numbers.
(3).Foxconn ePO will schedule a periodical job to call SAP RFC to return the allocation (with VPN number)
maintained by Foxconn Sourcer to SAP , then modify all the SAP BOMs with the same VPN number directly .
(4).the current configuration of SAP/ePO scheduled Job and tasks is described as bellow
(the period of scheduled Job will be updated properly with the newest status of productive environment through
the discussion by SAP and ePO both side):

1-1.Foxconn ePO call SAP RFC(ZRFC_PP_PCE_0052) 09:30 / 11:30 / 14:30 / 16:30 / 18:30 / 22:00 everyday
(This is for the Purpose of getting more Real-time allocation)
1-2.Foxconn SAP call program(ZRPP_PCE_0106) 00:00 everyday
1-3.Foxconn ePO call SAP RFC(ZRFC_PP_PCE_0051) 02:00 everyday

SiP Project Page 4 of 10

1.2 SAP/ePO Terms and Definition
Here is the list of SAP & ePO terms that have been used during process discussion.
No SAP/ePO Term Definition
1. VPN Virtual Part Number, 各 ERP 系統上對自己 BOM 中替代群組的編號,
目前 SiP Project 中 SAP 端採用 廠別+流水碼, 如 PSK10000001
2. Allocation 即 SAP 上的替代群組中使用率百分比,即 Usage prob.
3. JBS 物料主檔中 MRP controller = JBS, Buy and Sale from Asus
4. JAS 物料主檔中 MRP controller = JAS, Assign Vendor by Asus
5. JTK 物料主檔中 MRP controller = JTK, Buy by Foxconn self, Asus 傳到
Foxconn 時有會有 group id(因 Asus BOM 本身就有)
6. Module 替代 Allocation 落在 半成品階者,即半成品互為替代

1.3 Flow Chart

flow chart-VPN &

allocation

1.4 Rule & Policy

(1).BOM 材料若為 JBS or JAS, 都不用產生 VPN 傳給 ePO: 已與 Local BU(SCM)& ePO 確認
(2).BOM 展到最底階產生 VPN,只要任何一組 VPN 中含任何一顆料是 JTK, 則整組 VPN 傳給 ePO
已與 Local BU(SCM)& ePO 確認
(3).BOM 中若不是在最底階,則不用產生 VPN 傳到 ePO: 已與 ePO 確認
(4).VPN 中若含 JTK,會傳到 ePO,讓 Sourcer 在 ePO 上維護 allocation,
JTK 與非 JTK 都可在 SAP 上維護 allocation, 已與 Local BU(SCM)& ePO 確認

SiP Project Page 5 of 10

(5).SAP 端廠別會在設定檔(ZPCECONTROLVALUE)中做轉換 ,同一 BU 只會傳遞統一的”BU 識別碼”給 ePO
已與 Local BU(SCM)& ePO 確認
(6).SAP 會先將 [有需求的 BOM] 撈出,再展到最底階,最底階中有替代群組者才產生 VPN,
1.[有需求的 BOM] 指
9N/KN/PN 所有的 active FCST.BOM(ZPCEPP12), 及 Open W/O 的 Production BOM(RESB)
2. 為方便採購人員維護 allocation 時辨示，SAP 上傳 VPN 給 ePO 時，同時需將使用到該組 VPN 的上階料號一并
傳給 ePO。(FCST 為 9N/KN/PN 料號；Open W/O 為 W/O 成品料號)
3. 第一次上線時
視吳淞江廠 SIP 為新單位，依新單位作業重新上線。舊 SIP allocation 資料不需進行 data migration。
已與 SAP IT & ePO IT 確認
(7).ePO 端透過 RFC,只會傳在 ePO 上 allocation 有變動的 VPN 回 SAP 做 BOM 修改,沒變動的不傳,
VPN number 則以 VPN number 第五碼做識別(V: 有 allocation, X:只有自己為主料)
如: PSK1A000033
已與 SAP IT & ePO IT 確認
(8).VPN 中就算只有主料, 沒有替代材, 是要產生 VPN 傳給 ePO(allocation = 100%)
已與 Local BU(SCM)& ePO 確認

SiP Project Page 6 of 10

2 Related Process Detail
2.1 Program

2.1.1 ZRPP_PCE_0106
Alternative Group auto create program
Flow Chart

2.2 RFC

2.2.1 ZRFC_PP_PCE_0051
Download alternative group data into sfc
Flow Chart

Import

Para Type Ref Default Short Text

P_WERKS LIKE MARC-WERKS Plant

Export
None

Tables

SiP Project Page 7 of 10

 T_ZPCEPP33
Material and AltItemGroup mapping table
fields Field type Data Type Length Dec Check table Short text
MANDT MANDT CLNT 3 0 Client
VERION CHAR 2 0 Group Version
MATNR MATNR CHAR 18 0 Material number
WERKS WERKS_D CHAR 4 0 Plant
GRPID CHAR 20 0 Group id
Usage probability in % (alternative
ALLOC EWAHR DEC 3 0
item)
PUPRI INT2 5 0 purchase material pri
USEPRI INT2 5 0 use material pri
DESCR2 CHAR 50 0 desc
MEINS UNIT 3 Unit
LEN INT2 5 0 group contents prending field
group contentsalternative material1|
GRPCONT LCHR 800 0
alternative material2
T_ZPCEPP34
Group id& high level material mapping table

2.2.2 ZRFC_PP_PCE_0052
Update BOM alloc from EPO alloc
Flow Chart

SiP Project Page 8 of 10

 Import
Para Type Ref Default Short Text
P_MODE LIKE CSDATA-XFELD 'N' Mode

Export
None
Tables
IT_ZVPNALLOC
Material and AltItemGroup mapping table
fields Field type Data Type Length Dec Short text
WERKS WERKS_D CHAR 4 0 Plant
GRPID CHAR 20 0 Group ID(VPN ID)
MATNR MATNR CHAR 18 0 Material number
AML CHAR 60 0 AML short title
AML_PN CHAR 30 0 AML material
VENDOR_NO CHAR 30 0 Vendor NO
ALLOC EWAHR DEC 3 0 Usage probability in % (alternative item)

RETURN
The different alloc data between EPO and SAP
fields Field type Data Type Length Dec Short text
INPUTID CHAR 20 0 EPO Import batch id(ECN Number)
SiP Project Page 9 of 10
 WERKS WERKS_D CHAR 4 0 Plant
GRPID CHAR 20 0 Group ID(VPN ID)
MATNR MATNR CHAR 18 0 Material number
ALLOC EWAHR DEC 3 0 Usage probability in % (alternative item)
MSG CHAR 100 0 Error message

SiP Project Page 10 of 10