Pricing Procedure could not be determined

Hi..
basic doubt -- but causing issue.
I have assigned the combination of sales area + Doc. Pric Proc + Cust Pric -- > Pricing Procedure in customizing.
customer pric prc. -> assigned to BP sales area , billing data (Also seen on Prices tab of transaction)
Doc pric proc - > assigned to the transaction used.
Sales area of transaction -- > same as used to assign pric proc
Still error creating transaction - TA standard order, Message no. CRM_PRIDOC_COM401 - Pricing Procedure Could not be determined. Also the error says to assign a pricing procedure to the combination of sales area + doc pric proc + cust Pric proc which I have already done.
But on the prices tab of transaction I cant see the "Pricing Procedure" and a blank screen on Conditions Tab of transaction.
any clue.. pl help

Hi,
Please check again if your SALES AREA at header level is picked correctly and which matches with the SALES AREA in the PRICNG procedure determination
ALSO if the above is maintained correctly, it might happen that you have created the transaction earlier then you have assigned the sales are to the Customer along with the BILLING tab information.
Run one report
HRBCI_ATTRIBUTES_BUFFER_UPDATE
If you have done the second one then just delete the customer, assign any other customer with which this issue would not appear and the error would go. Now again delete the customer and reassign your previous customer and check.
Regards
Surendra More

Similar Messages

Getting Error "Pricing Procedure could not be determined" in CRM Functional

Hi Experts,
While creating Quotation for Products, am getting error message of " Pricing Procedure could not be determined".
Kindly reply, how 2 resolve this by steps-by-steps.
Thanks..
Edited by: poorav4293 on Aug 6, 2011 12:27 PM

Hi,
Go to SPRO-> IMG-> Basic Functions-> pricing. Here goto second node & select determine pricing procedure.
Here check the combination....
sales org-distribution channel-doc price-cust price-pricing procedure.
Here see the corresponding pricing procedure which should be proper based on the condition types.
Thanks!
Aswith.

Error message: the appropriate pricing procedure could not be determined

Hi SAP friends,
What does this error message means please?
The appropriate pricing procedure could not be determined because no entry with keys 'M100 20 P1' 'A' '1' exists in table 683V.
Tcode: VA01 (sales order).
Regards,
Bahia.

Hi Bahia,
This error means the pricing procedure has not been done.To assign your pricing procedure to sales area go to the transaction "OVKK" and specify sales org/dist channel/div/document pricing procedure/customer pricing procedure and the defualt condition type. This would solve your problem.
Regards
Ram Pedarla

CRM 2007 - Pricing procedure could not be determined

Hi Gurus
We starting an implementation of CRM 2007.
For my Service Ticket transaction we are receiving the message "Pricing procedure could not be determined". We do not need any Pricing as this is purely a service orientated call centre and pricing has no impact on the services we provide.
We're using the dummy service product "INVESTIGATION".
I've tried modifying the customizing to use a Pricing Procedure but this has failed to work.
Is there config which will prevent this error from showing up in the first place.
Maximum points for a speedy response.
Many Thanks
Panduranga

Hi Vishant
I checked the following
1. Assign the sales area of your sold to party a customer pricing procedure.
    In transaction BP for my customer in role "Consumer" data is as follows:
    Sales Org - Defined
    Dist Channel - Defined
    Billing Tab
            Cust Pric Procedure: Standard
2. Assign your transection a document pricing procedure.
     Transaction has Leading Category "Service Process" is not possible to assign a document pricing procedure. Unless you know of another way?
3. for document pricing procedure, customer pricing procedure and sales area data, define the pricing procedure to be used.
    Under SPRO - IMG - Customer Relationship Management -
              Basic Functions - Pricing - Pricing in the Business
              Transaction - Determine Pricing Procedure.
    Sales Org, Dist Channel, Division, Doc Procedure (S - Service Process), Cust Pric Procedure (Standard), Procedure ((0CRMBP) used this as it only has one condition)
4. in product master data, define the values of condition types being used in the pricing procedure (if you dont need the prices, you can just define them as zero).
Added conditions to the Product
Unfortunately I'm still receiving the same error, can you assist further?
Regards,
Panduranga

Partner procedure could not be determined

Hello All,
I have assigned the combination of sales area + Doc. Pric Proc + Cust Pric -- > Pricing Procedure in customizing.
customer pric prc. -> assigned to BP sales area
Doc pric proc - > assigned to the transaction used
Still when I create a service order in SAP CRM (it gives me an error). ' Pricing Procedure Could not be determined.'
Also the error says to assign a pricing procedure to the combination of sales area + doc pric proc + cust Pric proc which I have already done.
Would anyone of you have an idea on what might be missing?
Also I have checked this reference thread, however their resolution does not help me. Thanks.
Reference thread : Pricing Procedure could not be determined
Thanks.
Regards
Priyanka

Hi,
Please check the sales area determined in the service order.
For that sales area please check if the sold to party is extended to it and the billing attributes are maintained.
The system takes the transaction sales area to checks the sales area data of the sold to party.
The distribution channel and division combination should be correct.
Regards,
PP

Pricing Procedure Can't be determined

Hi,
I am working on CRM 5., When i create the sales order i am getting the following error "Pricing Procedure Can't be determined" I have maintained the pricing procedure in CRM.
Is there any link with IPC and How to know whether IPC has been installed or not?
Thanks

Hi Devi,
The error is because your pricing procedure is not being determined by your Customizing settings.
You need to maintain the Pricing Procedure determination setting which can be determined using Sales Organization,Distribution Channel,Division,Customer Pricing Procedure and Document Pricing Procedure.
For this you need to have appropriate Sales Organization,Distribution Channel,Division in your sales order at header level in Organization tab.
Customer Pricing Procedure it is assigned to the business partner. You can find the same under Sales Area data, Billing tab.
Document Pricing Procedure , is maintained in customizing of the transaction type at third level customizing.
To maintain the determination of pricing procedure follow below mentioned IMG path
Customer Relationship Management>Basic Functions>Pricing>Pricing in the Business Transaction>Determine Pricing Procedures
M sure, once these settings are maintained you will surely be able to determine the price.
Best Regards,
Pratik Patel
<b>Reward with Points!</b>

No pricing procedure could be determined

hi iam getting error in VA01 it is
No pricing procedure could be determined
Can u help me?

Hi
Please make a search in the forum.
IN OVKK assign the pricing procedure determination to your sales area+ doc pricing procedurecustomer Pri procedure your Pricing procedure
regards
Prashanth

Batch Job for ME59N getting error SE133 - Net value could not be determined

HI,
We can convert the PO automatically when run manually tcode ME59N successfully.
But when We schedule a batch job to run ME59N (RM06BB30) to create AUTO Purchase order for services item Purchase requistion.
Getting error message SE133 "Net value could not be determined". PO canot be converted automatically.

Hi,
Price/ Net value not picking!
Check info record based on Material Group for your service PR which need to be converted to PO.
Also check activation of Automatic Purchase order creation for Service requisitions in t.code: ML91.
Check vendor master , schema group of vendor and check MM pricing procedure, the availability of condition type for service master for service PO.
For more please read note 635511
Regards,
Biju K

Getting an error "Customer could not be determined" for IDOCs in SCM 7.0

Hi Friends,
I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
I have noticed that 2 things .
1. E1ADRE1 field is NOT being sent by the ECC system .
2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
Has anybody faced this problem before ?
I look forward to replies.
Detailed error is given below.
Regards,
Ranjini.
Customer could not be determined
Message no. /SAPAPO/EDI010
Diagnosis
The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
The section was not available in the processed IDoc.
System Response
The system cancels processing.
Procedure
Configure the EDI convertor in such a way that the corresponding section has a value.

Hi Ranjini,
Please look into the following
1) Customer master data is fully maintained
2) Customer number ranges are fully defined in customisation
3) Customer address details are maintained
4) Is there any special characters used while defining customer data or customer
number like $, #,[ etc.,?
5) Customer int models are active in SCM side prior to IDOC processing (including
customer, demand, stocks etc)
Please confirm your findings
Regards
R. Senthil Mareeswaran.

Report RSMIPROACT gives Customer could not be determined for IDOCs

Hi Friends,
I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
I have noticed that 2 things .
1. E1ADRE1 field is NOT being sent by the ECC system .
2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
Has anybody faced this problem before ?
I look forward to replies.
Detailed error is given below.
Regards,
Ranjini.
Customer could not be determined
Message no. /SAPAPO/EDI010
Diagnosis
The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
The section was not available in the processed IDoc.
System Response
The system cancels processing.
Procedure
Configure the EDI convertor in such a way that the corresponding section has a value.

Hi,
i'm facing the same problem. Could you solve it?
Regards

Withholding tax -number could not be determined for numbering group ID0017

While positing the FB60 transaction with withholding tax for country Indonesia, the below error is coming:
A number could not be determined for numbering group ID0017
Message no. 7Q630
"The system could not determine a certificate number for the numbering
group.
Withholding tax types exist that are relevant to numbering. The system
cannot determine a certificate number because the Customizing settings
are incomplete.
Sysem Response
Payment cannot be made.
Procedure
Check the number ranges in the numbering group."
Already seen the wothholding tax number range and it is coorec. Please advise how to resolve.

Dear,
Please check whether you have assigned the number range to the number group in the below setting
Spro
Financial Account Global Setting> Withholding Tax> Extended Withholding Tax> Posting> India> Remittance Challan> Assign Number Range to Number Groups

Customer/vendor could not be determined for intermediate document

does any one know how to solve this problem, i got this error for an inbound idoc 820 (remmitance advice).

Hi rob,
Message no. FD017
This is the following message:
Customer/vendor could not be determined for intermediate document 0000000000047039
Message no. FD017
Diagnosis
Several procedures are defined for determining the partner (customer or vendor):
1. The customer/vendor can send his/her account number (the account
   number in our system) in the address segment.
2. The customer/vendor can send his/her account number (our number at
   the customer or vendor) in the address segment.
3. Only the name in the address segment clearly identifies the
   customer/vendor. In this case you can create an allocation within
   intermediate document customizing (IDoc base -> Control -> Forward
   inbound).
4. The customer/vendor is determined using his/her bank details (only
   for the "INVOIC01" intermediate document type).
5. The customer/vendor is taken from the control record of the
   intermediate document.
For 1.-3.: One of the address segments with the partner functions
           "II", "RS", "SU", 'SE' ("INV_ID01"), or "RS" or
           "LF" ("INVOIC01") is used for determining the
           customer/vendor.
Procedure
Create the customer or vendor within Financial Accounting or maintain his/her bank details.
Create customer         - Proceed
Customer bank details   - Proceed
Create vendor           - Proceed
Vendor bank details     - Proceed
If the customer/vendor can only be determined using his/her name, create a record within intermediate document customizing with
logical address = name, application = "FI" or "MM" and physical target in the SAP system = customer number/vendor number.
Proceed

IDoc type could not be determined for the IDoc

I am trying to Post the payment run through the transaction F110.
In the payment run log i get the following message:
"IDoc type could not be determined for the IDoc"
But in fact the IDoc is generated and it is displayed in We05.
I have configured the Message type PAYEXT-PEXR2002 and EUPEXR-IDCREF01 both for the partner.
Has anybody Idea about why this error is coming and how i can resolve this?
This is important because in Payment run log, they need to know the IDoc number generated for that run, else it may become difficult for user to identify which IDoc was created for a particular payment run.
Would appreciate if anyone can please help on the same.
Thanks & Regards,
Narayanan

Hi,
If you are paying the payment through F110, if the payment exceeds the limit what you are spefied in available amounts in FI12 screen. First Please check this screen.
still if you are having any problem
Check in the below path:
IMG- Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Release for Payment - 1. Create Workflow Variant for Release for Payment
2. Assign Release Approval Procedure for Release for Payment
3. Define Users with Authorization to Payment Release
Thanks
Chandra

IDoc type could not be determined for the IDoc in F110

Dear All,
The below mentioned error is encountered by us in F110.We have check all the setiing and not able to find the solution for this error.
Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
The system is not creating the IDOC file.....
IDoc type could not be determined for the IDoc
Message no. B1090
Diagnosis
The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type from field DOCTYP.
Procedure
Possible error sources:
- The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
- The IDoc type is not known in your system and must be maintained.
Kindly do the needful.
Regards

If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

Release of system DSM could not be determined

We have set up charm and created projects, corrections and transports.
all seems fine until we try to pass correction to test.
the transport is shown in the pop up box and we can select it.
but when we hit ok, it seems to hang for several minutes then fails.
the error in the task list shows "Release of system DSM could not be determined"
with DSM being the development system.
The transport routes are fine and the system check is clean.
Has anyone seen this before?
Please help,
Thank you!

Hi,
Please make sure that you have performed all the TMS activities in the DSM system. Also make sure that you are done with the following prerequisites...
>transport routes defined between the systems in the landscape
>extended transport control is activated
>quality assurance approval procedure is deactivated and "single transports" strategy activated.
>TMS Trusted Services are activated in the system where the TDC runs.
>Transport Domain link activated if multiple transport domains are used.
>RFC destinations generated to client 000 of all domain controllers
Further queries in Solution Manager are appreciated.
Thanks and Regards,
Damanaidu J

Pricing Procedure could not be determined

Similar Messages

Maybe you are looking for