-
Sep 23rd , 2011SMI Group 3EDI MappingApproach Proposal
-
ScopeThis approach applicable only to messages already existing
in SMI landscape (SAP is either a source or target)
Message can be either in US or Oevel webMethods servers
Available business messages in SMI
landscapePurchaseOrderPurchaseOrderAcknowledgePurchaseOrderAcknowledgeOutAdvanceShipNoticeOutInvoiceOutShipmentOutListPriceListSellThruRemittanceAdviceInInventoryCountPlanningScheduleInDeliveryReceiptInDeliveryReceiptOutShipmentSummaryReturnsAnnouncement
-
SAP API Details
MessageDirectionAPIAPI
NameContactPurchaseOrderInboundRFCZ_VGT2317_SP_CREATE_SIMPLEChristian
BarbaPurchaseOrderAcknowledgeInboundRFCZ_VGT2317_SOMM_CHANGE_SIMPLEPaul
KeragaPurchaseOrderAcknowledgeOutOutboundIDOCORDERS05, ORDRSP,
Z01Christian BarbaAdvanceShipNoticeOutOutboundIDOCZEGT1DELVRY03,
DESADV, Z01Ravi GavankarShipmentOutListOutboundIDOCZEGTSHPMNT05EDI,
SHPADV, Z01Ravi GavankarInvoiceOutOutboundIDOCZEGT3028INVOIC02,
INVOIC, Z01Karin KestensPriceListOutboundIDOCPRICAT02, PRICATElsa
Goret/Bill
MorrisonSellThruInboundRFCZ_VGT2317_SP_CREATE_SIMPLEVerweijen,
BartRemittanceAdviceInInboundIDOCPEXR2002, REMADVMichael
CahillInventoryCountInboundRFCZ_VGT2317_SP_CREATE_SIMPLEVerweijen,
BartPlanningScheduleInInboundN/AN/AMangesh AdmaneShipmentOutList
(ShipmentSummary)OutboundIDOCZEGTSHPMNT05EDI, SHPADV, Z02Ravi
GavankarPurchaseOrder
(ReturnsAnnouncement)InboundRFCZ_VGT2317_SP_CREATE_SIMPLEChristian
BarbaDeliveryReceiptInInboundRFCZ_FRFC4084_DEL_RECPTChristian
Barba
-
Business Scenario DescriptionPurchaseOrder Inbound Purchase
Order message
PurchaseOrderAcknowledge Inbound Order Response / Order
Confirmation
PurchaseOrderAcknowledgeOut Outbound Reverse Purchase Order
notifying partner of orders created on their behalf
InvoiceOut Outbound Invoice / Billing Message
ShipmentOutList Outbound Shipment message notifying partner of
goods leaving our distribution center (multiple deliveries)
AdvanceShipNoticeOut Outbound Shipment message notifying partner
of goods leaving our distribution center (single delivery)
-
Business Scenario Description (Continued)SellThru Inbound Sales
Activity reported from our retail trading partners
RemittanceAdviceIn Inbound communication between trading
partners which provides a detailed accounting relative to a
payment
InventoryCount Inbound Inventory balance reporting from our
retail trading partners
PlanningScheduleIn Inbound Forecast / Planning Schedule message
used to plan for the supply of products
DeliveryReceiptIn Inbound message used to report the physical
receipt of goods at our trading partners selling locations or
warehouse
-
Business Scenario Description (Continued)DeliveryReceiptOut
Outbound message used to report the physical receipt of goods at
our warehouse (i.e. return shipments)
ReturnsAnnouncement Inbound message announcing return
merchandise shipment
ShipmentSummary Outbound message sent to freight forwarders for
shipment consolidation
PriceList Outbound Price / Sales Catalog message to supply ELC
product information to our trading partners
-
Mapping ApproachStep 1 Review existing functional
specificationStep 2 Analyze a sample production messageStep 3 -
Identify if the business scenario/message fits/exists in current
SMI landscapeStep 4 Identify the SMI global mapping document in
SharePoint
(Canonical_GlobalTemplate.xls)http://us-rp-smiproj01:9865/SMI/Shared%20Documents/Forms/AllItems.aspx?RootFolder=%2fSMI%2fShared%20Documents%2fInterfaces%20Reference%20Material%2fCanonical%20Mapping&FolderCTID=&View=%7bA266F078%2d2D18%2d41C6%2dBB9A%2d072D161AC70E%7dStep
5 Start mappingField MappingValue Mapping (Cross
reference)Structural MappingStep 6 Identify any EDI control
requirementsStep 7 Affiliate team to review the mapping document
with offshore functional specification author, validate and confirm
before submission
** EDI Standard Message Type Message Version EDI Partner (EANCOM
DESADV 96A Boots)
-
Cransoft / Middleware Cross-Referencing EDI EDI Cross Reference
Master Matrix;
