You are on page 1of 10

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 Pag e Date 4 2009/08 /24 1 Job Scheduled period 2 Rule & Policy modify. such as 有需求的 BOM / VPN 處理方式 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 5~6 2009/08 /24 .

............................................................................................................................................................................................................4 1.8 SiP Project Page 3 of 10 ...........7 2............................................................................2 RFC.................................................................2 SAP/ePO Terms and Definition.............................................................7 2..2 ZRFC_PP_PCE_0052.........5 1.......5 2..........7 2..................................................................................................................3 1............................................................7 2.............................................................................................................................................................................1 Functional description..........7 2..................5 1...........................................................................1 ZRFC_PP_PCE_0051..........................................................................................................................................................................................................................................................................................................目錄 目錄................................4 1..........................................................................................1 Program........................................ Business Flow .............................................................................................................................................................................................................................................................1 ZRPP_PCE_0106.......................................................................2.................... Related Process Detail .............1....2...............................................................................................................................................................................................................................................................................................................4 Rule & Policy.......................3 Flow Chart....................................................................................

1. then modify all the SAP BOMs with the same VPN number directly. the group id(1.Foxconn ePO will schedule a periodical job to call SAP RFC to return the allocation (with VPN number) maintained by Foxconn Sourcer to SAP .…) and allocation(100% and 0%) of alternative group will keep in SAP in the same time.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 will create the material master and BOM(FCST & Production) automatically as the edi 832 comes from ASUS. generate the VPN number of the alternative group within SAP Demanded BOM components. then Foxconn SAP will schedule a periodical job. Business Flow 1. and keep the VPN data in the Foxconn SAP addon tables. (4).Foxconn Sourcer will logon to ePO system in order to maintain the info record and allocation (usage%) of VPN alternative part numbers.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_0051) 02:00 everyday SiP Project Page 4 of 10 .1 Functional description (1). (2).In the B2B(Foxconn vs ASUS) real case. then Foxconn ePO will call SAP RFC to get all the VPN data in SAP Demanded BOM.2.3. (3).Foxconn SAP call program(ZRPP_PCE_0106) 00:00 everyday 1-3.

即 Usage prob. Buy by Foxconn self.只要任何一組 VPN 中含任何一顆料是 JTK.即半成品互為替代 1.BOM 展到最底階產生 VPN.BOM 材料若為 JBS or JAS. JAS 物料主檔中 MRP controller = JAS. 則整組 VPN 傳給 ePO 已與 Local BU(SCM)& ePO 確認 (3).4 Rule & Policy (1).VPN 中若含 JTK. SAP/ePO Term Definition VPN Virtual Part Number.BOM 中若不是在最底階. JTK 物料主檔中 MRP controller = JTK. 如 PSK10000001 2.1. 3. Buy and Sale from Asus 4. Assign Vendor by Asus 5. 都不用產生 VPN 傳給 ePO: 已與 Local BU(SCM)& ePO 確認 (2).3 Flow Chart flow chart-VPN & allocation 1. JTK 與非 JTK 都可在 SAP 上維護 allocation. Allocation 即 SAP 上的替代群組中使用率百分比. 目前 SiP Project 中 SAP 端採用 廠別+流水碼. SiP Project 已與 Local BU(SCM)& ePO 確認 Page 5 of 10 . No 1. Asus 傳到 Foxconn 時有會有 group id(因 Asus BOM 本身就有) 6. Module 替代 Allocation 落在 半成品階者. JBS 物料主檔中 MRP controller = JBS.則不用產生 VPN 傳到 ePO: 已與 ePO 確認 (4).讓 Sourcer 在 ePO 上維護 allocation. 各 ERP 系統上對自己 BOM 中替代群組的編號.會傳到 ePO.2 SAP/ePO Terms and Definition Here is the list of SAP & ePO terms that have been used during process discussion.

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

2. Related Process Detail 2.2 RFC 2.1 ZRPP_PCE_0106 Alternative Group auto create program Flow Chart 2.2.1 Program 2.1 ZRFC_PP_PCE_0051 Download alternative group data into sfc Flow Chart Import Para Type P_WERKS LIKE Ref MARC-WERKS Default Short Text Plant Export None Tables T_ZPCEPP33 SiP Project Page 7 of 10 .1.

2.2 ZRFC_PP_PCE_0052 Update BOM alloc from EPO alloc SiP Project Page 8 of 10 .Material and AltItemGroup mapping table Field Data Leng fields type Type th MANDT MANDT CLNT 3 VERION CHAR 2 MATNR MATNR CHAR 18 WERKS_ WERKS CHAR 4 D GRPID CHAR 20 ALLOC EWAHR DEC De c 0 0 0 Check table Short text Client Group Version Material number 0 Plant 0 Group id Usage probability in % (alternative item) purchase material pri use material pri desc Unit group contents prending field group contentsalternative material1| alternative material2 3 0 PUPRI USEPRI DESCR2 MEINS LEN INT2 INT2 CHAR UNIT INT2 5 5 50 3 5 0 0 0 GRPCON T LCHR 800 0 0 T_ZPCEPP34 Group id& high level material mapping table 2.

Flow Chart Import Para Type P_MODE LIKE Defa Ref ult CSDATA-XFELD 'N' Short Text Mode Export None Tables IT_ZVPNALLOC Material and AltItemGroup mapping table Field Data fields type Type WERKS WERKS_D CHAR GRPID CHAR MATNR MATNR CHAR AML CHAR AML_PN CHAR VENDOR_N CHAR O ALLOC SiP Project EWAHR DEC Leng th 4 20 18 60 30 De c 0 0 0 0 0 Plant Group ID(VPN ID) Material number AML short title AML material 30 0 Vendor NO 3 0 Usage probability in % (alternative item) Short text Page 9 of 10 .

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