SCEM: Procurement Visibility Scenario: Applies To

SCEM: Procurement Visibility
Scenario
Applies to:
SCM 5.0.
Supply Chain Event Management (SCEM) – Procurement Visibility using Web Communication Layer.
For more information, visit the Supply Chain Management homepage.
Summary
Supply Chain Event Management – Procurement Visibiltiy scenario enables the buyer and vendor
communication faster through web Inteface. Delays (or) Opportunities for improvement can be identified over
a period of time to improvise the procurement processes. We can meausre Supply Chain KPIs for business
partners (in this case, vendor) with SCEM in integration with Business Intelligence (BI). Planned and Actual
events and Unexpected events like delivery date change and/or Delivery Quantity change can be notified
due to short-supplies etc. Creation of Event Handlres can be controlled for different parameters from Source
ERP System. In this example, it is SAP.
This article explains about

- List of Expected and Unexpected Events for Procurement Visibility Scenario
- What is the filtering criteria to have Event Handler created in SCEM for Purchase Order
- How the Expected Dates and Times are derived to display in the Event Handler
- How the Actual Dates and are displayed in the Event Handler
- How the Status Attribute Values change
- Display of Events in Web Communication Layer (WCL).
Authors: Janakiram Katakam and Gopala Turaga

Company: Intelligroup Inc
Created on: 18 August 2009
Author Bio
Janakiram Katakam has over 13 years of experience in Supply Chain Management. He is a Senior Business
Consultant with 7+ years of experience in PP/PP-PI/WM/SNP Implementations / Upgrades and technical
Support. He has delivered on many complex projects in Energy Sector, Pharmaceuticals and Consumer
Products Industies.
Gopala Turaga has over 20+ years of experience in Supply Chain Management and is SAP Certified
Associate in MM, SD and CRM. He is a Senior Principal Consultant and Competency Lead for SAP Supply
Chain Event Management at Intelligroup with 12+ years of experience in functional MM/SD/PP/PP-
PI/WM/CRM implementations / upgrades. He has delivered many complex full cycle implementations and
rollouts at various capacities in manufacturing, public sector, petrochemicals, semi conductor and beverage
industries.
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

© 2009 SAP AG 1
SCEM: Procurement Visibility Scenario
Table of Contents
Introduction to Supply Chain Event Management (SCEM) ................................................................................3
Procurement Visibility .........................................................................................................................................3
Expected Events.................................................................................................................................................4
Unexpected Events ( ).....................................................................................................................................5

Statuses of Events..............................................................................................................................................6
Process Steps in Procurement Visibility .............................................................................................................7
Step 1: Creation of Purchase Order................................................................................................................7
Step 2: Receiving the Vendor Acknowledgement.........................................................................................13
Step 3: Receiving the Advanced Shipping Notification (ASN)......................................................................17
Step 4: Goods Receipt ..................................................................................................................................20
Conclusion: .......................................................................................................................................................23
Related Content................................................................................................................................................23
Disclaimer and Liability Notice..........................................................................................................................24

© 2009 SAP AG 19
Introduction to Supply Chain Event Management (SCEM)

Supply Chain Event Management maintains various events which enable customers and suppliers to monitor
the activities and necessary actions required, if there are any delays, etc. Web Interface (WCL) enables the
supplier to view and update the various activities like Purchase Order creation, vendor acknowledgement
along with their statuses. Faster corrective action can be taken for any unexpected delays from customer or
supplier.
Procurement Visibility
The Objective of Procurement Visibility scenario is to identify the events (activities) and notify the expected
(planned) dates for all activities when purchase order is created. Supplier and Vendor are able to access the
Events and improvise the process time to time.
The below schematic diagram briefly explains about the current example for ‘Procurement Visibility’ scenario
and importance of Expected / Actual / Unexpected Events.
Note: Standard SAP SCEM provides integration to Web Communication Layer (WCL) and necessary web components
to be activated. Basis consultant and Java expert would be helpful in this area.

© 2009 SAP AG 19
Expected Events
Menu Path: SPROÆ Event Management Æ Event Handlers and Event Handler data Æ Expected Events Æ
Define Profiles for Expected Events
An Expected Event can be defined as an Event that describes the normal flow of the business process.
The expected events Receive Acknowledgement, Receive Advanced Shipping Notification, Receive Goods,
Receive Invoice and Payment are configured to display in the Event Handler for the Purchase Order (PO).
The duration of events are also configured in this transaction. For example, if Payment expected event
expected date need to be displayed after 30 days (720 Hours) from Receive Invoice expected date can be
configured here.
Note: During execution of expected events, actual dates are reported either through SAP or Web Communication Layer
(WCL).

© 2009 SAP AG 19
Unexpected Events ( )
Unexpected Event can be defined as an Event which occurs unplanned in the flow of Business Process.
Below screenshot displays the unexpected events ‘Delivery Quantity Change’ and ‘Delivery Date Change’.
‘Delivery Date and Quantity Change’ unexpected event is displayed below.

© 2009 SAP AG 19
Statuses of Events
Status changes for Events can be traced in ‘Status Detail ’ tab.
Statuses Attribute Profiles and Status Attributes are configured in SCEM. Status Attribute Profiles are
assigned to Event Handlers.

© 2009 SAP AG 19
Process Steps in Procurement Visibility

Step 1: Creation of Purchase Order
Creation of PO in ECC system
Transaction: ME21N/ME22N/ME23N
4500018287 Purchase Order is created with:

• Purchase Organization = 0001
• Plant = 0001
• PO Quantity = 100
• Delete Flag for Item 0010 = NO
• Material = 1708
Event handler in SCEM:

Transaction: /SAPTRX/EH_LIST
Menu Path: Event Management Æ Monitoring and Lists Æ Event Handler List
Note: Event Handler is identified with Application Object Type (PCM10_ITEM), Purchase Order Number (4500018287)
Item number of purchasing document (00010).

© 2009 SAP AG 19
Configuration Setup:
Default statuses assigned under ‘Define Status Attribute Profiles’ are displayed in Event Handler.
Menu Path: SPRO --> Event Management --> Event Handlers and Event Handler data --> Status
Configuration Setup: How Event Handler is created in SCM system:

The Event Handler is created after satisfying the following criteria:
• LOEKZ (Deletion Indicator in Purchasing Document) <> L
• BSART (Purchasing Document Type) = NB ((Standard PO)
• EKORG (Purchasing Organization) = 0001
• PSTYP (Item Category in Purchasing Document) = 0 (Standard)
• MENGE (Target Quantity) > 0

© 2009 SAP AG 19
Menu Path: SPRO --> Integration with Other mySAP.com Components --> Event Management Interface -->
Define Application Interface --> Define SAP EM Interface Functions
Function Module /SAPTRX/XRA_MM_ITEM_PCM10 will ensure that Event Handlers get created only for
POs which satisfies defined Filter criteria (as highlighted in below screenshot).
Note: Custom Function Module can be built to create the Event Handlers for different parameters as per Business
requirements.

© 2009 SAP AG 19
How the expected event dates and times are derived for Events?
PO Creation (document) date: 08/13/2009
1st Event: Event ‘Receive Acknowledgment’
Event ‘Receive Acknowledgment’ expected date = PO Creation Date + 5 days, 17:00:00
= 08/18/2009, 17:00:00
Note:
(1) Standard SAP has provided the Event, ‘Receive Acknowledgment’ with expected date as 5 days after ‘PO
Creation Date’. Based on business requirements, this number of days can be varied (or) different condition may be
maintained.
(2) Time is configured across all events as constant as 17:00:00 Hours. Based on business requirements, this Time
can be defined accordingly.
2nd Event: Event ‘Receive Advance Shipping Notification’
Event ‘Receive Advance Shipping Notification’ = Delivery date – Plnd delivery days, 17:00:00
= 08/30/2009 – 1, 17:00:00
= 08/29/2009, 17:00:00
rd
3 Event: Receive Goods
Receive Goods = Delivery date, 17:00:00
= 08/30/2009, 17:00:00

© 2009 SAP AG 19
Function Module /SAPTRX/XEE_MM_ITEM_PCM10 has derived the Expected Events dates and times for
1st, 2nd and 3rd Events.
4th Event: Receive Invoice
Receive Invoice = Delivery date + 720 Hours, 17:00:00
= 08/30/2009 + 30 Days, 17:00:00
= 09/29/2009, 17:00:00
Menu Path: SPROÆ Event Management Æ Event Handlers and Event Handler data Æ Expected Events Æ
Define Profiles for Expected Events
In the below screenshot, event duration is displayed as 720 hours for Event Code ‘RECEIVE_INVOICE’ from
Event Code ’RECEIVE_GOODS’.
Note: If ‘Receive Invoice’ occurs within the Event Duration 720 hours(30 days) after ‘Receive Goods’ Event, then, the
Event is treated as Regular Event.

© 2009 SAP AG 19
5th Event: Payment:

Refer to ‘Payment’ event code, No Expected Event date and times are defined as per Standard SAP setup.
Display the Event Handler in WCL:
Each User will be authorized by assigning the role to his User Profile to execute Procurement Visibility
Process and/or Buyer - Procurement Visibility Process
Transaction: /SAPTRX/WCL_SEARCH
After logging into WCL with your credentials (user ID and password),
Choose the following selection criteria
Choose your tracking scenario: Supplier – Procurement Visibility Process (or) Buyer - Procurement Visibility
Process
Purchase Order Number – 4500018287
Procurement Status – SENT
Acknowledgement Status – No Acknowledgment Sent Yet
Click on ‘Search’ Button.
Note:The Selection Profile for each tracking scenario is configurable.

© 2009 SAP AG 19
All the Events are displayed with their descriptions and planned (expected) date and time.
Step 2: Receiving the Vendor Acknowledgement

Transaction: ME22N/ME23N
Confirmation Category – AB (Order Acknowledgement) is assigned with delivery date as current date and
quantity. Purchase Order is saved.


© 2009 SAP AG 19
Event ‘Receive Acknowledgement’ is reported with actual date and time
Acknowledgement Status is changed to OK.

Configuration Setup: How the acknowledgement status has changed from ‘No Acknowledgement
Sent yet’ to OK:
Execute ‘Define Rule sets’ and select ‘PCM10_ITEM’ Rule set and display the SET_ACK rule.

© 2009 SAP AG 19
Upon reporting the PO Acknowledgment, ‘Acknowledgement status’ is changed to OK based on above

configuration.
Display the Event Handler in WCL:

Process
Procurement Status – SENT
Acknowledgement Status – OK
Click on Search Icon

© 2009 SAP AG 19
Actual Date and time are displayed for event ‘Receive Acknowledgement’.
Configuration Setup: How the Actual date and time are derived:
Function Module /SAPTRX/XET_MM_ACKNOWL_PCM10 will derive the Actual dates and times at Real
time for Event ‘Receive Acknowledgement’. Actual dates and times for events are extracted from 'Event Data
Extractors' from source system and transferred to SCEM

© 2009 SAP AG 19
Step 3: Receiving the Advanced Shipping Notification (ASN)

Transaction: VL31N / VL32N / VL33N
Inbound delivery 180000502 is displayed under confirmations tab. Note the:

• Delivery Date: 08/13/2009
• Delivery Time: 10:50:00
Event handler in SCM:
Event ‘Receive Advanced Shipping Notification’ is reported with date 08/11/2009 and time: 10:30:00. This is
the Delivery Date / Time entered in Inbound Delivery.

© 2009 SAP AG 19
Procurement Status is changed to ‘In Transit’.

Configuration Setup: How the Procurement status changed from ‘Sent’ to ‘In Transit’
Execute ‘Define Rule sets’ and select ‘PCM10_ITEM’ Rule set and display the SET_PROC_IN_TRANSIT
rule.
Configuration Setup: How reported date and time are derived as Delivery date and time for Event
‘Receive Advanced Shipping Notification’.

© 2009 SAP AG 19
Function Module /SAPTRX/XET_MM_ASN_PCM10 will derive the Actual dates and times as Delivery Date
and Time for Event ‘Receive Advanced Shipping Notification’.
Display the Event Handler in WCL.

Choose the following selection criteria:
• Choose your tracking scenario: Supplier – Procurement Visibility Process (or) Buyer - Procurement
Visibility Process
• Purchase Order Number – 4500018287
• Procurement Status – In Transit
• Acknowledgement Status – OK
Event ‘Receive Advanced Shipping Notification’ is reported with Actual Date and time as delivery date and
time of ASN.

© 2009 SAP AG 19
Step 4: Goods Receipt

Transaction: VL32N/VL33N
Post Goods receipt (PGR) is successfully done against inbound delivery.

Event ‘Receive Goods’ is reported with Actual date and time.
Procurement status is displayed as ‘Completely Arrived’.

© 2009 SAP AG 19
Configuration Setup: How the Procurement status changed from ‘In Transit’ to ‘Completely Arrived’:
Execute ‘Define Rule sets’ and select ‘PCM10_ITEM’ Rule set and display the SET_PROC_ARRIVED rule.
Configuration Setup: How reported date and time are derived as Real date and time for Event
‘Receive Goods’.
Function Module /SAPTRX/XET_MM_GR_PCM10 will derive the Actual dates and times as Real-time Date
and Time for Event ‘Receive Goods’.
Display the Event Handler in WCL.

Process
Procurement Status – Completely Arrived.
Acknowledgement Status - OK

© 2009 SAP AG 19
Event ‘Receive Goods’ is reported with Actual Date and Time.

© 2009 SAP AG 19
Conclusion:
Similarly Step 5 (Receive Invoice) and Step 6 (Payment) could be executed with MIRO and F110
transactions respectively and reported events dates and times & Status Changes get displayed in SCEM and
WCL and config details can be explained about how the Status Changes and Reported Dates and Times are
derived.
Related Content
SAP Help: www.help.sap.com.
http://help.sap.com/saphelp_em70/helpdata/en/6e/b4393c95b04325e10000000a11405a/frameset.htm
for more information on Supply Chain Event Management.
http://help.sap.com/saphelp_em70/helpdata/en/0a/08233d32039017e10000000a114084/frameset.htm
for more information in Procurement scenario.
For more information, visit the Supply Chain Management homepage.

© 2009 SAP AG 19
Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not
supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,
and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or
code sample, including any liability resulting from incompatibility between the content within this document and the materials and
services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this
document.

© 2009 SAP AG 19

SCEM: Procurement Visibility Scenario: Applies To

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SCEM: Procurement Visibility Scenario: Applies To

Uploaded by

Copyright:

Available Formats

SCEM: Procurement Visibility

This article explains about

Authors: Janakiram Katakam and Gopala Turaga

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Unexpected Events ( ).....................................................................................................................................5

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Introduction to Supply Chain Event Management (SCEM)

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

‘Delivery Date and Quantity Change’ unexpected event is displayed below.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Process Steps in Procurement Visibility

4500018287 Purchase Order is created with:

Event handler in SCEM:

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Configuration Setup: How Event Handler is created in SCM system:

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2nd Event: Event ‘Receive Advance Shipping Notification’

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

5th Event: Payment:

Click on ‘Search’ Button.

Note:The Selection Profile for each tracking scenario is configurable.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Step 2: Receiving the Vendor Acknowledgement

Event handler in SCEM:

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Event ‘Receive Acknowledgement’ is reported with actual date and time

Acknowledgement Status is changed to OK.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Upon reporting the PO Acknowledgment, ‘Acknowledgement status’ is changed to OK based on above

Display the Event Handler in WCL:

Click on Search Icon

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Step 3: Receiving the Advanced Shipping Notification (ASN)

Inbound delivery 180000502 is displayed under confirmations tab. Note the:

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Procurement Status is changed to ‘In Transit’.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Display the Event Handler in WCL.

Click on Search Icon

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Step 4: Goods Receipt

Event handler in SCEM:

Event ‘Receive Goods’ is reported with Actual date and time.

Procurement status is displayed as ‘Completely Arrived’.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Display the Event Handler in WCL.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Click on Search Icon

Event ‘Receive Goods’ is reported with Actual Date and Time.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Disclaimer and Liability Notice

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

You might also like