Skip to Content

Default Sold-To Party (Partner Determination) on ZMCR


I'm having a challenge that I shouldn't be this difficult and was easy to set up in 7.0. We are now on 7.1 SP11.

I need to default the Sold-To Party on ZMCR, but it is not defaulting. It should default based on the ibase.

Here are my details:

1) There is no preceding document. ZMCR is the start of the ChaRM flow.

2) IB52 is setup....

3) The partner 151 in IB52 points to top of PPOMA_CRM...

and BP 151 is setup as a Sold-To Party in tcode BP...

4) Partner determination is currently using access sequence 0018.

But I have also tried access sequences AIC2 and AIC3. None of them work.

5) I found OSS note 1165357 . It says ... "

  • Execute the IMG Activity "Activate Partner and Address Inheritance, Change
    in the Past".
  • For IBase Category 01: set the flag in the column PInherit. and ensure that
    the flag is also set in the column IB Past. "

But in 7.1 SP11, the IMG task title does not include "Change in the Past".

But, looking at the task, it is missing one of the fields in the note. It is missing column "IB Past".

I set column PInherit per the note, but have not made any change for IB Past. I'm not sure if this part of the issue or not.

I have a feeling it is just the access sequence, but none are working so far.

Any ideas?

Thank you in advance for your help!

01.png (39.8 kB)
02.png (70.9 kB)
03.png (48.6 kB)
04.png (41.3 kB)
05.png (18.5 kB)
06.png (20.9 kB)
07.png (21.4 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

6 Answers

  • Best Answer
    Posted on May 07, 2015 at 02:06 AM

    Well, this IB52 solution is no longer working. We went to SP13 last week and the determination no longer works. Good new is that BRFplus worked! Since we only have one Sold To Party setup, I defined the decision table to check for ZMCR. I'll try to write a post about it soon.

    Add a comment
    10|10000 characters needed characters exceeded

    • Thanks for the update Robyn. I was also not able to get IB52 to populate the Sold-To in ZMCR. I'm on SP12. I have an incident open with SAP open for 2 weeks + now.

      I also think that BRF+ is the way to go too, but didn't have the time to look into it. Will be excited to see your post.


  • Posted on Jan 19, 2015 at 04:37 PM

    Here is more information about this issue. I put a breakpoint in function module COM_PARTNER_DETERM_STEP_ONE_OW. It is not being executed after entering the scope on ZMCR. Since the ibase is auto-populated when entering the scope (based on the project), it should re-execute the partner determination, but it is not.

    Another thought, if you are pre-filling Sold-To Party for ZMCR in 7.1, are you using an action with a rule parameter? If so, what is the rule?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Robyn Osby

      Hi Robyn,

      in your first screenshot you set the Sold-To Party for VB4 client 300.

      Is this your solution manager client?

      A change request gets per default the ibase component of the solution manager system, performed by this action:

      So maybe you assigned your Sold-To Party to the wrong IBase component?

      If not, maybe you have several IBase components for this system?

      Best Regards,


      scn11.png (27.9 kB)
  • author's profile photo Former Member
    Former Member
    Posted on Mar 11, 2015 at 07:52 AM

    Hi Robyn,

    the defaulting of a partner function (your Sold-To-Party) by partner determination works only for the ibase which is assigned to your RfC.

    An RfC always gets the ibase of the solution manager as a default value, as i mentioned in my last post.

    Any entries in the scope are not considered for this functionality, which is right, because you could have several different ibase componentes in your scope.

    The difference to 7.0 is that you had to assign an ibase in the RfC directly. This was changed with 7.1, where the RfC does not need an ibase, since it could be an cross system change. So the ibase gets assigned to the change document on creation based on the scope entires, the RfC itself gets an 'dummy' ibase for technical purposes only.

    Hope this helps,


    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Raufman,

      In 7.1, using the IB52 partner (like I was using) will only default the sold to party to the ibase partners of the SolMan system, not the ibase component selected in the RfC scope. I changed our strategy to go work with that. Since my client doesn't need more than one sold to party, I'm using the IB52 partner to default the value so the sold to party will be the same for all RfCs and I protected it in the UI.

      If you need to have multiple sold to partys and you want to have them defaulted, it may be possible using BRFplus. I'm not sure though. If you try it, please let me know.

  • Posted on Jan 15, 2015 at 03:55 PM

    Hi Robyn,

    Please check this thread:



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 10, 2015 at 06:25 PM

    Thank for the suggestions that were posted. None of the suggestions have worked so far. I did find out more information though about the issue.

    The ibase component that the sold to party determination is looking at is the ibase component assigned to SolMan itself. For example, the component assigned to SolMan that the RfC is created on is 1111 and the component assigned to the managed system in the scope is 2222. The sold to party determination is looking at the partners assigned in IB52 for component 1111. It should look at 2222.

    I'm still looking into the cause. If anyone knows why it is looking at the wrong component, I would love to award points!

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 01, 2019 at 09:35 AM

    Hi Robyn,

    we were you able to achieive this

    Default Sold-To Party on ZMCR using brfplus.

    we are on solman 7.2 sps 6.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.