Users opposing- the Import PO process

[Former Member]

hi experts,

As we all know in case of import creation of PO, MIGO, and MIRO is a lengthy and tedious process as while creating PO we have to enter all custom duties and against each condition the vendor and if the PO has many items say 50 then it becomes really a tough job.

<u><b>My issue is the import process is facing tough resistance from users.</b></u>

For the import pricing procedure I have maintained the conditions for CVD, Basic duty of customs, edu cess, ADC, etc.

Since these conditions are at item level, the client is finding it very very tedious and difficult to go at each line item and fill in for all line items, if there are more items say 50 items for import.

<b>Can we maintain these conditions-CVD, Basic duty of customs, ADC, etc at header level? Is this the right way? What I see is the problem that if the items are with different custom rate then it will be an issue.</b>

As import PO’s are not with GR-based invoice verification, at the time of MIRO when entering bill of entry from custom office, for say 50 line items it so puzzling and confusing to enter the details in MIRO.

Experts please share with your experience what should be done to make the life of <b>user comfortable</b> at the time of PO and especially MIRO? And what is the right way?

With this type of process users have become against SAP, they feel there current system is better and comfortable then SAP- as making import po, then entering in each condition the vendor details and in MIRO to find against which item what is the duty?

please advice.

thanks and regards

[Former Member · Accepted solution]

Hi Sweta

Except the custom duty, rest all like CVD, Ecess1, Ecess2, ADC, SEcess.. all these are fixed values irrespective of material or vendor.

So for these condition types, maitain a customized access sequence (you condition table may be for plant) and maintain condition records. To avoid edit facility mark the conditions for automatic only in condition entry option, so that these values can not be edited.

By doing this, as soon as you enter the PO item, these conditions will be defauled with appropriate percentages as specified in condition records.

Similarly for custom duty, maintain a different access sequence with material also a key so that you can maintain condition records specific to material (generally custom duty will be specific to import commodity)

This way you can avoid entry of import conditions. I believe this better option then maintianing as header conditions.

warm regards

sairam akundi

[Former Member · Accepted solution]

thank you very much sairam,

before proceeding further I want to clarify some doubts, as access sequence is cross client and i have fear in doing that.

1) as you have mentioned Except the custom duty, rest all like CVD, Ecess1, Ecess2, ADC, SEcess.. all these are fixed values irrespective of material or vendor.

<b>do i have to maintain different access sequence for each condition type?</b> <b>can i leave with one access sequence for all condition types ?</b>

2) <b>when creating the new condition table what fields do i have to select?</b>

can i copy the std 0002 access sequence and insert new condition table in it?

3) Similarly for custom duty, when i maintain a different access sequence with material as a key how can i enter many materials in the field <b>spec.value source</b>

if possible if you can simulate the solution and send me the screen shot in mail i will be greatful to you

swhetasonu@yahoo.com

thanks and regards

[Former Member · Accepted solution]

Hi Swetha,

Yes it is tedious job to enter to avoid that we use below method.

Everybody handles this with access sequence you denfine your access seqence based on plant as one of the critieria & maintain these values in MEK1 via various combined parameters say excise duty is maintained with control code for each control code you define your excise duty once in MEK1 by doing this any number of line items coming with this combination picks up correct value.

NOTE : Access sequence is at client level but when you include field Plant/pur organization it is relevent to your plant only/pur organization only so not to fear.

Regards

Rang

Message was edited by:

Ranganath Mysore

[Former Member · Accepted solution]

Hi Sweta

For all condition types except custom duty, you can manage with one single access sequece. Since these are fixed, even you can maintian at c.code. You can copy the std access seq 0001 (metal prices) as it is containing key c.code only.

For Custom duty, you may use the copy of Market price, create new access sequence and delete the info category from the created one.

Right now i am away from the system and hence i am not in a position to provide you the simulated solution.

warm regards

sairam akundi

[Former Member · Accepted solution]

thanks sai ram,

as proposed by Rang, shall i maintain in MEK1.

i will close it as rewarded once finished with config.

thanks and regards