BUPA_MAIN BDOC Error AM 605 - Assignment of usage & to communication type &

Hi Experts,
In our ISU to CRM replication of the Business partner we are seeing lots of BDOC error AM 605 - Assignment of usage & to communication type & not unique.
I have figured that the error occurs when the CONSNUMBER in the ADR* table reaches 999. Therefore, no more entries can be added for the communication type (ie another phone number) for that particular address number.
But the behaviour in our case is such that CONSNUMBER is reaching 999 by skiping many numbers ( i am not sure if thsi is the standard behavior or something is wrong), so its not the consistent behaviour. In some cases it suddely skips the CONSNUMBER range say which is at 400 for particular address number and goes to 990 range and reaches 999, the BDOC errors out.
We applied note 1070798 - Repair the consnumber in communication tables. The program Z_OSSNOTE_1070798 will be run to reorganize the consnumber, so no entry is at 999. Although this reorganies the number but this only acts as a fix after the error is already encountered.
We still see the AM 605 error , can any one please suggest is there any way to avoid this BDOC Error from occuring. We see these error in case of organisation BPs having many addresses and their phone number in table ADR2 CONSNUMBER reaches 999.
Immediate help is greatly appreciated.
Thanks,
Jessica

Hi Jessica,
Were you able to fix this issue of fill all required entries error?
i have a same error with my project too.
Yes, you know me. We worked in the same project earlier, now i am in this new project, where i get the same old error.
Thanks
Keerthi

Similar Messages

BUPA_MAIN BDOC Error 00 55 - Fill in all required entry fields

Hi All,
We have CRM 5.2 and i am currenlty having issues with BDOC Error 00 55 from CRM to R3.In our system we have custom code for business partner details changing where we have commit which results in creation of the BDOC.
When we end time slice the custom identification details the BDOC that is generated has the central_data section which is empty i.e the following fields are coming as blank.
CENTRAL_DATA->DATA->BP_CONTROL->CATEGORY
CENTRAL_DATA->DATA->BP_CONTROL-> GROUPING
CENTRAL_DATA->DATA->BP_CENTRALDATA->PARTNERLANGUAGE
CENTRAL_DATA->DATA->BP_CENTRALDATA->PARTNERLANGUAGEISO
CENTRAL_DATA->DATA->BP_PERSON->FIRSTNAME
CENTRAL_DATA->DATA->BP_PERSON-> LASTNAME.
The BDOC goes successfully but it deletes the name1 on sd customer. After that if we have any other change to the same bp then that errors out with error message 00 55 i.e. Fill in all required entry fields.
We have observed that in our custom code there are other places where we call the commit which generates the BDOC and those have central_data section populated with the above mentioned fields and it doesnt delete the name1 on sd customer.
It would be great if anyone can suggest if they have experienced a similar problem with business partner replication from CRM to R3 and how they resolved the same.
The thing to note here is that the ISU BP still has the name and is not deleted but name1 deletion only occurs for SD customer.
Any help is greatly appreciated.
Thanks,
Jessica

Hi Jessica,
Were you able to fix this issue of fill all required entries error?
i have a same error with my project too.
Yes, you know me. We worked in the same project earlier, now i am in this new project, where i get the same old error.
Thanks
Keerthi

Processing BDocs Errors in the background

Hi,
I was wondering whether the following is possible.
We currently have BDocs errors in SMW01 on a regular basis. This is because our users are opening the BP record in CRM and R/3. There the BDoc error will have a message saying that the business partner is currently being processed by XXXX. We can reprocess these BDocs and they are processed successfully. What we would like to do is process these BUPA_MAIN BDoc errors in the background so we don't need to go into them manually. I understand the program for transaction SMW01 is RSMW_SHOW_BDOC. Has anyone ever taken a copy of this program and modified it so that it can process the above BDoc errors automatically in the background? We are looking into this as our business process allows the user to launch a record in both CRM and R/3. (Don't ask)
Anyway if anyone has done anything similar - any tips would be much appreciated.
Thanks in advance.
Regards
JoJo

Hi Jojo,
I have not done anything similar but can point you in right direction.
You can refer to class cl_smw_mflow which handles the middleware for messaging bdoc's. You can write a bespoek program from scratch with some selection parameters and process the messaging bdocs by looking at the status of bdoc's. There is a function module 'SMW3_MFLOW_QPROCESSMBDOC' which allows to process the bdoc's by passing the header information.
You can read the status of bdoc's & other header infromation from table SMW3_BDOC.
Hope this helps.
Surendar

BDoc Error : Assignment of usage AD_DEFAULT to communication type TEL not

Hi ,
I got the below BDoc error with BDoc type : VEND_MAIN
Error : Assignment of usage AD_DEFAULT to communication type TEL not unique
Thanks

We had a similiar issue with pushing vendors from R/3 > SNC. I took all the entries out of but020 then used those address numbers to get a list of all the values in ADRCOMC. In ADRCOMC there was a single entry whose HIGH_VALUE was 999 and that was causing the issue. I went into the BP and manually deleted the Telephone & Email address of the BP then saved it. I then went back in and re-created the tele & email address for the BP and that fixed he sequence error.
We have several other BP's that have an usually high consnumber and I'm not sure why. Most of our BP have a connumber of 001, 002, 003,,, etc, howver there are some that have skipped a lot of numbers and gone straight from 12, 13, 991, 992. This last example is what happened with our problem BP record.
After I manually changed the data I was able to process the inbound CIF.
I hope this helps.
Will Foster

Bdoc error : Plant IT01 is not assigned to any location

Hi Experts,
I have downloaded the Plants from r/3 to CRM [7.0] using object DNL_PLANT through /nr3as. I have checked the entries in /nCRM_LOCMAP, all plants are downloaded to CRM except IT01 & MS01.
While downloading MATERIAL from r/3 to CRM, i am getting the following bdoc errors
Plant IT01 is not assigned to any location
Plant MS01 is not assigned to any location
Since these do not exists in /nCRM_LOCMAP, i can see that i am getting this error. I have re downloaded DNL_PLANT & checked the status of completion as green. Still these two particular plants are missing.
Also, when i checked the material [for which i am getting the bdoc error] in r/3, i can see that plants have maintained for that material.
Is there anyway, to fix the issue?
Appreciate if someone can suggest a solution on this.
Thanks & Regards,

Hi Chandrakant,
There are no filters set for this object. Also, i took your suggestion, & created a BP with role plant & maintained the details in /nCRM_LOCMAP. Reprocessed the bdoc's, & i am done, worked finally.
Thanks a lot for your valueable solution. I have another issue in bdoc error which says " Check-digit in GTIN 00001216000000 (unit of measure KG) is invalid"
This is the only one i am getting in /nsmw01 & almost in all the bdocs erros. I did search online, but have not got any suitable solution on this.
Can you help me resolving this issue also?
Thanks & Regards,

BDoc Error-Business partner is not a person

HI
We have a error in the BUPA_MAIN Bdoc for only one customer that "Business partner is not a person". What could be reason for this? How this can be rectified?
Thanks
Prince

Hello Varun,
If you want to have as contact Person for relationship XXXX as well organization , that could be an issue. Because in standard it is only forseen that Persons can be assigned as Contact Persons. There for you have to create a Z-Relationship type.
A Group can have a Contact PERSON, but no Contact ORGANIZATION. As stated in standard it is not possible to have an Organization as Contact Person.
thanks

BDOC errors after changes made in WebIC.

We are receiving BDOC errors (viewable via SMW01) for BDOC type BUPA_MAIN.
The errors reported are against message class COM_BUPA_BSP, errors 10 and 30, being:
Validity start date before issue date
and
Enter a selection date in the past for historical data
I have checked the validity start date for the BP/employee which has a from/to date of 01.01.0001 to 31.12.9999, however, I have not idea where the Issue date can be viewed against the BP/employee.
Table BUT000 reveals both from and to date and also the created date, which is 05.09.2009, but I'm sure this is NOT the Issue date that is referenced in the error message.
Can anyone be of help?
Gary
Edited by: Gary King on Nov 25, 2009 11:21 AM

It turned out that the message was somewhat masked and was pointing us in the wrong direction. We finally discovered that the Employee BP was actually missing some key data that was required by the externinal system. Non-employee BP's had that data which explained why these were being processed okay. We were so convinced that it was some kind of authorisation issue at the destination end that we missed the facts being (sort of) displayed.
Gary King

I need to know that how we should analyse the bdoc error

Hi Experts,
I am monitoring the BODCs in the crm system, through the transaction smw01 ( both in & out).
there are a alots of erros in the queue.most of the erros are related to BUPA_MAIN & the queue are from r/3 (R3AD_CUSTOME)
I need to know that how we should analyse the bdoc error. should i need to reprocess those error.
PLease add experts point on this.
Thanks & Regards
Prajith P
Moderation: Locked. Rule number one: Try to find the answer first. [See rules of engagement.|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
Edited by: Joaquin Fornas on Oct 25, 2011 8:45 AM

Install 7. Don't bother with applying drivers and such, just reboot again from DVD and install again, it will see the existing system and this time activation will be possible.
Vista is mess, takes longer etc. Hope you have SP1 version of 7. And for Vista, only SP2+ are even supported now, by MS.

BUPA BDoc Error "Tax Number Category IN0 Does Not Exist"

Hi,
I have a Bdoc error that I am working on.
The BUPA_MAIN BDoc has a error message "Tax Number Category IN0 Does Not Exist".
What object will be responsible in getting the Tax Number and Tax Type from R/3 to CRM?.
This Tax Type Category No 'IN0', does not exist in R/3 table TFKTAXNUMTYPE, But still it is coming in the Bdoc from R/3. Is there a possibility that this value exists in any other table. It looks like this 'IN0' is standard SAP delivered value.
There is also a note regarding this for you reference, Note no. 407719
Thanks in advance,
Reagrds,
Siva Vutukuri.

Hi Siva,
Go to transaction R3AM1 and check whether you have downloaded the object DNL_CUST_TAX or not.
Also you can maintain the Tax Number Category IN0 in transaction SPRO.
Follow the mentioned link below:-
SPRO->IMG->Cross application components-> SAP BP->BP-> basic settings-> Tax Number Categories->Maintain tax number categories.
Here you can maintain the category IN0.
After that reporcess the BDOCs.
<b>Reward points if it helps!!</b>
Best regards,
Vikash

Bdoc error status E02

Hi Experts,
In transaction BDoc monitor SMW01, the bdoc is showing in error state E02 (Partially send) and showing error "Personnel no. cannot be determined for Business partner xxxxxxxxxx". Please let me know how to resolve this error or tell me the step by step process to rectify this bdoc error.
Thanks,
Varun

Hello Varun,
You are getting this error because the corresponding persons do not exist in CRM with the corresponding personnel numbers
mentioned in the Bdocs errors. These personnel numbers do not correspond to customers from R/3, but to employees which are assigned to R/3 customers via employee specific partner functions.
Now the HR specific employee master data should be synchronized between R/3 and CRM first. In addition the HR integration must be active in your system so data for these employees is not rejected. You have information about it in the customizing documentation:
IMG: Customer Relationship Management > Master Data > Business Partner > Integration Business Partner-Employee >
Set Up Integration With HR.
You have to synchronise the HR and CRM data, this note 550055 contains necessary information.
thanks
Willie

Regd Bdoc Error

Hi All,
I have got some Bdoc errors of type "Industry Q2001 Not Defined for Industry Key System SAPS" .
I know where in they are maintained in ECC, but i'm not finding where we should maintain in CRM.
Could any one help me as where we can maintain or should i need to download any Object for this.
Regards,
Venkat

Hi Venkat, you haven't mentioned the bdoc type whether its for customer master bdocs or something else. If its BUPA_MAIN, then you can check the Industry in CRM under "Maintain Industry Systems and Industries" via IMG/Cross-Application Components/SAP Business Partner/Business Partner/Organizations whether your required entry is maintained with SAPS Industry system. If not, you may try download object "DNL_CUST_TBRC" to get the entry Q2001 into CRM. Then check CRM once again and reprocess the bdoc if the entry is updated in CRM.

Regd Bdoc Errors

Hi All,
I have got some Bdoc Errors of type BUPA_MAIN, and the error is "Number not in interval A - HQ99999999".
could anyone pls suggest me how to solve the issue....
Regards,
Venkat

Hi Rohit,
Thanks for your suggestion...
could you please guide me what is to be checked in the Filters?
Regards,
Venkat

BDOC error while customer activation in MDG

Hi,
We are using CRM integration scenario. MDG customer change request is getting triggered from CRM. During final activation we are getting this BDOC error 'UPD_IN_MI_BACK1 00505630006D1ED3B6E812B2E35D2E29TEL007AD_DEFAULT99 TEL007AD_HOME 9999123123595920140514000000X XXXXXXI'. We have referred the note 1240916 but couldn't point out anything. There is one more correction note 1076996 whose corrections are not in our system. If someone faced the same problem please help.
Thanks in Advance,
Jitendra

I am facing similar problem in the 0FIAP_O03 ODS.
One particular value 'CC ·µÐ¼þ' for field 0REF_DOC_NO gives error in Activation.0REF_DOC_NUM does not have any masterdata but the SID table is exists. We have ALL_CAPITAL in RSKC.
One strage observation was when I tried loading this value[value copied from the error message in a PSA] in Developement Box it was successfull.
I Do not understand if I am missing some setting in Production.
The Errors are
BRAIN 60 Value 'CC ·µÐ¼þ' (hex. '434320B7B5D0ADBCFE') of characteristic 0REF_DOC_NO contains invalid charact
RSDRO 303 Error when assigning SID (details in long text)
The SID did not get created in Prod but was created in Dev. ODS is available for reporting and it has to remain such.
If you have any Insights please help me as well.

Deleting BDOC Errors

Hi experts ,
Please tell me how to delete BDOC error in CRM .
My Error is Technical Error and BDOC type is BUPA_REL.
Please mail me urgent.
Thanks,
Swapna

hi swapna,
ur prob is solved or not? i am having same prob. but for BUPA_MAIN, do u have any idea....

Error while updating assignment of Contingent resource

Hi,
I am getting the below error while updating Assignment of contingent resource using the Standard API.
ORA-20001: HR_7949_ASG_DIF_SYSTEM_TYPE: N, SYSTYPE, ACTIVE_CWKCode for updating the record is -
Declare
Cursor c_emp_mig
Is
Select person_id, supervisor_person_id, code_comb_id, sob, assignment_id, assignment_number From customContingentTable;
x_person_id number;
x_validate BOOLEAN := FALSE;
x_supervisor_id number;
x_default_code_comb_id number;
x_set_of_books_id number;
x_assignment_id number;
x_assignment_number varchar2(20);
x_manager_flag char(1):='N';
x_comment_id number;
x_concatenated_segments varchar2(80);
x_no_managers_warning boolean ;
x_cagr_concatenated_segments VARCHAR2(80);
x_soft_coding_keyflex_id NUMBER; --- IN OUT
x_other_manager_warning boolean;
x_object_version_number NUMBER;
x_cagr_grade_def_id NUMBER;
x_effective_date DATE :='01-OCT-2011'; --cut off date from which the assignment will be effective
x_effective_start_date DATE :='01-OCT-2011';--cut off date from which the assignment will be effective
x_effective_end_date   DATE;
x_hourly_salaried_warning boolean;
x_org_now_no_manager_warning boolean;
x_error_code varchar2(240);
x_error_desc varchar2(2000);
Begin
   Open c_emp_mig;
   Loop
   Fetch c_emp_mig Into x_person_id, x_supervisor_id, x_default_code_comb_id, x_set_of_books_id, x_assignment_id, x_assignment_number;
   Exit when c_emp_mig%NOTFOUND;
    x_object_version_number:=1;
    hr_assignment_api.update_cwk_asg(
     p_validate => x_validate
     ,p_effective_date => x_effective_date
     ,p_datetrack_update_mode => 'UPDATE'
     ,p_assignment_id => x_assignment_id
     ,p_assignment_status_type_id => 1
     ,p_assignment_number =>x_assignment_number
     ,p_object_version_number => x_object_version_number
     ,p_default_code_comb_id => x_default_code_comb_id
     ,p_set_of_books_id => x_set_of_books_id
     ,p_supervisor_id=>x_supervisor_id
     ,p_manager_flag=>x_manager_flag
     ,p_concatenated_segments => x_concatenated_segments
     ,p_soft_coding_keyflex_id => x_soft_coding_keyflex_id
     ,p_comment_id => x_comment_id
     ,p_effective_start_date => x_effective_start_date
     ,p_effective_end_date => x_effective_end_date
     ,p_no_managers_warning => x_no_managers_warning
     ,p_other_manager_warning => x_other_manager_warning
     ,p_hourly_salaried_warning=>x_hourly_salaried_warning
     ,p_org_now_no_manager_warning=>x_org_now_no_manager_warning
      End Loop;
   Exception When Others Then
         x_error_code:=SQLCODE;
         x_error_desc:=SQLERRM;
        insert into emp_mig_error(error_code, error_desc) values(x_error_code, x_error_desc);
     Close c_emp_mig;
End;   Am I missing something here? I searched in metalink, there is no mention of this error. Can anyone help?
Regds,
ARS

The relevant parameter to identify an individual will be p_assignment_id.
You will need a query to obtain the relevant assignment_id from the given CWK number on the person row
Edited to add : whilst you are about it, you'll need to obtain the assignment object_version_number as well - that will be needed for the p_object_version_number parameter
Edited by: clive_t on 05-Apr-2012 16:10

BUPA_MAIN BDOC Error AM 605 - Assignment of usage & to communication type &

Similar Messages

Maybe you are looking for