Showing posts with label ERS. Show all posts
Showing posts with label ERS. Show all posts

Monday, 25 January 2010

ERS Numbering


ERS Numbering sapnote 1146308 ERS Numbering -

ERS Invoice - SAP Note about Number Range

<object id="_ds_23332944" name="_ds_23332944" width="670" height="550" type="application/x-shockwave-flash" data="http://viewer.docstoc.com/"><param name="FlashVars" value="doc_id=23332944&mem_id=&doc_type=pdf&fullscreen=0" /><param name="movie" value="http://viewer.docstoc.com/"/><param name="allowScriptAccess" value="always" /><param name="allowFullScreen" value="true" /></object><br /><font size="1"><a href="http://www.docstoc.com/docs/23332944/ERS Numbering sapnote 1146308 ERS Numbering ">ERS Numbering sapnote 1146308 ERS Numbering </a></font>

#END

 

Best Regards

 

Jay

Sweden : 00 46 70 39 69 274

India      : 00 91 9645 3737 47

 

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

Sunday, 20 December 2009

ERS Settings Required

In the vendor master, make sure the 3 ERS boxes are checked off in the
purchasing data section: GR-based inv verif, AutoEvalGRSetmt Del, &
AutoEvalGRSetmt Ret.

In the PO, make sure the following boxes are checked off: GR, IR,
GR-basedIV, & ERS. GR-basedIV has to be checked off in order for the ERS
program to create the invoice.

In the info record, check off GR-basedIV.

Yes, you need to set up message output but you don't need to print the
output. We set it up for company code and not by vendor and company code.
We set it up with a dispatch time of 3 so it won't print unless we do an
explicit request.

When we have a 102 movement, ERS creates a credit memo when the ERS program
is run.

ERS Invoice Posted 2 times. How to prevent it

Our config is OK, we have "check double invoice on" and zero tolerance. The
root cause of the problem is deeper than that.

Table EKRS stores ERS items which have been goods receipted and are to be
invoiced.

When an ERS is run it reads table EKRS to see what to invoice but does not
lock the items to be processed.

Therefore, if another ERS starts with overlapping selections ( as in my case
)while the first one is still running everything gets posted twice. As the
performance of ERS (or any SAP transaction involving purchasing documents
with history) is so appalling this can easily happen.

OSS note 175827 explains the cause and offers the helpful advice "make sure
you don't run two at once" i.e. make sure your users never make mistakes.
SAP never make mistakes so they have little tolerance for those of us that
do.

Note 216997 gives you a little program to see how many items got posted
twice.

Another note explains that if you try to manually reverse items posted twice
and accidentally put a wrong number in and reverse one only posted once it
has all sorts of dire consequences most notably that EKRS does not get
updated so you can't re-invoice it again.

None of the notes actually offer a solution. In the 564 "program error" OSS
notes relating to ERS I noticed references to user exits. I am going to see
if I can use one of those to lock the relevant EKRS entries for a running
ERS job.

Tuesday, 15 December 2009

How to deactivate ERS output??

 

Please refer to the column Information Text, which is stated that " ...

No message was found for....". Please double click on this for further

information about this and the error message should be M8 446:

 

You can change the attribute of the message thru path in customizing :

Materials Management, Logistic Invoice Verification => Define

attributes of Systems Messages'. Here you can use the pull down menu

and set the message to "switch off message" this can be set up for

individual users or for all users.

 

In this step, you can define the category of message received by

individual users for certain messages in Invoice Verification. This

allows you determine whether a user receives a message as an indication

of:

- Information

- Warning

- Error

- Or whether no message should be issued at all: message switched off