After attending the GS1 conference in Chicago two weeks ago and presenting the existing GLN functionality to GS1 staff and several U.S. Healthcare customers, the following requirements were identified and submitted via a Business Case:
Although we provide basic GLN functionality in standard ERP and IS-H, meeting customer requirements for the GLN Sunrise will require immediate enhancements in standard ERP (and IS-H?) and development in SRM. In the future, improved GLN integration among ERP, SRM, and AII will be required.
Required Enhancements u2013 by October 2010 (to allow sufficient time to implement, test, and correct)
1. GLN Table (transaction EANGLN): support additional business objects for GLNs
- Storage Location (V_T001L-LGORT, with referenced address in table ADDR1_DATA), for Ship-to Locations u2013 the same as
IS-H prototype function, which recognized the need for this level u2013 at a lower-level plant hierarchy. Storage location GLNs
need to override the plant GLN as the Ship-to location.
- Deliver-to-Locations (overrides Plant and supplements Ship-to Locations) -- optional, but desirable; will be required in near-
future; this would be 4th N1 segment on the 850 IDoc
- Warehouse (V_T3001-LGNUM)-- linked to plant/Storage Location u2013 overrides plant
- Multiple Vendor GLNs u2013 two Vendor GLNs (Order-from and Pay-to) are required, per GS1 standards, with Return-to as a
recommended third GLN.
o This means that the current single Vendor GLN (maintained in the Vendor Master as three concatenated fields) is not
sufficient.
- Customer: Manufacturers, distributors, GPOs, 3PLs, and other supply-side customers require support of multiple Customer
locations for Customer u2013 Buyer, Ship-to, Deliver-to, and Bill-to u2013 since the PO will contain all four GLNs
o Same for Sales Orders, Order Acknowledgements, ASNs, invoices, and other supplier-outbound documents.
o This means that the current single Customer GLN (maintained in the Customer Master as three concatenated fields) is not
sufficient
2. SRM and Supplier Self-Service (both ERP and SRM) support for GLNs, including SRM ability to replicate GLNs from ERP
(EANGLN and/or VENDORGLN and/or CUSTGLN) into similar SRM tables that are accessed by SRM procurement, receipt,
supplier self-service, invoicing, and sourcing functions
3. The program populates IDocs only; we need to add the GLN on numerous transactions
- ERP
o Create, Change Display PO (ME21N, ME22N, ME23N)
o Goods Receipt (MIGO and MB1A)
o Maintain Service Entry Sheet (ML81N)
o Print/Transmit Service Entry Sheet (ML83)
o PO Confirmation/Acknowledgement
o Monitor Order Acknowledgements (ME92F)
o Create, Change, Display Inbound Delivery (VL31N, 32N, 33N)
o Create, Change, Display Outbound Delivery with ref to Sales Order (VL01N, VL02N, VL03N)
o Create , Change, Display, Cancel Invoice (MIRO, MIR4, MR8M)
o Evaluated Receipt Settlement -- ERS (MRRL)
o Consignment and Pipeline Settlement (MRKO)
o Address Maintenance (MEAN)
o Export Service Data (ML86)
o Import Service Data (ML87)
3. SRM
o Process Purchase Order (BBP_POC)
o Enter Purchase Order Response (BBPPCO02)
o Process Purchase Order Response (BBPPCO01)
o Confirm Goods/Services (BBPCF02)
o Confirm Goods/Services Centrally (BBP_CF03)
o Edit Invoice/Credit Memo(BBPIV02)
o Edit Invoice/Credit Memo Centrally (BBPIV03)
o Edit Internal Addresses (BBPADDRINTC)
o Edit Addresses (BBPADDRINVT) u2013 for business partners
o Edit Addresses (BBPADDREXT)
o Manage Business Partners (BBPMAININT)
4. SRM-generated 850 IDoc
5. Printouts and reports (PO Print and FAX, plus others to be identified in Functional Specification)
6. Sales Order: Multiple Customer GLNs (for ship-tos and deliver-tos -- from PO)
7. Terminology u2013 both GS1 and several customers do not like the terms EAN, UCC, and ILN, and urge us to use GS1-standard
terms "GLN" and "GTIN." Perhaps the use of GuiXT will suffice.
For 2011, additional enhancements will be required
Edited by: Jonathan Arck on May 5, 2010 11:13 PM