December 17, 2007 SAP Discovery System version 3 English
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
SAP Discovery System Page 3 of 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 Access Information This section gives you the generic system access information needed to run this process.
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 Solution Component
001 SAP Exchange Infrastructure (XI) 7.0
200 SAP R/3 (ECC) 6.0 (ERP System)
300 SAP Business Intelligence (BI) 6.0
400 SAP Auto-ID Infrastructure (AII) 5.1
Logon Information To demonstrate this scenario, you need to logon to three clients. Their logon information is as following:
Client User Name and Password
001(XI 7.0) pisuper/sapides123
200 (ECC 6.0) admin/admin
400 (AII 5.1) 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 Value
Company Code BP01
Plant BP01
Division 01
Sales Organization BP01
Shipping Point BP01
Distribution Channel 01
Storage Location 0001
Customer C6120
Material AII_MAT
Company SSCC Number 0037000
Material AII_MAT information:
Material Defined UoM Sales Unit GTIN
AII_MAT (PC) Piece 00037000553212
AII_MAT (CV) Case = 10 PC X 00037000664321
AII_MAT (CAR) Carton = 20 PC 00037000775430
SAP Discovery System Page 5 of 17
Major Steps of RFID Enabled Flexible Outbound Delivery Processing
The following table lists major steps and message direction involved in RFID Enabled Flexible Delivery Processing.
From To Activity
Customer R/3(ERP System) Create Purchase Order
Supplier R/3 (ERP System) Create inventory if necessary
Supplier R/3 (ERP System) Create Sales Order
Supplier R/3 (ERP System) Create Outbound Delivery Document
Supplier R/3 (ERP System) Pick goods
Supplier R/3 (ERP System) AII Send Outbound Delivery Document
AII Tag goods
AII Load goods
AII (ERP System)
Update Outbound Delivery Document with goods issued status without EPC numbers
Supplier R/3 (ERP System) XI Send Advanced Shipping Notification document
XI AII Retrieve EPC information from AII and enrich Advanced Shipping Notification document
XI (ERP System)
Send enriched Advanced Shipping Notification document
Customer R/3 (ERP System) Create Inbound Delivery
Customer R/3 (ERP System) Unload goods
Create a Purchase Order (ERP System) ...
1. In Client 200 (ERP System).
SAPGUI Menu Path SAP Menu Logistics Materials Management Purchasing Purchase Order Create Vendor known
Transaction Code ME21N
1. Enter the value to proper fields as listed below.
Field name Value
Vendor RFID_VEND
Header > Org Data Tab
Purchase Org BP01
Purch Group 100
Company Code BP01
Item > Overview Tab
Item 10
Material AII_MAT
PO Quantity 10
OUn PC
Delivery Date One week from today
Net Price 1.00
Currency USD
Plant BP01
Storage Location 0001
Item Details > Confirmations Tab
Conf. Control Inbound Delivery
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.
Preparation (ERP System) After this demo has been executed for a period of time, you need to restock material AII_MAT.
Execute this step as necessary. You should also check that the posting period for the current date is open (via tcode MMPV).
Create Stock 1. In Client 200 (ERP System).
SAPGUI Menu Path SAP Menu -> Logistics -> Materials Management -> Inventory Management -> Goods Movement -> Goods Receipt -> Other
Transaction Code MB1C
2. Enter the following data:
Field name Value
Movement Type 501
Plant BP01
Storage Location 0001
3. Press Enter.
4. Enter one line item with the following data.
Field name Value
Item 1
Material AII_MAT
Quantity 1000
UnE PC
5. Press Enter.
SAP Discovery System Page 7 of 17
6. Press Save button . A document is posted message shows up at lower left corner.
Create Sales Order (ERP System) In this session, you create a Sales Order without a reference to a Purchase Order created in earlier step.
1. In Client 200 (ERP System)
SAPGUI Menu Path SAP Menu Logistics Sales and Distribution Sales Order Create
Transaction Code VA01
2. Enter the following in “Create Sales Order: Initial Screen”:
Field name Value
Sales Order Type OR
Sales Organization BP01
Distribution Channel 01
Division 01
3. Enter.
4. Enter the following in “Create Standard Order: Overview” screen.
Field name Value
Sold-to-party C6120
Ship-to-party C6120
Purchase order number
PO Number created previously
Item 10
Material AII_MAT
Order Quantity 1
SU CV
Plant BP01
Amount 10
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 Value
Shipping tab
Stor. Location 0001
Volume 100 GAL
Order Data tab
Sold-to-Party
PO Number PO Number created previously
Purchase Order Item 10 (it has to be exactly the same value as you entered for the PO item, 1 does not equal 10)
Customer Material AII_MAT
Ship-to-Party
PO Number PO Number created previously
Purchase Order Item 10
8. Click on Save button.
9. Make a note of the Sales Order number ______.
Create Outbound Delivery Order Document (ERP System) In this session, you create an Outbound Delivery Order based on previously created Sales Order. To save extra steps in delivery process, we are going to pick the goods at the same time the delivery order is created.
1. In Client 200 (ERP).
SAPGUI Menu Path SAP Menu Logistics Sales and Distribution Shipping and Transportation Outbound Delivery Create Single Document With Reference to Sales Order
Transaction Code VL01N
2. Enter the following in “Create Outbound Delivery with Reference to Sales Order” window.
Field name Value
Shipping Point BP01
Selection Date Make sure it is at least several days from today but not weekend or holidays.
Order 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_____.
SAP Discovery System Page 9 of 17
Monitor XI Messages (XI System) With current configuration, a DERQ output type Idoc is created as soon as an Outbound Delivery Order document is created and sent to the AII system via the XI system. We can take a look at the XI messages.
1. In Client 001 (XI).
SAPGUI Menu Path SAP Menu Exchange Infrastructure Monitoring Integration Engine- Monitoring
Transaction Code SXMB_MONI
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 XI’s 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.
Further scroll to the right, you can see,
6. Double clicking on each message, you can explore the content of them.
Don’t 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.
Load Goods (Auto-ID System) In this session, the warehouse worker will create RFID tags and put them on to relevant goods and pallet.
To reduce the complexity in demo process, we will use a Test Tool to complete the tag commissioning and loading in one step.
In flexible delivery processing, packing step is optional. We are going to skip this step and go to loading immediately based on the configuration of this demo system.
1. In Client 400 (AII).
AII Menu Path Auto-ID Infrastructure Tools Auto-ID Test Tool
Transaction Code /AIN/TEST_CLIENT
If you have ran this demo before, your XML message might be saved already. Click on Open
button , enter LOAD as Message Name, click on OK. The previously saved LOAD message 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 Value
Message Name LOAD
Device Controller ID AII_DC
Device ID DEV_LOAD
Command IN
3. Under Observation Parameter List pane, click on Add Row button , to add the following
Field name Value
Field Name DOCUMENT_NO
Field Value Outbound Delivery No, don’t forget two leading zeros, such as 0080000001.
4. Click Tags Tab.
5. Click on Tag Generation button , and enter the following value to generate one RFID Tag for material AII_MAT.
Field name Value
Tag Encoding Type SGTIN-96
Number of Tags 1
FILTER_VALUE 0
GTIN 00037000664321
Product AII_MAT
UOM CV
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 , and enter the following value to generate one RFID Tag for pallet.
Field name Value
Tag Encoding Type SSCC-96
Number of Tags 1
Filter Value 0
Company Prefix 0037000
8. Click OK button. One generated EPC is appended to the “Tag List”.
SAP Discovery System Page 11 of 17
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 , and enter AIN as Destination. Click on OK button.
10. Click on Save 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.
Monitor XI Messages (XI System) With current configuration, when the products are loaded, AII sends a delivery execution confirmation to ERP system. We can take a look at the messages.
1. In Client 001 (XI).
2. If you didn’t logout from last access, you can just click on Refresh button in XI system. Go to Step 5.
SAPGUI Menu Path SAP Menu Exchange Infrastructure Monitoring Integration Engine- Monitoring
Transaction Code SXMB_MONI
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.
Monitor Goods Issued – Outbound Delivery Order (ERP System)
In this session, you can observe the goods movement from outbound delivery document.
1. In Client 200 (ERP).
SAPGUI Menu Path SAP Menu Logistics Sales and Distribution Shipping and Transportation Outbound Delivery Display
Transaction Code VL03N
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 or F7 key. The status of goods issue for this delivery should be “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.
Monitor ASN Enrichment Process (XI System) In the demo configuration, the EPC numbers are not sent to ERP system along with a Goods Issued notification, but stored on AII system. To send an ASN with EPC numbers to a customer, XI system executes a ccBPM (cross-component Business Process Management) process to enrich the ASN by adding EPC numbers. We can observe this process in the XI system
1. In Client 001 (XI).
2. If you didn’t logout, you can just click on Refresh button in XI system. Go to Step 5.
SAPGUI Menu Path SAP Menu Exchange Infrastructure Monitoring Integration Engine- Monitoring
Transaction Code /SXMB_MONI
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.
SAP Discovery System Page 13 of 17
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 didn’t 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.
Monitor Outbound Delivery (Auto-ID Cockpit) As performed previously, the loading process is associated with an outbound delivery document. We can observe the information associated with this document within AII system.
1. Select Auto-ID Cockpit link on Demo Portal.
Portal Menu Customer AII – Unload Goods Auto-ID: Cockpit
SAPGUI Menu Path Auto-ID Infrastructure Auto-ID Cockpit
Transaction Code /AIN/DTUIURL
2. Click Auto-ID Infrastructure Searches Document.
3. Enter the following value
Field name Value
Filter by Document Outbound Delivery Document number (with two leading zeros, such as 0080000052)
Document Type 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.
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.
Validate Inbound Delivery Order (Customer System) In this session, you will observe an inbound delivery document automatically created in ERP system based on the received Advanced Shipping Notification (ASN) Idoc from supplier.
1. Select Customer System link on Demo Portal.
Portal Menu Customer ECC – Inbound Delivery: ECC Customer: Display Inbound Delivery
SAPGUI Menu Path SAP Menu Logistics Logistics Execution Inbound Process Goods Receipt for inbound Delivery Inbound Delivery Display Single Document
Transaction Code VL33N
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 Value
Item 10
Material AII_MAT
Delivery Quantity 1
Sales Unit CSE
Vendor Batch 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
SAP Discovery System Page 15 of 17
Unloading Goods (Auto-ID System) The warehouse worker moves the received pallets with their cases directly from the Truck through a RFID scanning gate that is mounted at the loading dock door into the Goods Received Area. Upon passing through the gate the Pallet and Case level EPC tags are scanned. This can be a repeated process as a single delivery can contain multiple pallets.
When AII system receives these scanned EPC numbers, it checks against the information sent from the Customer R/3 system. This is achieved automatically by AII System.
To reduce the complexity in demo process, we will use a Test Tool to complete this step.
1. Select Auto-ID System link on Demo Portal.
Portal Menu Customer AII – Unload Goods Auto-ID: Test Tool
AII Menu Path Auto-ID Infrastructure Tools Auto-ID Test Tool
Transaction Code /AIN/TEST_CLIENT
2. If your Test Tool is still open from previous Packing process, make minor changes to Device ID entry as following.
Field name Value
Device Controller ID AII_DC
Device ID DEV_ULD
Command IN
Under Observation Parameter List pane, check the following
Field name Value
Field Name DOCUMENT_NO
Field Value 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 , and verify if AII is still a Destination. Click on OK button.
5. Click on Send button .
6. A message sent successfully will show at lower left.
Monitor Goods Received – Unloading (Customer System)
In this session, you can observe the goods movement from outbound delivery document.
1. Select Customer System link on Demo Portal.
Portal Menu Customer ECC – Inbound Delivery: ECC Customer: Display Inbound Delivery
SAPGUI Menu Path SAP Menu Logistics Logistics Execution Inbound Process Goods Receipt for Inbound Delivery Inbound Delivery Display Single Document
Transaction Code VL33N
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 or F7 key. The status of goods receipt for this inbound delivery should be “completed”.
5. Click on Back button.
6. Select a new transaction.
Portal Menu Customer ECC – Purchase Order: ECC Customer: Display Purchase Order
SAPGUI Menu Path SAP Menu Logistics Materials Management Purchasing Purchasing Order Display
Transaction Code ME23N
2. Click on Menu Purchase Order Other Purchase Order, enter your own purchase order number.
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.
SAP Discovery System Page 17 of 17
Monitor Inbound Delivery (Auto-ID Cockpit) As performed previously, the unloading process is associated with an inbound delivery document. The EPC number contained in the document are used to check against scanned EPC numbers. We can observe the information associated with this document within AII system.
Select Auto-ID Cockpit link on Demo Portal.
Portal Menu Customer AII – Unload Goods Auto-ID: Cockpit
SAPGUI Menu Path Auto-ID Infrastructure Auto-ID Cockpit
Transaction Code /AIN/DTUIURL
2. Click Auto-ID Infrastructure Searches Document.
3. Enter the following value
Field name Value
Document Inbound Delivery Document number (with one leading zero, such as 0180000049)
Document type 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.