Purchase pricing error in contract type 0002

Hiya
While creating purchasing side contract i am getting following error
No basic purchase price relevant to pricing found with schema RM0000
Message no. WV185
Diagnosis
There is no condition record flagged as relevant to pricing in the master conditions defined for the basic purchase price.
Procedure
Check in Customizing (price determination, Purchasing) whether the condition types that are used as gross price or promotion price (these are PB00, PBXX and PA00 in the standard system) are flagged as relevant to pricing. Set this flag if you wish new condition records to be saved as relevant to pricing in future. If you wish to flag existing condition records as "relevant to pricing" in retrospect, use report RWVKP01U.
Kindly help
Regards
Ranjeet

I did tick it, however the error still persists...
any further suggetions...Also i am getting an error if i save and procees, at the time of releasing a contract to create follow on document...
*Message for follow on document
Item data for document 23 does not exist*
Thanks and regards
Ranjeet

Similar Messages

Urgently need solution for Pricing Error: Mandatory condition type missing

Hello, All
I am working on CRM 5.0 service module and I am facing a problem while creating a service order.
When I enter the product in the service order it gives me an error
"pricing error: mandatory condition type Z### is missing" even though I maintained the customer pricing procedure, the pricing procedure determination, and the condition record. The error shows that the pricing procedure is determined as the error shows the mandatory condition is determined but what I think is that it cant find the condition record.
I already maintained the condition table and the condition record in the product master data but it does not pick the price, kindly help. Deserving points will be rewarded.
Regards
Jacopo François

Hi,
Open u r transaction which u r getting the error, Double click on product u ll get the item level info, Select condition there u click on create icon, there u can define the condition.
OR
While creating a sold to party check whether u r entered a sales area data properly or not.
Hope it helps u
Gentila

Error while creating contract type 0002 [Purchase side]

Hiya
While creating a purchase side contract vide tcode wb21 i am getting following error
No basic purchase price relevant to pricing found with schema RM0000
Message no. WV185
Diagnosis
There is no condition record flagged as relevant to pricing in the master conditions defined for the basic purchase price.
Procedure
Check in Customizing (price determination, Purchasing) whether the condition types that are used as gross price or promotion price (these are PB00, PBXX and PA00 in the standard system) are flagged as relevant to pricing. Set this flag if you wish new condition records to be saved as relevant to pricing in future. If you wish to flag existing condition records as "relevant to pricing" in retrospect, use report RWVKP01U.
Kindly help
Regards
Ranjeet

Closing...

Error while creating contract type 0002

Hiya
While trying to create purchasing side contract, i am getting an error as below
No sales prices possible at plant level for distribution chain S001/01
Message no. WV228
Diagnosis
For distribution chain S001/01, in the distribution chain control parameters in Customizing, the "distribution chain pricing level" indicator does not allow plant level as an allowed pricing level below the distribution chain. Plant level must be allowed as a pricing level before you can calculate plant-specific sales prices in sales price calculations.
System response
Sales prices cannot be calculated for items containing plants belonging to distribution chain S001/01.
Procedure
Make sure you really want to calculate sales prices at plant level. If not, remove the plant(s) concerned.
If you want to calculate plant-specific sales prices for distribution chain S001/01, change the Customizing settings accordingly.
Make any necessary Customizing settings if you have the required authorization.
Contact your system administrator if you cannot make the settingsyourself.
Any help is appriciated
Regards

Hi Vijay
Thanks for the input, the issue got solved, however i got stuck ahead with another error. it is as belo
No basic purchase price relevant to pricing found with schema RM0000
Message no. WV185
Diagnosis
There is no condition record flagged as relevant to pricing in the master conditions defined for the basic purchase price.
Procedure
Check in Customizing (price determination, Purchasing) whether the condition types that are used as gross price or promotion price (these are PB00, PBXX and PA00 in the standard system) are flagged as relevant to pricing. Set this flag if you wish new condition records to be saved as relevant to pricing in future. If you wish to flag existing condition records as "relevant to pricing" in retrospect, use report RWVKP01U.
This seems to be from MM side, however if you have any idea please suggest
Regards
Ranjeet

Pricing error with condition type HI02

Hi Friends,
I have problem in pricing procedure for customer hierarchy condition type HI02. I have created the condition node i.e.6222 and assigned customer 1500 and i also maintained the condition record for the same and also put in the pricing procedure as well. Now while i am creating sales order the condition type HI02 is not coming automatically rather i am able to put the same manually. I want the system should pick the condition type HI02 automatically. Please suggest me IMG setting which i sould maintain for customer hierarchy pricing.
Thanks in advance,
Bharat B

Dear Barath
You are right
HI02 is a item condition type only used for customer hierarchy discounts and the access sequence for the same is HI02 with condition table 065 that is customer hierarchy/material and the same is positioned in V/07 in the access sequence details in seven consecutive steps (the same condition table in all the seven steps) but the field in each table differing
The field in table 065 which is positioned in no 1 is HIENR 01
The field in table 065 which is positioned in no 2 is HIENR 02
The field in table 065 which is positioned in no 3 is HIENR 03
and the most important thing here is exclusive indicator ticked in all the steps exept the seventh step
That means if at hierarchy level 1 system finds a record then it stops searching
I have a feeling that your access sequence alignmemt must be wrong somewhere and check for exclusive indicator marking
HI01 is a item condition type only used for customer hierarchy discounts and the access sequence for the same is HI01 with condition table 064 that is customer hierarchy and the same is positioned in V/07 in the access sequence details in seven consecutive steps (the same condition table in all the seven steps) but the field in each table differing
The field in table 064 which is positioned in no 1 is HIENR 01
The field in table 064 which is positioned in no 2 is HIENR 02
The field in table 064 which is positioned in no 3 is HIENR 03
and the most important thing here is exclusive indicator ticked in all the steps exept the last step
That means if at hierarchy level 1 system finds a record then it stops searching
I have a feeling that your access sequence alignmemt must be wrong somewhere and check for exclusive indicator marking
Moreover importantly if there is condition type in a PP then if a condition record is maintained if the same is not picked up in sales order then analysis has to give some hint and what is the hint you are getting
Regards
raja

GTM Issue whencreating purchase order from trading contract 0002 (purchase)

Hiya
While trying to create a purchase order from trading contract type 0002, i am getting below error message. While doing it for sales order it is working fine. [for contract type 0003]
Message: Item data for document 61 does not exist.
Any help is welcome...
Regards
Ranjeet

Closing

Purchase order creation : internal pricing error

Hi,
While creating a purchase order, i am getting an error 'internal pricing error'. Message type : V1806
This is basically for creating an Invoicing plan !
Let me know in case of any clue.
-Sachin D

Hi
is it this error
Internal pricing error
Message no. V1 806
Diagnosis
The program link between tables KOMT1 and XKOMV using the XKOMV-IX_KOMT1 field no longer works in the pricing program SAPLV61A. This could be because the PRICING_REFRESH function module has been called up from another function module, even though you did not require it.
Procedure
Inform SAP.

Contract Type ZK to PO Type Z006 is not allowed

Hi Seniors,
While trying to create PO with doc type Z006 with ref to contract type ZK, it is showing error like
" Contract Type ZK to PO Type Z006 is not allowed "
If i check in SPRO, PO doc.type has been assigned with PR doc.type only not with contract doc.type and vice versa to contract doc.type to PR doc.type not with PO doc.type. How and where PO doc.type and Contract doc.type will directly link in order to check whether it is maintained or not. kindly advise.
Regards,
JanaMM

>
JanaMM wrote:
> Hi,
>
> Its not STO normal PO only. I am generally asking...if a PO is been created with ref to contract...the doc.type of both PO and contract should have been assigned somewhere i guess. Where that will be ?? kindly clear me plz..
> regards,
> janamm
For checking the document type of contract follow: spro>MM>Purchasing>contract>Define document type, here you will see document types created for contract.
For checking the document type of PO follow: spro>MM>Purchasing>Purchase Order>Define document type, here you will see document types created for PO.
Now to find a link between contract and PO, look up document type of contract LINK PURCHASE REQUISITION option, you will see what PR's can be created relating to a contract. Now look up PO document type with the above procedure, which will tell you which Po document is linked with Contract. SAP Standard Po document type is CONTRACT RELEASE ORDER, but if customized, the name or document type can be different.
Hope I am helpfull.

Tax codition type in purchase pricing procedure

Dear Sir,
My scenario is like that I want to define a tax condition in purchase pricing procedure which is paid to a differnet vendor, other than material vendor , I want the in system , In GR this value does not loaded on inventory value , But during vendor invoice this will appear as separete line item & goes to differnt vendor .
this is possible or not , if yes how what is done so that whenever this condition in Purchase order is there , in doing vendor invoice paid to different vendor
condition will not look like a delivery cost , It is cost paid to differnet vendor that material
thanks & regards
Shailendra

hi
for this u have to create a transaction event type and a new ondition
goto spro>Materials Management>Purchasing>Conditions>Define Price Determination Process>Define Transaction/Event Keys
here create a new key say ABC
now goto M/06 here copy the condition of freiight FRA1 ,say xyz
now goto M/08 here in ur pricing just add this condition and give the acct kay and accrual as ABC
now in OBYC u have to define a separate G/l acct for the key ABC
now when u create PO add condition XYZ now select this condition and click on deatails here u can change the vendor
regards
kunal

Pricing Error- Condition type not found.

Hi Gurus,
I have a issue with pricing.
Scenario :
For a pricing procedure i have 3 condition types ;
For example :
ZXED, ZXE1 & ZXE2.
Of these ZXED is Manual, Mandatory & Statistical in nature.
ZXE1 & ZXE2 are Manual.
When i create a sales order my pricing procedure is getting determined correctly.
The issue comes in when i try to key in the values at the item level condition in the sales order:
If i see the options(F4) available for me to select the condition types i get have see only one condition type i.e ZXE1. but esentially i should get to see all the 3 condition types as an choice of code(condition type).
Can any one help me to find out the possible reason why i get to have only one condition type for selection.
Your suggestion is highly appreciable.
Rgd
VIVEK.

Hi,
1. Understand onething that a particular condition type if maintained "mandatory" in the pricing procedure then you will have to create the condition record for it using transaction code "VK11". If it is manual then you can give the rate directly in the sales order after selecting it. Since you have maintained "manual", "mandatory" & "statistical" for the condition type "ZXED" at the same time that is why the system is giving you the error "Pricing error" Mandatory condition ZXED is missing."
2. Also you want the system to show you all threee condition types "ZXED', "ZXE1", "ZXE2" to choose manually as per your requirement. Do one thing go to transaction code "V/06" - select the required condition type say "ZXED" - double click on it - in the "changes which can be made" section you will see a field for "Manual entries" - in this select "no limitations" and save the condition type. Similarly do it for the other 2 condition types and save it.
I tell you you must have maintained there "D-not possible to process manually". If this is maintained then the system will never show you the condition type to choose from the condition type list in the sales order.
Note: You have maintained for "ZXED" manual/mandatory/statistical. Now as it is mandatory also you have to maintain the condition record for it in "VK11". Now if you change the rate of this condition type in the sales order then when you will create the invoice in "VF01" the system will show that value only which has been maintained using "VK11" because in billing also the system fetches the condition record from VK11 for the mandatory conditions.
Hope this clarifies and solves your doubt.
Reward points if solution helps.
Regards,
Allabaqsh G. Patil

Error message is 'TYPE' is not a component of data object 'PAYLOAD'.

Hello,
I have sceanrio where file->Synchronus bapi ->File.
For this I have defined a bpm.
Text file inut will be read and converted using sender FCC.
Bpm will call a synchronus bapi from r/3 and collect response. I need to create a success or error response file from the status of bapi response. I have used switch step to do that.
But here when I give condtion as this XPath SOResonse./p1:Z_BAPI_SALESORDER_CREATEFROM3.Response/RETURN1/TYPE = S, SXI_CACHE gives status of bpm as 99 and error message is 'TYPE' is not a component of data object 'PAYLOAD'.
At the same time if i just put a condition of simple type container variable (SuccessCounter = 0), it gives status 0 in SXI_CACHE.
Pl can anyone suggest on this as its urgent.
thanks in advance,
Sharada

Thanks for quick response.
Yes BAPI response has TYPE field.
Pl cehck this response xml
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:Z_BAPI_SALESORDER_CREATEFROM3.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <RETURN1>
<TYPE>E</TYPE>
<ID>V4</ID>
<NUMBER>115</NUMBER>
<MESSAGE>Purchase order number in document number: 304928 already exists</MESSAGE>
<LOG_NO />
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1>304928</MESSAGE_V1>
<MESSAGE_V2 />
<MESSAGE_V3 />
<MESSAGE_V4 />
<PARAMETER>SALES_HEADER_IN</PARAMETER>
<ROW>0</ROW>
<FIELD />
<SYSTEM>DEV200</SYSTEM>
</RETURN1>
<SALESDOCUMENT />
- <EXTENSIONIN>
- <item>
<STRUCTURE>BAPE_VBAK</STRUCTURE>
<VALUEPART1>X</VALUEPART1>
<VALUEPART2 />
<VALUEPART3 />
<VALUEPART4 />
</item>
</EXTENSIONIN>
<ORDER_CCARD />
<ORDER_CFGS_BLOB />
<ORDER_CFGS_INST />
<ORDER_CFGS_PART_OF />
<ORDER_CFGS_REF />
<ORDER_CFGS_REFINST />
<ORDER_CFGS_VALUE />
<ORDER_CFGS_VK />
<ORDER_CONDITIONS_IN />
<ORDER_CONDITIONS_INX />
<ORDER_ITEMS_IN />
<ORDER_ITEMS_INX />
- <ORDER_KEYS>
- <item>
<REFOBJTYP />
<REFOBJECT>HEADER</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000000</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000001</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000002</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000003</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000004</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
</ORDER_KEYS>
- <ORDER_PARTNERS>
- <item>
<PARTN_ROLE>RE</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK>0001</ADDR_LINK>
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
- <item>
<PARTN_ROLE>WE</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK>0002</ADDR_LINK>
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
- <item>
<PARTN_ROLE>Z1</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK>0003</ADDR_LINK>
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
- <item>
<PARTN_ROLE>AG</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK />
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
</ORDER_PARTNERS>
<ORDER_SCHEDULES_IN />
<ORDER_SCHEDULES_INX />
- <ORDER_TEXT>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000020</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000030</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000040</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000050</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000020</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000030</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000040</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000050</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
</ORDER_TEXT>
- <PARTNERADDRESSES>
- <item>
<ADDR_NO>0001</ADDR_NO>
<FORMOFADDR />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<C_O_NAME />
<CITY />
<DISTRICT />
<CITY_NO />
<POSTL_COD1 />
<POSTL_COD2 />
<POSTL_COD3 />
<PO_BOX />
<PO_BOX_CIT />
<DELIV_DIS />
<STREET />
<STREET_NO />
<STR_ABBR />
<HOUSE_NO />
<STR_SUPPL1 />
<STR_SUPPL2 />
<LOCATION />
<BUILDING />
<FLOOR />
<ROOM_NO />
<COUNTRY />
<LANGU />
<REGION />
<SORT1 />
<SORT2 />
<TIME_ZONE />
<TAXJURCODE />
<ADR_NOTES />
<COMM_TYPE />
<TEL1_NUMBR />
<TEL1_EXT />
<FAX_NUMBER />
<FAX_EXTENS />
<STREET_LNG />
<DISTRCT_NO />
<CHCKSTATUS />
<PBOXCIT_NO />
<TRANSPZONE />
<HOUSE_NO2 />
<E_MAIL />
<STR_SUPPL3 />
<TITLE />
<COUNTRYISO />
<LANGU_ISO />
<BUILD_LONG />
<REGIOGROUP />
<HOME_CITY />
<HOMECITYNO />
<PCODE1_EXT />
<PCODE2_EXT />
<PCODE3_EXT />
<PO_W_O_NO />
<PO_BOX_REG />
<POBOX_CTRY />
<PO_CTRYISO />
<HOMEPAGE />
<DONT_USE_S />
<DONT_USE_P />
<HOUSE_NO3 />
<LANGU_CR />
<LANGUCRISO />
</item>
- <item>
<ADDR_NO>0002</ADDR_NO>
<FORMOFADDR />
<NAME>SUPERIOR SELECTED STONE</NAME>
<NAME_2 />
<NAME_3>33-53 10TH STREET</NAME_3>
<NAME_4 />
<C_O_NAME />
<CITY />
<DISTRICT />
<CITY_NO />
<POSTL_COD1 />
<POSTL_COD2 />
<POSTL_COD3 />
<PO_BOX />
<PO_BOX_CIT />
<DELIV_DIS />
<STREET />
<STREET_NO />
<STR_ABBR />
<HOUSE_NO />
<STR_SUPPL1 />
<STR_SUPPL2 />
<LOCATION />
<BUILDING />
<FLOOR />
<ROOM_NO />
<COUNTRY />
<LANGU />
<REGION />
<SORT1 />
<SORT2 />
<TIME_ZONE />
<TAXJURCODE />
<ADR_NOTES />
<COMM_TYPE />
<TEL1_NUMBR />
<TEL1_EXT />
<FAX_NUMBER />
<FAX_EXTENS />
<STREET_LNG />
<DISTRCT_NO />
<CHCKSTATUS />
<PBOXCIT_NO />
<TRANSPZONE />
<HOUSE_NO2 />
<E_MAIL />
<STR_SUPPL3 />
<TITLE />
<COUNTRYISO />
<LANGU_ISO />
<BUILD_LONG />
<REGIOGROUP />
<HOME_CITY />
<HOMECITYNO />
<PCODE1_EXT />
<PCODE2_EXT />
<PCODE3_EXT />
<PO_W_O_NO />
<PO_BOX_REG />
<POBOX_CTRY />
<PO_CTRYISO />
<HOMEPAGE />
<DONT_USE_S />
<DONT_USE_P />
<HOUSE_NO3 />
<LANGU_CR />
<LANGUCRISO />
</item>
- <item>
<ADDR_NO>0003</ADDR_NO>
<FORMOFADDR />
<NAME>Langenscheidt Publishers Inc.</NAME>
<NAME_2 />
<NAME_3 />
<NAME_4 />
<C_O_NAME />
<CITY />
<DISTRICT />
<CITY_NO />
<POSTL_COD1 />
<POSTL_COD2 />
<POSTL_COD3 />
<PO_BOX />
<PO_BOX_CIT />
<DELIV_DIS />
<STREET />
<STREET_NO />
<STR_ABBR />
<HOUSE_NO />
<STR_SUPPL1 />
<STR_SUPPL2 />
<LOCATION />
<BUILDING />
<FLOOR />
<ROOM_NO />
<COUNTRY />
<LANGU />
<REGION />
<SORT1 />
<SORT2 />
<TIME_ZONE />
<TAXJURCODE />
<ADR_NOTES />
<COMM_TYPE />
<TEL1_NUMBR />
<TEL1_EXT />
<FAX_NUMBER />
<FAX_EXTENS />
<STREET_LNG />
<DISTRCT_NO />
<CHCKSTATUS />
<PBOXCIT_NO />
<TRANSPZONE />
<HOUSE_NO2 />
<E_MAIL />
<STR_SUPPL3 />
<TITLE />
<COUNTRYISO />
<LANGU_ISO />
<BUILD_LONG />
<REGIOGROUP />
<HOME_CITY />
<HOMECITYNO />
<PCODE1_EXT />
<PCODE2_EXT />
<PCODE3_EXT />
<PO_W_O_NO />
<PO_BOX_REG />
<POBOX_CTRY />
<PO_CTRYISO />
<HOMEPAGE />
<DONT_USE_S />
<DONT_USE_P />
<HOUSE_NO3 />
<LANGU_CR />
<LANGUCRISO />
</item>
</PARTNERADDRESSES>
- <RETURN>
- <item>
<TYPE>E</TYPE>
<ID>V4</ID>
<NUMBER>115</NUMBER>
<MESSAGE>Purchase order number in document number: 304928 already exists</MESSAGE>
<LOG_NO />
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1>304928</MESSAGE_V1>
<MESSAGE_V2 />
<MESSAGE_V3 />
<MESSAGE_V4 />
<PARAMETER>SALES_HEADER_IN</PARAMETER>
<ROW>0</ROW>
<FIELD />
<SYSTEM>DEV200</SYSTEM>
</item>
- <item>
<TYPE>E</TYPE>
<ID>V4</ID>
<NUMBER>219</NUMBER>
<MESSAGE>Sales document was not changed</MESSAGE>
<LOG_NO />
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1 />
<MESSAGE_V2 />
<MESSAGE_V3 />
<MESSAGE_V4 />
<PARAMETER />
<ROW>0</ROW>
<FIELD />
<SYSTEM>DEV200</SYSTEM>
</item>
</RETURN>
</rfc:Z_BAPI_SALESORDER_CREATEFROM3.Response>

Configuration enabling goods receipt of purchasing pricing condition

Hi Gurus,
a) If I check the "Accruals" flag for a pricing condition, then only, that pricing condition will create a delivery costs goods receipt, while we receive the purchase order having that condition type......is it correct?
b) Is any other configuration change critical for a condition type to generate it's goods receipt?
Thanks,
Kumar

Hi Kumar,
Just check your condition type in tcode M/06 whether all the below mentioned parameters are correct..
In control data 1 -
Cond. class - A (Discount or surcharge)
Calculat.type - A (Percentage)
Cond.category - B (Delivery costs)
Plus/minus - A (Positive)
Thanks

Free Goods Pricing Error

Dear SAP Gurus,
I have configurde the Free Goods as Exclusive and accordingly kept the condition records. When I am creating Sales Order, I have given the first line item as 1482 and when I entered
, the second line item automaticaly vame with item category TANN. Everything is fine up to this. I have kept price in VK11 for the material 1482 and 1483 is the free material.
At the time of creating Sales Order, it giving the error as "Pricing error: Mandatory Condition ZPR1 is missing"
I could not find out any solution for this. Please help in finding the solution for this.
Thanks,
Jans

Hi Jans
Your free goods configuration is something like buy 10 pens and get one pencil free
Free goods are picked by R100 condition type with requirement 55 and aternate base value formula 28 in the pricing procedure
Free goods are represented with item category TANN with pricing as B in VOV7 which measns 100 % discount
This means the price of the pencil is to be maintained as condition record in VK11 for the condition type ZPR1 (in your case) which will be picked by the system and nullifies it with 100 % discount
This is missing from your end (this is my guess only)
Without knowing the price of the second material 1483 how the system will give 100 % discount for it
Soln is
Maintain the condition record for the condition type ZPR1 in VK11 for the free material 1483
Hope this may help you
Regards
Raja

FREE OF CHARGE DELIVERY pricing error

Hi SAP SD Gurus
I am krishna new to this forum also new to SAP SD
I have dought about free of charge delivery subsequent process.
Can anybody please explain about the difference between those also what are the item category and scheduling cat for both.
i created free of charge delivery but it is showing pricing error .where I have done mistake please explain?
Regards,
KRISHNA
Edited by: kris_hna on Sep 19, 2010 2:14 PM

Hi Krishna,
When you wantto send some Promotional Materials or Sample materials ( which do not have any commercial value), we use Order Type FD (Free-of charge Delivery) in standard SAP.
Order Type FD does not require any reference document.
But, suppose we had already sent 10 pieces of material to the Customer out of which let say 2 pieces are damaged and customer has returned back it to you.
Now, you have two options, either to issue a credit memo for the 2 pieces or you need to send fresh 2 units to the customer again.
If you want to send fresh 2 units (which we call replacement) instead of giving him a Credit memo then we process with Order Type SDF (Subsequent Free-of-charge Delivery).
Order Type SDF always requires a reference document. It is created with ref to the Return order.
In both the above case (FD & SDF), Pricing is not applicable.
Ensure that Item category is KLN in the Sales order and in the Item category details, "Pricing" check box should be blank.
Regards
Pradyumna

Pricing Error in Sales Order - How to Maintain...

I am newbie in SD and having issue, I have a sales order where I enter material and get "Pricing error: Mandatory condition PB00 is missing". Now I know this condition is set for manual entry if it is not found via procedure. But where do I maintain this manual entry, I have checked everywhere and cannot find where I can manually enter or edit the PB00 condition at the item order level?

GaryGrewal ,
In SD we use PR00 Condition type and not PB00. For PR00 you maintain datas in various combinations. Customer/ Materila or Material or Price list catgeory/ currency/material. This condition can be either kept manual or maintained as manadatory.
Can you explain us why you are using PB00 - Gross- Price Only if you have some special scenario...
You rename PB00 to ZPB0 and include in the pricing procedure.
This codition type does not have access sequence so you enter data manually during sales processing.
Which means moment you create sales order by entering sold to party, po no, material and the qty. Then Double click Item details --> Choose Condition tab. OR Choose the line item and then Click GoTo --> Item --> Conditions
In Condition Type column enter "ZPB0"
In Amount Column enter the value.
That's it check the value. click save
Please visit
[www.sap-img.com ] Choose sales and Distribution and go through the concepts i hope it will help you understand the basic principle and the process
Regards
Sathya
Edited by: Sathya Pavan Yedavalli venkata on May 5, 2009 9:41 AM

Purchase pricing error in contract type 0002

Similar Messages

Maybe you are looking for