ASNPurchase Req ready for ConvertingASN:An Advance Shipping Notice (ASN) is a notification of pending deliveries, sent in an electronic format used to list the contents of a shipment of goods.Convert PR to POApprove POPO ApprovedCreate PO output in Mail AttachmentPurchase Order Mail AttachmentSend PO mail attachment to Vendor, Purchase TeamReceive and Ack POConfirm Delivery DateManufacturer sends the ASN File after receiving the PO through SFTP Server.Upload ASN file by SFTPContact vendor and Goods issue Team via email with link to download ASN file to resolve.Send an email notification to the vendor about the ASN rejection details.ASN File not ValidASN: Advanced Shipping NoticeValidate ASN FileEmail Notification will be sent to goods in Team and VendorInbound Delivery Document(IDN)If ASN is Validated successfullyBy standard Idoc type DESADVSAP Batch job is triggered to process the file.Create Inbound DeliverySend Email Confirmation with Link to ASN file to Manufacturer

GOODS RECEIPTInbound Delivery CreatedOn Successfull receipt of goods in SAP EWM , Dynamic RFC will be called to update SAP Inventory and then update SAP CORP system by the IDOC.Receive GoodsOutside SAPQI Failed CompletelyReturn complete goods to vendorCancel Inbound DeliveryCancel ASNCreate Equipment with Supplier GUID as characteristic value in SAPSLED date updated in Equipment MasterGoods arrive at CDC location with pallet barcode taggingConduct QIQI Failed PartiallyReturn rejected goods to vendorUpdate Inbound DeliveryPut Away Task based on volumetric(capacity planning of the Warehouse).

In SAP System the task is confirmed by scanning the pallet id

Volumetric inf : weight + dimension needs to be maintained.Confirm the Task and Update Inventory in EWMDock Stock ReportSLED date = goods receipt date + 90 days during put awayScan the pallet and unpack itManual ProcessQI PassedPallet Id and delivery Id scanned for unloading.

System proposes destination bin by scanning pallet id.Asset unloaded in CDCAssets packed in destination BinReplication :Update BGR and Sap CORP SystemsSLED life duration maintained in MM SLED fieldBased on SLED , system will propose oldest asset for consumptionSMETS2 COMMS HUB SLED date will be the GR dateSMETS2 assets identified by BGSM asset tag and unique GUIDQS failed within 5 days of arrival - Reject DeliveryRaise a service request in OMSQS failed after 5 days of arrival - Receive Asset and follow vendor return processStore the GUID for : SMETS2 meters(gas and electricity) , Comms hubs , Gas proxy GUID (against the comms hub)

Track SMETS2 comms hubs using the GUID and NOT a BGSM tagShelf Life Expiry Date(SLED) assigned to Asset based on Received DateDCC will be updated on GR confirmation via BS001Goods Movement DocumentEquipment created and stock updatedSAP NW batch will pick the file and transform it into XML file and send to IHSAP will extract the inventory file and store it in application server.File based interface will be used to call BS001 to update DCC Inventory. File with asset information sent to Integration Hub(IH) using NW batch frameworkInterface will be triggered and goods related information will be updated from SAP to IH connected to DCCDCC will send the response back to SAP on submitting inventory file with exceptionsThe exceptions will be picked by SAP NW and store in application server in file format.SAP will pick up the exceptions and record in exceptions tool

Sheet1SMETS2 meter assetsSupplier Guid16-digitPhysically arrive into the CDC with pallet bar code attachedBGSM asset tag16-digit unique GUIDCHF GuidAsset IDSerial No in SAPSMETS2 Comms Hub assets16-digit CHF GUIDSerial number in SAP systemAssets packed in palletsAssets go for QS16-digit GPF GUID