FSCM Collections Management Multiple Scenario - MDS_LOAD_COCKPIT

[Former Member]

Hi

We are implementing FSCM in a two system scenario. With all the A/R data residing in SAP R/3 4.7 system and ECC6.0 having the FSCM module.

We have established the RFC onnection and the necessary ALE settings between the two systems.

Also all the settings for CVI have been made.

We have sent one customer from R3 to ECC6 using BD12 and DEBMAS message type.

However, when we run MDS_LOAD_COCKPIT in ECC6.0 it does not replicate the customer as a business partner.

Please advise

Thanks and regards

Ashish Gupta

[Former Member · Accepted solution]

Hi Allain

Thanks for the reply.

Few quick queries?

In current scenario We have all the customers in R3 4.7. Do these need to be replicated in ECC 6.0 also before running of the cockpit.

If that is the case then will it not result in duplication of customer master data.

Currently we have maintained message types DEBMAS, BUPA_INBOUND_MAIN_SAVE_M and BUPA_INBOUND_REL_SAVE_M in the Distribution Model.

Key questions?

1. Do we need to send all customers from R/3 4.7 to ECC 6 and do these need to be stored in ECC6.0 before running of the cockpit. If yes then what is the tcode for sending these customers.

2. What is the significance of messgeypes INBOUNDMAIN_SAVE_M and BUPA_INBOUND_REL_SAVE_M

Thnaks in advance

Regards

Ashish

[Former Member · Accepted solution]

Hi Gupta,

well for the BUPA and the second point, I'm sorry but I have no clue.

For DEBMAS, I can only say that at the deep end of the inbound processing there will be the Business Transaction event 1321 that will be triggered.

This event is also used to synchronise with business partners.

I've not yet tried such process from ALE but briefly thinking I guess it should work.

As a result, sending customers with DEBMAS could be enough.

The load cockpit run for BP synchronisation might even be avoided.

Best regards

Alain

[Former Member · Accepted solution]

hi

i have a big problem during using mds_load_cockpit

when i click on product category->material group and un select backround proccess and execute the transaction i have terminated in program

Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_X
ABAP Program           SAPLMDS_LOAD_BRIDGES
Application Component  AP-MD-BF-SYN
Date and Time          10.06.2014 09:39:47

Short text
     The current application triggered a termination with a short dump.

What happened?
     The current application program detected a situation which really
     should not occur. Therefore, a termination with a short dump was
     triggered on purpose by the key word MESSAGE (type X).

Error analysis
     Short text of error message:

     Long text of error message:

     Technical information about the message:
     Message class....... "MSI_PRODCAT_CUST"
     Number.............. 303
     Variable 1.......... 1
     Variable 2.......... 432339
     Variable 3.......... " "
     Variable 4.......... " "

[Former Member]

Hello Ashish,

I guess the customizing is not setup properly.

Look in :

/SPRO
 /Cross-Application Components 
  /Master Data Synchronization
   /Customer/Vendor Integration
    /Business Partner Settings 
    /Settings for Customer Integration
     ==>Define BP Role for Direction Customer to BP

There at least the account group customized with a valid BP role.

Maybe you should also start from the customer master data standard maintenance (XD02 or XD01) to check if the standard synchronisation is running properly.

Check for the results and/or errpr codes in transaction MDS_PPO2.

Eventually deactivate PPO in order to stop processing at the first error. This should help you to find the reason of the trouble.

/SPRO
 /Cross-Application Components 
  /Master Data Synchronization
   /Synchronization Control
    ==>Activate PPO Requests for Platform Objects in the Dialog
    ==>Activate Synchronization Options

Good luck

Best regards

Alain