Skip to Content
author's profile photo Former Member
Former Member

Issue in Field Initialization:Pricing condition type not picked

We are trying to add another key combination in the AccessSequence(ZI02) of a condition type(ZP01) . This key combination Country/dest. Country/Ship-to party/material is created in a condition table ,so that we can maintain the condition records specific to some customers .

After maintaining condition record in ZP01 , while creating a PO , the condition record is accessed , but cannot be picked .

Going through analysis log , it tells that ship-to field couldn't be initialised during PO creation. As we couldn't get KUNWE field anywhere in the PO screen , we made a new condition table with Sold-to(KUNNR) field, which is there in PO shipping tab.And maintained again the whole scenario .Still condition wasn't picked and same issue that KUNNR field couldn't be initialised .

Hope this is clear now. Pls suggest .

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Sep 21, 2011 at 02:04 AM


    Could you please clarify which pricing procedure you are follwing standard pricing procedure or STO pricing procedure? Because shipping information will there in PO for STO process. If you cofigure the pricing procedure from standard PO pricing procedure descripencies may come.Hope it helps you. Thanking you.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member zafar karnalkar

      Thanks for your reply , Zafar .

      But as much as I know , the field 'customer' 'in delivery address tab , that you are refering to , is used for third party processing and will be active to be populated, when some appropriate account assgnment category (e.g.S) is given in the line item .

      Also If I check the technical properties of this tab , this is KUNNR (Sold-to) and not Ship-to (KUNWE) .

      Open for further suggestions .

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.