SRM SUS

16.10.2010 Page 1 of 4

SAP Note 887348 - SRMSUS: FAQ for error analysis andlogging OSS tickets

Note Language: English Version: 2 Validity: Valid Since 29.03.2006

Summary

SymptomYou want to report a problem within the SRM SUS application. Please checkthe following information beforehand:

1. Configuration guides and online documentation:

If you need to find the SRM configuration and installation guides fora special SRM scenario, e.g. the plan-driven procurement, please havea look at note 853753.

2. Problems within the SUS UI:

If you think that your problem is rather due to a problem in the BSPframework (e.g. you found by BSP debugging that the problem is notlocated in the application layer) and you would like to forward themessage to the BC-BSP component, please make sure that you have readnote 800854 (BSP Checklist for Opening Problem Tickets).

Please also make sure that your settings for the service 'srmsus' intransaction 'SICF' are correct.

Sometimes, especially when the problem is not SUS applicationspecific, but rather a problem within the BSP framework, the problemhas to be forwarded to OSS component 'BC-BSP' for further analysis. Ifpossible, provide a protocol of a problem analysis with 'httpwatch' asan xml file attached to the message.

3. Problems within the XI server or the XI content mapping:

Please check note 793669 (FAQ: SUS in SRM 4.0 with XI 3.0) and makesure that the latest content mapping has been applied on the XIserver.

Sometimes, especially when the problem is not SRM specific, but rathera problem within the XI infrastructure, the problem has to beforwarded to OSS component 'BC-XI' for further analysis.

4. Check customizing settings in the SRM server and the UI:

Please check if the Customizing settings have been maintainedcorrectly under 'SAP Implementation Guide -> Supplier RelationshipManagement -> Supplier Self-Services'. Especially, the settings under'Master Data -> Make settings for the business partners' should bechecked.

Additionally, you can check the settings in the SUS application itselfunder 'Administration -> Company data'.

Some customizing that might be needed within the SUS application, e.g.the settings for the TTE (tax transaction engine) for tax calucation,should be assigned to the corresponding component, e.g. 'AP-TTE'.

5. Problems with master data replication:

16.10.2010 Page 2 of 4


Before you exchange order documents, the corresponding businesspartner master data must exist in the SUS system (purchasingorganization and vendors). You may check any intermediate problemduring the replication with help of transaction 'SLG1' with objects'BBP*'. If a problem occurs during the master data replication, youmight log a ticket or forward the message to component'SRM-EBP-ADM-XBP' (External Business Partner).

The replicated vendor master data must exist in table 'VENMAP', youcan identify the corresponding business partner by selecting thepartner guid and entering it for table 'BUT000', you'll get thebusines partner id that you can enter in transaction 'BP'. You mayalso check the purchasing organization in transaction 'PPOMA_BBP',e.g. for maintained attributes.

6. Portal integration and UME:

For the integration of the SUS into the portal, the User ManagementEngine (UME) is needed. Within the context of integrating UME and SUSin one installation, the following notes should be checked:

Note 848299 : External Vendor number not mapped to SUS when UME isused

Note 839985 : Incorrect role assignment in SUS-UME-API

Note 752761 : BADI implementation for user Replication /w UME4.0

Note 880735 : UME/SUS: error with administrational user creation

Note 723610 : SUS 3.0: Portal Integration doesn't work

If the problem is rather located in the UME, please use the OSS basiscomponent 'BC-SEC-USR-ADM'.

7. OTR texts and translational issues:

If there is a problem with displaying texts in the SUS UI in a certainlanguage, e.g. the user is logged in in English and some texts areonly displayed in German, then note 807604 should be considered. Ifpossible, please report the OTR texts id's where translations aremissing (see transaction 'SOTR_EDIT').

8. Performance, Upgrade and Archiving:

These are separate topics that should be treated on the correspondingcomponents like SRM-EBP-TEC-PFM, SRM-EBP-TEC-UPG and SRM-EBP-ARV, incase that the problem is not SUS application specific, but rathergeneric, e.g. for archiving of SUS documents

9. Logon information and system access:

If the above information should not help in solving your problem,please provide the following information in case you want to log a OSSticket on component SRM-SUS:

a) Which SRM release and patch level has been installed?

16.10.2010 Page 3 of 4


b) Which SRM scenario are you running, e.g. plan-driven procurement orservice procurement?

c) Do you have a SRM system setup according to the standard SP stackas described in the release and information notes or are youdeviating from theses stacks, e.g. by using a combination of SRMparts of different releases? In the last case, the problem mightturnout to be a consulting issue.

d) Do you have any modifications or BADI-implementations in yoursystem?

e) If the problem is related to users or roles: Are you using the SUSuser management or the User Management Engine (UME)?

f) Is the problem really caused in the SUS application or is theprocess rather initiated in the purchasing application (EBP or MM)?

g) Did you perform a note search on component 'SRM-SUS' for thecorresponding SP level?

h) In case that the problem is not clearly isolated in a part of theapplication (e.g. in the UI or in the XI), describe clearly thesteps that are needed for reproducing the problem, e.g. where doesthe process start before you observe the error.

i) In case that logon to the UI is needed, please also provide logondata via httpconnect, WTS or PCanywhere connection. For debuggingpurposes, please provide a user that is able to logon to the SUSapplication and reproduce the problem, but also that has debugauthorization within the SRM Server. This will help the supportmembers when debugging the BSP application.

If you provide answers to the above questions when you logon theticket, it will definitely reduce the processing times of your OSSmessage.

Other termsFAQ, additional information, consulting, trouble shooting, debugging, erroranalysis.

Reason and PrerequisitesProgram errors or wrong settings in the customizing.

SolutionSee above.

Header Data

Release Status: Released for CustomerReleased on: 10.04.2006 12:19:46

16.10.2010 Page 4 of 4


Master Language: EnglishPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: SRM-SUS Supplier Self-Services

Secondary Components:SRM-EBP-TEC-UPG Upgrade

SRM-EBP-TEC-INS Installation

SRM-EBP-CA-XML XML Communication

SRM-EBP-PD Procurement Document Methods

SRM-XI-MAP Content Mapping

SRM-ROS Supplier Registration

SRM-SUS-ORD Order / Order Response

SRM-SUS-COF ASN / Confirmation

SRM-SUS-INV Invoice

SRM-SUS-ADM Business Partner, User, Customizing

SRM-SUS-XI XI Mapping, Interfaces, ProcessIntegration

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SRM_SERVER 500 500 500

Related Notes

Number Short Text

880735 UME/SUS: error with administrational user creation

848299 External Vendor number not mapped to SUS when UME is used

839985 Incorrect role assignment in SUS-UME-API

807604 SUS: Missing or incorrect translations of OTR texts

800854 BSP Checklist for Opening Problem Tickets

793669 FAQ: SUS in SRM 4.0 with XI 3.0

752761 BADI implementation for user Replication /w UME4.0

723610 SUS 3.0: Portal Integration doesn't work

616900 BSP Troubleshooting and Frequently Asked Questions

598860 Browsers supported by BSP

Documents

SRM SUS