cancel
Showing results for 
Search instead for 
Did you mean: 

Error with inbound Orders IDocs (msg V1217 / Taxes have been re-determined)

Former Member
0 Kudos

Hello everybody,

We've got an error about inbound ORDERS IDocs with error msg V1217

(Taxes have been re-determined).

We are running SAP ECC 6.0

Our system is receiving inbound ORDERS IDocs from partner systems via standard ALE inbound function, FM IDOC_INPUT_ORDERS will be triggered to create SO once an inbound ORDERS IDoc is received.

Since we do some local mapping in user exit to change the sold to, ship to etc,

there will be a pop up window to inform you "Taxes have been re-determined" during SO creation,

and it's just an information not an error pop up.

Now the situation is:

The inbound will fail with error "Taxes have been re-determined"

once an inbound IDoc is received from partner R/3. (We porcess the inbound IDoc immediately).

If we use BD87 to process the failed inbound IDoc, the SO will be created successfully.

Weird about this is, that the error seems just to occure for a small range of partner ID's.

And another thing is, that if e.g. 5 minutes later the partner is sending the data again,

in most of the cases the problem won't occur again, so it just seems to be temporarily.

I tried to figure out what is different with these partner-ID's that have this problem

but I could not find anything in particular which is different with these ID's.

As far as I know there has not been any kind of update on the System

and the error first occured about 3 weeks ago.

Thanks for anyone who could give me some ideas about this issue.

Regards,

Marc

Accepted Solutions (0)

Answers (2)

Answers (2)

n_soni
Participant
0 Kudos

Thought of sharing some idea if that helps!

SAP has given two global variables in SAPMV45A program as shown below:

CALL_FUNCTION; CALL_BAPI

Check if setting value to this variable at appropriate user-exit can help to avoid this information message (V1 217) in VA01.

danilo_adam
Explorer
0 Kudos

Hi Marc,

we are faced with the same problem. Do you have an solution for it?

Best Regards,

Danilo

danilo_adam
Explorer
0 Kudos

Hi All,

our reason was an ABAP instruction which caused an commit work within one of our customer exits. After cleaning this, everything worked fine.

Greets,

Danilo

Edited by: Danilo Adam on Jan 5, 2010 3:43 PM