Error in BDOC while uploading the pricing condition record to ECC from CRM

Hi all,
I have created a condition record for ECC pricing condition type (I have maintained all settings required for maintaining ECC condition type in CRM 7.0) in CRM 7.0. But theis condition record is not uploaded to ECC. I have checked BDOC, it is showing with error status for BDOC type "CND_M_SUP". The errors are as below.
1. sBDoc CNBCCPSAP005 does not contain structure CDBD_CONDREF
Message no. CND_MAST064
2. sBDoc CNBCCPSAP005 does not contain structure CDBD_CONDREF
Message no. CND_MAST064
3. Service that caused the error: CND_MAST_INT_DEEP_MB_TO_SBDOC
Message no. SMO8047Diagnosis
A service caused/ reported an error.
Can some one help me in fixing this issue please.
Thanks in advance,
JM
Edited by: JM on Sep 7, 2010 4:46 PM

Hi,
sBDOCs are not used in ECC to CRM or CRM to ECC data replication scenario. You can either ignore the error or disable mobile bridge.
Regards
Prasenjit

Similar Messages

Extracting the pricing condition records

Hi,
I would like to extract the pricing condition records of a particular sales organization. I need to upload these records to another system.
Any guidelines?
Thanks a million.

Hi,
For Sales dacuments pricing conditions you can use :
RV_PRICE_PRINT_HEAD --Header pricing conditions
RV_PRICE_PRINT_ITEM -- Item level.
Lanka
Message was edited by: Lanka Murthy

How to Maintain the Pricing Condition Records in CRM

Hi
I am new to the CRM
How to maintain the pricing condition records in crm for the particular condition type?
as we do in SD(VK11)
Thanks

Hi Binu,
First of all, you could maintain pricing conditions in the following places:
1. In General Condition Maintenance (GCM)
2. At the product maintenance level
3. At the 'Price agreement' tab of Contracts
4. As manual conditions during order processing at item level
Now, if you want to maintain conditions using GCM, you first have to maintain a condition maintenance group in the customizing where in you can assign condition table and condition type for different counter values. I am assuming that you have done this activity successfully.
When you run the transaction '/SAPCND/GCM', for application 'CRM', your condition maintenance group name and context 'GCM', you will be initially taken to a screen where in you'll have an item area which would be blank and then condition fields would be displayed in a tree on the left.
Here, select the field 'Condition type' and click on icon 'Select records'. You would get a dialog prompting you to enter condition type. Here you can specifiy the condition type for which you want to maintain/view condition records.
If no condition records are available, item area would be left blank. Here, you can choose a condition type using the standard F4 help. Depending on condition types that are assigned to condition maintenance group, different condition types would be displayed in the F4-help using which you can maintain condition records.
Hope this helps.
Regards,
Pavithra
**PS: Please reward points if this helps.

Changing currency in the Pricing Condition Records after saving

Hello,
I would like to know whether there is any way we can change the currency in VK12 in the pricing conditions records created via VK11. Please let me know.
For example, for PR00 condition type, I am maintaining condition records in VK11. I enter an amount and currency as USD and I save it. Now, in VK12, I would like to change the currency to EUR. Is this possible? Please share your ideas.
Regards,
Venkata Phani Prasad K

Closing this thread.

Downloading Pricing condition records for products from ECC to CRM

Hi All,
I have a requirement where i need to download condition records for products from ECC to CRM. The Inputs available for me are Product Id or the material number and the Sales org data.Kindly let me know the step by step procedure that i should follow to download the condition records for the products.
Note: 1. The Products are already in the CRM system.
2. I have downloaded the adapter object "DNL_CUST_CNDALL" already.
Thanks & Regards,
Shwetha.

First of check and ensure that if the records are already downloaded. To do so,
1) Log to ECC system and go to tcode V/06
2) From here select the condition type you are looking at. Dbl click on the condition type and note down the access seq.
3) Go to V/07. seelect the access seq you obtained in previous step and dbl click on "Accesses". Here you will come to know the condition table numbers. Note down the table numbers. (example: 002, 567)
Understand at this juncture that tables from 1-500 are SAP Standard tables and 501 - 999 are customer specific tables.
1) Log to CRM system and go to se16
2) Type CNCCRMPR002 or CNCCRMPR567 and Choose F4 from keyboard.
3) you should find an entry which looks like CNCCRMPRSAP002 or CNCCRMPRCUS567.
4) query the table with input parameters like Product or Sales Org. YOu should find the records.
If you fail in step 3, it means that the table itself has not come to CRM. For this do DNL_CUST_CNDALL with OPEN client (go to SCC4 and there Dbl clik on your client. There "NO CHANGES ALLOWED" should not have been selected. If it is so, consult your basis team and explain that DNL_CUST_CNDALL should be done on open client.(Repeat this even if you have already done that)
If you fail in step4, try downloading DNL_COND_A*** adapter Objects. *** stands for the ECC condition table captured from ECC (step3)
If you still are unable to find the record in the database table level, Check for the log in SLG1 tcode in CRM system. This gives you an idea of what's wrong.
Note: Even if you maintain conditions via Product master, ultimateley it gets stored in A* tables in ECC and CNCCRMPR* tables in CRM. So the above procedure holds good for whatever the case might be.
Hope this helps
Regds,
Raghu

Error while mainitain the pricing ( condition type - j3ap )

Hi,
While i am creating the pricing for an AFS material in T code mek1 ( condition type is j3ap ) i am getting the following error ::
Information 857    Report RV13F002 generated.
Information 711    No Screens are generated.
Information 857    Report RV13F003 generated.
Information 711    No screens are generated
Errors        806     Report RV13F004 has a syntax error
Information 711    No screens are generated.
What is these error?? what setting should i change to correct it ,.
Regards
Rakesh

you can refer to
http://www.triggergroup.org/blog/archives/585

Error while creating a pricing condition record.

Hi
I am trying to use the Material Group 1 (MVGR1) field from the field catalog to create a pricing condition table(9 series). I was able to create the table with MVGR1 as one of the columns but when I try to maintain condition records in the table, System gives me the following error. I have maintained certain values in the config for material group1. there is neither F4 values for the field Material group nor I can type in config values of MVGR1 in that field. I am getting this error. Any help on how to get past this issue will be highly appreciated.
Thanks
Object Material group 1 not provided with characteristic AS. (Note other fields!)
Message no. VK432
Diagnosis
The value entered in a field is not permitted.
System response
The system issues an error message.
Procedure
Check the entry and make the necessary corrections. Note any relationships between the individual fields. Entries in other fields may also be incorrect.
Example: There are two fields for maintaining the country and region. These fields are linked. The country chosen would be permitted if it were by itself. So would the region. But the region may not be in the the country chosen. In this case, an error message is issued. The country should then be corrected, not the region!
Edited by: Suraj Ramakrishnan on Dec 24, 2009 2:45 AM

Message no. VK432
Check note 750841
thanks
G. Lakshmipathi

CATS - error in workflow while releasing the time entry record

Dear Experts,
I have setup the configuration for CATS with approval along with workflow. I have maintained the Entry profile and also the Approval steps.
After entering the time sheet and while releasing the record, system is prompting to enter the user id, I have entered the user id and click OK button, system is producing the following error message:
An error occurred on starting the workflow
Message no. LR365
Diagnosis
For technical reasons, the system cannot start the SAP Business Workflow.
Procedure
Contact your system administrator.
I have activated the work flow customization using Trnx SWU3.
Can some one please help me out in solving this problem.
Thanks in advance,
Regards,
Praveen

I got the solution, we have to maintain the task TS31000004 as general task in the transaction PFTC - 31000004 -> Additional Data -> Agent Assignment -> Maintain, in the next screen GOTO -> Attributes (F8), then Change the task type to General task.
Also we have to create variant by name WORKFLOW for the program RCATSB01.
The above has solved my problem.
Thanks for support.
Praveen

Uploading the pricing master records using bapi

Hi I have to transfer the pricing database from legacy to SAP using bapi but I am not able to find a bapi for that. Pls guide.

Check BAPI: BAPI_PRICES_CONDITIONS. You can also find sample codes in SDN for the BAPI.
Check this link [Example for Price Conditions|Re: Sample code for BAPI_PRICES_CONDITIONS]
Regards
Eswar
Edited by: Eswar Rao Boddeti on Sep 22, 2008 3:52 PM

Bulk Pricing condition record upload

can any body help out for , Is there any transaction code for uploading the pricing condition record in BUlk.
Ex: 1000 condition records upload for condition type PR00..
Ragards

Dear Ramesh,
This you can do by creating an LSMW,one of the mass upload tool.
Regards,
AKD
Edited by: Ashish Dikshit on Sep 19, 2009 9:31 AM

Problem in data upload using pricing conditions with sales deal

hi...
i have to upload following fields -
Condition Type
Condition Table
Valid from
Valid to
Sales deal
Amount/Rate
Currency / %
Pricing Unit
Pricing UoM
Sales organization
Distribution channel
Sold to Party
Material Number
Material Pricing Grp
Batch number
Buying Group of Sold-to
Customer
Customer Group
CustomerHierarchy 01
CustomerHierarchy 02
CustomerHierarchy 03
CustomerHierarchy 04
CustomerHierarchy 05
Division
Sales Order Type
Sales Document Type
End user
Material Group
Tax Classification Material
Payer
Plant
Price Group
Price list type
Pricing reference material
Prod. Hier -1
Prod. Hier -2
Prod. Hier -3
Prod. Hier -4
Prod. Hier -5
Product hierarchy
Region of Dly Plant
Sales district
Sales group
Sales office
Sales unit
Ship-To
Shipping point
Buying Group of end user
Tax classification for customer
Type of Transaction
Scale Basis1
Scale Rate1
Scale Basis2
Scale Rate2
Scale Basis3
Scale Rate3
Scale Basis4
Scale Rate4
using XK15 t-code and SALES DEAL is the major concern.
1) First i used RV14 BTCI , that is a standard report for uploading the pricing conditions. But by using this all fields are updating except SALES DEAL becoz this is not present in the structures (like- BKOND-1, BKOND-2, BKOND-3 etc) that is used in RV14BTCI program. I searched other structures also but SALES DEAL is not present there.
2) Second i tried to find out some Function module that is containg SALES DEAL and i found two FMs - IDOC_INPUT_COND_A and BAPI_PRICES_CONDITIONS.....but
a) the FM - IDOC_INPUT_COND_A is used with ALE and where third party is involved, so we require control data and status data for this I dont have this. so we cant use it.
b) and the FM BAPI_PRICES_CONDITIONS is also not working for SALES DEAL....by using this it is also not uploaded becoz some mandatory information related to sales deal like- sales organisation, distribution channel are not present in this FM.
3) to upload this we can use the BDC recording method.....but the problem is - there are almost 15 condition types and based on these conditions almost 20 - 25 condition tables are there for every condition and based on the every table different screen sequence are there.....so if we go for BDC recording...than we have to make 325 recordings.....also not feasible solution.
so plz give the suggestions for this problem and check my efforts also may be i missed something that can be a solution.
Thanx in advance for all.......plz help.....

Hi Jitendra,
Goto RSA3 trans in the source system. Check if are able to extract the data.
If so then replicate the DS once in BW system. Activate all the DS, transfer rules etc & try to load it again.
Hope this will solve your problem!
Regards,
Pavan

Pricing condition records should not be picked up

Hi,
I have configured a scenario for Supplementary Invoice for which I created a new sales order type. The requirement is such that this order type should not pick the pricing condition records that have been created in VK11. Please suggest how can this be configured.
Do I have to use any Userexits, if so which one?
Regards,
Abhishek

As mentioned by you, you have created a new Sales Order Type, you can create a new document pricing procedure, based on which you can determine a new pricing procedure.
To configure new Document Pricing Procedure:
IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Define Document Pricing Procedure. (Maintain the new Document Pricing Procedure in new Sales Order Type)
Maintain a new Pricing Procedure, maintaining the Condition Types as manual. Maintain the determination of Pricing Procedure appropriately.
Pricing Procedure Determination:
In SD, Pricing Procedure is determined (T.Code: OVKK) based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Pricing Procedure Configuration:
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka

Pricing condition record

Hi All,
There is a problem with the invoice condition records.In our case invoices are actually created via Idocs.
Usually the condition record type is sent in the Idoc and the corresponding condn. type comes in the invoice.But in one case,the Idocs do not have a particular condition record type present in the data segment ,yet the invoice when created has the condition type in it.
Does any one have a idea if the condition type gets picked from any master table or is there any other way it appears in the invoice.
As far as the program that creates the Idocs,It picks the condition records from a Z table and fills in the Idocs.
Thanks for your help!
Regards,
Gowthami SK

Hi Sam,
the preceding document is the sales order.
the scenario is like the sales order gets created through Idocs (msg type:VLCCPO),the pricing condition record is filled in the Idoc ( KSCHL) and it appears in the invoice.
But in a particular case,there is no condition type in the Idoc ,yet the condition type appears in the invoice.
Is it possible that any standard pricing condition has been defined???
Regards,
Gowthami SK.

Duplicate pricing condition records in Billing

Helllo evry one,
I have an issue with an Invoice document, Where the pricing condition records is appearing twice both at the item level and header level.
It is appearing as
Condition Type     Condition base value        Condition value
ZABC                               20.00                                       200.00
ZABC                                20.00                                      200.00
Any clue at what level is might happen and how can we avoid such issues
Regards,
Ganesh
Edited by: Tcode on Dec 15, 2009 5:56 PM

Hi,
Check Whether the CONDITION TYPE is a HEADER CONDITION
Goto V/06 and check the HEADER DISCOUNT filed is activate for the condition type, if yes then it will copy to Item also.
Please check and revert back.
regards,
santosh

Pricing condition records maintanence

Hello All,
We have a requirement to store the pricing condition records in 3 decimal places say 1.733 instead of 1.73 that way standard SAP is doing.
Do we have any solution for this? Can we maintain the pricing condition records in 3 decimal places?
Any suggestions would be appreciated ?
Thanks,
Vinay

chk the following thread:
https://forums.sdn.sap.com/click.jspa?searchID=5045505&messageID=3878405
Regards
AK

Error in BDOC while uploading the pricing condition record to ECC from CRM

Similar Messages

Maybe you are looking for