ISU Contract Parner with no SD Customer in ECC

[Former Member]

Hi All

We have a scenario where ISU Contract Partner was created without a corresponding SD reference customer when the data was migrate from legacy. EMIGALL created entries only in BUT000 table, but none in KNA1 and corresponding SD customer tables.

We are now integrating ISU with CRM. As CRM initial download requires a sold-to-party in ECC, I wanted to know the options we have for creating SD customer for each of the ISU contract partner record.

Can any one please guide me ?

Thanks in advance...

Ram

[former_member229976]

Hi,

the easiest way would be to check if changing a business partner creates the missing SD customer (please check customizing first - was the reference customer set up correctly? --> this might also be the reason why EMIGALL did not create an entry [as it usually does!!]).

IF via FPP2 the missing SD customer is created, you should create a small report which selects ALL business partners and call BAPI BAPI_ISUPARTNER_CHANGE to change something for each business partner e.g. change the name and change it back (or something similiar) and perform a commit (e.g. via BAPI_TRANSACTION_COMMIT) afterwards. The SD customers should be added atfer this. You can put this into a batch run...

KR

Uwe

[Former Member]

Hi Uwe,

Thanks a lot for your response.

I was contemplating to use the EMIGALL object PARTNERCHA as the documentation for this object specifies that, "Generation of SD customers for existing business partners" is possible with this object.

Do you think we can use this object ?

Regards,

Ram

[raja_narayanan2]

Follow this Procedure... it works....

Procedure

1. Review the number ranges that have been created: The number ranges for the business partner in the Best Practices are defined as follows:

IMG u2192 Cross Application Components u2192 SAP Business Partner u2192 Business Partner u2192 Basic Settings u2192 Number Ranges and Groupings u2192 Define Number Ranges

01: The Regular business partner uses this number range: 2100000000 to 2199999999 and 03: 7100000000 to 7199999999 is used in the setting above for the ship-to party. Both are internal number ranges.

XX is the external number assignment used to create the SD reference customer.

2. The account group DEBI must temporarily be assigned to this external number assignment for the creation of this business partner:

IMG u2192 Financial Accounting u2192 Accounts Receivable and Accounts Payable u2192 Customer Accounts u2192 Master Data u2192 Preparations for creation customer master data u2192 Assign Number Ranges to Customer Account Groups:

Set account group: DEBI to external number range XX for the Business Partner creation step.

3. Create an SD customer:

Call transaction XD01: Easy Access u2192 Logistics u2192 Sales and Distribution u2192 Master Data u2192 Business Partner u2192 Customer u2192 Create u2192 Complete

u2022 Select account group: Customer (general)

u2022 Enter the Customer key: MUST_ALL

u2022 Enter company code (1000)

u2022 Enter sales area as follows:

u2022 Sales organization: 1000,

u2022 Distribution channel: 01

u2022 Division: 10.

u2022 Select Continue.

Assign MUST_ALL in Master data>bp>settings for creating standard customers.

[Former Member]

We did use the Partner Change object avbl in EMIGALL. It works fine.

However, we had to apply the note

Note 1029347 - SAP BP:Error R11 665 when AKTYP is 04 (Modify)

before we could use the EMIGALL Object.