SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 1
Duet Enterprise Feature Pack 1
Developer Guide ndash Consuming
OData Services via BDC Browser
Applies to
Duet Enterprise FP1 SP03 Consuming OData Service via BDC Browser in SharePoint2010
Summary
This paper explains how Duet Enterprise FP1 SP03 can be used to consume OData Service created with SAP Netweaver Gateway BDC Browserrsquos capabilities have been enhanced to include OData service as one of the data sources The tool provides no-code approach to get SharePoint2010 BDC models
Author Advay Borkar and Alexander Puettner
Company SAP
Created on 14 September 2012
Author Bio
Advay is working in Duet Enterprise Product Devleopment team in SAP Labs India
Alexander is part of Duet Enterprise Solution Management team in SAP Labs Toronto
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 3
Overview
OData Services ndash SAP Netweaver Gateway is provisioning access to SAP data via OData services which is a standard way of accessing SAP data for future use
BDC Browserrsquos capability is enhanced to use OData Services as the data source to create BDC models
The generated BDC models will be exactly similar to the ones which were generated with GW data models To make use of this new feature following are the starting points
Pre-requisite
BDC Browser Service Settings
Service Implementation Workbench Settings
OData Service
Creating BDC models out of OData Services using BDC Browser
Deploying BDC models
Custom UI in SharePoint
Enabling entity to Entity Relationship
Troubleshooting and Best Practice
Use Case EPM Sales Order entity is used to showcase the CRUDQ functionality EPM Sales Order is a pre-delivered Sales Order business Object The functionality includes
Query list of Sales Order Headers
View details of a Sales Order Header
Update of Sales Order Header
Delete Sales Order
Query list of Sales Order Items for a Sales Order Header
View details of Sales Order Item
Create a Sales Order Header Along with Sales Order Items
1 Pre-requisite
These are certain pre-requisite which must be followed
Software Pre-requisites
SAP NetWeaver Gateway SP05
IW TNG SP03
Configuration Pre-requisite for Service Builder Tool
Install IW_BEP component (part of GW SP05)in the SAP backend system
Provide required authorization to user running the Service Builder tool
Configurations Pre-requisites for BDC Browser tool
ESR Configuration should be done
BDC Browser -gt Service settings should be updated (as explained in chapter 2)
Service Implementation workbench settings (as explained in chapter 3)
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 4
2 BDC Browser Service Settings
BDC Browser now supports creation of SOAP service and BDC models from
Gateway Data Model (Generic channel approach)
OData Service (OData Approach)
In order to support both data sources 2 different configurations have to be maintained in BDC browser Service settings
Above figure indicates 2 separate service settings used in BDC browser and only one is marked as Active
For each Service setting corresponding SIW configuration has to be defined SIW configuration explained in chapter 3
If you have previously worked with BDC browser then same service settings can be copied for OData related settings (Service settings can be viewed from IWTNGBDC_BROWSER transaction)
Note Service settings should be maintained using the BDC browser configuration guide ESR configuration steps
include creation of software component namespace and generic global data types Follow the steps provided in
how-to- guide (from page 3 to 20) to complete the configuration until the service settings
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 5
3 Service Implementation Workbench Settings
The active configuration ID (SAP_GW_ODC_CONFIG) is referred in Service Implementation Wrokbench IMG (Go to transaction SIMGH and open IMG structure Service Implementation Wrokbench -gt Define Configuration) Check the entry corresponding to active configuration ID
Make sure Config Class entry is maintained to IWFNDCL_MGW_SB_SIW_CONFIG
For the GW data model approach this entry should be IWFNDCL_DST_SIW_FLAT_CONFIG
Following screenshot shows Config Class for each Configuration ID
4 OData Service
OData Service can be created via Service Builder tool (installed via IW_BEP component in backend system) Use the attached EDMX file to import it into service builder tool Follow the steps to create and configure OData Service
41 Import EDMX File
Download the attached Data Model file (EPM_SOxml) to local system Login to backend system make sure that backend system has IW_BEP component installed (part of GW SP05)
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 7
The imported data model now contains 2 Entities SOHeader and SOItem An Association is provided
between SOHeader and SOItem Expand nodes SOHeader and SOItem to navigate to various
properties
42 MPC Class changes
As soon as the changes are saved click on Generate Runtime Objects button on the top menu This action will generate the runtime artifacts for OData Service
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 9
The ZCL_SALESORDER_MPC class has the generated definition of the OData Service The additional code has to be written in ZCL_SALESORDER_MPC_EXT class Right click on ZCL_SALESORDER_MPC_EXT and select on Workbench option
This will open the class ZCL_SALESORDER_MPC_EXT in ABAP Workbench
Select Source code ndashBased option and then click on Edit button
DELETE entire existing code
Copy entire code from ZCL_SALESORDER_MPC_EXTtxt and paste here
Click on Save Check for any errors you should not get any errors
Click on the Form Based button on top menu
Save and Activate the class
Define method should already have the code now activate your changes
Even though following properties are maintained in Service builder tool they are again explicitly marked
Explicitly marking entities SOHeader and SOItem as creatable updatable and deletable
SALESORDERID and CustomerID are marked as Filterable properties in the SOHeader
SALESORDERID is marked as filterable property for SOItem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 10
The Define method should look like this
43 DPC Class changes
The generator will also generate DPC (Data Provider class) The data provider class will provide methods to perform CRUDQ calls for each Entity We need to add code to call BAPIs to from corresponding method of DPC class
In the generated artifact look for class ZCL_SALESORDER_DPC_EXT right click on select Workbench option This action will open class ZCL_SALESORDER_DPC_EXT in ABAP workbench
Once you are in class window go to Source Code-Based option and click on Edit button
Delete any existing code in the source code based view
Copy entire code (CTRL+A) from ZCL_SALESORDER_DPC_EXTtxt and paste it
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 3
Overview
OData Services ndash SAP Netweaver Gateway is provisioning access to SAP data via OData services which is a standard way of accessing SAP data for future use
BDC Browserrsquos capability is enhanced to use OData Services as the data source to create BDC models
The generated BDC models will be exactly similar to the ones which were generated with GW data models To make use of this new feature following are the starting points
Pre-requisite
BDC Browser Service Settings
Service Implementation Workbench Settings
OData Service
Creating BDC models out of OData Services using BDC Browser
Deploying BDC models
Custom UI in SharePoint
Enabling entity to Entity Relationship
Troubleshooting and Best Practice
Use Case EPM Sales Order entity is used to showcase the CRUDQ functionality EPM Sales Order is a pre-delivered Sales Order business Object The functionality includes
Query list of Sales Order Headers
View details of a Sales Order Header
Update of Sales Order Header
Delete Sales Order
Query list of Sales Order Items for a Sales Order Header
View details of Sales Order Item
Create a Sales Order Header Along with Sales Order Items
1 Pre-requisite
These are certain pre-requisite which must be followed
Software Pre-requisites
SAP NetWeaver Gateway SP05
IW TNG SP03
Configuration Pre-requisite for Service Builder Tool
Install IW_BEP component (part of GW SP05)in the SAP backend system
Provide required authorization to user running the Service Builder tool
Configurations Pre-requisites for BDC Browser tool
ESR Configuration should be done
BDC Browser -gt Service settings should be updated (as explained in chapter 2)
Service Implementation workbench settings (as explained in chapter 3)
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 4
2 BDC Browser Service Settings
BDC Browser now supports creation of SOAP service and BDC models from
Gateway Data Model (Generic channel approach)
OData Service (OData Approach)
In order to support both data sources 2 different configurations have to be maintained in BDC browser Service settings
Above figure indicates 2 separate service settings used in BDC browser and only one is marked as Active
For each Service setting corresponding SIW configuration has to be defined SIW configuration explained in chapter 3
If you have previously worked with BDC browser then same service settings can be copied for OData related settings (Service settings can be viewed from IWTNGBDC_BROWSER transaction)
Note Service settings should be maintained using the BDC browser configuration guide ESR configuration steps
include creation of software component namespace and generic global data types Follow the steps provided in
how-to- guide (from page 3 to 20) to complete the configuration until the service settings
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 5
3 Service Implementation Workbench Settings
The active configuration ID (SAP_GW_ODC_CONFIG) is referred in Service Implementation Wrokbench IMG (Go to transaction SIMGH and open IMG structure Service Implementation Wrokbench -gt Define Configuration) Check the entry corresponding to active configuration ID
Make sure Config Class entry is maintained to IWFNDCL_MGW_SB_SIW_CONFIG
For the GW data model approach this entry should be IWFNDCL_DST_SIW_FLAT_CONFIG
Following screenshot shows Config Class for each Configuration ID
4 OData Service
OData Service can be created via Service Builder tool (installed via IW_BEP component in backend system) Use the attached EDMX file to import it into service builder tool Follow the steps to create and configure OData Service
41 Import EDMX File
Download the attached Data Model file (EPM_SOxml) to local system Login to backend system make sure that backend system has IW_BEP component installed (part of GW SP05)
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 7
The imported data model now contains 2 Entities SOHeader and SOItem An Association is provided
between SOHeader and SOItem Expand nodes SOHeader and SOItem to navigate to various
properties
42 MPC Class changes
As soon as the changes are saved click on Generate Runtime Objects button on the top menu This action will generate the runtime artifacts for OData Service
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 9
The ZCL_SALESORDER_MPC class has the generated definition of the OData Service The additional code has to be written in ZCL_SALESORDER_MPC_EXT class Right click on ZCL_SALESORDER_MPC_EXT and select on Workbench option
This will open the class ZCL_SALESORDER_MPC_EXT in ABAP Workbench
Select Source code ndashBased option and then click on Edit button
DELETE entire existing code
Copy entire code from ZCL_SALESORDER_MPC_EXTtxt and paste here
Click on Save Check for any errors you should not get any errors
Click on the Form Based button on top menu
Save and Activate the class
Define method should already have the code now activate your changes
Even though following properties are maintained in Service builder tool they are again explicitly marked
Explicitly marking entities SOHeader and SOItem as creatable updatable and deletable
SALESORDERID and CustomerID are marked as Filterable properties in the SOHeader
SALESORDERID is marked as filterable property for SOItem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 10
The Define method should look like this
43 DPC Class changes
The generator will also generate DPC (Data Provider class) The data provider class will provide methods to perform CRUDQ calls for each Entity We need to add code to call BAPIs to from corresponding method of DPC class
In the generated artifact look for class ZCL_SALESORDER_DPC_EXT right click on select Workbench option This action will open class ZCL_SALESORDER_DPC_EXT in ABAP workbench
Once you are in class window go to Source Code-Based option and click on Edit button
Delete any existing code in the source code based view
Copy entire code (CTRL+A) from ZCL_SALESORDER_DPC_EXTtxt and paste it
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 3
Overview
OData Services ndash SAP Netweaver Gateway is provisioning access to SAP data via OData services which is a standard way of accessing SAP data for future use
BDC Browserrsquos capability is enhanced to use OData Services as the data source to create BDC models
The generated BDC models will be exactly similar to the ones which were generated with GW data models To make use of this new feature following are the starting points
Pre-requisite
BDC Browser Service Settings
Service Implementation Workbench Settings
OData Service
Creating BDC models out of OData Services using BDC Browser
Deploying BDC models
Custom UI in SharePoint
Enabling entity to Entity Relationship
Troubleshooting and Best Practice
Use Case EPM Sales Order entity is used to showcase the CRUDQ functionality EPM Sales Order is a pre-delivered Sales Order business Object The functionality includes
Query list of Sales Order Headers
View details of a Sales Order Header
Update of Sales Order Header
Delete Sales Order
Query list of Sales Order Items for a Sales Order Header
View details of Sales Order Item
Create a Sales Order Header Along with Sales Order Items
1 Pre-requisite
These are certain pre-requisite which must be followed
Software Pre-requisites
SAP NetWeaver Gateway SP05
IW TNG SP03
Configuration Pre-requisite for Service Builder Tool
Install IW_BEP component (part of GW SP05)in the SAP backend system
Provide required authorization to user running the Service Builder tool
Configurations Pre-requisites for BDC Browser tool
ESR Configuration should be done
BDC Browser -gt Service settings should be updated (as explained in chapter 2)
Service Implementation workbench settings (as explained in chapter 3)
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 4
2 BDC Browser Service Settings
BDC Browser now supports creation of SOAP service and BDC models from
Gateway Data Model (Generic channel approach)
OData Service (OData Approach)
In order to support both data sources 2 different configurations have to be maintained in BDC browser Service settings
Above figure indicates 2 separate service settings used in BDC browser and only one is marked as Active
For each Service setting corresponding SIW configuration has to be defined SIW configuration explained in chapter 3
If you have previously worked with BDC browser then same service settings can be copied for OData related settings (Service settings can be viewed from IWTNGBDC_BROWSER transaction)
Note Service settings should be maintained using the BDC browser configuration guide ESR configuration steps
include creation of software component namespace and generic global data types Follow the steps provided in
how-to- guide (from page 3 to 20) to complete the configuration until the service settings
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 5
3 Service Implementation Workbench Settings
The active configuration ID (SAP_GW_ODC_CONFIG) is referred in Service Implementation Wrokbench IMG (Go to transaction SIMGH and open IMG structure Service Implementation Wrokbench -gt Define Configuration) Check the entry corresponding to active configuration ID
Make sure Config Class entry is maintained to IWFNDCL_MGW_SB_SIW_CONFIG
For the GW data model approach this entry should be IWFNDCL_DST_SIW_FLAT_CONFIG
Following screenshot shows Config Class for each Configuration ID
4 OData Service
OData Service can be created via Service Builder tool (installed via IW_BEP component in backend system) Use the attached EDMX file to import it into service builder tool Follow the steps to create and configure OData Service
41 Import EDMX File
Download the attached Data Model file (EPM_SOxml) to local system Login to backend system make sure that backend system has IW_BEP component installed (part of GW SP05)
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 7
The imported data model now contains 2 Entities SOHeader and SOItem An Association is provided
between SOHeader and SOItem Expand nodes SOHeader and SOItem to navigate to various
properties
42 MPC Class changes
As soon as the changes are saved click on Generate Runtime Objects button on the top menu This action will generate the runtime artifacts for OData Service
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 9
The ZCL_SALESORDER_MPC class has the generated definition of the OData Service The additional code has to be written in ZCL_SALESORDER_MPC_EXT class Right click on ZCL_SALESORDER_MPC_EXT and select on Workbench option
This will open the class ZCL_SALESORDER_MPC_EXT in ABAP Workbench
Select Source code ndashBased option and then click on Edit button
DELETE entire existing code
Copy entire code from ZCL_SALESORDER_MPC_EXTtxt and paste here
Click on Save Check for any errors you should not get any errors
Click on the Form Based button on top menu
Save and Activate the class
Define method should already have the code now activate your changes
Even though following properties are maintained in Service builder tool they are again explicitly marked
Explicitly marking entities SOHeader and SOItem as creatable updatable and deletable
SALESORDERID and CustomerID are marked as Filterable properties in the SOHeader
SALESORDERID is marked as filterable property for SOItem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 10
The Define method should look like this
43 DPC Class changes
The generator will also generate DPC (Data Provider class) The data provider class will provide methods to perform CRUDQ calls for each Entity We need to add code to call BAPIs to from corresponding method of DPC class
In the generated artifact look for class ZCL_SALESORDER_DPC_EXT right click on select Workbench option This action will open class ZCL_SALESORDER_DPC_EXT in ABAP workbench
Once you are in class window go to Source Code-Based option and click on Edit button
Delete any existing code in the source code based view
Copy entire code (CTRL+A) from ZCL_SALESORDER_DPC_EXTtxt and paste it
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 4
2 BDC Browser Service Settings
BDC Browser now supports creation of SOAP service and BDC models from
Gateway Data Model (Generic channel approach)
OData Service (OData Approach)
In order to support both data sources 2 different configurations have to be maintained in BDC browser Service settings
Above figure indicates 2 separate service settings used in BDC browser and only one is marked as Active
For each Service setting corresponding SIW configuration has to be defined SIW configuration explained in chapter 3
If you have previously worked with BDC browser then same service settings can be copied for OData related settings (Service settings can be viewed from IWTNGBDC_BROWSER transaction)
Note Service settings should be maintained using the BDC browser configuration guide ESR configuration steps
include creation of software component namespace and generic global data types Follow the steps provided in
how-to- guide (from page 3 to 20) to complete the configuration until the service settings
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 5
3 Service Implementation Workbench Settings
The active configuration ID (SAP_GW_ODC_CONFIG) is referred in Service Implementation Wrokbench IMG (Go to transaction SIMGH and open IMG structure Service Implementation Wrokbench -gt Define Configuration) Check the entry corresponding to active configuration ID
Make sure Config Class entry is maintained to IWFNDCL_MGW_SB_SIW_CONFIG
For the GW data model approach this entry should be IWFNDCL_DST_SIW_FLAT_CONFIG
Following screenshot shows Config Class for each Configuration ID
4 OData Service
OData Service can be created via Service Builder tool (installed via IW_BEP component in backend system) Use the attached EDMX file to import it into service builder tool Follow the steps to create and configure OData Service
41 Import EDMX File
Download the attached Data Model file (EPM_SOxml) to local system Login to backend system make sure that backend system has IW_BEP component installed (part of GW SP05)
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 7
The imported data model now contains 2 Entities SOHeader and SOItem An Association is provided
between SOHeader and SOItem Expand nodes SOHeader and SOItem to navigate to various
properties
42 MPC Class changes
As soon as the changes are saved click on Generate Runtime Objects button on the top menu This action will generate the runtime artifacts for OData Service
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 9
The ZCL_SALESORDER_MPC class has the generated definition of the OData Service The additional code has to be written in ZCL_SALESORDER_MPC_EXT class Right click on ZCL_SALESORDER_MPC_EXT and select on Workbench option
This will open the class ZCL_SALESORDER_MPC_EXT in ABAP Workbench
Select Source code ndashBased option and then click on Edit button
DELETE entire existing code
Copy entire code from ZCL_SALESORDER_MPC_EXTtxt and paste here
Click on Save Check for any errors you should not get any errors
Click on the Form Based button on top menu
Save and Activate the class
Define method should already have the code now activate your changes
Even though following properties are maintained in Service builder tool they are again explicitly marked
Explicitly marking entities SOHeader and SOItem as creatable updatable and deletable
SALESORDERID and CustomerID are marked as Filterable properties in the SOHeader
SALESORDERID is marked as filterable property for SOItem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 10
The Define method should look like this
43 DPC Class changes
The generator will also generate DPC (Data Provider class) The data provider class will provide methods to perform CRUDQ calls for each Entity We need to add code to call BAPIs to from corresponding method of DPC class
In the generated artifact look for class ZCL_SALESORDER_DPC_EXT right click on select Workbench option This action will open class ZCL_SALESORDER_DPC_EXT in ABAP workbench
Once you are in class window go to Source Code-Based option and click on Edit button
Delete any existing code in the source code based view
Copy entire code (CTRL+A) from ZCL_SALESORDER_DPC_EXTtxt and paste it
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 5
3 Service Implementation Workbench Settings
The active configuration ID (SAP_GW_ODC_CONFIG) is referred in Service Implementation Wrokbench IMG (Go to transaction SIMGH and open IMG structure Service Implementation Wrokbench -gt Define Configuration) Check the entry corresponding to active configuration ID
Make sure Config Class entry is maintained to IWFNDCL_MGW_SB_SIW_CONFIG
For the GW data model approach this entry should be IWFNDCL_DST_SIW_FLAT_CONFIG
Following screenshot shows Config Class for each Configuration ID
4 OData Service
OData Service can be created via Service Builder tool (installed via IW_BEP component in backend system) Use the attached EDMX file to import it into service builder tool Follow the steps to create and configure OData Service
41 Import EDMX File
Download the attached Data Model file (EPM_SOxml) to local system Login to backend system make sure that backend system has IW_BEP component installed (part of GW SP05)
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 7
The imported data model now contains 2 Entities SOHeader and SOItem An Association is provided
between SOHeader and SOItem Expand nodes SOHeader and SOItem to navigate to various
properties
42 MPC Class changes
As soon as the changes are saved click on Generate Runtime Objects button on the top menu This action will generate the runtime artifacts for OData Service
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 9
The ZCL_SALESORDER_MPC class has the generated definition of the OData Service The additional code has to be written in ZCL_SALESORDER_MPC_EXT class Right click on ZCL_SALESORDER_MPC_EXT and select on Workbench option
This will open the class ZCL_SALESORDER_MPC_EXT in ABAP Workbench
Select Source code ndashBased option and then click on Edit button
DELETE entire existing code
Copy entire code from ZCL_SALESORDER_MPC_EXTtxt and paste here
Click on Save Check for any errors you should not get any errors
Click on the Form Based button on top menu
Save and Activate the class
Define method should already have the code now activate your changes
Even though following properties are maintained in Service builder tool they are again explicitly marked
Explicitly marking entities SOHeader and SOItem as creatable updatable and deletable
SALESORDERID and CustomerID are marked as Filterable properties in the SOHeader
SALESORDERID is marked as filterable property for SOItem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 10
The Define method should look like this
43 DPC Class changes
The generator will also generate DPC (Data Provider class) The data provider class will provide methods to perform CRUDQ calls for each Entity We need to add code to call BAPIs to from corresponding method of DPC class
In the generated artifact look for class ZCL_SALESORDER_DPC_EXT right click on select Workbench option This action will open class ZCL_SALESORDER_DPC_EXT in ABAP workbench
Once you are in class window go to Source Code-Based option and click on Edit button
Delete any existing code in the source code based view
Copy entire code (CTRL+A) from ZCL_SALESORDER_DPC_EXTtxt and paste it
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 7
The imported data model now contains 2 Entities SOHeader and SOItem An Association is provided
between SOHeader and SOItem Expand nodes SOHeader and SOItem to navigate to various
properties
42 MPC Class changes
As soon as the changes are saved click on Generate Runtime Objects button on the top menu This action will generate the runtime artifacts for OData Service
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 9
The ZCL_SALESORDER_MPC class has the generated definition of the OData Service The additional code has to be written in ZCL_SALESORDER_MPC_EXT class Right click on ZCL_SALESORDER_MPC_EXT and select on Workbench option
This will open the class ZCL_SALESORDER_MPC_EXT in ABAP Workbench
Select Source code ndashBased option and then click on Edit button
DELETE entire existing code
Copy entire code from ZCL_SALESORDER_MPC_EXTtxt and paste here
Click on Save Check for any errors you should not get any errors
Click on the Form Based button on top menu
Save and Activate the class
Define method should already have the code now activate your changes
Even though following properties are maintained in Service builder tool they are again explicitly marked
Explicitly marking entities SOHeader and SOItem as creatable updatable and deletable
SALESORDERID and CustomerID are marked as Filterable properties in the SOHeader
SALESORDERID is marked as filterable property for SOItem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 10
The Define method should look like this
43 DPC Class changes
The generator will also generate DPC (Data Provider class) The data provider class will provide methods to perform CRUDQ calls for each Entity We need to add code to call BAPIs to from corresponding method of DPC class
In the generated artifact look for class ZCL_SALESORDER_DPC_EXT right click on select Workbench option This action will open class ZCL_SALESORDER_DPC_EXT in ABAP workbench
Once you are in class window go to Source Code-Based option and click on Edit button
Delete any existing code in the source code based view
Copy entire code (CTRL+A) from ZCL_SALESORDER_DPC_EXTtxt and paste it
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 7
The imported data model now contains 2 Entities SOHeader and SOItem An Association is provided
between SOHeader and SOItem Expand nodes SOHeader and SOItem to navigate to various
properties
42 MPC Class changes
As soon as the changes are saved click on Generate Runtime Objects button on the top menu This action will generate the runtime artifacts for OData Service
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 9
The ZCL_SALESORDER_MPC class has the generated definition of the OData Service The additional code has to be written in ZCL_SALESORDER_MPC_EXT class Right click on ZCL_SALESORDER_MPC_EXT and select on Workbench option
This will open the class ZCL_SALESORDER_MPC_EXT in ABAP Workbench
Select Source code ndashBased option and then click on Edit button
DELETE entire existing code
Copy entire code from ZCL_SALESORDER_MPC_EXTtxt and paste here
Click on Save Check for any errors you should not get any errors
Click on the Form Based button on top menu
Save and Activate the class
Define method should already have the code now activate your changes
Even though following properties are maintained in Service builder tool they are again explicitly marked
Explicitly marking entities SOHeader and SOItem as creatable updatable and deletable
SALESORDERID and CustomerID are marked as Filterable properties in the SOHeader
SALESORDERID is marked as filterable property for SOItem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 10
The Define method should look like this
43 DPC Class changes
The generator will also generate DPC (Data Provider class) The data provider class will provide methods to perform CRUDQ calls for each Entity We need to add code to call BAPIs to from corresponding method of DPC class
In the generated artifact look for class ZCL_SALESORDER_DPC_EXT right click on select Workbench option This action will open class ZCL_SALESORDER_DPC_EXT in ABAP workbench
Once you are in class window go to Source Code-Based option and click on Edit button
Delete any existing code in the source code based view
Copy entire code (CTRL+A) from ZCL_SALESORDER_DPC_EXTtxt and paste it
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 9
The ZCL_SALESORDER_MPC class has the generated definition of the OData Service The additional code has to be written in ZCL_SALESORDER_MPC_EXT class Right click on ZCL_SALESORDER_MPC_EXT and select on Workbench option
This will open the class ZCL_SALESORDER_MPC_EXT in ABAP Workbench
Select Source code ndashBased option and then click on Edit button
DELETE entire existing code
Copy entire code from ZCL_SALESORDER_MPC_EXTtxt and paste here
Click on Save Check for any errors you should not get any errors
Click on the Form Based button on top menu
Save and Activate the class
Define method should already have the code now activate your changes
Even though following properties are maintained in Service builder tool they are again explicitly marked
Explicitly marking entities SOHeader and SOItem as creatable updatable and deletable
SALESORDERID and CustomerID are marked as Filterable properties in the SOHeader
SALESORDERID is marked as filterable property for SOItem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 10
The Define method should look like this
43 DPC Class changes
The generator will also generate DPC (Data Provider class) The data provider class will provide methods to perform CRUDQ calls for each Entity We need to add code to call BAPIs to from corresponding method of DPC class
In the generated artifact look for class ZCL_SALESORDER_DPC_EXT right click on select Workbench option This action will open class ZCL_SALESORDER_DPC_EXT in ABAP workbench
Once you are in class window go to Source Code-Based option and click on Edit button
Delete any existing code in the source code based view
Copy entire code (CTRL+A) from ZCL_SALESORDER_DPC_EXTtxt and paste it
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 9
The ZCL_SALESORDER_MPC class has the generated definition of the OData Service The additional code has to be written in ZCL_SALESORDER_MPC_EXT class Right click on ZCL_SALESORDER_MPC_EXT and select on Workbench option
This will open the class ZCL_SALESORDER_MPC_EXT in ABAP Workbench
Select Source code ndashBased option and then click on Edit button
DELETE entire existing code
Copy entire code from ZCL_SALESORDER_MPC_EXTtxt and paste here
Click on Save Check for any errors you should not get any errors
Click on the Form Based button on top menu
Save and Activate the class
Define method should already have the code now activate your changes
Even though following properties are maintained in Service builder tool they are again explicitly marked
Explicitly marking entities SOHeader and SOItem as creatable updatable and deletable
SALESORDERID and CustomerID are marked as Filterable properties in the SOHeader
SALESORDERID is marked as filterable property for SOItem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 10
The Define method should look like this
43 DPC Class changes
The generator will also generate DPC (Data Provider class) The data provider class will provide methods to perform CRUDQ calls for each Entity We need to add code to call BAPIs to from corresponding method of DPC class
In the generated artifact look for class ZCL_SALESORDER_DPC_EXT right click on select Workbench option This action will open class ZCL_SALESORDER_DPC_EXT in ABAP workbench
Once you are in class window go to Source Code-Based option and click on Edit button
Delete any existing code in the source code based view
Copy entire code (CTRL+A) from ZCL_SALESORDER_DPC_EXTtxt and paste it
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 10
The Define method should look like this
43 DPC Class changes
The generator will also generate DPC (Data Provider class) The data provider class will provide methods to perform CRUDQ calls for each Entity We need to add code to call BAPIs to from corresponding method of DPC class
In the generated artifact look for class ZCL_SALESORDER_DPC_EXT right click on select Workbench option This action will open class ZCL_SALESORDER_DPC_EXT in ABAP workbench
Once you are in class window go to Source Code-Based option and click on Edit button
Delete any existing code in the source code based view
Copy entire code (CTRL+A) from ZCL_SALESORDER_DPC_EXTtxt and paste it
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 27
A Modelszip is ready for download Download it to local system
Modelszip contains Model files for SOHeader and SOItem Entities
SOHeaderxml and SOItemxml can be imported in SharePoint
62 Importing BDC Models in SharePoint
The generated BDC models can be deployed on SharePoint The out of the box forms will be rendered Login to SharePoint server and go to central admin page
Click on Business Data Connectivity Service
Click on Import button
Here browse and select file SOHeader_Modelxml from the local directory Click Import
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 31
From the ribbon menu click on modify view and in data source filters provide value for a sales order id (copy it from external list of sales order header) Now all the sales order items for this specific sales order header will be displayed
Select View Item from ECB menu to see details of sales order item
7 Custom UI in SharePoint
For deep create (creating header and item together) a custom solution is required on SharePoint
The DEEP _CREATE method is shipped as generic invoker method in BDC model SharePoint custom code must call this Generic Invoker method for achieving Deep Create functionality
MSDN documentation on Generic Invoker httpmsdnmicrosoftcomen-uslibraryee558358aspx
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 32
8 Maintaining Entity to Entity Relationship (Custom Coding in ABAP and SharePoint)
A Sales Order header can have multiple Sales Order Items Here Sales Order Header is parent entity and Sales Order Item is child entity This can be achieved in SharePoint via custom coding or via BDC association method
Entity to Entity relationship can be maintained via two ways Approach 1
o Use Custom Code on SharePoint
o The custom code will refer QUERY method of Child entity as the association method
o Advantage here is no additional coding on ABAP is required Existing service should be able
to provide you association related data
o Important point to note is that for Child entity always specify Parent ID as filter in MPC class
Approach 2
o Add a new method in Child Entity in ESR service
o Activate the service in GW system and provide an implementation for the new method
o The implementation is same as the Query method
o Update BDC model of Child entity with Association method
o A web part can be added without doing any additional coding on SharePoint The web part
will get all related Sales Order Items for selected Sales Order Header
Approach 1 is highly recommended
9 Troubleshooting and Best Practices
Following are some key pointsbest practices to make sure your scenario is working perfectly
91 OData Service
Service Registration in Gateway
Make sure that OData Service is properly registered in GW system Service must be of type BEP the ICF node ODATA should be green A system alias must be assigned to OData service
No Reverse Association in OData Service
In the Service builder tool association can be made circular but Duet Enterprise does not support such circular associations Only forward associations are supported
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 33
In the above example only forward association is supported ie Sales Items can be obtained from Sales Order Header
DateTime Handling
Date fields must be converted into timestamp fields in the MPC class
To convert a date into timestamp precision values must be used as specified as specified above
Precision value 8 for a date field indicates itrsquos a Timestamp field Make sure each date field is converted into Timestamp in the Service Builder tool (This is mandatory step
because SharePoint understands only DATETIME objects) Also note that dateTime field should be marked as Nullable
Case 1 RFC exposes a timestamp field
If RFC exposes a timestamp field then it can be directly mapped in the DPC class (to corresponding timestamp field of OData service)
Case 2 RFC exposes DATS 8 field
In this case explicit conversion of DATS to DATETIME is required
For QueryRead operations DATS must be converted into DATETIME while returning data back
CONVERT DATE ltls_datagt-created_on TIME lv_time
INTO TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz
For CreateUpdate Operations incoming request DATETIME must be converted into DATS CONVERT TIME STAMP ltls_datagt-created_on TIME ZONE lv_tz INTO DATE ltls_datagt-created_on TIME lv_time
In any case MPC class will expose a timestamp field and the conversion will happen in DPC class
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 34
Handling Complex Key
SharePoint works with single identifier for a BDC model
Because of this constraint complex keys has to be flattened For example Sales Order Scenarios
To uniquely identify a Sales Order Item two keys are required
Sales Order Header ID and
Sales Order Item ID is required
Such scenarios can be handled by creating a flattened key in Service builder
Example Sales Order Header ID 0500000003
Sales Order Item ID 0000000030
Flattened Key 0500000003_0000000030
Example ITEMKEY as added as the new flattened key It will hold a concatenated key of Sales Order Header ID and Sales Order Item ID separated by the underscore symbol (eg 0500000003_0000000030)
Forming Dummy key in READ methods (for QUERY AND READ methods of DPC class)
CONCATENATE ls_salesorderitem-salesorderid _
ls_salesorderitem-salesorderitem INTO ls_salesorderitem-itemkey
Getting individual Keys (for UPDATE method of DPC class)
SPLIT ls_salesorderitem AT _
INTO ls_salesorderitem-salesorderid ls_salesorderitem-salesorderitem
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
SAP COMMUNITY NETWORK SDN - sdnsapcom | BPX - bpxsapcom | BA - bocsapcom | UAC - uacsapcom
copy 2011 SAP AG 36
Copyright
copy Copyright 2012 SAP AG All rights reserved
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 Excel Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation
Linux is the registered trademark of Linus Torvalds in the US and other countries
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of Technology
Java is a registered trademark of Oracle Corporation
JavaScript is a registered trademark of Oracle Corporation used under license for technology invented and implemented by Netscape
SAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign 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 other countries
Business Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects SA in the United States and in other countries Business Objects is an SAP company
All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
![DUET Enterprise Partner Opportunity FINAL[1]](https://static.documents.pub/doc/80x56/577d29f21a28ab4e1ea84b53/duet-enterprise-partner-opportunity-final1.jpg)
