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

Users opposing- the Import PO process

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

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 25, 2007 at 09:26 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

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.