2010 Nov 15 4:00 PM
We have to send sales activities from an ECC-system to CRM and tried to do this with message type SFADPSA and Idoc SFADPSA01.
When adding this message type to the distribution model (transaction BD64) we got the SAP-message to use a BAPI instead: IF1037SR with method RECEIVEPARTNERSALESACTIVITY. So we did.
To trigger the Idoc, we customized an output type, with transmission medium ALE, program RSNASTED and processing ALE_PROCESSING.
When processing the output type we get an error B1 129: "No recipient found for message type SFADPSA in the ALE model".
Analysing the error I found out following: during processing (RSNASTED, ALE_PROCESSING) function module MMODEL_INT_VALID_GET is called. This FM only looks into table TBD05, in which no entry for message type SFADPSA is found.
However, also function module BMODEL_INT_VALID_GET exist, searching table TBD06.
This table does contain an entry for the above BAPI and method and would not lead to an error message.
Obviously this last FM should be called, but this never happened...
Has anyone a clue?
Do we use the correct processing code?
Another message type to use could be SFADSACTIVITY, but this message type has no Idoc type assigned.
We have to send sales activities from an ECC-system to CRM and tried to do this with message type SFADPSA and Idoc SFADPSA01.
When adding this message type to the distribution model (transaction BD64) we got the SAP-message to use a BAPI instead: IF1037SR with method RECEIVEPARTNERSALESACTIVITY. So we did.
To trigger the Idoc, we customized an output type, with transmission medium ALE, program RSNASTED and processing ALE_PROCESSING.
When processing the output type we get an error B1 129: "No recipient found for message type SFADPSA in the ALE model".
Analysing the error I found out following: during processing (RSNASTED, ALE_PROCESSING) function module MMODEL_INT_VALID_GET is called. This FM only looks into table TBD05, in which no entry for message type SFADPSA is found.
However, also function module BMODEL_INT_VALID_GET exist, searching table TBD06.
This table does contain an entry for the above BAPI and method and would not lead to an error message.
Obviously this last FM should be called, but this never happened...
Has anyone a clue?
Do we use the correct processing code?
Another message type to use could be SFADSACTIVITY, but this message type has no Idoc type assigned.
2010 Nov 15 4:11 PM
2010 Nov 16 8:06 AM
Hi Praveen,
With WE20 we configured our partner number with partner type LS and message type SFADPSA:
- tab Outbound Options: correct receiver port and basic Idoc type SFADPSA01.
- tab Message Control: application K1, our Z output type and process code ABI_AIDN_OUT.
To my opinion this is correct.
2010 Nov 16 8:36 AM
In BD64 have you distibuted your distribution model
If not select your distribution model goto Edit->Model View->Distribute->Continue
Any errors will be dispayed in the list.
Regards
Praveen
2010 Nov 16 8:47 AM
Hi Praveen,
When distributing the model with BD64 no errors are reported.
Hans
2010 Nov 17 11:20 AM
Did you generate the distribution model using transaction SALE?
2010 Nov 17 11:27 AM
Hello Wolf,
This error message come while determing the distribution channel.
This error come from one of below includes. Can you please put a break point and swich update debugging on and check whether the program is populating reuqired parameters to determine the distribution model. by doing this you can understand what is going wrong....
LBDMOU17
PCHEAF01
PCITEF01
RBDSECOP
RBDSEGLM
if you are not able to check this let us know..
Regards
Naresh
2010 Nov 17 1:28 PM
Naresh,
I did this analysis already.
The error comes from the first hit LBDMOU17, which is Function RECIPIENT_GET_FROM_ALE_MODEL.
This Function calls ALE_MODEL_INFO_GET and this one in turn calls MMODEL_INT_VALID_GET.
Like I said above in my initial posting.
Hans
2010 Nov 17 2:36 PM
Wolf,
I checked the RSNASTED program ans nowhere SAP is calling BAPI methond for message control. you want to triger BAPI method using message control mechanism.. I did some more investigation and found this message type only triggers with methof BUS1037->Replicate and ReplicateChanged menthods..
Please double check whether you going on right direction..
Naresh