Issue in changing the subject of PAYMENT ADVICE E-mail

Hi Murthy/Pavan,

 

 

 

Here I have an issue of changing the subject line of an payment advice  that was sent through an email. Can you Guide us. At the same time I want to know the configuration settings that has to be made regarding this email settings.

 

 

Thanks

Venkata Pulagam

SAP FI Consultant

DTT

1 Braxton way, Glen mills, PA, Zip code :19342

Tel/Direct:

vpulagam@deloitte.com | www.deloitte.com

 

 

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, you should delete this message. 

Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]

Message type of error M8 155

Hi Pavan,
You have to change the message type of error M8 155 to an information message or warning with transaction OKZZ. Message M8155 links to message CKPRCH025.

Issue with message M8155

Murthy garu,
In MM02, in costing tab, I want to update the price unit from 183 to 105 for one of my materials. It gives an error saying that Std cost estimates already exists. I open that help on this error, now it says to change the message number M8155. My question is how to change the message number M8155 to wanring

Please suggest

Pavan

SAP Market

Update on the SAP Market


We see or hear about this recession that we're in just about everywhere we turn. I'd like to share some thoughts about what we see in the market about SAP Talent.



Strictly in terms of SAP, we don't see a recession or at least the current indicators are that maybe it hasn't caught up with us yet! Below are some market indicators that we see, and I'm curious to know if any of you are seeing similar indicators or different?

1. All the Fortune 500 clients and SAP Consulting Firms are hiring people at all levels and in all skills sets throughout the United States.

2. The SAP Market seems hot in major markets like: Chicago, Atlanta, Dallas, Houston, St. Louis, Minneapolis, Milwaukee, Florida, NY/NJ, and in California.

3. We see a little bit of a slow down in markets like Detroit, Michigan and Ohio but it isn't dead by any means.

4. The SAP Consulting Market seems to be very strong. Indicators include the fact that 50% or more of the people are in consulting. Bill rates are strong. Great SAP Talent are always on project and can easily get multiple contract offers in a fairly short time.

5. Major companies are committing to NEW SAP implementations and major upgrades creating large-scale hiring projects and opportunities for consulting partnerships

6. Certain industries are really HOT - including Medical Device/Equipment, Pharmaceutical, Banking/Insurance, Aerospace & Defense, Mining (Gold/Copper/Coal), Energy/Utility, Hi-Tech Mfg, and the Public Sector. We see a little slow down with Manufacturing, Food/Beverage, CPG, and Chemical industries.



7. Companies are still seeking SAP Direct-Hire talent and are willing to pay very healthy fees & relocation to get the talent they seek, but many of clients are still very picky and in a very tight candidate-market, it results in open positions for sometimes 3-6 months.

8. Companies & Hiring Authorities that realize we're in a very tight candidate-market are seeing success through a very quick interview-to-offer process.

9. GREAT SAP Talent in today's market, generally speaking, can easily find a very good opportunity to take advantage of their talents. (Especially those in major markets or willing to relocate)

10. The guess is that 40-60% of all companies that run SAP in the U.S. are open to transferring a visa if the person still has 2-3+ years remaining to work on a visa. Even these companies may be picky to hire someone with great soft-skills and very solid SAP technical skills and wait 6 months - 1 year before helping with Green Card Processing.

11. Lastly, certain SAP skills seem to be in HIGH Demand including: Netweaver, XI, Enterprise Portals, BI 7.0, APO, CRM, SCM/SRM, WM, IS-Retail, AFS, HCM, and as always FI/CO!



In summary, the market indicators shows that many of our country's major Fortune 500 companies across industries and across the U.S. are still hiring!



(Thanks to Jeremy Sisemore for his great analysis on SAP market)

Validation and Substitution

Validation(OB28)


A validation rule is basically a check on a certain field's data. When a user is entering a transaction and enters data in that certain field which violates the validation rule, a error message appears for the user and generally will not allow the transaction to continue. The functional analyst designs the validation rule in one of several transactions. You can set them up to be called at the Document Header level, at the Line Item level.
These checks are created in transaction GGB0 and activated for FI in transaction OB28

Substitution(OBBH)

The substitution rule also checks a certain field's data (that you design in configuration). If the field's data matches what has been configured in the substitution rule, the data will be removed. Then specific other data will be substituted into that field. Substitutions can also be set up at the header, line item, or complete document level, and if a certain set of user-defined criteria are met, then a new value is put into a specific field. For instance, if Company = X and Cost Center = Y, then change Profit Center to be Z. It doesn't work on all fields, but can come in handy for Profit Centers or Allocations, and sometimes Texts such as SGTXT.

Substitutions are set up using GGB1 transaction and are activated in FI using transaction OBBH.

Invoice verification

Invoice verification in SAP is a solid and efficient process.


Select Logistics  Materials Management  Logistics Invoice Verification  Document Entry  Enter Invoice.- MIRO



Invoice frication allows you to capture the details of vendor invoices. If the details of an invoice match the expected details that are specified by any related purchase order and goods receipts, the invoice can be automatically made available for payment. Unmatched invoices are excluded from the payment run and need to be investigated and released before payments can be made.

The main aim of any invoice-verifrication process is to ensure that vendors are paid the correct amount at the right time ( not too late but also not too early ). The process should have a high incidence of first-time matching, to ensure that as little time as possible is spent trying to manually match invoices that appear to be incorrect. It is important to include as few steps as possible in the process, considering that the process of handling payments does not in itself add value to the company or to the vendor.

The Main Steps

1. The capture of the vendor’s invoice details (T code: MIRO)

Note: This also includes the automatic release for payment if the match is successful.

- First ensures that the details entered add up mathematically.

- Second checks to see if the invoice should be blocked or made available for payment.

2. Handling of mismatched invoices (T code: MRBR)

The handling of mismatched invoices occurs in transaction MRBR , which also includes the release for payment if the invoice is successfully matched. Mismatched invoices are those where the details on the invoice do not match the details expected according to the purchase order. This transaction lists all of the invoices that have been blocked for payment.

MRBR should be checked regularly, and this transaction should be seen as the sole transaction for managing the release of blocked invoices . You can list blocked invoices by vendor , by date, by purchasing group , or by user, among other criteria. The system will then display the blocked invoices that match the selection options, and you will then be able to release invoices manually.

Using Workflow when Mismatches Occur:

MIRO can trigger a workflow message ( normally an SAP mail or email message that can be formatted to suit your needs ) to an appropriate user whenever a mismatch occurs. This is normally a request to correct a price or complete a goods receipt to make the details match the invoice.

Parking Invoices

Menu option> Edit > Switch to Document Parking

This option is used to address situations where, for whatever reason, the user does not wish to complete the invoice-verification transaction but wishes to keep the data entered so far.

The other option is to start off by using the Invoice Parking function directly, instead of MIRO, using transaction MIR7 . This is used in situations where you know that you will not want to process the invoice at this stage.

Automatic invoice release

There is actually no setting for automatic invoice release for payment as such. If you have an invoice that is blocked because the goods receipt has not yet been posted and then the goods receipt is posted, the invoice will not be automatically released for payment. However you can use transaction MRBR in a scheduled job with the flag release automatically set on, and this will then release all invoices where the blocking reason is no longer relevant. This will then act the same as an automatic release, but will only release when the job has run. Ideally, this should be at least once a day.



3. The release for payment of matched invoices

4. Posting of accounting entries involved

a. During Invoice Verification

G/R I/R Account - Dr

Vendor – Cr

b. during Goods Receipt

Stock Account - Dr

G/R I/R Account – Cr

Invoice verification process in SAP

Hi, I got an interview question that 1.How does an invoice verification process happen in SAP and what are all the steps? 2.What are Valuations and Substitutions and  tell briefly how it works.? If anybody know the answer please help me. Advance thanks, Gopi