Professional Documents
Culture Documents
RFID Enabled Integrated Inbound and Outbound Scenario with SAP Discovery System
Table of Content
Purpose ....................................................................................................................................................3 System Access Information......................................................................................................................3 System Landscape ...............................................................................................................................3 Logon Information.................................................................................................................................4 Process Flow ..................................................................................................................................4 Data used in this Process .....................................................................................................................4 Major Steps of RFID Enabled Flexible Outbound Delivery Processing ...............................................5 Create a Purchase Order (ERP System)........................................................................................5 Preparation (ERP System) ...................................................................................................................6 Create Stock .........................................................................................................................................6 Create Sales Order (ERP System).......................................................................................................7 Create Outbound Delivery Order Document (ERP System) ................................................................8 Monitor XI Messages (XI System) ..................................................................................................9 Load Goods (Auto-ID System) .............................................................................................................9 Monitor XI Messages (XI System) ................................................................................................11 Monitor Goods Issued Outbound Delivery Order (ERP System) ..............................................12 Monitor ASN Enrichment Process (XI System) ............................................................................12 Monitor Outbound Delivery (Auto-ID Cockpit) ..............................................................................13 Validate Inbound Delivery Order (Customer System) ........................................................................14 Unloading Goods (Auto-ID System) .............................................................................................15 Monitor Goods Received Unloading (Customer System)..........................................................16 Monitor Inbound Delivery (Auto-ID Cockpit).................................................................................17
Purpose
This demo showcases an automated inbound and outbound delivery processing in an ERP system using the radio frequency identification (RFID) technology. It starts with a purchase order from customer followed by sales order and delivery document in supplier system. Then picking and loading/shipping the products and issuing an Advanced Shipping Notification (ASN) to a customer. Finally, the demo shows how to create an inbound Delivery, Unload/Unpack, and good receipt in the customer system. The entire process is based on RFID Electronic Product Code (EPC) capture. The demo process allows you to do the following: Create Purchase Order for customer in ERP system Create a Sales Order and an Outbound Delivery Order for Supplier in ERP system Load in SAP Auto-ID Infrastructure (AII) system Send an advanced shipping notification (ASN) to the Customer in ERP system Create Inbound Delivery, Unload and Good Receipt for Customer in ERP system.
The following features are showcased in the demo: Integrated inbound and outbound Delivery Processing, including AII 5.1, ECC 6.0, and XI 7.0 Flexible delivery without packing step Out-of-box implementation without any custom development EPC related activities are conducted on a Test Tool using XML messages
System Landscape
The RFID Enabled Flexible Outbound Delivery Processing is built as part of SAP Discovery System. One character of this system is that it has one Web AS, and different SAP components acting on different clients as shown below.
The following table lists the details of SAP Solution Components on different clients. Client 001 200 300 400 Solution Component SAP Exchange Infrastructure (XI) 7.0 SAP R/3 (ECC) 6.0 (ERP System) SAP Business Intelligence (BI) 6.0 SAP Auto-ID Infrastructure (AII) 5.1
Page 3 of 17
Logon Information
To demonstrate this scenario, you need to logon to three clients. Their logon information is as following: Client 001(XI 7.0) 200 (ECC 6.0) 400 (AII 5.1) User Name and Password pisuper/sapides123 admin/admin admin/sap123
Note: Both customer and supplier will use Client 200 of SAP R/3 (ECC) 6.0 system as ERP system. We are not using BI capabilities in this demo.
Process Flow
Data used in this Process
The ERP system (Client 200) adopts SAP Best Practice setup. The data for this process is listed as following: Item Company Code Plant Division Sales Organization Shipping Point Distribution Channel Storage Location Customer Material Company SSCC Number Value BP01 BP01 01 BP01 BP01 01 0001 C6120 AII_MAT 0037000
Material AII_MAT information: Material Defined AII_MAT (PC) AII_MAT (CV) AII_MAT (CAR) UoM Piece Case = 10 PC Carton = 20 PC X Sales Unit GTIN 00037000553212 00037000664321 00037000775430
1. In Client 200 (ERP System). SAPGUI Menu Path Transaction Code SAP Menu Logistics Materials Management Create Vendor known Purchase Order ME21N Purchasing
1. Enter the value to proper fields as listed below. Field name Vendor Header > Org Data Tab Purchase Org Purch Group Company Code Item > Overview Tab Item Material SAP Discovery System 10 AII_MAT Page 5 of 17 BP01 100 BP01 Value RFID_VEND
PO Quantity OUn Delivery Date Net Price Currency Plant Storage Location
2. Enter. Acknowledge any information or warnings. 3. Save and take a note of Purchase Order 4500000_____. Even though not required for the successful creation of the purchase order, it is highly important to maintain a net price and a storage location for the successful creation of the inbound delivery later on in the process.
Create Stock
1. In Client 200 (ERP System). SAPGUI Menu Path SAP Menu -> Logistics -> Materials Management -> Inventory Management -> Goods Movement -> Goods Receipt -> Other MB1C
Transaction Code 2. Enter the following data: Field name Movement Type Plant Storage Location 3. Press Enter.
4. Enter one line item with the following data. Field name Item Material Quantity UnE 5. Press Enter. Value 1 AII_MAT 1000 PC
2. Enter the following in Create Sales Order: Initial Screen: Field name Sales Order Type Sales Organization Distribution Channel Division Value OR BP01 01 01
Field name Sold-to-party Ship-to-party Purchase order number Item Material Order Quantity SU Plant Amount 5. Press Enter.
6. Click on Enter (Continue) button when Partner Selection window shows up (Partner C6120 is checked). 7. Double click on the item in order to maintain the following settings Field name Shipping tab Stor. Location Volume Order Data tab 0001 100 GAL Value
Page 7 of 17
Sold-to-Party PO Number Purchase Order Item Customer Material Ship-to-Party PO Number Purchase Order Item PO Number created previously 10 PO Number created previously 10 (it has to be exactly the same value as you entered for the PO item, 1 does not equal 10) AII_MAT
8. Click on Save button. 9. Make a note of the Sales Order number ______.
1. In Client 200 (ERP). SAPGUI Menu Path SAP Menu Logistics Sales and Distribution Shipping Outbound Delivery Create and Transportation With Reference to Sales Order Single Document VL01N
Transaction Code
2. Enter the following in Create Outbound Delivery with Reference to Sales Order window. Field name Shipping Point Selection Date Order Value BP01 Make sure it is at least several days from today but not weekend or holidays. The default value should be the same Sales Order number created in previous step. Double check it.
3. Enter. 4. Select Picking tab. 5. Selecting Picking tab, and enter 1 in Picked Quantity column. 6. Save and make a note of the Outbound Delivery number 00800000_____.
2. Click on Monitor for Processed XML Messages. 3. Enter a time when you saved Delivery Order; otherwise you will get a lot of messages if the system is used for other purposes. 4. Click on Execute (F8) button. If you see any messages with an error status, try to click on the Restart button, in order to reschedule the sending of the message. 5. You will notice there are two messages similar as following. From XIs point of view, there is one inbound message from ERP (200) to XI (001) via IDoc adapter, and another outbound message from XI (001) to AII (400); all of them are for DeliveryExecutionRequestIn Receiver Interface.
6. Double clicking on each message, you can explore the content of them.
Dont proceed to Load Goods step until you see the delivery order in XI system. It sometimes takes a longer time if the system is heavily used.
1. In Client 400 (AII). AII Menu Path Transaction Code Auto-ID Infrastructure /AIN/TEST_CLIENT Tools Auto-ID Test Tool
Page 9 of 17
If you have ran this demo before, your XML message might be saved already. Click on Open , enter LOAD as Message Name, click on OK. The previously saved LOAD message button will be loaded to the test tool. Skip Step 2, and continue with Step 3, but with a modification to the value of DOCUMENT_NO with your own Delivery Order number.
2. Click Info Tab, and enter the following value Field name Message Name Device Controller ID Device ID Command Value LOAD AII_DC DEV_LOAD IN , to add the following
3. Under Observation Parameter List pane, click on Add Row button Field name Field Name Field Value Value DOCUMENT_NO
Outbound Delivery No, dont forget two leading zeros, such as 0080000001.
4. Click Tags Tab. 5. Click on Tag Generation button RFID Tag for material AII_MAT. Field name Tag Encoding Type Number of Tags FILTER_VALUE GTIN Product UOM Value SGTIN-96 1 0 00037000664321 AII_MAT CV , and enter the following value to generate one
You can use drop down list to select GTIN to avoid any typo.
6. Click OK button. One generated EPC is entered into the Tag List. 7. Click on Tag Generation button RFID Tag for pallet. Field name Tag Encoding Type Number of Tags Filter Value Company Prefix Value SSCC-96 1 0 0037000 , and enter the following value to generate one
Up to this step, you completed tag commissioning. The sequence of generating tags is not important, as long as you have a product tag and a pallet tag generated before next step. 9. Click on RFC button 10. Click on Save button . , and enter AIN as Destination. Click on OK button.
11. Click on Send button . This step represents a loading procedure in the real world. The XML message you sent is equivalent to that generated by a gate reader in a warehouse. 12. A message sent successfully will show at lower left.
Monitoring
2. Click on Monitor for Processed XML Messages. 3. Enter a time when you saved Delivery Order; otherwise you will get a lot of messages if the system is used for other purposes. 4. Click on Execute (F8) button. 5. Sometimes, XI messages are not aligned in the sequence as you like, either mixed with messages from other scenarios, or different execution time. You need to find out two messages with Sender Service ERPAII, Sender Interface DeliveryExecutionConfirmationOut, and Receiver Service SAPERP. In the following screenshot, messages 7-8 are the ones we are looking for.
7. Double clicking on each message, you can explore the content of them. These two messages inform ERP system that goods are issued.
Page 11 of 17
2. Enter your Outbound Delivery Order number, Enter. 3. Select Status Overview Tab. The Total Goods Movement Status (GM) should have an entry of C. 4. Click Document Flow button completed. 5. Click on Back button. 6. From menu, select Extras Delivery Output Header, you will see a list of output types, ASN1 and DERQ. Output Type DERQ triggers an IDoc to send delivery order information to AII. Output Type ASN1 triggers another IDoc to issue an Advanced Shipping Notification after ERP system received Goods Issued notification from AII. or F7 key. The status of goods issue for this delivery should be
3. Click on Monitor for Processed XML Messages. 4. Enter a time when you saved Delivery Order; otherwise you will get a lot of messages if the system is used for other purposes. 5. Click on Execute (F8) button. It takes some time to process messages in ccBPM. You might have to wait a few minutes if the system is heavily used.
3. Look for a message with ASNElectricLabelEnrichment as Sender Service, DespatchedDeliveryNotificationAbstract as Sender Interface, SAPERP as Receiver Service, and DESADV.DELVRY05 as Receiver Interface. It is the last message in the above screenshot. Open this message, and click on the path on the left pane: XML Message Inbound Message (CENTRAL)
Payload MainDocument (application/xml). Click on Display Window 1 button . The XML message is displayed on the right upper window. This is an XML format ASN with EPC numbers.
This enriched ASN is sent to client 200 (ERP system as a fake customer), you can find it in transaction /we05. However, there are two errors with reasons: 1) no purchase order is associated with it (there is no inbound process in this demo), and 2) arrived ASN message does not have EPC numbers (we didnt map the aforementioned XML format ASN to the IDoc DESADV.DELVRY05). In a closed loop delivery processing scenario (inbound and outbound), the customer side (inbound) will receive an ASN completed with EPC numbers.
1. Select Auto-ID Cockpit link on Demo Portal. Portal Menu SAPGUI Menu Path Transaction Code Customer AII Unload Goods Auto-ID Infrastructure /AIN/DTUIURL Auto-ID: Cockpit
Auto-ID Cockpit
2. Click Auto-ID Infrastructure 3. Enter the following value Field name Filter by Document Document Type
Searches
Document.
Value Outbound Delivery Document number (with two leading zeros, such as 0080000052) Outbound Delivery
3. Click on Go button. 4. In the Form View pane, double click the outbound delivery number. A new pane with three tabs (Document Items, Document Status) appears. SAP Discovery System Page 13 of 17
5. In the Document Items tab, you should see the Expected Quantity equals Actual Quantity for each item. 6. Select Document Status tab, you can see the Action Type ALBO-Load with a status Sent. 7. Select View Actual Document Item Objects button, you can view when, where and which device is used to load the products. There are multiple entries there. Each entry represents one scan of EPC number; for example, one for pallet and two for products.
Transaction Code
2. To find your Inbound delivery number, which was created automatically by the Customer ERP System, choose Search (F4), go to Tab External Delivery Number of Vendor and enter the Outbound Delivery number in the field External Delivery ID with leading zeros. Enter. 3. Take a note of Inbound Delivery number 1800000______. 4. Enter. 5. Check the following Data: Field name Item Material Delivery Quantity Sales Unit Vendor Batch Value 10 AII_MAT 1 CSE The batch number created during stock creation
6. In Status Overview Tab, check the Total Goods Movement Status. It should be A not started. 7. Select menu Extras -> Delivery Output. It shows an Idoc with Output Type AUBO is created. This Idoc is sent to AII System for unloading purpose
2. If your Test Tool is still open from previous Packing process, make minor changes to Device ID entry as following. Field name Device Controller ID Device ID Command Value AII_DC DEV_ULD IN
Under Observation Parameter List pane, check the following Field name Field Name Field Value Value DOCUMENT_NO Inbound Delivery No with a leading zero, such as 0180000047
3. If your Test Tool is closed, you can reload your previous saved message: click on Open button , and open your PACK document. Repeat Step 2 again. The reason of using previous Test message content is to avoid re-entering EPC numbers. The only difference between a PACK and an UNLOAD message is the Device ID in this demo configuration. 4. Click on RFC button 5. Click on Send button , and verify if AII is still a Destination. Click on OK button. .
Page 15 of 17
Transaction Code
2. Enter your Inbound Delivery Order number, Enter. 3. Select Status Overview Tab. The Total Goods Movement Status (GM) should have an entry of C. 4. Click Document Flow button should be completed. 5. Click on Back button. 6. Select a new transaction. Portal Menu SAPGUI Menu Path Transaction Code Customer ECC Purchase Order: ECC Customer: Display Purchase Order SAP Menu Purchasing ME23N Logistics Materials Management Purchasing Order Display or F7 key. The status of goods receipt for this inbound delivery
Purchase Order
3. Select Delivery Schedule tab. The delivered quantity should appear in the column GR Qty (goods receipt quantity). The column Open Quantity shows remaining goods from the Supplier. Scheduled Quantity minus Receipt Quantity equals Open Quantity.
Auto-ID Cockpit
2. Click Auto-ID Infrastructure 3. Enter the following value Field name Document Document type
Searches
Document.
Value Inbound Delivery Document number (with one leading zero, such as 0180000049) Inbound Delivery
3. Click on Apply button. 4. In the Standard View panel, double click the inbound delivery number. A new pane with two tabs (Document Items, Document status) appears. 5. Select the line and click View Actual Document Item Objects tab; you can view the handling unit hierarchy with EPC numbers. 6. Select Document Status tab, you can view action type and the status the action type.
Page 17 of 17