SAP AG 1

SRM 4.0 -
Supplier Self
Services
Customer Fields
Field Services, APA
SAP AG 2
Up to 8 topics
Session Objectives
Customer Fields: Architecture
SUS-EBP Scenario
SUS-MMScenario
Follow-On Documents
Summary
SAP AG 3
SAP AG 2004
Sessi on Obj ec t i ves
This session will focus on the Supplier Self-Services (SUS)
modification concept
At the end of this session, you will be able to:
Add customer extension fields for SUS
Make the configuration settings needed to enable customer
extension fields
Please refer to RKT-SRM40Abbreviation.xls for the description of the terms used in
this material if necessary.
SAP AG 4
SAP AG 2004
Agenda: SUS Cust omer Fi el ds
Overview
Architecture
SAP Enterprise Buyer (EBP) SUS scenario
Configuration in EBP
Configuration in the Exchange Infrastructure (XI)
Configuration in SUS
XI interface
User interface - Business Server Pages (BSP) Interface
SAP Materials Management (MM) SUS Scenario
Configuration in MM
Configuration in XI.
Customer fields for follow-on documents
Advance Shipping notification (ASN)
Confirmation
Invoice
SAP AG 5
Up to 8 topics
Session Objectives
Customer Fields: Architecture
SUS-EBP Scenario
SUS-MMScenario
Follow-On Documents
Summary
SAP AG 6
SAP AG 2004
SUS Cust omer Fi el ds : Ar c hi t ec t ur e
EBP
Extension
structures
Application
Message
processing
UI
EBP XML
Funct. group
BBP_BD_DRIVER_SAPXM
L1
1
Application
MM
IDoc processing
Extension
1 Optional
SUS-EBP
REPOSITORY CONTENT
Service_Procurement_
Supplier_Enablement
Scenario
Routing
No mapping needed
SUS-MM
REPOSITORY CONTENT
Plan_Driven_Procureme
nt_Supplier_Enablement
Scenario
Routing
mapping needed
IDoc SUS XML
XI SUS
Extension
structures
Application
Message
processing
UI
SUS XML
Funct. group
BBP_BD_DRIVER_SAPXM
L1
2 3
4
5
SAP AG 7
Up to 8 topics
Session Objectives
Customer Fields: Architecture
SUS-EBP Scenario
SUS-MMScenario
Follow-On Documents
Summary
SAP AG 8
SAP AG 2004
1) Conf i gur at i on i n EBP
a) Extension structure that needs to be extended
b) Integration of Extension structure to EBP
application
c) Integration of Extension structure to message
processing and to output XML
d) Class interface used for sending output XML
EBP
Extension
structures
Application
Message
processing
UI
EBP XML
Funct. group
BBP_BD_DRIVER_SAPXM
L1
1
Class
CO_BBPX1_PO_REQUES
T* method
Execute_Asynchronous
XML output
SAP AG 9
SAP AG 2004
1.a) Ex t ensi on St r uc t ur e t hat Needs t o be ex t ended: Header
In Structure
INCL_EEW_ORDERADM_H use
include
CI_EEW_ORDERADM_H for
Customer fields.
This Structure is meant for
EBP Application interface.
Define Customer Fields in
Structure
CI_EEW_ORDERADM_H.
For Customer Fields ensure
that the field Label Exists.
In Structure
INCL_EEW_PD_HEADER_CSF_
SUSPO add the same fields as
in the earlier structure.
This Structure is used by the
Message Header interface
Structure
BBP_PDS_SUSPO_HEADER_D
SAP AG 10
SAP AG 2004
1.a) Ex t ensi on St r uc t ur e t hat Needs t o be ex t ended: I t em
In Structure
INCL_EEW_ORDERADM_I use
include CI_EEW_ORDERADM_I
for Customer fields.
This Structure is meant for EBP
Application interface
Define Customer Fields in
Structure CI_EEW_ORDERADM_I.
For Customer Fields ensure that
the field Label Exists.
In Structure
INCL_EEW_PD_ITEM_CSF_SUSP
O add the same fields as in the
earlier structure.
This Structure is used by the
Message Header interface
Structure
BBP_PDS_SUSPO_ITEM_D
SAP AG 11
SAP AG 2004
1.b,c ,d) I nt egr at i on of St r uc t ur e i n Message Pr oc essi ng
CO_BBPX1_PO_REQUEST_* method Execute_asynchronous is used to send output. * represents different Classed used for
Create, Change and Delete Process
Form Map_Extension_out is used for populating extension values in XML output
Converts to XML Output BBP_DOCUMENT_TO_SAP
XML1_MAPS
INCL_EEW_PD_HEADER_C
SF_SUSPO
INCL_EEW_PD_ITEM_CSF
_SUSPO
Converts All Structures to
XML Output
BBP_SAPXML1_PO_SEND
In Program BBP_PD_SUSPO_GETDETAIL move-corresponding structure copies data from Application Extension to Message
Extension
CI_EEW_ORDERADM_H
CI_EEW_ORDERADM_I
Header and Item Uses Application Extension
Structure
BBP_PROCDOC_GETDETA
IL
Uses
BBP_PROCDOC_GETDETA
IL to get PO Data
Links to Application output.
Send XML Output
Action Performed
INCL_EEW_PD_HEADER_C
SF_SUSPO
INCL_EEW_PD_ITEM_CSF
_SUSPO
Header and Item BBP_PD_SUSPO_GETDET
AIL
Xml string output Structures:
bbpx1_purchase_order_requ
est for Create;
bbpx1_po_change_request
for change;
bbpx1_po_cancellation_requ
for Delete
BBP_OUTPUT_SUSPO_XM
L
Extension Structures Used Header / Item Program Sequence
SAP AG 12
SAP AG 2004
2) Mappi ng i n Ex c hange I nf r ast r uc t ur e
SUS-EBP
REPOSITORY CONTENT
Service_Procurement_
Supplier_Enablement
Scenario
Routing
No mapping needed
XI
2
No mapping needed in XI
Both EBP and SUS share same
message ORDER, which means that
the extension data is transferred
automatically.
SAP AG 13
SAP AG 2004
2.a) Rout i ng Def i ned: No Mappi ng bet w een
I nt er f ac es
No mapping Needed
SAP AG 14
SAP AG 2004
2.b) Same message t ype used by EBP and SUS I nt er f ac e
EBP Interface
SUS Interface
Same Message
Type Used
SAP AG 15
SAP AG 2004
3) Conf i gur at i on i n SUS
SUS
Extension
structures
Application
Message
processing
UI
SUS XML
Funct. group
BBP_BD_DRIVER_SAPXM
L1
3
a) Extension structure that needs to be extended
b) Customizing settings for BSP UI Integration
c) Integration of structure to message processing
and to input XML
d) Integration of structure in SUS application
e) Changes to BSP templates
SAP AG 16
SAP AG 2004
3.a) Ex t ensi on St r uc t ur e t hat Needs t o be Mapped
If EBP and SUS have the same instance but different clients, the
ABAP Dictionary changes made in EBP are client-independent and
also applicable in the SUS client
Integration in message and application modules takes place
automatically.
If EBP and SUS have different instances, the following structures
must be changed:
Name of the field and type must be identical to that of EBP
Integration in message and application modules takes place
automatically
SAP AG 17
SAP AG 2004
3.a) Addi t i onal Ex t ensi on St r uc t ur e
In addition to the above mentioned structures INCL_EEW_PD_HEADER_CST and INCL_EEW_PD_ITEM_CST
needs to be extended with same fields.
SAP AG 18
SAP AG 2004
3.b) Mai nt ai n Vi ew BBPC_SUS_TABDEF
View BBPC_SUS_TABDEF has to be maintained in SM30:
All fields that needs to be displayed in BSP should be maintained in this table. Fields include:
Table: key of the table to be rendered. Fixed Values as per the details specified Below.
Field name: name of the column/ field inside the DDIC structure. Should be same as field name defined in the extension structure.
UI type: defines how the field shall be rendered [INPUT | IMAGE | BUTTON | DROP DOWN|...]
Row pos: Column Position inside a row.
Position: Position inside a column cell - A maximum of two fields can be rendered inside a cell.
Not display if empty - do not render anything if field has no value (for performance reasons)
Sort - enable column sort
Wrapping
Alias for OTR entry OTR column header text key
Iterator Image Link (Link for an image - works only with UI type image )
Image OTR alias (tooltip for image)
Table Key:
Z.ASN.DET.EDIT: extensions for ASN header edit mode
Z.ASN.DET.VIEW: extensions for ASN header display mode
Z.ASN.ITM.EDIT: extensions for ASN item edit mode
Z.ASN.ITM.VIEW: extensions for ASN item display mode
Z.CF.DET.EDIT : extensions for confirmation header edit mode
Z.CF.DET.VIEW: extensions for confirmation header display mode
Z.CF.ITM.EDIT: extensions for confirmation item edit mode
Z.CF.ITM.VIEW: extensions for confirmation item view mode
Z.INV.DET.EDIT: extensions for invoice header edit mode
Z.INV.DET.VIEW: extensions for invoice header display mode
Z.INV.ITM.EDIT: extensions for invoice item edit mode
Z.INV.ITM.VIEW: extensions for invoice item display mode
Z.PO.DET.EDIT: extensions for order header edit mode
Z.PO.DET.VIEW: extensions for order header display mode
Z.PO.ITM.EDIT: extensions for order item edit mode
Z.PO.ITM.VIEW: extensions for order item display mode
SAP AG 19
SAP AG 2004
3.b) Mai nt ai n Vi ew BBPC_SUS_TABDEF
Be aware that the Extension field has to be declared inside the
INCL_EEW_PD_HEADER_CSF_SUSPCO structure.
SAP AG 20
SAP AG 2004
3.c ,d) I nt egr at i on of St r uc t ur e i n Message Pr oc essi ng
INCL_EEW_PD_HEADER_CST
INCL_EEW_PD_ITEM_CST
Creates customer field values in
table BBP_PDHCF and
BBP_PDICF
BBP_PDHCF_CREATE or
Update
CI_EEW_ORDERADM_H
CI_EEW_ORDERADM_I
Posts application BBP_PROCDOC_Create or
BBP_PROCDOC_UPDATE
Class II_BBPX1_SUSPO_IN for Create PO; Class II_BBPX1_SUSPO_CANCEL_REQU_IN for Cancel; Class
II_BBPX1_SUSPO_CHANGE_REQU_IN for Change ; method EXECUTE_ASYNCHRONOUS. Triggers FM
BBP_SAPXML1_SUSPO_CREATE_IN, BBP_SAPXML1_SUSPO_CANCEL_IN, BBP_SAPXML1_SUSPO_CHANGE_IN
respectively.
INCL_EEW_PD_HEADER_CSF_SU
SPO
INCL_EEW_PD_ITEM_CSF_SUSP
O CI_EEW_ORDERADM_H
CI_EEW_ORDERADM_I
Converts message extension to
application extension; calls
application program
BBP_PD_SUSPO_UPDATE;
BBP_PD_SUSPO_CREATE;
BBP_PD_SUSPO_Status_Chan
ge
INCL_EEW_PD_HEADER_CSF_SU
SPO
INCL_EEW_PD_ITEM_CSF_SUSP
O
Header and Item Message extension structure is
used.
BBP_API_SUSPO_CANCEL for
Cancel; BBP_API_SUSPO_CRT
for Create;
BBP_API_SUSPO_UPD for
Change
Uses form map_extension_in for
converting xml customer fields
to internal structures. message
extension structure is used.
Creates, changes, or deletes
PO.
Action Performed
INCL_EEW_PD_HEADER_CSF_SU
SPO
INCL_EEW_PD_ITEM_CSF_SUSP
O
Header and item BBP_DOCUMENT_FROM_SAP
XML1_MAPS
INCL_EEW_PD_HEADER_CSF_SU
SPO
INCL_EEW_PD_ITEM_CSF_SUSP
O
bbp_sapxml1_suspo_*_i: *
represents Create, Change, or
Cancel
Extension Structures Used Header / Item Program Sequence
SAP AG 21
SAP AG 2004
3.e) Tr ansf er f r om Appl i c at i on t o BSP Fr ont -end
Application data
Function module
BBP_PROCDOC_GET
DETAIL
Function module
BBP_PD_SUSPO_GET
DETAIL
Function module
BBP_PD_SUSPO_GE
TDETAIL_UI
Class
CL_SUS_M_ORDER_DETAIL
Attributes:
PT_HEADER_PO
PT_ITEMS_PO
PT_ITEM_PO
PT_ITEMS_PCO
PT_ITEM_PCO
Method
IF_SUS_DOCUMENT_DETAIL
~GET_DETAIL
Method
IF_SUS_DOCUMENT_DETAIL
~POPULATE_ITEM_DETAIL
Extension structure CI_EEW_ORDERADM_H FOR header
CI_EEW_ORDERADM_I for item
Extension structure
INCL_EEW_PD_HEADER_CSF_SUSPO for header
INCL_EEW_PD_ITEM_CSF_SUSPO for item
Attribute
PT_HEADER_PO
( Header extension )
PT_ITEMS_PCO
BSP view
Order detail_edit.inc;
detail_view.inc
Attribute
PT_ITEM_PCO
PT_ITEM_PO
( Item extension )
BSP view
Order item_edit.inc;
Item_view.inc
Continue to next page
SAP AG 22
SAP AG 2004
Tr ansf er f r om Appl i c at i on t o BSP Fr ont -end ( HEADER)
BSP Application
in SE80
Extraction of Header
Customer fields
SAP AG 23
SAP AG 2004
Tr ansf er f r om Appl i c at i on t o BSP Fr ont -end ( I TEM )
BSP Application
in SE80
Extraction of Item
Customer fields
SAP AG 24
Up to 8 topics
Session Objectives
Customer Fields: Architecture
SUS-EBP Scenario
SUS-MMSUS Scenario
Follow-On Documents
Summary
SAP AG 25
SAP AG 2004
4) Conf i gur at i on i n MM
Application
MM
IDoc processing
Extension
1
1 Optional
4
SAP Materials Management uses IDocs for the MM SUS process
Customer fields in the SUS-MMscenario may be of two types:
Scenario 1: field exists in the MM IDoc, but may be missing from the SUS XML. If this is the
case, you must:
Create a customer field in SUS as in step 3
Define additional mapping between the IDos and new XML field in XI repository for the scenario
Make no changes in MM. Changes are restricted to the XI and SUS
Scenario 2: field does not exist in the MM IDoc (optional)
Create extension in the IDoc
Populate the field in the IDoc
Create a customer field in SUS as in step 3
Define additional mapping between the IDoc and new XML field in XI
repository for the scenario.
Changes in MMfor IDoc extension, XI for mapping and SUS for
customer field
SAP AG 26
SAP AG 2004
Conf i gur at i ons i n MM: I Doc Ex t ensi on
For for information on how to extend IDocs to include additional
data, see SAP Library at help.sap.com
Basis Services / Communication Interfaces Communication
Interfaces IDoc Interface/Electronic Data Interchange ( BC-SRV
EDI) Structure, Documentation and Definition of IDoc Types
Extending an IDoc Type
SAP AG 27
SAP AG 2004
5) Conf i gur at i on i n t he XI
SUS-MM
REPOSITORY CONTENT
Plan_Driven_Procureme
nt_Supplier_Enablement
Scenario
Routing
mapping needed
IDoc SUS XML
XI
5
Additional mapping needs to be defined in the XI. The
MMIDoc should be mapped to the SUS XML
Mappings can be found in the XI Repository:
SAP SRM SERVERSAP SRM SERVER 5.0
http://sap.com/xi/SRM/SupplierEnablement/Global
Mapping Objects Message Mappings
Order: MM2SUSOrderCreate
ASN: SUS2MMShippingNotification
Invoice: SUS2MMInvoice
SAP AG 28
SAP AG 2004
Mappi ng i n XI Reposi t or y
SUS
XML
ORDER IDoc
SAP AG 29
SAP AG 2004
Add Addi t i onal Fi el ds i n SUS XML
There is no extension structure available for this purpose
SAP AG 30
SAP AG 2004
Add Addi t i onal Mappi ng i n SUS XML (?)
No extension Structure available for the Purpose. Need to Check.
SAP AG 31
Up to 8 topics
Session Objectives
Customer Fields: Architecture
SUS-EBP Scenario
SUS-MMScenario
Follow-On Documents
Summary
SAP AG 32
SAP AG 2004
Fol l ow -On Doc ument s
The follow-on documents in SUS include:
Confirmation.
ASN
Invoice
If you want the customer fields to be carried from the order document to the follow-on
documents, then define these fields in the corresponding extension structure
If different fields are needed then the fields must be defined in the extension structures meant for follow
on documents
Also Maintain Extension fields in the table BBPC_SUS_TABDEF
In the EBP scenario, mapping is done in the XI. Once again these fields should exist in the EBP
extension structure
In the MM, scenario these mappings must be done in the XI
Also ensure these fields exists in the application extension structure
INCL_EEW_PD_ITEM_CS
F_SUSINV
INCL_EEW_PD_HEADER_CSF
_SUSINV
Invoice
INCL_EEW_PD_ITEM_CS
F_SUSASN
INCL_EEW_PD_HEADER_CSF
_SUSASN
ASN
INCL_EEW_PD_ITEM_CS
F_SUSCF
INCL_EEW_PD_HEADER_CSF
_SUSCF
Confirmation
CI_EEW_ORDERADM_H;
CI_EEW_ORDERADM_I
INCL_EEW_PD_ITEM_CS
F_SUSPO
INCL_EEW_PD_HEADER_CSF
_SUSPO
Order
Application Structure Item Structure Header Structure Document
SAP AG 33
Up to 8 topics
Session Objectives
Customer Fields: Architecture
SUS-EBP Scenario
SUS-MM Scenario
Follow-On Documents
Summary
SAP AG 34
SAP AG 2004
Summar y
You are now able to:
Add customer extension fields within SUS.
Make the configuration settings needed to enable customer
extension fields
SAP AG 35
SAP AG 2004
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
Microsoft

, WINDOWS

, NT

, EXCEL

, Word

, PowerPoint

and SQL Server

are registered trademarks of

Microsoft Corporation.
IBM

, DB2

, DB2 Universal Database, OS/2

, Parallel Sysplex

, MVS/ESA, AIX

, S/390

, AS/400

, OS/390

,
OS/400

, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere

, Netfinity

, Tivoli

, Informix
and Informix

Dynamic Server
TM
are trademarks of IBM Corporation in USA and/or other countries.
ORACLE

is a registered trademark of ORACLE Corporation.

UNIX

, X/Open

, OSF/1

, and Motif

are registered trademarks of the Open Group.

Citrix

, the Citrix logo, ICA

, Program Neighborhood

, MetaFrame

, WinFrame

, VideoFrame

, MultiWin

and
other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C

, World Wide Web Consortium,

Massachusetts Institute of Technology.
JAVA

is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT

is a registered trademark of Sun Microsystems, Inc., used under license for technology invented
and implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, R/3, mySAP, mySAP.com, xApps, xApp and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and service names mentioned are the trademarks of their respective
companies.
Copyr i ght 2004 SAP AG. Al l Ri ght s Reser ved