Condition types not showing in PO

[Former Member]

Hi all,

I noticed that some condition types don't show on Purshasing order ( CU00, CUFR, CUPZ, CUDL and all Condition types relation to customs).

Even when I maintain these condition types in MEK1, I still can't find them in PO.

What can be the problem? Am I missing something?

P.S: I am using RMIMPO as pricing procedure.

Thank you.

[Prasoon · Accepted solution]

Hi,

   Click on the "Analysis" button in the conditions tab and analyze whether the condition records are fetched  correctly and showing in green. Here system will show the messages on right side.

    If its green, check the following:

• Condition is item condition (M/06)
• Any routine assigned to the condition types in pricing procedure (M/08) - you may remove the routine and test again.
• "Manual" indicator is flagged for the condition type in pricing procedure (M/08) - if so, remove the flag and test again.
• Click on "update" button in conditions tab and carry out new pricing and check.

Regards,

AKPT

[Former Member · Accepted solution]

Hello,

The condition don't show on the condition tab in PO, however they are present when I click on Analysis, and even if I maintained it in MEK1 I get this when I click on the analysis button.

(It is an item condition and the manual flag is not checked)

[Prasoon · Accepted solution]

Hi,

   Your screen shot shows that the fields mentioned in the access is not identified during pricing.

   Go to M/07 and open the access sequence assigned to the condition type. Now, go to "Fields" folder and select the field and click on the field catalog button.

    System will open a new window, where you can select the exact fields from the structure (KOMP if item and KOMK if header field). Select the correct fields for each field from the structure and save. Test the scenario again with a new PO and revert back.

Regards,

AKPT

[Former Member · Accepted solution]

Hello,

I tried what you said, and it still doesn't work. Instead of the sign now I get this:

So it's not working.

and I still don't get why the condition types don't show in the PO, I still need to add them manually and enter their value manually (They re not manual in PO )

[kunal_ingale · Accepted solution]

Hello Sam ,

the issue is with the condition record determination , it seems that the 3 fields are not maintained in the condition record properly.

recheck the condition record you created or check the access sequence field catalog as suggested by Prasoon.

thanks

kUnal

[kunal_ingale · Accepted solution]

can you send the screenshot of access sequence , condition record.      

[Prasoon · Accepted solution]

Hi,

  Please share the screenshot frm Access Sequence - Fields folder.

Regards,

AKPT

[former_member233510 · Accepted solution]

Please check the SAP note  363212 ("Pricing analysis" mode of operation, Question no. 6) and also check the below referred thread for analyzing.

[former_member280154 · Accepted solution]

Hi Sam,

Please make sure that your import code number (HTS code) is properly maintained per country in the config path spro-->sales and distribution --> Foreign trade/customs --> Basic data for foreign trade --> Define commodity codes/import code numbers by country. And make sure that this number is maintained in your materials master Foreign trade export and import tabs

And usually customs related condition records are created in TK11 T.Code and not in MEK1. You can create your condition here .

Please refer to the post   to create import condition types.

Thank you,

Sri

[Former Member · Accepted solution]

Hello,

I didn't create anything, it is the standard condition table and the standard access sequence

[Former Member · Accepted solution]

Hello,

here is the screenshot you asked for,

It became like this after I chose a field  from field catalog and now I can't go back. At the beginning it was like the second line with "HLAND" instead of COIMP.

[Former Member · Accepted solution]

Hello,

here is the screenshot you asked for,

It became like this after I chose a field  from field catalog and now I can't go back. At the beginning it was like the second line with "HLAND" instead of COIMP.

[former_member210560]

Dear Sam A,

The import fields you mentioned KOMP-COADI usually not fill in standard FM.

You can use exit_saplmeko_002 to fill in the komp-coadi structure.

Best Regards,

ian Wong LF

[Former Member]

Hello Mr Ian,

Thank you for you answer.

I will see if we can do that.

[Former Member]

Hi all,

Thank you all for your help.

Condition types still don't show on my pricing procedure in PO.

So, I am using the standard pricing procedure RMIMP0, with the standard condition types and access sequences.

on Vendor master I chose schema group for foreign trade and the pricing procedure does triger in PO.

In analysis I can see all the condition types.

However, it cannot fetch the condition rate I chose in MEK1 for some reason. The following image shows what I am talking about:

I am open to any suggestion as I couldn't find a solution yet.

Thank you all.

Regards.

[BijayKumarBarik]

Hi,

Considering you have done all configuration for picking price with condition types in your Import Pricing procedure RMIMPO.

Also you maintained condition record for condition types but no result in your PO.

Can share screens of following

1. Pricing procedure RMIMPO with condition details- if any routine assigned to condition type(M/08)

2. Condition types details- Check any exclusion indicator set(M/06)

3. Share Condition keys which you have in your condition table.

Regards,

Biju K

[Former Member]

Hi Bijay,

Here are the screenshots you asked for:

1. Pricing procedure RMIMP0

2. There is no exclusion indicator in any of the condition types

3. What do you mean by condition keys?

[BijayKumarBarik]

Hi,

You have not shared all your screens for MM Pricing procedure RMIMPO.

I believe your configuration step start with 10 for pricing procedure RMIMPO for condition types and proceed with 20, 30, 40 and 50------so on.......120-------130-----150------200

Taking consideration of your one condition type CUFR, start with step 40 and referring calculation step 30 (FROM) and step 0 ( TO)

Do you have step 0 in you MM pricing procedure RMIMPO?

Regards,

Biju K

[Former Member]

Hello,

The Pricing procedure starts with step 10

[vamsikrishnag]

Hi Bijay,

When you check the calculation schema in display mode, the empty 'To' column will show as '0'..

I hope that's not a problem..

Regards,

Vamsi Krishna

[JL23]

Your screenshot shows a yellow diamond with an exclamation mark for 3 fields.

This means that you do not have values in those 3 fields, hence the access to the condition could not be carried out. Maintain the data in the import data tab of your PO and refresh your pricing afterwards

[Former Member]

Hello,

Screenshots of the information in my import tabs:

Header leveel:

By post:

( The designation doesnt show here for the antidumping code because I created it just for testing)

And here is a screenshot of what I get in the analysis tab (In order for the Import code no to populate, I had t change the field in the access sequence, they re now different, but it's working)

I changed the COIMP with STAWN in order for the import code number to work. But I couldn't find a solution for the antidumping code.

Please guide me to what to do in order to solve this issue.

Thank you for your time.

[JL23]

I have never worked with anti dumping field, but if it is in the SAP given communication structure then it is supposed to work. I think you have to debug to know the root cause why it does not be taken, and finally you may have to contact SAP Support for a fix.

[Former Member]

Thank you Jurgen for your help

I will keep looking.

[Former Member]

I have not worked on this procedure, Just want to check if there are tax conditions so we need to maintain in FV11.

[BijayKumarBarik]

Hi,

While creating your Import PO with Import PO document type- did import pricing procedure RMIMPO triggers?

If Yes, Then check following:

1. Pricing elements defined for condition type CU00,CUFR,CUPZ and CUDL

2. Access sequence for these condition types

3. Access sequence linked with pricing condition table

4. Find the condition keys associated with condition table of pricing

5. Also check import vendor details (XK03)

Now check - did you maintain  condition record in t.code: MEK1 for condition type with the condition keys considered in table.

Also check why system referring  Import code no. , county origin and country dispatch details.

Regards,

Biju K

[balakonda_chandrasekhar]

This message was moderated.

[vamsikrishnag]

Hi Chandu,

Did you check that Error log.. Try to post screenshot of it..

[balakonda_chandrasekhar]

This message was moderated.

[balakonda_chandrasekhar]

This message was moderated.

[vamsikrishnag]

Hi Sam,

Is the problem solved ?

If not, can you send the screenshots of

--- condition record which you are using for condition when you click the 'Analysis' in PO

--- fields tab of access sequence for your condition

Thanks,

Vamsi

[Former Member]

Hello,

No the problem is not solved yet.

Screenshots you asked for:

1. 

2.

Regards

[vamsikrishnag]

Hi Sam,

With which condition type u r facing issue ? And what is it's access sequence and condition table ?

[Former Member]

Hello,

The problem is with all the condition types related to foreign trade.

For example, Condition type CUDL, Access sequence CUDL, and Condition tables 320 and 321.

[vamsikrishnag]

Hi Sam,

Go to M/07.. Select condition table 320 of access sequence CUDL and go into fields.. Check whether you properly saved fields of the table or not (few times if you don't save properly also error comes).. Then try again PO !!

[Former Member]

Hi Vamsi,

Fields look okay (Screenshot I showed you earlier)

Do you have any other ideas?

Thank you

[former_member233510]

Please check the custom conditions which mentioned by you are maintained in the pricing procedure.

[Former Member]

Hello,

Yes, they are maintained in the pricing procedure.