srm integration with docb snote 1084258

01/12/2011 of 6

SAP Note 1084258 - Integrating PS SRM and Document Builder

Note Language: English Version: 8 Validity: Valid Since 04/13/2010

Summary

SymptomThis note provides additional information on the configuration steps for PSSRM and Document Builder integration. You must read the IMG help filesassociated with the configuration steps in the SRM system in order to coverall the required steps.

1. Establish System Connections

Document Builder and SRM may be installed on either the same or differentservers. Please follow instructions in 1.1 to install on the same serveror 1.2 to install on different servers.

1.1 Same Server Install Option

In the system maintain an entry in transaction SM59 for an ABAP connectionto the SRM system. Setup the name of the RFC destination as the logicalsystem name of the SRM system, e.g. UT5CLNT300 if the system ID of the SRMsystem is UT5 and the client is 300.

When you establish the RFC Destination, on the tab "Logon & Security", select the "Current User" Checkbox for the RFC connection to the DocumentBuilder system.

Verify that the SRM users that will be using Document Builder have the rolethat allows the creation of Documents e.g. /IPRO/AUTHOR.

A prerequisite for the next steps is that you must have an existingDocument Builder content.

In the Document Builder IMG, set up the configuration parameter for the SRMSystem and client.Execute Transaction SPRO. Go to: SAP Customizing Implementation Guide ->Cross-Application Components -> Document Builder -> Basic Functions ->Define Configuration Parameters

Select your content, then create the Configuration Parameter LOGSYS_SRM andsupply the Parameter Value, which is the logical system name and client, asidentified above. (e.g. UT5CLNT300).

Go to the SRM IMG Step via SAP Implementation Guide --> SupplierRelationship Management --> SRM Server --> Industry-Specific Solutions -->Procurement for Public Sector --> Integration with SAP Document Builder toActivate Document Builder Integration.

Fill out the fields and leave the ID field blank since a direct functioncall is used to integrate with DocB.

1.2 Different Server Install Option

In the SRM system maintain an entry in transaction SM59 for an ABAP

01/12/2011 of 6


connection to the Document Builder system. The name of the RFC destinationmust be a 10 character name and must be the same name that is used for theID in the SRM IMG Step via SAP Implementation Guide --> SupplierRelationship Management --> SRM Server --> Industry-Specific Solutions -->Procurement for Public Sector --> Integration with SAP Document Builder toActivate Document Builder Integration.

When you establish the RFC Destination, on the tab "Logon & Security", select the "Current User" Checkbox for the RFC connection to the DocumentBuilder system.

In the Document Builder system, verify that the SRM users that will beusing Document Builder are created as users (with the same username) andhave a role that allows the creation of Documents e.g. /IPRO/AUTHOR.

In the Document Builder system maintain an entry in transaction SM59 for anABAP connection to the SRM system. Setup the name of the RFC destination asthe logical system name of the SRM system, e.g. UT5CLNT300 if the system IDof the SRM system is UT5 and the client is 300.

A prerequisite for the next steps is that you must have an existingDocument Builder content.

In the Document Builder IMG, set up the configuration parameter for the SRMSystem and client.Execute Transaction SPRO. Go to: SAP Customizing Implementation Guide ->Cross-Application Components -> Document Builder -> Basic Functions ->Define Configuration Parameters

Select your content, then create the Configuration Parameter LOGSYS_SRM andsupply the Parameter Value, which is the logical system name and client, asidentified above. (e.g. UT5CLNT300).

2. Activate Document Builder Integration

In the SRM system, go to the IMG Step to "Activate Document BuilderIntegration".Please follow the steps documented for the IMG node.

Note that the Document Builder URL required as part of this configurationcan be found when displaying Web Dynpro component /IPRO/WD_DOCB(transaction se80 ) under node "Web Dynpro Application in the DocumentBuilder system.

3. Creating and Mapping Document Builder Variables

In this step you can setup the variables to map from SRM to DocumentBuilder with the SRM IMG Step for the Document Builder Integration "MapFields".Note that you must flag the "External Map" property for the DocumentBuilder Simple Variables and their Structures so they accept external data.

01/12/2011 of 6


In addition you can also run a report in the Document Builder IMG tocreate the variables in this table as Document Builder simple variables. Read this whole section including notes prior to starting.

Follow the steps documented in the SRM IMG node "Map Fields".

Note that the SRM variables that can be selected for the different mappingtypes are part of the following structures:

Type Description Structure01 Header BBP_PDS_HEADER02 Item BBP_PDS_ITEM03 Accounting BBP_PDS_ACC04 Organizational Unit P1028 andP1000-STEXT05 Purchasing Org. P1028 andP1000-STEXT06 Purchasing Group P1028 andP1000-STEXT10 - 27 Partner Data BBP_PDS_PARTNER

To map SRM attributes to Document Builder simple variables, specify therequested information: Object, Type, Attribute, DocB variable.

Note: Do not use a dash or period in the name of the Document Buildervariable as this will result in an issue with the proxy generation and willnot integrate properly.

In addition you may map more complex structures as follows:

For types 02, 03 and 10 - 27 tables entries on the SRM side are mapped toDocument Builder table variables. Each SRM attribute contained in thetable must be mapped to its corresponding Document Builder simple variableas well.

To allow the mapping of table variables an additional mapping table entryfor the relevant type is needed. In this entry the value for "DocumentAttribute" is blank and the value for "Document Builder Variable Name" hasthe name of the Document Builder table variable, such as, "table_ var_tab1".

For the mapping of PO item data the mapping table entries could look asfollows ( the first column with Object type BUS2201 is not shown )

Type Attribute DocB Variable02 Item LI_TABLE02 Item DESCRIPTION LI_DESCRIPTION02 Item QUANTITY LI_QUANTITY

In this example the name of the Document Builder table variable for itemdata is "LI_TABLE". The "SRM" item fields "DESCRIPTION" and "QUANTITY" willbe mapped to the Document Builder variables "LI_DESCRIPTION" and

01/12/2011 of 6


"LI_QUANTITY

As a note: to set up Document Builder Table Variables, you must firstcreate the simple variables, next create a structure variable to containthem, and then create the table variable.

For more complex mapping logic BADI /SAPPSSRM/DOCB_MAPPING can beimplemented. This BADI could be used for example to set a Document BuilderDocument Selection variable according to the SRM Document Process Type. TheBADI documentation van be accessed via the corresponding IMG node.

To create the corresponding simple variables in Document Builder run thereport /IPRO/READ_SRM_VARIABLES in the Document Builder system. Thisreport is also available in the IMG under the node: Document BuilderContent Management -> Basic Functions -> Variables -> Integration withOther Components -> Populate Variables Base on SRM Data.This report can be used to create Document Builder simple variables basedon the data maintained in the SRM mapping table /SAPPSSRM/DB_MAP which isexposed in the SRM IMG Step "Map Fields".Note: The report only creates simple variables, not table variables. After the simple variables have been created, you may need to go to theDocument Builder IMG to maintain the variables to assign them to structuresand organize them.

After running this report, it may be necessary to create data elements inDocument Builder that the report identifies as missing. This may becompleted in the ABAP dictionary via SE11.

4. Define Reference Data

In the SRM system, go to the IMG step to "Define Reference data". Followthe steps documented for the IMG note.

Note: To proceed further all the Document Builder variables must beconfigured prior to generating the Document Builder WSDL file.

Note: The local WSDL file needed to generate the mapping structure can becreated out of the Document Builder IMG following this path:

Cross-Application Components -> Document Builder -> Basic Functions-> Variables -> Information Systems -> Display Output as WSDL

The name entered as "WSDL message" name will be part of the proxy generatedon SRM side.

To generate the corresponding proxy in the SRM system select:

transaction se80 -> Edit Object (Shift+F5) -> Enterprise Services-> Client Proxy -> Create (F5 )

Select the local WSDL file created earlier.

The mapping reference structure needed is genererated as part of the proxyand will be a structure with name *CT_DOCB_ROOT where "*" has to bereplaced with the prefix selected during the proxy generation.This mapping structure which reflects the data tree structure for aspecific Document Builder content is the only part of the client proxy thatis used.

01/12/2011 of 6


Please note that Document Builder variables that contain a dash or periodwill have their name changed during proxy generation. These variables canNOT be used for an integrated SRM Document Builder scenario.

Also note that if the proxy and the mapping structure have to beregenerated because of a variable change in the Document Builder system theproxy should be deleted first. Otherwise only parts of the mappingstructure might get updated and it will be invalid.

If different proxies and mapping structures are needed because differentSRM objects are mapped to a different Document Builder contents, theseproxies should be generated in different packages. Otherwise parts of thestructure are mixed and become invalid even if differents prefixes havebeen assigned.

Other termsDocB

Reason and Prerequisites

SolutionSee above.

Header Data

Release Status: Released for CustomerReleased on: 10/17/2008 16:00:12Master Language: EnglishPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: PSM-GPR Procurement for Public Sector

Secondary Components:CA-GTF-DOB Document Builder

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SRM_SERVER 600 600 600

Attachments

01/12/2011 of 6


FileType

File Name Language Size

TXT change_mapping1.txt E 6 KB