sold-to-party attribute field is not filled automatically

[Former Member]

Dear consultants,

We have a problem for on our Solution Manager's service desk.  Our system is Solman 7.1 SP08.We have three VAR customers. One of our customer has a problem related to incident management work center. The others are ok. All master data of our customers were created automatically at the same time, according to service.sap.com data's by background jobs.

When our customer wants to create an incident message on work center, message is  created successfully, but sold-to-party field is empty.

But, with same user, our customer can create message via transaction code NOTIF_CREATE.

If the message is created via NOTIF_CREATE, sold-to-party attribute areais filled automatically by the system.

We have checked our business partner and organisation definitions via trancaction code BP . All of them seem correct. Identification tab for ornanisation and business partner has correct values for systems, customer number etc. Relationship between organisation and users of organisation seem correct.

Also, IB52 definitons are correct. All level of this customer,     " IB52 --> Customer no or system --> go --> partner    " has definition for sold-to-party and customer's organization is available on this page. 

We have checked tables v_aisapcustnos, aiinstallations, AIINSTACCESS etc.  All necessary columns are available.

Also, roles and profiles or customer's user is checked.

Is there any solution for this problem?

Best regards,

[Former Member · Accepted solution]

Hello Arzu,

What is set for Sold-to-party in 'Define Partner Determination Procedure'  (tcode SPRO)?

Did you use one transaction type for incident messages ?

Aslo check note 1858608 - Sold-To Party not filled in Incidents

BR,

Kamil

[Former Member · Accepted solution]

Dear Kamil,

Thank you for this note. But, in our system ther is only one installed base and all definitions seem correct. I have created customer message vith high priority, yesterday. But, there is not any answer, yet.

System definitions on SMSY & SLD & LMDB are correct. Ibase components are created automatically by background job REFRESH_ADMIN_DATA_FROM_SUPPORT.Also, business partner, organisation and relationship between them are correct.

Best regards,

Arzu

[Former Member · Accepted solution]

Hello Arzu,

What about Partner determination procedure ? could you paste screen with these settings ?

BR,

Kamil

[Former Member · Accepted solution]

Hello Kamil,

We are using transactiom type ZMIV which was copied from SMIV.

We have three customers and only one customer has a problem when creating message from incident management workcenter. sold-to-party and system areas are missing. But, this customer can cretae message via t-code NOTIF_CREATE and all attribute areas are fileed automaticaly.

Partner determination customizing for ZMIV is pasted below:

[Former Member]

Dear consultants,

This issue is solved. I have checked all background jobs which update or change installed base definitoons and found background job AI_CRM_AIDIAGNOTIF_CREATE.

There were several error messages on spool of this job:

"

Problem occured during processing of GUID5410330d-6410-1ed2-bcf2-f24aa6ecb507

Please have a look at the application log SOLAR - AI_CRM_PRD_IO"

I found sap note 1856234  Missing sort string in Ibase text components and this note solved my problem.

Best regards,

1856234

Missing sort string in Ibase text components

1856234

Missing sort string in Ibase text components