SRM@ERP Orgstructure on Object S Attributes are missing

[Former Member]

Hi everyone,

We are trying to setup SRM@ERP. We have created an Demoorgstructe and put our Users inside. If we run Report HRALXSYNC we get red bubbles on the coloum attributes for our S-Objects. There are messages like:

"For Application XX you have to define Attribute CUR" or
"For Application XX you have to define Attribute EXT_ITS"

and many more.

The problem is I have set all these missing attributes. And they are set if if check transaction ppoma_bbp. Does somebody know why srm have a problem here? Here are two screens:

The HRALXSYNC Report

My Orstructure in PPOMA_BBP

Thanks for your help:)

[Former Member · Accepted solution]

Hi,

Symptom

Transaction PPOMA_BBP (tab page 'Check') Transaction BBP_ATTR_CHECK and report BBP_CHECK_CONSISTENCY: When you check a user, the system generates messages stating that certain attributes have not been defined, although values for the named attributes can be found on the tab pages 'Attributes' or 'Extended attributes'.

Reason and Prerequisites

This is due to an error in includes LBBP_ATTR_CHECKF01 and LBBP_OM_DIALOGF40.

This above was the cause in the older versions of SRM.

Solution

Please check for the latest Note over this in the market place.

We are on SRM 7 EHP 2 and we are still getting this error. So its not an issue with you or your system. Its is known issue and problem of SAP.

If we do SE38 -->HRALXSYNC -- Position then ALL GREEN - even Attribute supply

and if we do same with RUN attribute checked - then Attribute supply RED.

Thanks,

From RBEI,

Snehal

[Former Member · Accepted solution]

Hi RBEI SRM,

Yes this is excatly the same like in our system. So did you report this to SAP and they are working on a fix? Are you able to start Shopping Cart Application? Because we can't do it. I believe that there is a connection between this "missing Attributes" and the not starting of Shopping Cart Application.

Thanks

[Former Member · Accepted solution]

Hi Birgit,

I dont think so there is any Link between these. Could you please explain/or give screen shot on what is happening and why your not able to start Shopping cart Application to investigate more.

No, I dont think we have reported this to SAP. However, i will get it confirmed. But Our Shopping cart application is working perfectly and the issue your looking into is not the Show Stopper.

thanks,

From RBEI,

Snehal

[Former Member · Accepted solution]

Hi RBEI SRM,

Thanks for your Answer. If I will start shopping Cart Application I got the following Error:

500 SAP Internal Server Error

ERROR: Zugriff über 'NULL' Objektreferenz nicht möglich. (termination: RABAX_STATE)

The ST22 Logs says this:

Category ABAP Programming Error

Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED

ABAP Program /SAPSRM/CL_CH_WD_NAVI_SERV====CP

Application Component SRM-EBP-CA-UI

Date and Time 19.12.2013 18:49:32

Short text

Access via 'NULL' object reference not possible.

What happened?

Error in the ABAP Application Program

The current ABAP program "/SAPSRM/CL_CH_WD_NAVI_SERV====CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

You attempted to use a 'NULL' object reference (points to 'nothing')

access a component (variable: " ").

An object reference must point to an object (an instance of a class)

before it can be used to access components.

Either the reference was never set or it was set to 'NULL' using the

CLEAR statement.

How to correct the error

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"OBJECTS_OBJREF_NOT_ASSIGNED" " "

"/SAPSRM/CL_CH_WD_NAVI_SERV====CP" or "/SAPSRM/CL_CH_WD_NAVI_SERV====CM00Y"

"NAVIGATE_BY_PORTAL"

Server-Side Connection Information

Information on Caller of "HTTPS" Connection:

Plug-in Type.......... "HTTPS"

Caller IP............. "10.94.40.114"

Caller Port........... 1443

Universal Resource ID. "/sap/bc/webdynpro/sapsrm/wda_wscp"

Program............. "/SAPSRM/CL_CH_WD_NAVI_SERV====CP"

Screen.............. "SAPMHTTP 0010"

Screen Line......... 2

Information on Caller ofr "HTTPS" Connection:

Plug-in Type.......... "HTTPS"

Caller IP............. "10.94.40.114"

Caller Port........... 1443

Universal Resource Id. "/sap/bc/webdynpro/sapsrm/wda_wscp"

Information on where terminated

Termination occurred in the ABAP program "/SAPSRM/CL_CH_WD_NAVI_SERV====CP" -

in "NAVIGATE_BY_PORTAL".

The main program was "SAPMHTTP ".

In the source code you have the termination point in line 58

of the (Include) program "/SAPSRM/CL_CH_WD_NAVI_SERV====CM00Y".

Source Code Extract

Line SourceCde

28 ** 'toolbar=no,resizable=yes,width=90%,height=85%,top=0,left=0'.

29 ** 'toolbar=no,resizable=yes,width=''+screen.width*0.96+''px,height=''+screen.height*0.85

30 *

31 *

Date and Time 19.12.2013 18:49:32

32 ** IF lv_target_title IS INITIAL.

33 ** lv_target_title = text-001.

34 ** ENDIF.

35 *

36 * CALL METHOD mo_portal_manager->navigate_absolute

37 * EXPORTING

38 * navigation_target = lv_url

39 * navigation_mode = '3'

40 * window_features = lv_window_feat

41 * business_parameters = is_obn_components-business_parameters

42 ** window_name = 'Hallo Welt'

43 ** history_mode = IF_WD_PORTAL_INTEGRATION=>CO_NO_DUPLICATES

44 ** target_title = lv_target_title

45 ** context_url =

46 ** post_parameters = abap_false

47 ** use_sap_launcher = abap_true

48 ** launcher_parameters = lt_launcher_param.

49 * .

50

51 DATA: lv_pcd_location TYPE /sapsrm/cll_wd_pcd_location,

52 lo_fpm TYPE REF TO if_fpm.

53

54 * Get the current FPM instance

55 lo_fpm = cl_fpm=>get_instance( ).

56

57 * Get the PCD location

>>>>> CALL METHOD lo_fpm->mo_app_parameter->get_value

59 EXPORTING

60 iv_key = mc_catalog_parameters-key_pcdlocation

61 IMPORTING

62 ev_value = lv_pcd_location.

63

64 IF lv_pcd_location CS mc_catalog_parameters-federated_gpn_param2.

65 * federal portal scenario

66 * the resolving_mode should be Default

67 mo_portal_manager->navigate_to_object(

68 system = lv_obn_system

69 object_type = is_obn_components-object_type

70 object_value_name = is_obn_components-object_value_name

71 object_value = is_obn_components-object_value

72 operation = is_obn_components-operation

73 business_parameters = is_obn_components-business_parameters

74 forward_obn_metadata = is_obn_components-forward_obn_metadata

75 use_forwardparameters_of_al = abap_true

76 resolving_mode = IF_WD_PORTAL_INTEGRATION=>CO_RESOLVING_MODE-USER_SET_OF_ROLES

77 ).

Maybe you have an Idea. I checked Oss and also various helps here at scn.

Thanks for your help:)

Regards

Birgit

[Former Member · Accepted solution]

Hello Birgit,

Is the error is like the screen shot below :

If your starting the application and at that time it is throwing a DUMP then the possible reason is that somewhere in the PPOMA in your Org Structure you have entered the Logical system wrongly.

Please check each and every node for the attributes Company code, and Others where ever your maintaining Logical system.

Hope this may help you resolve.

Thanks

From RBEI,

Snehal

[Former Member · Accepted solution]

Hello Birgit,

Please have a look on the below links, may be useful -

http://scn.sap.com/thread/1447920

http://scn.sap.com/thread/3299124

http://scn.sap.com/thread/416848

http://scn.sap.com/thread/334423

https://scn.sap.com/thread/2047835

https://scn.sap.com/thread/1703866

https://scn.sap.com/thread/212244

https://scn.sap.com/message/10897862

From RBEI,

Snehal

[Former Member]

Hi,

In SRM, there are attributes that are mandatory. This are:

ACS: Specifies the backend system where the account assignment is checked.

BSA: Defines the transaction type in the respective system for follow-on documents from shopping carts.

CUR: Default currency of the user

ITS_DEST: System URL for access by internal partner

KNT: Available account assignment categories when creating shopping cart or SRM purchase order.

PRCAT: Defines the product categories for which the user has authorization. You define this attribute using tab card Extended attributes.

SYS: Defines the systems to be searched to find purchase orders. This attribute is used to generate worklists for employees that create confirmations or invoices.

WRK: Specifies the plant in the ERP backend system. You define this attribute using tab card Extended attributes.

Hope this information helps you

BR

Emanuel

[Former Member]

Hi Emanuel,

First sorry for the late reply. I was at holidays last week.

Thanks for your answer. I know that SRM need this Attributes to work. I also set this attributes in PPOMA_BBP but they don't get accepted. So Report HRALXSYNC say attributes are missing but they are set correctly. You can see this in the screenshots I hope. So my question: Where is my failure what I'am doing wrong?

Thanks for your help:)

[former_member1246879]

Dear Birgit,

Have you got any solution? I am also facing exactly same issue.. I am integrating my test users into the org structure.. In spite of setting all the required attributes correctly (verified by tcode BBP_ATTR_CHECK) in PPOMA_bbp, when I run the report HRALXSYNC with check box 'Run Attribute Check', I am getting the error of "Attribute Supply" for positions.

Thanks and regards,

Ranjan

[Former Member]

Hi,

Is the Org Unit replicated successfully?

Regards,

Sheetal

[Former Member]

Hi Sheetal,

No for testing we have created an own small test Org Unit. This Org Unit is based on SAP Best Practice.